Karl Heinz Marbaise wrote: > Hi, > > On 10/5/15 7:51 PM, Jörg Schaible wrote: >> Hi Michael, >> >> michael.ctr.taru...@faa.gov wrote: >> >>> My apology about part of this reply. I did not understand part of your >>> suggestion. >>> >>> I thought you were saying 3.0.5 is the latest release. >>> >>> That said, I don't see how using the latest release or an older release >>> makes any difference. >>> >>> I have a requirement to use 3.1.1 from a COTS product vendor, so that is >>> probably not an option. And "bogus" is just not a good enough >>> explanation >>> for me. What specifically is wrong with what I am doing that does not >>> work in this release? >> >> I just cite my original mail: >> >>> IIRC you have problems with 3.1.x when using dependencies with import >>> scope, because it ignores then your settings then for transitive >>> deps declaring their own repository in the POM. >> >> AFAICS, you are using dependencyManagement with dependencies declared >> with scope "import"". > > > The given pom does not contain any dependencyManagement...so it does > simply plays not a role here...
If you read the OPs question from last week, you will see that he did not provide his POM there and from that description, I assumed he used an import scope. That was not the case. > Apart from that import scope means only > to use the dependencyManagement part and nothing else as described in > the documentation...so it does not ignore it nor is it wrong... And what does that have to do with the stuff defined in settings.xml? > See the original documentation > https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html. As long as the dependencies are resolved from the repos declared in settings.xml ... https://issues.apache.org/jira/browse/MNG-5781 We were affected by this more than once, but - honestly - I could not reproduce it today (3.3.3, 3.1.1, 3.0.5). > so this is NOT a problem in contrary it is exactly working as it should > be...Apart from using repository definition in a pom is a bad > practice... Definitely. > But this is a different story... Sadly it was not forbidden when it was discussed the last time ... Cheers, Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
