Michael Koch wrote:
If we can't work around this we will need to upload a commons-cli-1.0
package just for maven2. Would not be nice but a workaround.
Hi Michael,
It's good to have that option as a backup.
Currently commons-cli 1.1 silently discards all but the first instance
of any option (it throws an exception internally, which is then caught
but discarded). I can't imagine anything deliberately depending on this
behaviour, so I feel it should be safe to patch it. Once I'm more
certain I'll clone the bug (as I'll have to revert the original Maven2
patch).
It looks as though upstream accept that this behaviour is buggy
(https://issues.apache.org/jira/browse/CLI-137). It's as much a question
of what the code *should* be doing.
Thanks,
Paul
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
