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 compiler source level should be inferred at build time.
Also, not specifying the version needed hides information that may be necessary to have a reproducible build. OTOH, I would be in favor of such a default being inferred by an archetype. At archetype:create time, the compiler source level configuration would be inserted into the created pom.xml. This could work regardless of the maven implementation language by using the first found version of Java found by some search alorithm (i.e., $JAVA_HOME, then $PATH, then /usr/bin, then default to 1.3) -Al On Fri, May 04, 2007 at 08:52:07AM -0700, Dan Tran spake thus: > 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.5. > >Is there a reason that it can't work like that? *snip* -- :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: Alan D. Salewski Software Developer Health Market Science, Inc. :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
