unv-unv opened a new issue, #1306: URL: https://github.com/apache/maven-assembly-plugin/issues/1306
### Affected version 3.8.0 ### Bug description When building a multi-module project using maven-assembly-plugin, the build repeatedly prints warnings for dependencies from a repository defined in the parent POM (which contains artifacts not present in the Maven Central). The warning message is: ``` [INFO] Artifact <groupId>:<artifactId>:pom:<version> is present in the local repository, but cached from a remote repository ID that is unavailable in current build context, verifying that is downloadable from [central (https://repo.maven.apache.org/maven2, default, releases)] ``` This occurs even though all artifacts are successfully resolved during the main build phase and are present in the local cache. It appears the plugin ignores the project's repositories configuration. This leads to dozens of warnings, slowing down the build. The root cause seems similar to the previously resolved issue MASSEMBLY-855. The problem is that the plugin's internal DefaultDependencyResolver does not properly inherit the session's repository list when executed from a child module in a reactor build. I attached test multi-module project which represents this issue. [test.zip](https://github.com/user-attachments/files/27264710/test.zip) -- 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]
