My only concern would be plugins... but since 2.0.9 locked down the plugin versions that should not be as big an issue any more
On Mon, May 5, 2008 at 2:31 AM, Jason van Zyl <[EMAIL PROTECTED]> wrote: > I think the sentiment is fairly clear. I am going to unwind the > retrotranslating I put in place and leave 2.1 requiring Java 1.5. > > > On 4-May-08, at 1:35 PM, Sejal Patel wrote: > > +1 on maven 2.1 >> -1 on maven 2.0.x (please don't mess with the current maintenance >> releases. >> even feature enhancements should be minimal. just fix regressions mostly) >> >> On Sun, May 4, 2008 at 4:14 PM, Arnaud HERITIER <[EMAIL PROTECTED]> >> wrote: >> >> +1 for 2.1 >>> >>> Arnaud >>> >>> On Sun, May 4, 2008 at 12:02 PM, nicolas de loof <[EMAIL PROTECTED]> >>> wrote: >>> >>> 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. >>>> >>>> >>> >> >> >> -- >> Justice is nothing more than that which is in the greatest self-interest >> of >> the largest portion of the population. >> > > Thanks, > > Jason > > ---------------------------------------------------------- > Jason van Zyl > Founder, Apache Maven > jason at sonatype dot com > ---------------------------------------------------------- > > In short, man creates for himself a new religion of a rational > and technical order to justify his work and to be justified in it. > > -- Jacques Ellul, The Technological Society > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
