cstamas commented on PR #13446: URL: https://github.com/apache/maven/pull/13446#issuecomment-6640101519
Failing IT mystery solved: this change https://github.com/apache/maven-resolver/commit/d2dda33407f37b9f8ca8ddac7d8f7486ce52640e And look how IT "redefines" Central, this is the snippet from ITs used `settings.xml`: ```xml <repository> <id>central</id> <name>mng-0479</name> <url>@baseurl@/target/mng-0479</url> <releases> <enabled>false</enabled> <checksumPolicy>ignore</checksumPolicy> <updatePolicy>always</updatePolicy> </releases> <snapshots> <enabled>true</enabled> <checksumPolicy>fail</checksumPolicy> <updatePolicy>never</updatePolicy> </snapshots> </repository> ``` This means, that IT not only _redefines_ the URL of Central, but also makes Central a snapshot only repository. And, rightfully, that commit above, _eliminates_ the repository from consideration, when resolving parent POM, and whole project fails early, as project POM (that indirectly uses this parent POM) cannot have model built. Have to note, that this IT (MavenITmng0479OverrideCentralRepoTest, related to [MNG-479](https://issues.apache.org/jira/browse/MNG-479)) seems "refurbished" by [MNG-4769](https://issues.apache.org/jira/browse/MNG-4769) that on the other hand, _ensures_ this redefinition is possible (the change even added further assertions that this policy change did happen). But, with that commit above, an old bug got fixed, and the IT is not passing anymore. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
