I can reproduce this with Maven 3.0.5 on Mac OS 10.8.3 with Apple JDK 1.6.0_43.
/Anders On Wed, Mar 27, 2013 at 9:46 PM, Baptiste MATHUS <[email protected]> wrote: > OK, I think I've got it. > This is related to the assembly plugin. > > This issue is only during the release since it's in the mojo-release > profile. > To reproduce, bump to mojo-parent/31, and then run: > $ mvn [clean] package -Pmojo-release > > I think this is related to a dependency that was forced in the past int > the m-assembly-p configuration: > <dependency><https://fisheye.codehaus.org/browse/mojo/trunk/mojo/mojo-parent/pom.xml?hb=true#to442> > <!-- NOTE: The fix for PLXUTILS-120 is crucial for the new > assembly descriptor > --><https://fisheye.codehaus.org/browse/mojo/trunk/mojo/mojo-parent/pom.xml?hb=true#to442> > > <groupId>org.codehaus.plexus</groupId><https://fisheye.codehaus.org/browse/mojo/trunk/mojo/mojo-parent/pom.xml?hb=true#to442> > > <artifactId>plexus-utils</artifactId><https://fisheye.codehaus.org/browse/mojo/trunk/mojo/mojo-parent/pom.xml?hb=true#to442> > > <version>2.0.1</version><https://fisheye.codehaus.org/browse/mojo/trunk/mojo/mojo-parent/pom.xml?hb=true#to442> > > </dependency><https://fisheye.codehaus.org/browse/mojo/trunk/mojo/mojo-parent/pom.xml?hb=true#to442> > > We were previously using m-a-p 2.2.1. For m-a-p 2.4, plexus-utils is now > 3.0.8. From the major version change, we can imagine there's incompatible > changes. > > Could someone confirm he reproduces the issue locally before I create the > corresponding JIRA? > > I guess we'll have to release a new version of mojo-parent? > > Cheers > > > 2013/3/27 Baptiste MATHUS <[email protected]> > >> Already on 3.x. >> >> $ mvn -version >> Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) >> Maven home: /home/tiste/tools/Mavens/maven >> Java version: 1.5.0_22, vendor: Sun Microsystems Inc. >> Java home: /home/tiste/tools/JDKs/jdk1.5.0_22/jre >> Default locale: fr_FR, platform encoding: UTF-8 >> OS name: "linux", version: "3.5.0-26-generic", arch: "i386", family: >> "unix" >> >> In the meantime, I downgraded to 30 as said. >> release:prepare went fine, release:perform is about to finish. >> >> So it seems there's an issue with mojo-parent-31 and at least the >> build-helper-maven-plugin. >> >> I'm launching the corresponding release vote and will dig on what are >> more precisely the difference between those parent versions. >> From the log I posted, seems like it's m-assembly-p related, so I'll >> start by checking if its version was touched last time. >> >> Cheers >> >> >> >> 2013/3/27 Olivier Lamy <[email protected]> >> >>> Maven version ? >>> Looks to be 2.x ? >>> Can you try with 3.x ? >>> >>> Olivier >>> On Mar 28, 2013 7:08 AM, "Baptiste MATHUS" <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> Trying to release:prepare BHMP, I get the following error [1]. >>>> Does it ring a bell for someone? >>>> >>>> I'm gonna try to downgrade to mojo-parent 30 to see if this could be >>>> related. >>>> >>>> Thanks >>>> [1] http://pastebin.com/2ZYeuhbs >>>> >>>> <http://pastebin.com/2ZYeuhbs>-- >>>> Baptiste >>>> >>> >> >> >> -- >> Baptiste <Batmat> MATHUS - http://batmat.net >> Sauvez un arbre, >> Mangez un castor ! >> > > > > -- > Baptiste <Batmat> MATHUS - http://batmat.net > Sauvez un arbre, > Mangez un castor ! >
