1.3 has been end-of-lifed. Any reason not to make 1.4 the minimum base version?
James
On 04/05/07, Ian Springer <[EMAIL PROTECTED]> wrote:
Nope, that doesn't sound crazy at all. Both of your points make perfect sense.
I retract my earlier +1 :-)
One minor quip - the docs should be updated to
Nope, that doesn't sound crazy at all. Both of your points make perfect sense.
I retract my earlier +1 :-)
One minor quip - the docs should be updated to state the default is 1.3...
http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#source
http://maven.apache.org/plugins/ma
That makes perfect sense.
On 5/4/07, Wayne Fay <[EMAIL PROTECTED]> wrote:
I believe the reason for this is as follows:
jdk3 is the lowest common denominator
pom.xml is supposedly the "one true source" for all data you need to
know about a project, and builds are supposed to be
repeatable/reprod
I think the fact maven-2.x is written in Java should be treated just as
an implementation detail, not as something to be relied upon.
Hypothetically, someone could re-implement maven in something else, and
no Java version would be available from which to infer the version. So I
don't think the java
BERAICH
www.ilem.ma
- Message d'origine
De : Dan Tran <[EMAIL PROTECTED]>
À : Maven Users List
Envoyé le : Vendredi, 4 Mai 2007, 15h52mn 07s
Objet : Re: Maven 2.0.6 using JDK 1.3
I totally agree with Paul here, any one else?
On 5/4/07, Paul Gier <[EMAIL PROTECTED]> wrote:
&
I believe the reason for this is as follows:
jdk3 is the lowest common denominator
pom.xml is supposedly the "one true source" for all data you need to
know about a project, and builds are supposed to be
repeatable/reproducible using "only" this information
automatically picking up and using the c
+1
Dan Tran wrote:
I totally agree with Paul here, any one else?
On 5/4/07, Paul Gier <[EMAIL PROTECTED]> wrote:
It seems like a better default behavior for the compiler plugin would be
to use the current jvm version.
If I'm running maven with jdk1.5 I would expect the compiler plugin to
defa
I totally agree with Paul here, any one else?
On 5/4/07, Paul Gier <[EMAIL PROTECTED]> wrote:
It seems like a better default behavior for the compiler plugin would be
to use the current jvm version.
If I'm running maven with jdk1.5 I would expect the compiler plugin to
default to source level 1
It seems like a better default behavior for the compiler plugin would be
to use the current jvm version.
If I'm running maven with jdk1.5 I would expect the compiler plugin to
default to source level 1.5.
Is there a reason that it can't work like that?
Wayne Fay wrote:
This is one of the most
This is one of the most common questions on this list...
It has been answered repeatedly -- check the archives at Nabble.
Also it is very well documented on the Maven website -- both in the
FAQ and in the Maven Compiler plugin docs.
Google also has numerous links when you search for "maven gene
Add this to your POM.xml:
org.apache.maven.plugins
maven-compiler-plugin
1.5
1.5
Best regards!
Copernic
On 5/4/07, David Smith <[EMAIL PROTECTED]> wr
I'm having a problem compiling my project with maven 2.0.6. Maven is
using JDK 1.3 to compile the java files that contain generics. The
build fails with an error stating that 1.3 does not support generics.
How do I switch JDKs so that maven will use 1.5 instead of 1.3? My
classpath and path
12 matches
Mail list logo
