Paul Cager wrote: > Mike Paul wrote: >> Package: maven2 >> Version: 2.0.8-3 >> Followup-For: Bug #458895 > > [...] > >> It turns out that /usr/share/maven2/lib/commons-cli.jar is >> the one that makes the difference: if I copy that jar into a >> freshly-unpacked copy of Apache's Maven distribution, the problem >> occurs there too. > [...] > It would seem that this behaviour relies on Maven using an old version > of commons-cli. I'll investigate further. > > [...]
I've not had time to fix this problem yet, so I thought I'd just let you know what's happening. The problem happens because of a change introduced in commons-cli 1.1, which is described in http://issues.apache.org/jira/browse/CLI-137 Although the change has destroyed backwards compatibility (and I don't like that), the new behaviour agrees with cli's API specification. So I think we should call this a bug in Maven which just happens to be harmless with cli version 1.0. I'll prepare a new revision of the maven2 Debian package with Maven's calls to commons.cli patched, and send the bug upstream to the Maven developers (although they still use cli version 1.0). It'll probably take a few days as I want to give it a good test. Thanks, Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
