Hi Karl Heinz,
I would expect the problem to be in the maven-aether-provider.
Aether does all the management, but it is this provider which decides what
are dependencies.
And yes, there's a cache:
org.apache.maven.repository.internal.DefaultModelCache
Robert
On Mon, 18 Jul 2016 20:40:26 +
Hi,
no one and idea ?
Kind regards
Karl Heinz
On 7/17/16 11:46 AM, Karl Heinz Marbaise wrote:
Hi,
so after I found the issue related to reactor order (MNG-6057) (Thanks
Robert for the tip which brought me to right direction) now I'm diving
more into the problem related to the resolution of t
Hi,
so after I found the issue related to reactor order (MNG-6057) (Thanks
Robert for the tip which brought me to right direction) now I'm diving
more into the problem related to the resolution of the artifacts which I
have described related to maven-assembly-plugin after more testing I
have
Hi Karl Heinz,
I think you should focus on the org.apache.maven.graph.DefaultGraphBuilder
when you're talking about the reactor order.
Robert
On Fri, 01 Jul 2016 19:55:56 +0200, Karl Heinz Marbaise
wrote:
Hi,
I have described two issues within this issue.
First the changed reactor or
Hi,
I also realized that we currently having failing Maven Core IT[1] which
is related to this subject[2]
Kind regards
Karl Heinz
[1]:
https://builds.apache.org/view/M-R/view/Maven%20Core%20ITs/job/core-integration-testing-maven-3-jdk-1.7/1820/console
[2] https://issues.apache.org/jira/brow
Hi,
I have described two issues within this issue.
First the changed reactor order based on using a property for the
version and second the problem related to the version which is used for
artifacts.
At the moment I'm trying to identify the first issue...but currently I'm
a little bit lost.
