For a hardy backport, please follow the instructions for "How to request
new packages" at https://help.ubuntu.com/community/UbuntuBackports
#request-new-packages
** Changed in: maven2 (Ubuntu)
Status: New => Invalid
--
Maven's command line processing broken - fix available in Debian
https
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 packa
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
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
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-
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.
--
Maven's command line processing broken - fix available in Debian
https://bugs.launchpad.net/bugs/224141
You received this bug
