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 MNG-5663 <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 ?
Regards, -- Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
