[
https://issues.apache.org/jira/browse/MNG-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiahongchao updated MNG-6833:
-----------------------------
Description:
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.
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: core
> Affects Versions: 3.6.1
> Reporter: Jiahongchao
> Priority: Major
> Fix For: wontfix-candidate
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
