[ https://issues.apache.org/jira/browse/MNG-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17006441#comment-17006441 ]
Sylwester Lachiewicz commented on MNG-6833: ------------------------------------------- Please check recently added functionality in MNG-6065 Create option --fail-on-severity (Maven 3.7.0-SNAPSHOT) > Add an option to fail a build when dependency pom is invalid and transitive > dependencies are not available > ---------------------------------------------------------------------------------------------------------- > > Key: MNG-6833 > URL: https://issues.apache.org/jira/browse/MNG-6833 > Project: Maven > Issue Type: Wish > Components: Command Line > Affects Versions: 3.6.1 > Reporter: Jiahongchao > Priority: Minor > > Once, I build a war file on jenkins, then put it in tomcat. Then I got a > "class not found" exception when I start tomcat, after that I found there are > some jar files missing in the war file. > At last, I checked maven logs on jenkins, found warnings like "The POM for > xxx is invalid, transitive dependencies (if any) will not be available“, so > some transitive dependency jar files are not included, which caused "class > not found" exception. > So I think it is better to have an option to fail a build when dependency pom > is invalid, so I can get the error at the build time. I would rathar see > error in jenkins instead of in tomcat. > E.g. if use "mvn -bar clean compile", maven will exit with error when "The > POM for xxx is invalid" -- This message was sent by Atlassian Jira (v8.3.4#803005)