[
https://issues.apache.org/jira/browse/MNG-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiahongchao updated MNG-6833:
-----------------------------
Description:
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"
was:
When I build a war file on jenkins, I got a warning:The POM for xxx is invalid,
transitive dependencies (if any) will not be available
However this war file is build successfully and I didn't notice that warning.
But there are jar files missing in that war file, so I got a "class not found
exception" in tomcat after I put that war file in it.
So I think it is better to have a option to fail a build when dependency pom is
invalid, so I can get the error in jenkins instead of tomcat.
> Add a 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
> Fix For: wontfix-candidate
>
>
> 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)
