Paul Cager schrieb:
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.
Thanks, Paul, I think that's the w
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 distributi
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 to
Package: maven2
Version: 2.0.8-3
Followup-For: Bug #458895
Comparing the Java commands run by Debian's /usr/bin/mvn script and the
one in Apache's release, it turns out that the problem occurs if
the -Dmaven.home= option is set to /usr/share/maven2, but not if it
refers to Apache's distribution.
4 matches
Mail list logo
