On 4-May-08, at 10:08 AM, nicolas de loof wrote:
Right about leaving 2.0.10 as is, and use it for maintenance purpose
only.
About 2.1 beeing already java 1.5, I can read this in main POM.xml :
<artifactId>maven-compiler-plugin</artifactId>
<!-- Maybe someday...
<configuration>
<source>1.5</source>
<target>1.5</target>
</configuration>
-->
Did I miss something ?
Yes.
Two dependencies, maven-artifact and XBR, now use Java 1.5. Look in
the POM for maven-artifact and if you run the build for trunk you will
see the retrotranslation artifacts.
I retrotranslated maven-artifact so that users of 1.4 in m2eclipse
would not be inconvenienced. I have not retrotranslated XBR as we
asked users about 1.5 use on the m2eclipse list and the only people
that responded were those who wanted to drop support for 1.4. Users
don't seem to be bothered about dropping 1.4 so at least in trunk I
don't think we're going to harm anyone going to 1.5. I would very much
rather use 1.5, I just don't want to inconvenience or screw users
inadvertently.
We cannot require 1.5 in the lifetime of the 2.0.x series, as we just
don't know what people are using and how.
2008/5/4 Brian E. Fox <[EMAIL PROTECTED]>:
This is already the case for 2.1, and we can't change it in 2.0.10.
Just
because we used to break peoples' builds with regularity doesn't
mean it
is going to continue.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of nicolas de loof
Sent: Sunday, May 04, 2008 6:03 AM
To: Maven Developers List
Subject: [proposal] java5 as minimal runtime for maven 2.1 (and
2.0.10
?)
Hello,
As you can read at http://java.sun.com/j2se/1.4.2/
*" J2SE 1.4.2 is in its Java Technology End of Life (EOL) transition
period*.
The EOL transition period began Dec, 11 2006 and will complete
October
30th,
2008"
I don't think we have plan yet to release maven 2.1, so I think it
would
be
a valid to require java 1.5 as minimal runtime.
Main beneficts (IMHO) :
- annotation can replace javadoc-style IoC an Maven plugin
declarations
(code allready available :
http://docs.codehaus.org/display/MAVEN/Java+5+Annotations+for
+Plugins)
- jsr-250 annotations can replace some plexus interfaces
( LogEnabled ->
@Resource('log') , Initializable --> @PostConstruct ...) and make
component
more "standard" and accessible to developpers without plexus
knowledge.
- generics can make the maven model more comprehensible. The current
"Collection project.getArtifacts()" is not really clear and the fiew
available javadoc don't help a lot.
Other possible improvements :
- plugin test tool could use jUnit 4 runners to create something
comparable
to spring-test-context :
annotate your plugin test class with
@Runwith( "MavenPluginTestRunner" )
@Pom( "myTestPom.xml" )
and the test will prepare the plugin set in the test pom and inject
it
in
the test class.
- benefict from java.util.concurrent to do some tasks in parallel ?
Example
: dependencies downloading
- any other ?
WDYT ?
Nicolas.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
We all have problems. How we deal with them is a measure of our worth.
-- Unknown
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
