About Q1... That WAS a bug and is fixed. Try to update your install
plugin using "mvn -U install"
About Q2... The compiler can be configured to use a certain compiler
version. Please see:
http://maven.apache.org/plugins/maven-compiler-plugin/howto.html
^_^
Romain Rouvoy wrote:
Hi everybody,
Concerning the documentation of maven ... it is sure that the
documentation is not perfect but no one is perfect ... let's try to
improve it :-). Maven plugin for Cargo has a good documentation
describing well how to install/configure/execute the plugin, I think
that it is the basis to build a solid documentation in Maven. By
experience, I know that writing a documentation is not so easy as we
can think when we read this documentation.
Then, it can be interesting to create a Maven2 (or Maven1)
specific mailing list... first to reduce the traffic on this mailing
list and then to avoid the merge of question related to maven2 and
maven1 ... I'm quite new to maven and sometimes I wonder if questions
are related to maven2 (and then interesting for me) or maven1 (and
then less interesting for me) ... so any opinion ? After all there is
a mailing list for eclipse plugin so why not doing so for maven2 ?
end of my 2 cents...
beginning my 2 questions :-)
Finally, I'm currently trying to deploy jars that are not
currently built with Maven2 (but will be in a near future) on the
ObjectWeb repository (http://maven.objectweb.org/). I wonder what is
the best way to do so ? I'm trying to first deploy these jars on my
local repository using install:install-file goal and the
-DgeneratePom=true property but even if the jar is correcttly
installed in my local repository no artefact.pom file is generated
:-( and how can I generate checksum and so on if currently my project
is not a maven project ? :-/
My second question is about java and the version of the compiler
... is there a way of specifying somewhere in the metadata of
artefacts, the version of the compiler used to compile this artefact
? Basically if you compile a class using 1.5 compiler and execute
using a 1.4 jre, you will obtain a class version error :-/ ... How
Maven2 handles this problems ?
end of my 2 questions
Regards,
Romain
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
