[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=17003441#comment-17003441 ] Jiahongchao commented on MNG-6833: -- I want an option "bar", if use "mvn -bar clean compile", maven will

[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"

[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

[jira] [Commented] (MNG-6420) ComparableVersion incorrectly parses certain version strings

[ https://issues.apache.org/jira/browse/MNG-6420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003383#comment-17003383 ] Elliotte Rusty Harold commented on MNG-6420: Do all the bugs involve version strings that

[jira] [Comment Edited] (MSHADE-286) Shading fails when a dependency's main artifact does not exist

[ https://issues.apache.org/jira/browse/MSHADE-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003368#comment-17003368 ] Peter De Maeyer edited comment on MSHADE-286 at 12/25/19 8:41 PM: --

[jira] [Commented] (MSHADE-286) Shading fails when a dependency's main artifact does not exist

[ https://issues.apache.org/jira/browse/MSHADE-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003368#comment-17003368 ] Peter De Maeyer commented on MSHADE-286: I'm working on a solution on a branch in my fork. >

[jira] [Updated] (MSHADE-286) Shading fails when a dependency's main artifact does not exist

[ https://issues.apache.org/jira/browse/MSHADE-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter De Maeyer updated MSHADE-286: --- Description: Shading fails when a dependency's main artifact does not exist, see the methods

[jira] [Updated] (MSHADE-286) Shading fails when a dependency's main artifact does not exist

[ https://issues.apache.org/jira/browse/MSHADE-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter De Maeyer updated MSHADE-286: --- Issue Type: Bug (was: Improvement) > Shading fails when a dependency's main artifact does

[jira] [Updated] (MSHADE-286) Shading fails when a dependency's main artifact does not exist

[ https://issues.apache.org/jira/browse/MSHADE-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter De Maeyer updated MSHADE-286: --- Summary: Shading fails when a dependency's main artifact does not exist (was: Artifacts to

[jira] [Updated] (MSHADE-286) Artifacts to be included for shading are not consistently checked for existence

[ https://issues.apache.org/jira/browse/MSHADE-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter De Maeyer updated MSHADE-286: --- Description: While looking at {{ShadeMojo.execute}}, I noticed that the artifacts to be

[jira] [Commented] (MSHADE-340) Shaded test jar artifact is not attached

[ https://issues.apache.org/jira/browse/MSHADE-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003366#comment-17003366 ] Peter De Maeyer commented on MSHADE-340: Integration test added illustrating scenario, fix

[GitHub] [maven-shade-plugin] peterdemaeyer commented on issue #34: [MSHADE-340] - Shaded test jar artifact is not attached to the project

peterdemaeyer commented on issue #34: [MSHADE-340] - Shaded test jar artifact is not attached to the project URL: https://github.com/apache/maven-shade-plugin/pull/34#issuecomment-568925286 Fixed {{ShadeMojo}} such that the shaded test JAR is attached to the project also when

[GitHub] [maven-shade-plugin] peterdemaeyer opened a new pull request #34: [MSHADE-340] - Shaded test jar artifact is not attached to the project

peterdemaeyer opened a new pull request #34: [MSHADE-340] - Shaded test jar artifact is not attached to the project URL: https://github.com/apache/maven-shade-plugin/pull/34 Following this checklist to help us incorporate your contribution quickly and easily: - [x] Make sure

[jira] [Updated] (MSHADE-340) Shaded test jar artifact is not attached

[ https://issues.apache.org/jira/browse/MSHADE-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter De Maeyer updated MSHADE-340: --- Description: When {{shadedArtifactAttached=true}} and {{shadeTestJar=true}}, the shaded test

[jira] [Commented] (MCOMPILER-372) Unable to compile modularized test code depending on test-jar

[ https://issues.apache.org/jira/browse/MCOMPILER-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003361#comment-17003361 ] François Loison commented on MCOMPILER-372: --- The exception is this one: javac -d

[jira] [Commented] (MRESOURCES-250) Add ability to flatten folder structure into target directory when copying resources

[ https://issues.apache.org/jira/browse/MRESOURCES-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003352#comment-17003352 ] Jamie Spence commented on MRESOURCES-250: - I think you guys are on the right track. The

[jira] [Commented] (MNG-6420) ComparableVersion incorrectly parses certain version strings

[ https://issues.apache.org/jira/browse/MNG-6420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003351#comment-17003351 ] Ross Goldberg commented on MNG-6420: I assume lambdas are OK, then. Is there any way to see what I

[jira] [Commented] (MNG-6420) ComparableVersion incorrectly parses certain version strings

[ https://issues.apache.org/jira/browse/MNG-6420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003350#comment-17003350 ] Karl Heinz Marbaise commented on MNG-6420: -- Based on the current state we could think about Java 8

[jira] [Commented] (MNG-6420) ComparableVersion incorrectly parses certain version strings

[ https://issues.apache.org/jira/browse/MNG-6420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003348#comment-17003348 ] Michael Osipov commented on MNG-6420: - It should be Java 7/8 w/o external deps. > ComparableVersion

[jira] [Commented] (MNG-6420) ComparableVersion incorrectly parses certain version strings

[ https://issues.apache.org/jira/browse/MNG-6420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003345#comment-17003345 ] Ross Goldberg commented on MNG-6420: I can redo the new version parser for whatever Java version you

[jira] [Commented] (MNG-6420) ComparableVersion incorrectly parses certain version strings

[ https://issues.apache.org/jira/browse/MNG-6420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003316#comment-17003316 ] Michael Osipov commented on MNG-6420: - No we don't, but we need to address this issue somehow. >

[jira] [Commented] (MNG-6420) ComparableVersion incorrectly parses certain version strings

[ https://issues.apache.org/jira/browse/MNG-6420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003299#comment-17003299 ] Elliotte Rusty Harold commented on MNG-6420: Patch wise, I don't think we want to introduce a

[jira] [Commented] (MASSEMBLY-775) Emit WARNING instead of ERROR

[ https://issues.apache.org/jira/browse/MASSEMBLY-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003278#comment-17003278 ] Mark Struberg commented on MASSEMBLY-775: - proposed change up for review

[jira] [Closed] (MNG-6749) Maven 3.x fails when following 301 redirects

[ https://issues.apache.org/jira/browse/MNG-6749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-6749. --- Fix Version/s: (was: wontfix-candidate) Resolution: Incomplete No reaction since August. >

[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=17003242#comment-17003242 ] Michael Osipov commented on MNG-6833: - I still don't understand what you want. > Add a option to fail

[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=17003232#comment-17003232 ] Jiahongchao commented on MNG-6833: -- Never mind. It is a wish, not a bug. > Add a option to fail a build

[jira] [Commented] (MNG-6420) ComparableVersion incorrectly parses certain version strings

[ https://issues.apache.org/jira/browse/MNG-6420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003229#comment-17003229 ] Michael Osipov commented on MNG-6420: - [~elharo], you may want to take a look at this. Maybe work on

[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

[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

[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=17003205#comment-17003205 ] Michael Osipov commented on MNG-6833: - Still not helpful. Unless you provide some log output or sample

[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=17003203#comment-17003203 ] Jiahongchao commented on MNG-6833: -- updated this issue > Add a option to fail a build when dependency pom

[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=17003203#comment-17003203 ] Jiahongchao edited comment on MNG-6833 at 12/25/19 10:27 AM: - updated

[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

[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

[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=17003192#comment-17003192 ] Michael Osipov commented on MNG-6833: - Please provide subtantial information about the problem. I fail

[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 ] Michael Osipov updated MNG-6833: Fix Version/s: wontfix-candidate > Add a option to fail a build when dependency pom is invalid and