On Sun, May 17, 2009 at 10:40 PM, Dave Meikle <[email protected]> wrote: > Hi, > > 2009/5/17 Dave Meikle <[email protected]> > >> 2009/5/17 Robert Burrell Donkin <[email protected]> >> >>> i'd prefer just to maintain a maven 2 if we're looking just to maintain >>> a JDK1.5+ version. >>> >>> jdk1.4 is now EOL'd and i don't have any particular need to support 1.4 >>> but i'm happy to target 1.4 if there's a need. >>> >> >> +1 from me - that is what I had done with my local copy. Although I have >> some Java 1.4 projects, targeting 1.5 sounds good to me as these will be >> moving up the way. >> >> We could do what we do in Tika and run the retrotranslator plugin in the >> Maven build to allow the classes to be used on 1.4. >> > > OK, I have went for the above and removed the Ant builds. Coupled with > Robert's earlier change of removing the Maven 1 build, we are now just using > Maven 2. > > I have set the Target to 1.5 and added in a retrotranslator just now.
I made a couple of changes since some of what was in resources pom was duplicating what we already have in the commons-parent pom. The compiler "properties" you set to 1.5 are used in the parent to configure the compiler plugin. Also we tie the site and assembly plugins to the "package" phase in the parent so you can run "mvn -Prc package" already and it will do the assembly and site stuff. Niall > Cheers, > Dave > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
