jira-importer commented on issue #245: URL: https://github.com/apache/maven-jar-plugin/issues/245#issuecomment-2956686809
**[Chad Lyon](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=clyon)** commented The problem is actually in the resolution of dependencies. I have a multi-module project. The project packages up a test JAR in the first module in the reactor order. This JAR is needed by the tests of the other modules. If my local repository is clean and I try to build while specifying -Dmaven.test.skip=true then two things happen that cause the build to fail: -The building of the test JAR is skipped because tests are skipped. -Skipping of tests does not instruct the dependency resolver for the other modules to NOT download the test JAR of the first module. Thus, I must first get the test-jar packaged up and in my local repo before my build can succeed. I can either run with tests or specify -Dmaven.test.execute=false I think the proper fix for this would be to fix the resolution of dependencies. Basically, if tests are skipped then don't check for deps that are scope=test. This problem seems to be related to MJAR-90. I bet before this fix went in this issue didn't exist. -- 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]
