bmarwell opened a new issue, #13732: URL: https://github.com/apache/maven/issues/13732
### Affected version 3.10.0 ### Bug description When upgrading to 3.10.0 or 4.0.0-rc-*, resolver 2 changed how dependency resolution works. Without `-Daether.remoteRepositoryFilter.prefixes.resolvePrefixFiles=false`, some plugins, like assembly-plugin, will try to load prefixes from remote repos defined in dependencies. Instead, I expected mirror configuration to be used (or remote repository filtering, as I defined). Code in question: https://github.com/apache/maven/blob/23da179b75ed2b5b625e79eabc36961b24418959/maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/ArtifactDescriptorReaderDelegate.java#L55-L57 Reproducer: https://codeberg.org/bmarwell/mvn-reproducer-3.10.0-assembly-repoconf Artifact in question: ``` package └─ org.liquibase:liquibase-core:4.31.0 └─ javax.xml.bind:jaxb-api:2.3.1 (its parent is jaxb-api-parent:2.3.1) └─ parent: net.java:jvnet-parent:5 ← declares jvnet-nexus-releases ``` Leads to check of `jvnet-nexus-releases`, when it should not: ``` [DEBUG] Adding artifact: org.hibernate.orm:hibernate-core:jar:6.6.5.Final with file: /home/$USER/.m2/repository/org/hibernate/orm/hibernate-core/6.6.5.Final/hibernate-core-6.6.5.Final.jar to assembly location: lib/hibernate-core-6.6.5.Final.jar. [DEBUG] Selecting RepositoryConnector for jvnet-nexus-releases (https://maven.java.net/content/repositories/releases/, default, releases) [DEBUG] Final pipeline: offline( rrf( basic( jvnet-nexus-releases (https://maven.java.net/content/repositories/releases/, default, releases) ) ) ) [WARNING] Could not transfer metadata /.meta/prefixes.txt from/to jvnet-nexus-releases (https://maven.java.net/content/repositories/releases/): (certificate_expired) PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed ``` Positive example when switching back to 3.9.16 or earlier. -- 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]
