Note that the test project fails on Maven 2.0.11 and 2.2.1 with the same issue
(missing zip dependency) so in that regard the 3.1.0 behaviour is consistent
with Maven2.
On 9 Aug 2013, at 15:34, Stanislav Ochotnicky wrote:
> Adding -llr switch makes no difference in this case. To expand a bit on
Adding -llr switch makes no difference in this case. To expand a bit on my
initial explanation the issue is not related just to the assemblies but to any
attached artifacts apparently.
Quoting Baptiste Mathus (2013-08-09 13:34:51)
> Hi,
>
> Just a thought, could you please retry with -llr mvn opt
Hi,
Just a thought, could you please retry with -llr mvn option and see how it
goes?
Thanks
2013/8/9 Stanislav Ochotnicky
> During rebuild of our Java packages for Fedora 20 we have encountered an
> interesting issue with Maven 3.1.0[1]
>
> When pom.xml is referencing assemblies in other modu
During rebuild of our Java packages for Fedora 20 we have encountered an
interesting issue with Maven 3.1.0[1]
When pom.xml is referencing assemblies in other module they are not resolved
unless they are already in local or remote repository (i.e. reactor resolution
of assemblies fails). Maven 3.0
