Maven uses newer maven-assembly-plugin than official Apache release

Bug #551724 reported by Stian Soiland-Reyes on 2010-03-30
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
maven2 (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: maven2

The maven-assembly-plugin don't seem to work when using the bundled maven2 2.2.1-1 from Ubuntu, but does when using 2.2.1 downloaded from http://maven.apache.org/download.html

I get:

stain@ubuntu01:~/94/taverna-workbench-2.1.2-src/products/net.sf.taverna.t2.taverna-workbench/workbench-distro$ MAVEN_OPTS="-Xmx200m -XX:MaxPermSize=140m" /usr/bin/mvn clean install -Prelease
..
[INFO] Copying xom-1.0.jar to /home/stain/94/taverna-workbench-2.1.2-src/products/net.sf.taverna.t2.taverna-workbench/workbench-distro/target/repository/xom/xom/1.0/xom-1.0.jar
[INFO] Copying xom-1.0.pom to /home/stain/94/taverna-workbench-2.1.2-src/products/net.sf.taverna.t2.taverna-workbench/workbench-distro/target/repository/xom/xom/1.0/xom-1.0.pom
[INFO] [assembly:single {execution: default}]
[INFO] Reading assembly descriptor: src/main/assembly/release-assembly.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error reading assemblies: Error reading descriptor at: src/main/assembly/release-assembly.xml: Unrecognised tag: 'finalName' (position: START_TAG seen ...</baseDirectory>\n\t<finalName>... @7:13)

[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------

If I replace /usr/share/maven2/lib/maven-debian-uber.jar with apache-maven-2.2.1/lib/maven-2.2.1-uber.jar from the Apache download everything works.

I'll create and attach to this bug a mini-version of our Java project as the whole build is quite large.

ProblemType: Bug
Architecture: amd64
Date: Tue Mar 30 14:55:57 2010
DistroRelease: Ubuntu 9.10
Package: maven2 2.2.1-1
PackageArchitecture: all
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.53-server
SourcePackage: maven2
Uname: Linux 2.6.31-16-server x86_64

See attached mini-project.

/usr/bin/mvn clean install fails, while ~/apache-maven-2.2.1/bin/mvn clean install works.

It turns out that the 'real' bug in my project is that yes, the tag <finalName> is not allowed according to the XSD - and in fact I get the same error if I use <soup> instead. The question is why is Ubuntu Maven strict on this, while standalone Apache Maven is not? Different XML libraries?

It seems that Ubuntu's Maven prefers:

<artifactId>maven-assembly-plugin</artifactId>
<version>2.2-beta-4</version>

.. while Apache's Maven prefers:

<artifactId>maven-assembly-plugin</artifactId>
<version>2.2-beta-2</version>

(which does not fail on the element)

If I hardcode the version to either of these I get consistent behavior, ie. both work with 2.2-beta-2, or both fail with 2.2-beta-4.

Not sure if this is still a valid bug, it is still interesting that a different (newer) version is preferred by Ubuntu's Maven..

summary: - assembly plugin fails with unrecognized tag finalName
+ Maven uses newer maven-assembly-plugin than official Apache release
Ludovic Claude (ludovicc) wrote :

Maven assembly plugin beta 4 works much better than the previous version, this is why it has been updated in Debian then in Ubuntu.

Changed in maven2 (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers