jira-importer commented on issue #153: URL: https://github.com/apache/maven-install-plugin/issues/153#issuecomment-2771841656
**[Henning Gross](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=gaffa)** commented Someone at some point thought that the build should break on test failure as well. Someone did have a valid use-case and that when the option to not fail the build on test failure was added. Some time later (not long ago) surefire introduced another parameter to not fail if not tests werde found for a specified filter. Just to proof thath making behaviour configurable is not that uncommon. What you say about package seems to be true. I thought so before, then did a test run which succeeded and I did not question why. Maybe I simply forgot to run clean (me idiot). I just set up a test project and it was as expected and stated by you. The maven3-Feature you named does only work with direct dependencies I guess. I added a zip to demonstrate the issue. It will fail when running mvn clean test. Anyway. I was mistaken and you may close this issue. We need to find another way. Either by making sure that there are only direct inner-module-dependencies or by making sure that those libs are built independently. -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
