Am 17.07.2014 12:57, schrieb Arnaud Héritier:
On Thu, Jul 17, 2014 at 12:41 PM, Christian Schulte <[email protected]> wrote:
Am 17.07.2014 11:46, schrieb Arnaud Héritier:
if projectA imports projectB which imports projectC then maven doesn't try
to download projectC pom with 3.2.2
I will report a new issue because I'm not sure that it is related (but
probably) to c <http://jira.codehaus.org/browse/MNG-5663>
I'll try to create an IT to prove it
When creating an IT, maybe pay attention to things like: Do all projects
specify a different parent POM or do they share the same parent ? If
resolution fails, does 'mvn -U' make a difference ? Are profiles involved ?
That is, are there any repositories specified in a profile which isn't
active although it should ?
I don't yet have this level of study but I will try
In my case repositories entries in projects are useless because I'm using a
mirror
In my case they have the same parent (but it doesn't define any dependency
or depMgt) and -U didn't help
FYI: Reverting commit 016932edbc6dfae2d0a8714a186a4e3a44174a78 building
the MNG-5663 POM succeeded here locally.
Regards,
--
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
