> -----Original Message----- > From: sebb [mailto:seb...@gmail.com] > Sent: Thursday, January 20, 2011 15:10 > To: Commons Developers List > Subject: Re: [site][commons-parent] Build with Maven 2 and 3. > > On 20 January 2011 19:49, Gary Gregory <ggreg...@seagullsoftware.com> > wrote: > >> -----Original Message----- > >> From: sebb [mailto:seb...@gmail.com] > >> Sent: Thursday, January 20, 2011 14:33 > >> To: Commons Developers List > >> Subject: Re: [site][commons-parent] Build with Maven 2 and 3. > >> > >> On 20 January 2011 19:20, Gary Gregory <ggreg...@seagullsoftware.com> > >> wrote: > >> >> -----Original Message----- > >> >> From: sebb [mailto:seb...@gmail.com] > >> >> Sent: Thursday, January 20, 2011 14:17 > >> >> To: Commons Developers List > >> >> Subject: Re: [site][commons-parent] Build with Maven 2 and 3. > >> >> > >> >> On 20 January 2011 16:45, Gary Gregory <ggreg...@seagullsoftware.com> > >> >> wrote: > >> >> > Hi All, > >> >> > > >> >> > I recently added a profile to commons-parent that allows a build to > >> use > >> >> the Maven site 2.x plugin on Maven 2.x and Maven site 3.x plugin on > >> Maven > >> >> 3.x. > >> >> > > >> >> > I just got [codec] to build both ways using this profile (in > codec's > >> >> POM.) > >> >> > > >> >> > I had to override a couple of things in codec's pom.xml. I would > like > >> to > >> >> push these changes up to commons-parent: > >> >> > > >> >> > > >> >> > - maven-site-plugin 2.0.1 -> 2.2 > >> >> > > >> >> > - maven-project-info-reports-plugin 2.1.2 -> 2.3.1 > >> >> > > >> >> > Thoughts? > >> >> > >> >> OK by me. > >> >> > >> >> I think we also need to update surefire to 2.7.1. > >> >> There have been some important fixes, and 2.7+ has re-instated the > >> >> ability to run tests against Java 1.3+. > >> > > >> > The Surefire version is currently set to ${commons.surefire.version}, > >> which is set where...? > >> > >> The default is line 741; also set at line 614 (java-1.3 profile). > >> > >> The Java 1.3 profile no longer needs to use surefire 2.2 > > > > Then we no longer need to set the Java 1.3 profile to surefire 2.2, like > this: > > > > Index: pom.xml > > =================================================================== > > --- pom.xml (revision 1061474) > > +++ pom.xml (working copy) > > @@ -645,7 +645,6 @@ > > > <commons.compiler.compilerVersion>1.3</commons.compiler.compilerVersion> > > > <commons.compiler.javac>${JAVA_1_3_HOME}/bin/javac</commons.compiler.javac> > > > <commons.surefire.java>${JAVA_1_3_HOME}/bin/java</commons.surefire.java> > > - <commons.surefire.version>2.2</commons.surefire.version> > > </properties> > > </profile> > > > > @@ -811,7 +810,7 @@ > > <commons.compiler.compilerVersion /> > > <commons.compiler.javac /> > > <commons.surefire.java /> > > - <commons.surefire.version>2.5</commons.surefire.version> > > + <commons.surefire.version>2.7.1</commons.surefire.version> > > > > <!-- Default values for the download-page generation by commons- > build-plugin --> > > <commons.release.name>${project.artifactId}- > ${commons.release.version}</commons.release.name> > > > > This works for me when I install it locally with Maven 2 and 3 for > [codec] trunk. > > > > But, I am not testing the 1.3 profile. > > Works for me just now when I tried testing Exec, having installed > parent 18-SNAPSHOT locally, and updated the exec pom.
Nice. Committed then. Should we call a formal vote to release 18? We could update any other plugins to their current versions in a version 19. Release early, release often... Gary > > > Gary > > > >> > >> > Gary > >> > > >> >> > >> >> > Gary Gregory > >> >> > Senior Software Engineer > >> >> > Rocket Software > >> >> > 3340 Peachtree Road, Suite 820 * Atlanta, GA 30326 * USA > >> >> > Tel: +1.404.760.1560 > >> >> > Email: > >> ggreg...@seagullsoftware.com<mailto:ggreg...@seagullsoftware.com> > >> >> > Web: > >> seagull.rocketsoftware.com<http://www.seagull.rocketsoftware.com/> > >> >> > > >> >> > > >> >> > > >> >> > >> >> --------------------------------------------------------------------- > >> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > >> >> For additional commands, e-mail: dev-h...@commons.apache.org > >> > > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > >> > For additional commands, e-mail: dev-h...@commons.apache.org > >> > > >> > > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > >> For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
