Maven's command line processing broken - fix available in Debian

[Paul Cager]

Binary package hint: maven2

The command line option processing in Maven version 2.0.8-3 (as in hardy) is broken, making the package all but useless - for full details please see Debian's bugs http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466860 and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=458895.

I'm one of the maintainers for Maven in Debian, but I know very little about Ubuntu, I'm afraid. Do you issue fixes for Hardy that could include a synced Maven2 package? Is there any way I can help get the fix in a release?

You might also need to include the updated libcommons-cli-java package.

Thanks

[Manfred Moser (mosabua)]

I am one of the corporate users of Maven and all our developers run Ubuntu with Maven and we currently are using the Debian package since the Ubuntu package is broken.

[Thierry Carrez (ttx)]

Hello Paul, thanks for reporting this bug.

The procedure to get this fixed in hardy would be to have a minimal patch for the affected packages and follow the SRU procedures (https://wiki.ubuntu.com/StableReleaseUpdates) to get the fix in hardy-updates.

Intrepid looks fixed since it ships maven2-2.0.8-5 and libcommons-cli-java-1.1-2.
Hardy ships maven2-2.0.8-3 and libcommons-cli-java-1.0-11. Reading the above-mentioned bugs this combination should work ?
I'll test and see what I can reproduce and what would be the minimal fix.

[Thierry Carrez (ttx)]

On my hardy workstation both these commands seem to work correctly :

mvn -e archetype:create -DgroupId=org.x.y -DartifactId=z -DarchetypeArtifactId=maven-archetype-j2ee-simple
mvn -Dsome.option=0 install

Versions used are the current hardy ones :
maven2-2.0.8-3
libcommons-cli-java-1.0-11

Could you please explain in more detail how I could trigger the bug using the combination of versions present in hardy ?

[wolfger (wolfger)]

5 months with no reply. We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[Manfred Moser (mosabua)]

As far as I can tell the original bug reports in debian bug tracking linked off this report contain all the relevant information. However I think that given that hardy is a LTS and Maven 2.0.8 is severly broken according to the Maven developers themselves I suggest to backport the Maven 2.0.9 package from Intrepid to Hardy. That package works great.

[Thierry Carrez (ttx)]

For a hardy backport, please follow the instructions for "How to request new packages" at https://help.ubuntu.com/community/UbuntuBackports#request-new-packages