[jira] [Commented] (MNGSITE-388) Need to change "property" to "system property" in POM Reference
[ https://issues.apache.org/jira/browse/MNGSITE-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17019181#comment-17019181 ] Jiahongchao commented on MNGSITE-388: - System properties and commandline properties are not the same thing? > Need to change "property" to "system property" in POM Reference > --- > > Key: MNGSITE-388 > URL: https://issues.apache.org/jira/browse/MNGSITE-388 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Jiahongchao >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > In "Profiles" section, it says "The profile will activate if Maven detects a > property". > > I think it's better to change "property" to "system property" since project > property can not activate profile -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MNG-6851) Need to change "property" to "system property" in POM Reference
Jiahongchao created MNG-6851: Summary: Need to change "property" to "system property" in POM Reference Key: MNG-6851 URL: https://issues.apache.org/jira/browse/MNG-6851 Project: Maven Issue Type: Bug Components: Documentation: General Reporter: Jiahongchao In "Profiles" section, it says "The profile will activate if Maven detects a property". I think it's better to change "property" to "system property" since project property can not activate profile -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNG-6833) Add an option to fail a build when dependency pom is invalid and transitive dependencies are not available
[ https://issues.apache.org/jira/browse/MNG-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003441#comment-17003441 ] Jiahongchao commented on MNG-6833: -- I want an option "bar", if use "mvn -bar clean compile", maven will exit with error when "The POM for xxx is invalid" > 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 > 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)
[jira] [Updated] (MNG-6833) Add a option to fail a build when dependency pom is invalid and transitive dependencies are not available
[ 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)
[jira] [Updated] (MNG-6833) Add an option to fail a build when dependency pom is invalid and transitive dependencies are not available
[ https://issues.apache.org/jira/browse/MNG-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiahongchao updated MNG-6833: - Summary: Add an option to fail a build when dependency pom is invalid and transitive dependencies are not available (was: Add a option to fail a build when dependency pom is invalid and transitive dependencies are not available) > 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 > 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)
[jira] [Commented] (MNG-6833) Add a option to fail a build when dependency pom is invalid and transitive dependencies are not available
[ https://issues.apache.org/jira/browse/MNG-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003232#comment-17003232 ] Jiahongchao commented on MNG-6833: -- Never mind. It is a wish, not a bug. > 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 > > > 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)
[jira] [Updated] (MNG-6833) Add a option to fail a build when dependency pom is invalid and transitive dependencies are not available
[ https://issues.apache.org/jira/browse/MNG-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiahongchao updated MNG-6833: - Priority: Minor (was: Major) > 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: Minor > 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)
[jira] [Updated] (MNG-6833) Add a option to fail a build when dependency pom is invalid and transitive dependencies are not available
[ https://issues.apache.org/jira/browse/MNG-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiahongchao updated MNG-6833: - Component/s: (was: core) Command Line > 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 > > > 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)
[jira] [Commented] (MNG-6833) Add a option to fail a build when dependency pom is invalid and transitive dependencies are not available
[ https://issues.apache.org/jira/browse/MNG-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003203#comment-17003203 ] Jiahongchao commented on MNG-6833: -- updated this issue > 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)
[jira] [Comment Edited] (MNG-6833) Add a option to fail a build when dependency pom is invalid and transitive dependencies are not available
[ https://issues.apache.org/jira/browse/MNG-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003203#comment-17003203 ] Jiahongchao edited comment on MNG-6833 at 12/25/19 10:27 AM: - updated description was (Author: ihavenoem...@163.com): updated this issue > 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)
[jira] [Updated] (MNG-6833) Add a option to fail a build when dependency pom is invalid and transitive dependencies are not available
[ 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)
[jira] [Updated] (MNG-6833) Add a option to fail a build when dependency pom is invalid and transitive dependencies are not available
[ 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, I got a warning like this.However this war file is build successfully and I got a "class not found exception" in my tomcat. 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. > 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)
[jira] [Created] (MNG-6833) Add a option to fail a build when dependency pom is invalid and transitive dependencies are not available
Jiahongchao created MNG-6833: Summary: 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 When I build a war file, I got a warning like this.However this war file is build successfully and I got a "class not found exception" in my tomcat. 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. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNG-5950) only first active proxy considered
[ https://issues.apache.org/jira/browse/MNG-5950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070838#comment-15070838 ] Jiahongchao commented on MNG-5950: -- same as https://issues.apache.org/jira/browse/MNG-2305 but I can not reopen that one > only first active proxy considered > -- > > Key: MNG-5950 > URL: https://issues.apache.org/jira/browse/MNG-5950 > Project: Maven > Issue Type: Bug > Components: core >Affects Versions: 3.0.5 > Environment: windows 7 ,jdk 1.8 >Reporter: Jiahongchao > > only http proxy or https proxy can be used at the same time,however,only one > proxy should be used for both http and https -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MNG-5950) only first active proxy considered
Jiahongchao created MNG-5950: Summary: only first active proxy considered Key: MNG-5950 URL: https://issues.apache.org/jira/browse/MNG-5950 Project: Maven Issue Type: Bug Components: core Affects Versions: 3.0.5 Environment: windows 7 ,jdk 1.8 Reporter: Jiahongchao only http proxy or https proxy can be used at the same time,however,only one proxy should be used for both http and https -- This message was sent by Atlassian JIRA (v6.3.4#6332)
