[jira] [Commented] (SUREFIRE-1004) Enhance pattern/wildcard capabilities for dependenciesToScan to GAVT
[ https://issues.apache.org/jira/browse/SUREFIRE-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469874#comment-16469874 ] ASF GitHub Bot commented on SUREFIRE-1004: -- Tibor17 commented on issue #173: [SUREFIRE-1004] Support full gavtc format for dependenciesToScan URL: https://github.com/apache/maven-surefire/pull/173#issuecomment-387941555 @bindul The issue `SUREFIRE-1383` was pushed to master. Please rebase your fork on master and update the conflicts - `AbstractSurefireMojo.java`. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Enhance pattern/wildcard capabilities for dependenciesToScan to GAVT > > > Key: SUREFIRE-1004 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1004 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Failsafe Plugin, Maven Surefire Plugin >Affects Versions: 2.15 >Reporter: Andreas Gudian >Priority: Major > > * Enhance what has been built with SUREFIRE-569 to support patterns as in > maven-shade-plugin. Use maven-common-artifact-filters for that. > * Add/Adapt documentation and examples. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] Tibor17 commented on issue #173: [SUREFIRE-1004] Support full gavtc format for dependenciesToScan
Tibor17 commented on issue #173: [SUREFIRE-1004] Support full gavtc format for dependenciesToScan URL: https://github.com/apache/maven-surefire/pull/173#issuecomment-387941555 @bindul The issue `SUREFIRE-1383` was pushed to master. Please rebase your fork on master and update the conflicts - `AbstractSurefireMojo.java`. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (SUREFIRE-1383) dependenciesToScan Does Not Leverage Classpath Elements
[ https://issues.apache.org/jira/browse/SUREFIRE-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469873#comment-16469873 ] ASF GitHub Bot commented on SUREFIRE-1383: -- Tibor17 commented on issue #164: SUREFIRE-1383: Split IT569 in to multiple lifecycles URL: https://github.com/apache/maven-surefire/pull/164#issuecomment-387940764 @owenfarrell This feature was merged and will be released in version 2.22.0. You can close the PR. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > dependenciesToScan Does Not Leverage Classpath Elements > > > Key: SUREFIRE-1383 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1383 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.20 >Reporter: Owen Farrell >Assignee: Tibor Digana >Priority: Major > Fix For: 2.22.0 > > Attachments: scanned-dependencies-sample.zip > > Time Spent: 48h > Remaining Estimate: 24h > > The configuration attribute relies solely on installed > artifacts. This is an issue when the targeted dependencies were built as part > of the current session. The net result is that stale artifacts are used (i.e. > if the dependency has changed since it was last installed) or the tests are > not executed at all (if the dependency has not been previously installed. > Attached is a sample project that illustrates this issue: > Given I have a multi-module project >And the first module built includes test classes as part of the project > artifact >And subsequent modules scan the first for unit tests to execute > When I execute the _*test*_ goal (prior to any install) > Then the build should succeed >And tests should be executed with each module -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1383) dependenciesToScan Does Not Leverage Classpath Elements
[ https://issues.apache.org/jira/browse/SUREFIRE-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469872#comment-16469872 ] ASF GitHub Bot commented on SUREFIRE-1383: -- Tibor17 commented on issue #157: SUREFIRE-1383 dependenciesToScan Does Not Leverage Classpath Elements URL: https://github.com/apache/maven-surefire/pull/157#issuecomment-387940702 @owenfarrell This feature was merged and will be released in version 2.22.0. You can close the PR. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > dependenciesToScan Does Not Leverage Classpath Elements > > > Key: SUREFIRE-1383 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1383 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.20 >Reporter: Owen Farrell >Assignee: Tibor Digana >Priority: Major > Fix For: 2.22.0 > > Attachments: scanned-dependencies-sample.zip > > Time Spent: 48h > Remaining Estimate: 24h > > The configuration attribute relies solely on installed > artifacts. This is an issue when the targeted dependencies were built as part > of the current session. The net result is that stale artifacts are used (i.e. > if the dependency has changed since it was last installed) or the tests are > not executed at all (if the dependency has not been previously installed. > Attached is a sample project that illustrates this issue: > Given I have a multi-module project >And the first module built includes test classes as part of the project > artifact >And subsequent modules scan the first for unit tests to execute > When I execute the _*test*_ goal (prior to any install) > Then the build should succeed >And tests should be executed with each module -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] Tibor17 commented on issue #164: SUREFIRE-1383: Split IT569 in to multiple lifecycles
Tibor17 commented on issue #164: SUREFIRE-1383: Split IT569 in to multiple lifecycles URL: https://github.com/apache/maven-surefire/pull/164#issuecomment-387940764 @owenfarrell This feature was merged and will be released in version 2.22.0. You can close the PR. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] Tibor17 commented on issue #157: SUREFIRE-1383 dependenciesToScan Does Not Leverage Classpath Elements
Tibor17 commented on issue #157: SUREFIRE-1383 dependenciesToScan Does Not Leverage Classpath Elements URL: https://github.com/apache/maven-surefire/pull/157#issuecomment-387940702 @owenfarrell This feature was merged and will be released in version 2.22.0. You can close the PR. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Closed] (SUREFIRE-1383) dependenciesToScan Does Not Leverage Classpath Elements
[ https://issues.apache.org/jira/browse/SUREFIRE-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1383. -- Resolution: Fixed https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=2d9b1707b57af58c323493229573735c7f81e6d1 > dependenciesToScan Does Not Leverage Classpath Elements > > > Key: SUREFIRE-1383 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1383 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.20 >Reporter: Owen Farrell >Assignee: Tibor Digana >Priority: Major > Fix For: 2.22.0 > > Attachments: scanned-dependencies-sample.zip > > Time Spent: 48h > Remaining Estimate: 24h > > The configuration attribute relies solely on installed > artifacts. This is an issue when the targeted dependencies were built as part > of the current session. The net result is that stale artifacts are used (i.e. > if the dependency has changed since it was last installed) or the tests are > not executed at all (if the dependency has not been previously installed. > Attached is a sample project that illustrates this issue: > Given I have a multi-module project >And the first module built includes test classes as part of the project > artifact >And subsequent modules scan the first for unit tests to execute > When I execute the _*test*_ goal (prior to any install) > Then the build should succeed >And tests should be executed with each module -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SUREFIRE-1383) dependenciesToScan Does Not Leverage Classpath Elements
[ https://issues.apache.org/jira/browse/SUREFIRE-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1383: --- Fix Version/s: (was: 3.0.0-M1) 2.22.0 > dependenciesToScan Does Not Leverage Classpath Elements > > > Key: SUREFIRE-1383 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1383 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.20 >Reporter: Owen Farrell >Assignee: Tibor Digana >Priority: Major > Fix For: 2.22.0 > > Attachments: scanned-dependencies-sample.zip > > Time Spent: 48h > Remaining Estimate: 24h > > The configuration attribute relies solely on installed > artifacts. This is an issue when the targeted dependencies were built as part > of the current session. The net result is that stale artifacts are used (i.e. > if the dependency has changed since it was last installed) or the tests are > not executed at all (if the dependency has not been previously installed. > Attached is a sample project that illustrates this issue: > Given I have a multi-module project >And the first module built includes test classes as part of the project > artifact >And subsequent modules scan the first for unit tests to execute > When I execute the _*test*_ goal (prior to any install) > Then the build should succeed >And tests should be executed with each module -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6404) Cassandra-Maven plugin does not start
[ https://issues.apache.org/jira/browse/MNG-6404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravindra updated MNG-6404: -- Attachment: pom.png Error Screen.png > Cassandra-Maven plugin does not start > - > > Key: MNG-6404 > URL: https://issues.apache.org/jira/browse/MNG-6404 > Project: Maven > Issue Type: Bug > Components: Plugin API >Affects Versions: 3.5.0 > Environment: local >Reporter: Ravindra >Priority: Major > Labels: newbie > Attachments: Error Screen.png, pom.png > > > I am working on Spring Boot REST API. I use cassandra-maven plugin to start > the cassandra instance to run in local for integration testing purposes. The > cassandra starts sometimes with out any issues and executes all the > integration tests but most of the time it throws the following error > mentioned below. I cannot figure how to resolve the issue. I have attached > the pom.xml where I used the plugin. Thanks in advance. > > [INFO] Cassandra not running! > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 03:18 min > [INFO] Finished at: 2018-05-09T17:57:11-05:00 > [INFO] Final Memory: 95M/1452M > [INFO] > > [ERROR] Failed to execute goal > org.codehaus.mojo:cassandra-maven-plugin:3.5:start (start-cassandra) on > project odr-parameter-cloud: Cassandra failed to start within 180s -> [Help > 1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.codehaus.mojo:cassandra-maven-plugin:3.5:start (start-cassandra) on > project odr-parameter-cloud: Cassandra failed to start within 180s > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > at org.codehaus.classworlds.Launcher.main(Launcher.java:47) > Caused by: org.apache.maven.plugin.MojoFailureException: Cassandra failed to > start within 180s > at > org.codehaus.mojo.cassandra.StartCassandraMojo.execute(StartCassandraMojo.java:107) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) > ... 21 more > [ERROR] > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > [http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException] > > > Can you please help me with this. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6404) Cassandra-Maven plugin does not start
[ https://issues.apache.org/jira/browse/MNG-6404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravindra updated MNG-6404: -- Attachment: Screen Shot 2018-05-09 at 6.13.50 PM.png > Cassandra-Maven plugin does not start > - > > Key: MNG-6404 > URL: https://issues.apache.org/jira/browse/MNG-6404 > Project: Maven > Issue Type: Bug > Components: Plugin API >Affects Versions: 3.5.0 > Environment: local >Reporter: Ravindra >Priority: Major > Labels: newbie > > I am working on Spring Boot REST API. I use cassandra-maven plugin to start > the cassandra instance to run in local for integration testing purposes. The > cassandra starts sometimes with out any issues and executes all the > integration tests but most of the time it throws the following error > mentioned below. I cannot figure how to resolve the issue. I have attached > the pom.xml where I used the plugin. Thanks in advance. > > [INFO] Cassandra not running! > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 03:18 min > [INFO] Finished at: 2018-05-09T17:57:11-05:00 > [INFO] Final Memory: 95M/1452M > [INFO] > > [ERROR] Failed to execute goal > org.codehaus.mojo:cassandra-maven-plugin:3.5:start (start-cassandra) on > project odr-parameter-cloud: Cassandra failed to start within 180s -> [Help > 1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.codehaus.mojo:cassandra-maven-plugin:3.5:start (start-cassandra) on > project odr-parameter-cloud: Cassandra failed to start within 180s > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > at org.codehaus.classworlds.Launcher.main(Launcher.java:47) > Caused by: org.apache.maven.plugin.MojoFailureException: Cassandra failed to > start within 180s > at > org.codehaus.mojo.cassandra.StartCassandraMojo.execute(StartCassandraMojo.java:107) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) > ... 21 more > [ERROR] > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > [http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException] > > > Can you please help me with this. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6404) Cassandra-Maven plugin does not start
[ https://issues.apache.org/jira/browse/MNG-6404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravindra updated MNG-6404: -- Attachment: (was: pom doc.rtf) > Cassandra-Maven plugin does not start > - > > Key: MNG-6404 > URL: https://issues.apache.org/jira/browse/MNG-6404 > Project: Maven > Issue Type: Bug > Components: Plugin API >Affects Versions: 3.5.0 > Environment: local >Reporter: Ravindra >Priority: Major > Labels: newbie > > I am working on Spring Boot REST API. I use cassandra-maven plugin to start > the cassandra instance to run in local for integration testing purposes. The > cassandra starts sometimes with out any issues and executes all the > integration tests but most of the time it throws the following error > mentioned below. I cannot figure how to resolve the issue. I have attached > the pom.xml where I used the plugin. Thanks in advance. > > [INFO] Cassandra not running! > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 03:18 min > [INFO] Finished at: 2018-05-09T17:57:11-05:00 > [INFO] Final Memory: 95M/1452M > [INFO] > > [ERROR] Failed to execute goal > org.codehaus.mojo:cassandra-maven-plugin:3.5:start (start-cassandra) on > project odr-parameter-cloud: Cassandra failed to start within 180s -> [Help > 1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.codehaus.mojo:cassandra-maven-plugin:3.5:start (start-cassandra) on > project odr-parameter-cloud: Cassandra failed to start within 180s > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > at org.codehaus.classworlds.Launcher.main(Launcher.java:47) > Caused by: org.apache.maven.plugin.MojoFailureException: Cassandra failed to > start within 180s > at > org.codehaus.mojo.cassandra.StartCassandraMojo.execute(StartCassandraMojo.java:107) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) > ... 21 more > [ERROR] > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > [http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException] > > > Can you please help me with this. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6404) Cassandra-Maven plugin does not start
[ https://issues.apache.org/jira/browse/MNG-6404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravindra updated MNG-6404: -- Attachment: (was: Screen Shot 2018-05-09 at 6.00.31 PM.png) > Cassandra-Maven plugin does not start > - > > Key: MNG-6404 > URL: https://issues.apache.org/jira/browse/MNG-6404 > Project: Maven > Issue Type: Bug > Components: Plugin API >Affects Versions: 3.5.0 > Environment: local >Reporter: Ravindra >Priority: Major > Labels: newbie > > I am working on Spring Boot REST API. I use cassandra-maven plugin to start > the cassandra instance to run in local for integration testing purposes. The > cassandra starts sometimes with out any issues and executes all the > integration tests but most of the time it throws the following error > mentioned below. I cannot figure how to resolve the issue. I have attached > the pom.xml where I used the plugin. Thanks in advance. > > [INFO] Cassandra not running! > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 03:18 min > [INFO] Finished at: 2018-05-09T17:57:11-05:00 > [INFO] Final Memory: 95M/1452M > [INFO] > > [ERROR] Failed to execute goal > org.codehaus.mojo:cassandra-maven-plugin:3.5:start (start-cassandra) on > project odr-parameter-cloud: Cassandra failed to start within 180s -> [Help > 1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.codehaus.mojo:cassandra-maven-plugin:3.5:start (start-cassandra) on > project odr-parameter-cloud: Cassandra failed to start within 180s > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > at org.codehaus.classworlds.Launcher.main(Launcher.java:47) > Caused by: org.apache.maven.plugin.MojoFailureException: Cassandra failed to > start within 180s > at > org.codehaus.mojo.cassandra.StartCassandraMojo.execute(StartCassandraMojo.java:107) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) > ... 21 more > [ERROR] > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > [http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException] > > > Can you please help me with this. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6404) Cassandra-Maven plugin does not start
[ https://issues.apache.org/jira/browse/MNG-6404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravindra updated MNG-6404: -- Attachment: (was: Screen Shot 2018-05-09 at 6.13.50 PM.png) > Cassandra-Maven plugin does not start > - > > Key: MNG-6404 > URL: https://issues.apache.org/jira/browse/MNG-6404 > Project: Maven > Issue Type: Bug > Components: Plugin API >Affects Versions: 3.5.0 > Environment: local >Reporter: Ravindra >Priority: Major > Labels: newbie > > I am working on Spring Boot REST API. I use cassandra-maven plugin to start > the cassandra instance to run in local for integration testing purposes. The > cassandra starts sometimes with out any issues and executes all the > integration tests but most of the time it throws the following error > mentioned below. I cannot figure how to resolve the issue. I have attached > the pom.xml where I used the plugin. Thanks in advance. > > [INFO] Cassandra not running! > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 03:18 min > [INFO] Finished at: 2018-05-09T17:57:11-05:00 > [INFO] Final Memory: 95M/1452M > [INFO] > > [ERROR] Failed to execute goal > org.codehaus.mojo:cassandra-maven-plugin:3.5:start (start-cassandra) on > project odr-parameter-cloud: Cassandra failed to start within 180s -> [Help > 1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.codehaus.mojo:cassandra-maven-plugin:3.5:start (start-cassandra) on > project odr-parameter-cloud: Cassandra failed to start within 180s > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > at org.codehaus.classworlds.Launcher.main(Launcher.java:47) > Caused by: org.apache.maven.plugin.MojoFailureException: Cassandra failed to > start within 180s > at > org.codehaus.mojo.cassandra.StartCassandraMojo.execute(StartCassandraMojo.java:107) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) > ... 21 more > [ERROR] > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > [http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException] > > > Can you please help me with this. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6404) Cassandra-Maven plugin does not start
[ https://issues.apache.org/jira/browse/MNG-6404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravindra updated MNG-6404: -- Attachment: pom doc.rtf > Cassandra-Maven plugin does not start > - > > Key: MNG-6404 > URL: https://issues.apache.org/jira/browse/MNG-6404 > Project: Maven > Issue Type: Bug > Components: Plugin API >Affects Versions: 3.5.0 > Environment: local >Reporter: Ravindra >Priority: Major > Labels: newbie > Attachments: Screen Shot 2018-05-09 at 6.00.31 PM.png, pom doc.rtf > > > I am working on Spring Boot REST API. I use cassandra-maven plugin to start > the cassandra instance to run in local for integration testing purposes. The > cassandra starts sometimes with out any issues and executes all the > integration tests but most of the time it throws the following error > mentioned below. I cannot figure how to resolve the issue. I have attached > the pom.xml where I used the plugin. Thanks in advance. > > [INFO] Cassandra not running! > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 03:18 min > [INFO] Finished at: 2018-05-09T17:57:11-05:00 > [INFO] Final Memory: 95M/1452M > [INFO] > > [ERROR] Failed to execute goal > org.codehaus.mojo:cassandra-maven-plugin:3.5:start (start-cassandra) on > project odr-parameter-cloud: Cassandra failed to start within 180s -> [Help > 1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.codehaus.mojo:cassandra-maven-plugin:3.5:start (start-cassandra) on > project odr-parameter-cloud: Cassandra failed to start within 180s > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > at org.codehaus.classworlds.Launcher.main(Launcher.java:47) > Caused by: org.apache.maven.plugin.MojoFailureException: Cassandra failed to > start within 180s > at > org.codehaus.mojo.cassandra.StartCassandraMojo.execute(StartCassandraMojo.java:107) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) > ... 21 more > [ERROR] > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > [http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException] > > > Can you please help me with this. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6404) Cassandra-Maven plugin does not start
[ https://issues.apache.org/jira/browse/MNG-6404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravindra updated MNG-6404: -- Description: I am working on Spring Boot REST API. I use cassandra-maven plugin to start the cassandra instance to run in local for integration testing purposes. The cassandra starts sometimes with out any issues and executes all the integration tests but most of the time it throws the following error mentioned below. I cannot figure how to resolve the issue. I have attached the pom.xml where I used the plugin. Thanks in advance. [INFO] Cassandra not running! [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 03:18 min [INFO] Finished at: 2018-05-09T17:57:11-05:00 [INFO] Final Memory: 95M/1452M [INFO] [ERROR] Failed to execute goal org.codehaus.mojo:cassandra-maven-plugin:3.5:start (start-cassandra) on project odr-parameter-cloud: Cassandra failed to start within 180s -> [Help 1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:cassandra-maven-plugin:3.5:start (start-cassandra) on project odr-parameter-cloud: Cassandra failed to start within 180s at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) at org.codehaus.classworlds.Launcher.main(Launcher.java:47) Caused by: org.apache.maven.plugin.MojoFailureException: Cassandra failed to start within 180s at org.codehaus.mojo.cassandra.StartCassandraMojo.execute(StartCassandraMojo.java:107) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) ... 21 more [ERROR] [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] [http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException] Can you please help me with this. was: I am working on Spring Boot REST API. I use cassandra-maven plugin to start the cassandra instance to run in local for integration testing purposes. It runs fine sometimes and it throws the following error mentioned below. I cannot figure how to resolve the issue. [INFO] Cassandra not running! [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 03:18 min [INFO] Finished at: 2018-05-09T17:57:11-05:00 [INFO] Final Memory: 95M/1452M [INFO] [ERROR] Failed to execute goal org.codehaus.mojo:cassandra-maven-plugin:3.5:start (start-cassandra) on project odr-parameter-cloud: Cassandra failed to start within 180s -> [Help 1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:cassandra-maven-plugin:3.5:start (start-cassandra) on project odr-parameter-cloud: Cassandra failed to start within
[jira] [Created] (MNG-6404) Cassandra-Maven plugin does not start
Ravindra created MNG-6404: - Summary: Cassandra-Maven plugin does not start Key: MNG-6404 URL: https://issues.apache.org/jira/browse/MNG-6404 Project: Maven Issue Type: Bug Components: Plugin API Affects Versions: 3.5.0 Environment: local Reporter: Ravindra Attachments: Screen Shot 2018-05-09 at 6.00.31 PM.png I am working on Spring Boot REST API. I use cassandra-maven plugin to start the cassandra instance to run in local for integration testing purposes. It runs fine sometimes and it throws the following error mentioned below. I cannot figure how to resolve the issue. [INFO] Cassandra not running! [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 03:18 min [INFO] Finished at: 2018-05-09T17:57:11-05:00 [INFO] Final Memory: 95M/1452M [INFO] [ERROR] Failed to execute goal org.codehaus.mojo:cassandra-maven-plugin:3.5:start (start-cassandra) on project odr-parameter-cloud: Cassandra failed to start within 180s -> [Help 1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:cassandra-maven-plugin:3.5:start (start-cassandra) on project odr-parameter-cloud: Cassandra failed to start within 180s at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) at org.codehaus.classworlds.Launcher.main(Launcher.java:47) Caused by: org.apache.maven.plugin.MojoFailureException: Cassandra failed to start within 180s at org.codehaus.mojo.cassandra.StartCassandraMojo.execute(StartCassandraMojo.java:107) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) ... 21 more [ERROR] [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] [http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException] Can you please help me with this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (MCHANGES-388) Add option to include issues using the -SNAPSHOT suffix for version/milestone
[ https://issues.apache.org/jira/browse/MCHANGES-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469615#comment-16469615 ] Marcelo Riss edited comment on MCHANGES-388 at 5/9/18 10:33 PM: I have a use case where a number of SNAPSHOTS will require changes to be documented before the final release. It is to allow fast prototyping, where snapshots are less tested, but their changes still need to be documented. was (Author: mriss): I have a use case where a number of SNAPSHOTS will require changes to be documented before the final release. It is to allow fast prototyping, where snapshots are less tested, but still need to be documented. > Add option to include issues using the -SNAPSHOT suffix for version/milestone > - > > Key: MCHANGES-388 > URL: https://issues.apache.org/jira/browse/MCHANGES-388 > Project: Maven Changes Plugin > Issue Type: Wish >Reporter: Marcelo Riss >Priority: Minor > > I have a use case where the version id/name at the issue tracking system > (GHE) will have the -SNAPSHOT suffix. Currently, when setting GHE as issue > tracking system and the parameter > *[onlyCurrentVersion|http://maven.apache.org/plugins/maven-changes-plugin/github-report-mojo.html#onlyCurrentVersion]* > to true, the -SNAPSHOT suffix is removed when filtering the issues. My > suggestion is to add a configuration parameter allowing to consider or not > the -SNAPSHOT suffix as the version id/name when searching for issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MCHANGES-388) Add option to include issues using the -SNAPSHOT suffix for version/milestone
[ https://issues.apache.org/jira/browse/MCHANGES-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469615#comment-16469615 ] Marcelo Riss commented on MCHANGES-388: --- I have a use case where a number of SNAPSHOTS will require changes to be documented before the final release. It is to allow fast prototyping, where snapshots are less tested, but still need to be documented. > Add option to include issues using the -SNAPSHOT suffix for version/milestone > - > > Key: MCHANGES-388 > URL: https://issues.apache.org/jira/browse/MCHANGES-388 > Project: Maven Changes Plugin > Issue Type: Wish >Reporter: Marcelo Riss >Priority: Minor > > I have a use case where the version id/name at the issue tracking system > (GHE) will have the -SNAPSHOT suffix. Currently, when setting GHE as issue > tracking system and the parameter > *[onlyCurrentVersion|http://maven.apache.org/plugins/maven-changes-plugin/github-report-mojo.html#onlyCurrentVersion]* > to true, the -SNAPSHOT suffix is removed when filtering the issues. My > suggestion is to add a configuration parameter allowing to consider or not > the -SNAPSHOT suffix as the version id/name when searching for issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MSHARED-728) Upgrade maven-shared-utils to 3.2.1
Karl Heinz Marbaise created MSHARED-728: --- Summary: Upgrade maven-shared-utils to 3.2.1 Key: MSHARED-728 URL: https://issues.apache.org/jira/browse/MSHARED-728 Project: Maven Shared Components Issue Type: Dependency upgrade Components: maven-invoker Affects Versions: maven-invoker-3.0.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: maven-invoker-3.0.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MCHANGES-388) Add option to include issues using the -SNAPSHOT suffix for version/milestone
[ https://issues.apache.org/jira/browse/MCHANGES-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469436#comment-16469436 ] Michael Osipov commented on MCHANGES-388: - What is the purpose? Changes is supposed to document released version only. I do not fully understand the request. > Add option to include issues using the -SNAPSHOT suffix for version/milestone > - > > Key: MCHANGES-388 > URL: https://issues.apache.org/jira/browse/MCHANGES-388 > Project: Maven Changes Plugin > Issue Type: Wish >Reporter: Marcelo Riss >Priority: Minor > > I have a use case where the version id/name at the issue tracking system > (GHE) will have the -SNAPSHOT suffix. Currently, when setting GHE as issue > tracking system and the parameter > *[onlyCurrentVersion|http://maven.apache.org/plugins/maven-changes-plugin/github-report-mojo.html#onlyCurrentVersion]* > to true, the -SNAPSHOT suffix is removed when filtering the issues. My > suggestion is to add a configuration parameter allowing to consider or not > the -SNAPSHOT suffix as the version id/name when searching for issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MENFORCER-303) Upgrade mave-surefire/failsafe-plugin 2.21.0
Karl Heinz Marbaise created MENFORCER-303: - Summary: Upgrade mave-surefire/failsafe-plugin 2.21.0 Key: MENFORCER-303 URL: https://issues.apache.org/jira/browse/MENFORCER-303 Project: Maven Enforcer Plugin Issue Type: Dependency upgrade Affects Versions: 3.0.0-M1 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSITE-823) Documentation says JDK 1.6 required, doxia dependency requires 1.7
[
https://issues.apache.org/jira/browse/MSITE-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469434#comment-16469434
]
Michael Osipov commented on MSITE-823:
--
[~hboutemy], this seems odd. Why did the enforcer not fail?
> Documentation says JDK 1.6 required, doxia dependency requires 1.7
> --
>
> Key: MSITE-823
> URL: https://issues.apache.org/jira/browse/MSITE-823
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: documentation
>Affects Versions: 3.7, 3.7.1
>Reporter: Adam Voss
>Priority: Major
>
> [https://maven.apache.org/plugins/maven-site-plugin/plugin-info.html] lists
> System Requirements:
> |JDK|1.6|
>
> However doxia 1.8 is referenced, which requires JDK 1.7
> As a result Java 6 builds will fail after updating to 3.7 or newer
> {quote}
> Caused by: java.lang.UnsupportedClassVersionError:
> org/apache/maven/doxia/module/markdown/MarkdownParserModule : Unsupported
> major.minor version 51.0
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469261#comment-16469261
]
Alan Czajkowski edited comment on MNG-6397 at 5/9/18 7:45 PM:
--
*Work-around #1:*
- use mirrors inside {{settings.xml}}
{code:xml}
...
mirror-1
Mirror - 1
https://artifacts.example.com/repository/maven/
spring-milestone
mirror-2
Mirror - 2
https://artifacts.example.com/repository/maven/
spring-snapshot
mirror-3
Mirror - 3
https://artifacts.example.com/repository/maven/
rabbit-milestone
...
{code}
*Work-around #2:*
- restate the hi-jacking repositories inside your {{pom.xml}}, keep the
{{}} tags the same, and then do your own hi-jacking of the {{}} tags
inside the {{}} definitions, like so:
{code:xml}
...
false
spring-milestone
Spring Milestone
https://artifacts.example.com/repository/maven/
true
spring-snapshot
Spring Snapshot
https://artifacts.example.com/repository/maven/
false
rabbit-milestone
Rabbit Milestone
https://artifacts.example.com/repository/maven/
...
{code}
was (Author: alan-czajkowski):
*Work-around #1:*
- use mirrors inside {{settings.xml}}
{code:xml}
...
mirror-1
Mirror - 1
https://artifacts.example.com/repository/maven/
spring-milestone
mirror-2
Mirror - 2
https://artifacts.example.com/repository/maven/
spring-snapshot
mirror-3
Mirror - 3
https://artifacts.example.com/repository/maven/
rabbit-milestone
...
{code}
*Work-around #2:*
- restate the hi-jacking repositories inside your {{pom.xml}}, keep the
{{}} tags the same, and then do your own hi-jacking of the {{}} tags
inside the repository definitions, like so:
{code:xml}
...
false
spring-milestone
Spring Milestone
https://artifacts.example.com/repository/maven/
true
spring-snapshot
Spring Snapshot
https://artifacts.example.com/repository/maven/
false
rabbit-milestone
Rabbit Milestone
https://artifacts.example.com/repository/maven/
...
{code}
> Maven Transitive Dependency Resolution Does Not Respect Repository Definition
> -
>
> Key: MNG-6397
> URL: https://issues.apache.org/jira/browse/MNG-6397
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies, POM
>Affects Versions: 3.5.0, 3.5.2, 3.5.3
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /usr/local/share/maven
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
>Reporter: Alan Czajkowski
>Priority: Critical
> Labels: maven
>
> _*Note:* I am trying to do a build behind a firewall which means I cannot
> access the Internet, I can only access my internal Maven repository inside my
> network, so:_
> - _grabbing artifacts from https://artifacts.example.com/repository/maven/
> works fine_
> - _grabbing artifacts from anywhere fails due to firewall restrictions_
> Let's begin:
> My {{pom.xml}} has the following:
> {code:xml}
> ...
>
> ...
>
> org.springframework.boot
> spring-boot-starter-web
> 2.0.0.RELEASE
>
> ...
>
> ...
>
> ...
>
> central
> Public
> https://artifacts.example.com/repository/maven/
>
> true
>
>
> true
>
>
> ...
>
> ...
> {code}
> The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
> {code:java}
> +- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
> | +-
> org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
> | | +-
>
[jira] [Comment Edited] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469347#comment-16469347
]
Alan Czajkowski edited comment on MNG-6397 at 5/9/18 7:44 PM:
--
To be clear: this is a bug that needs to be fixed
"The point is that you are expecting to overwrite the repository definitions of
the dependencies/transitive dependencies which is not possible by using a
repository entry in the pom." <-- this is not true, my simple expectation is
that the Maven build *at least* try to attempt to reach out to the repo that i
have in my own pom.xml alongside the repos defined in the dependency pom.xml
<-- this is a reasonable expectation of Maven
Your dependencies whether transitive or not, should not be allowed to do a
*complete hi-jacking* of the list of repositories that the Maven build pulls
from, which is what is happening here <-- that is the bug, the hi-jacking part
the mirror work-around is not possible as i am not allowed to modify the
current build system in place, which means the only way forward is to either
explicitly define *all* of the problematic dependencies in my pom.xml (a very
tedious and horrible solution), or do the second work-around i mentioned above
by re-hi-jacking the repos again ... none of these work-arounds are ideal, nor
do they follow reasonable expectations of Maven
was (Author: alan-czajkowski):
To be clear: this is a bug that needs to be fixed
"The point is that you are expecting to overwrite the repository definitions of
the dependencies/transitive dependencies which is not possible by using a
repository entry in the pom." <-- this is not true, my simple expectation is
that the Maven build *at least* try to attempt to reach out to the repo that i
have in my own pom.xml alongside the repos defined in the dependency pom.xml
<-- this is a reasonable expectation of Maven
Your dependencies whether transitive or not, should not be allowed to do a
*complete hi-jacking* of the list of repositories that the Maven build pulls
from, which is what is happening here <-- that is the bug, the hi-jacking part
the mirror work-around is not possible as i am not allowed to modify the
current build system in place, which means the only way forward is to either
explicitly define *all* of the problematic dependencies in my pom.xml (a very
tedious and horrible solution), or do the second work-around i mentioned above
by re-hi-jacking the repos again ... none of these work-arounds are ideal, nor
do they follow natural expectations of Maven
> Maven Transitive Dependency Resolution Does Not Respect Repository Definition
> -
>
> Key: MNG-6397
> URL: https://issues.apache.org/jira/browse/MNG-6397
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies, POM
>Affects Versions: 3.5.0, 3.5.2, 3.5.3
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /usr/local/share/maven
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
>Reporter: Alan Czajkowski
>Priority: Critical
> Labels: maven
>
> _*Note:* I am trying to do a build behind a firewall which means I cannot
> access the Internet, I can only access my internal Maven repository inside my
> network, so:_
> - _grabbing artifacts from https://artifacts.example.com/repository/maven/
> works fine_
> - _grabbing artifacts from anywhere fails due to firewall restrictions_
> Let's begin:
> My {{pom.xml}} has the following:
> {code:xml}
> ...
>
> ...
>
> org.springframework.boot
> spring-boot-starter-web
> 2.0.0.RELEASE
>
> ...
>
> ...
>
> ...
>
> central
> Public
> https://artifacts.example.com/repository/maven/
>
> true
>
>
> true
>
>
> ...
>
> ...
> {code}
> The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
> {code:java}
> +- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
> | +-
> org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
> | | \-
> com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
> | +-
>
[jira] [Commented] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469347#comment-16469347
]
Alan Czajkowski commented on MNG-6397:
--
To be clear: this is a bug that needs to be fixed
"The point is that you are expecting to overwrite the repository definitions of
the dependencies/transitive dependencies which is not possible by using a
repository entry in the pom." <-- this is not true, my simple expectation is
that the Maven build *at least* try to attempt to reach out to the repo that i
have in my own pom.xml, alongside the repos defined in the dependency pom.xml
<-- this is a reasonable expectation of Maven
Your dependencies whether transitive or not, should not be allowed to do a
*complete hi-jacking* of the list of repositories that the Maven build pulls
from, which is what is happening here <-- that is the bug, the hi-jacking part
the mirror work-around is not possible as i am not allowed to modify the
current build system in place, which means the only way forward is to either
explicitly define *all* of the problematic dependencies in my pom.xml (a very
tedious and horrible solution), or do the second work-around i mentioned above
by re-hi-jacking the repos again ... none of these work-arounds are ideal, nor
do they follow natural expectations of Maven
> Maven Transitive Dependency Resolution Does Not Respect Repository Definition
> -
>
> Key: MNG-6397
> URL: https://issues.apache.org/jira/browse/MNG-6397
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies, POM
>Affects Versions: 3.5.0, 3.5.2, 3.5.3
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /usr/local/share/maven
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
>Reporter: Alan Czajkowski
>Priority: Critical
> Labels: maven
>
> _*Note:* I am trying to do a build behind a firewall which means I cannot
> access the Internet, I can only access my internal Maven repository inside my
> network, so:_
> - _grabbing artifacts from https://artifacts.example.com/repository/maven/
> works fine_
> - _grabbing artifacts from anywhere fails due to firewall restrictions_
> Let's begin:
> My {{pom.xml}} has the following:
> {code:xml}
> ...
>
> ...
>
> org.springframework.boot
> spring-boot-starter-web
> 2.0.0.RELEASE
>
> ...
>
> ...
>
> ...
>
> central
> Public
> https://artifacts.example.com/repository/maven/
>
> true
>
>
> true
>
>
> ...
>
> ...
> {code}
> The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
> {code:java}
> +- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
> | +-
> org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
> | | \-
> com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
> | +-
> org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
> | | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
> | +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
> | | +- javax.validation:validation-api:jar:2.0.1.Final:compile
> | | +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
> | | \- com.fasterxml:classmate:jar:1.3.1:compile
> | \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
> {code}
> How is it that the build fails as such:
> {code:java}
> ...
> Downloading:
> https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://repo.spring.io/snapshot/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://dl.bintray.com/rabbitmq/maven-milestones/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://repo.maven.apache.org/maven2/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> ...
> [ERROR] Failed to execute goal on project maven-multi-module-demo-backend:
> Could not resolve dependencies for project
> com.example.pipe:maven-multi-module-demo-backend:war:1.0.0-SNAPSHOT: Failed
> to collect
[jira] [Comment Edited] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469347#comment-16469347
]
Alan Czajkowski edited comment on MNG-6397 at 5/9/18 7:21 PM:
--
To be clear: this is a bug that needs to be fixed
"The point is that you are expecting to overwrite the repository definitions of
the dependencies/transitive dependencies which is not possible by using a
repository entry in the pom." <-- this is not true, my simple expectation is
that the Maven build *at least* try to attempt to reach out to the repo that i
have in my own pom.xml alongside the repos defined in the dependency pom.xml
<-- this is a reasonable expectation of Maven
Your dependencies whether transitive or not, should not be allowed to do a
*complete hi-jacking* of the list of repositories that the Maven build pulls
from, which is what is happening here <-- that is the bug, the hi-jacking part
the mirror work-around is not possible as i am not allowed to modify the
current build system in place, which means the only way forward is to either
explicitly define *all* of the problematic dependencies in my pom.xml (a very
tedious and horrible solution), or do the second work-around i mentioned above
by re-hi-jacking the repos again ... none of these work-arounds are ideal, nor
do they follow natural expectations of Maven
was (Author: alan-czajkowski):
To be clear: this is a bug that needs to be fixed
"The point is that you are expecting to overwrite the repository definitions of
the dependencies/transitive dependencies which is not possible by using a
repository entry in the pom." <-- this is not true, my simple expectation is
that the Maven build *at least* try to attempt to reach out to the repo that i
have in my own pom.xml, alongside the repos defined in the dependency pom.xml
<-- this is a reasonable expectation of Maven
Your dependencies whether transitive or not, should not be allowed to do a
*complete hi-jacking* of the list of repositories that the Maven build pulls
from, which is what is happening here <-- that is the bug, the hi-jacking part
the mirror work-around is not possible as i am not allowed to modify the
current build system in place, which means the only way forward is to either
explicitly define *all* of the problematic dependencies in my pom.xml (a very
tedious and horrible solution), or do the second work-around i mentioned above
by re-hi-jacking the repos again ... none of these work-arounds are ideal, nor
do they follow natural expectations of Maven
> Maven Transitive Dependency Resolution Does Not Respect Repository Definition
> -
>
> Key: MNG-6397
> URL: https://issues.apache.org/jira/browse/MNG-6397
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies, POM
>Affects Versions: 3.5.0, 3.5.2, 3.5.3
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /usr/local/share/maven
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
>Reporter: Alan Czajkowski
>Priority: Critical
> Labels: maven
>
> _*Note:* I am trying to do a build behind a firewall which means I cannot
> access the Internet, I can only access my internal Maven repository inside my
> network, so:_
> - _grabbing artifacts from https://artifacts.example.com/repository/maven/
> works fine_
> - _grabbing artifacts from anywhere fails due to firewall restrictions_
> Let's begin:
> My {{pom.xml}} has the following:
> {code:xml}
> ...
>
> ...
>
> org.springframework.boot
> spring-boot-starter-web
> 2.0.0.RELEASE
>
> ...
>
> ...
>
> ...
>
> central
> Public
> https://artifacts.example.com/repository/maven/
>
> true
>
>
> true
>
>
> ...
>
> ...
> {code}
> The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
> {code:java}
> +- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
> | +-
> org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
> | | \-
> com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
> | +-
>
[jira] [Comment Edited] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469279#comment-16469279
]
Karl Heinz Marbaise edited comment on MNG-6397 at 5/9/18 6:41 PM:
--
If you don't like my "work around" sorry...the {{settings.xml}} is the solution
to that particular problem. If you have already a build system this should
already being configured correctly that way otherwise it not correctly
configured (for example you should use config file provider plugin which offers
this exactly for the settings.xml) ...
I would suggest to define a {{*}} which is easier...
The point is that you are expecting to overwrite the repository definitions of
the dependencies/transitive dependencies which is not possible by using a
repository entry in the pom.
The point is that each pom/artifact maintainer can put repository definitions
into their pom file (which is not a good idea cause it exactly happens what
here is described...different story)...which results in exactly this situation.
There for you have the option via {{settings.xml}} and define a mirror which
redirects all request from each pom through the given mirror.
If you don't like the solution or is not acceptable for you than please provide
a patch(es) to solve it the way you like it...
was (Author: khmarbaise):
If you don't like my "work around" sorry...the {{settings.xml}} is the solution
to that particular problem. If you have already a build system this should
already being configured correctly that way otherwise it not correctly
configured (for example you should use config file provider plugin which offers
this exactly for the settings.xml) ...
The point is that you are expecting to overwrite the repository definitions of
the dependencies/transitive dependencies which is not possible by using a
repository entry in the pom.
The point is that each pom/artifact maintainer can put repository definitions
into their pom file (which is not a good idea cause it exactly happens what
here is described...different story)...which results in exactly this situation.
There for you have the option via {{settings.xml}} and define a mirror which
redirects all request from each pom through the given mirror.
If you don't like the solution or is not acceptable for you than please provide
a patch(es) to solve it the way you like it...
> Maven Transitive Dependency Resolution Does Not Respect Repository Definition
> -
>
> Key: MNG-6397
> URL: https://issues.apache.org/jira/browse/MNG-6397
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies, POM
>Affects Versions: 3.5.0, 3.5.2, 3.5.3
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /usr/local/share/maven
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
>Reporter: Alan Czajkowski
>Priority: Critical
> Labels: maven
>
> _*Note:* I am trying to do a build behind a firewall which means I cannot
> access the Internet, I can only access my internal Maven repository inside my
> network, so:_
> - _grabbing artifacts from https://artifacts.example.com/repository/maven/
> works fine_
> - _grabbing artifacts from anywhere fails due to firewall restrictions_
> Let's begin:
> My {{pom.xml}} has the following:
> {code:xml}
> ...
>
> ...
>
> org.springframework.boot
> spring-boot-starter-web
> 2.0.0.RELEASE
>
> ...
>
> ...
>
> ...
>
> central
> Public
> https://artifacts.example.com/repository/maven/
>
> true
>
>
> true
>
>
> ...
>
> ...
> {code}
> The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
> {code:java}
> +- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
> | +-
> org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
> | | \-
> com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
> | +-
> org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
> | | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
> | +-
[jira] [Commented] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469279#comment-16469279
]
Karl Heinz Marbaise commented on MNG-6397:
--
If you don't like my "work around" sorry...the {{settings.xml}} is the solution
to that particular problem. If you have already a build system this should
already being configured correctly that way otherwise it not correctly
configured (for example you should use config file provider plugin which offers
this exactly for the settings.xml) ...
The point is that you are expecting to overwrite the repository definitions of
the dependencies/transitive dependencies which is not possible by using a
repository entry in the pom.
The point is that each pom/artifact maintainer can put repository definitions
into their pom file (which is not a good idea cause it exactly happens what
here is described...different story)...which results in exactly this situation.
There for you have the option via {{settings.xml}} and define a mirror which
redirects all request from each pom through the given mirror.
If you don't like the solution or is not acceptable for you than please provide
a patch(es) to solve it the way you like it...
> Maven Transitive Dependency Resolution Does Not Respect Repository Definition
> -
>
> Key: MNG-6397
> URL: https://issues.apache.org/jira/browse/MNG-6397
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies, POM
>Affects Versions: 3.5.0, 3.5.2, 3.5.3
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /usr/local/share/maven
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
>Reporter: Alan Czajkowski
>Priority: Critical
> Labels: maven
>
> _*Note:* I am trying to do a build behind a firewall which means I cannot
> access the Internet, I can only access my internal Maven repository inside my
> network, so:_
> - _grabbing artifacts from https://artifacts.example.com/repository/maven/
> works fine_
> - _grabbing artifacts from anywhere fails due to firewall restrictions_
> Let's begin:
> My {{pom.xml}} has the following:
> {code:xml}
> ...
>
> ...
>
> org.springframework.boot
> spring-boot-starter-web
> 2.0.0.RELEASE
>
> ...
>
> ...
>
> ...
>
> central
> Public
> https://artifacts.example.com/repository/maven/
>
> true
>
>
> true
>
>
> ...
>
> ...
> {code}
> The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
> {code:java}
> +- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
> | +-
> org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
> | | \-
> com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
> | +-
> org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
> | | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
> | +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
> | | +- javax.validation:validation-api:jar:2.0.1.Final:compile
> | | +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
> | | \- com.fasterxml:classmate:jar:1.3.1:compile
> | \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
> {code}
> How is it that the build fails as such:
> {code:java}
> ...
> Downloading:
> https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://repo.spring.io/snapshot/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://dl.bintray.com/rabbitmq/maven-milestones/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://repo.maven.apache.org/maven2/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> ...
> [ERROR] Failed to execute goal on project maven-multi-module-demo-backend:
> Could not resolve dependencies for project
> com.example.pipe:maven-multi-module-demo-backend:war:1.0.0-SNAPSHOT: Failed
> to collect dependencies at
> org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE ->
>
[jira] [Commented] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469275#comment-16469275
]
Alan Czajkowski commented on MNG-6397:
--
is anybody looking into this bug?
> Maven Transitive Dependency Resolution Does Not Respect Repository Definition
> -
>
> Key: MNG-6397
> URL: https://issues.apache.org/jira/browse/MNG-6397
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies, POM
>Affects Versions: 3.5.0, 3.5.2, 3.5.3
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /usr/local/share/maven
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
>Reporter: Alan Czajkowski
>Priority: Critical
> Labels: maven
>
> _*Note:* I am trying to do a build behind a firewall which means I cannot
> access the Internet, I can only access my internal Maven repository inside my
> network, so:_
> - _grabbing artifacts from https://artifacts.example.com/repository/maven/
> works fine_
> - _grabbing artifacts from anywhere fails due to firewall restrictions_
> Let's begin:
> My {{pom.xml}} has the following:
> {code:xml}
> ...
>
> ...
>
> org.springframework.boot
> spring-boot-starter-web
> 2.0.0.RELEASE
>
> ...
>
> ...
>
> ...
>
> central
> Public
> https://artifacts.example.com/repository/maven/
>
> true
>
>
> true
>
>
> ...
>
> ...
> {code}
> The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
> {code:java}
> +- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
> | +-
> org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
> | | \-
> com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
> | +-
> org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
> | | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
> | +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
> | | +- javax.validation:validation-api:jar:2.0.1.Final:compile
> | | +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
> | | \- com.fasterxml:classmate:jar:1.3.1:compile
> | \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
> {code}
> How is it that the build fails as such:
> {code:java}
> ...
> Downloading:
> https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://repo.spring.io/snapshot/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://dl.bintray.com/rabbitmq/maven-milestones/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://repo.maven.apache.org/maven2/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> ...
> [ERROR] Failed to execute goal on project maven-multi-module-demo-backend:
> Could not resolve dependencies for project
> com.example.pipe:maven-multi-module-demo-backend:war:1.0.0-SNAPSHOT: Failed
> to collect dependencies at
> org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE ->
> org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Failed to read
> artifact descriptor for
> org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Could not
> transfer artifact org.jboss.shrinkwrap:shrinkwrap-bom:pom:1.2.3 from/to
> spring-milestone (https://repo.spring.io/milestone): Connection reset ->
> [Help 1]
> ...
> {code}
> when I did not even reference this repo {{spring-milestone
> ([https://repo.spring.io/milestone])}} anywhere in my {{pom.xml}}?
> When you go down the Spring Boot rabbit hole (go into the
> {{spring-boot-starter-web}}'s {{pom.xml}} and then traverse up its parent-pom
> structure a few jumps) you'll eventually get to a parent-pom
> {{spring-boot-dependencies}} with this definition:
> {code:xml}
> ...
>
>
>
> false
>
> spring-milestone
> Spring Milestone
> https://repo.spring.io/milestone
>
>
>
> true
>
>
[jira] [Comment Edited] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469261#comment-16469261
]
Alan Czajkowski edited comment on MNG-6397 at 5/9/18 6:37 PM:
--
*Work-around #1:*
- use mirrors inside {{settings.xml}}
{code:xml}
...
mirror-1
Mirror - 1
https://artifacts.example.com/repository/maven/
spring-milestone
mirror-2
Mirror - 2
https://artifacts.example.com/repository/maven/
spring-snapshot
mirror-3
Mirror - 3
https://artifacts.example.com/repository/maven/
rabbit-milestone
...
{code}
*Work-around #2:*
- restate the hi-jacking repositories inside your {{pom.xml}}, keep the
{{}} tags the same, and then do your own hi-jacking of the URLs inside the
repository definitions, like so:
{code:xml}
...
false
spring-milestone
Spring Milestone
https://artifacts.example.com/repository/maven/
true
spring-snapshot
Spring Snapshot
https://artifacts.example.com/repository/maven/
false
rabbit-milestone
Rabbit Milestone
https://artifacts.example.com/repository/maven/
...
{code}
was (Author: alan-czajkowski):
*Work-around #1:*
- use mirrors inside {{settings.xml}}
{code:xml}
...
mirror-1
Mirror - 1
https://artifacts.example.com/repository/maven/
spring-milestone
mirror-2
Mirror - 2
https://artifacts.example.com/repository/maven/
spring-snapshot
mirror-3
Mirror - 3
https://artifacts.example.com/repository/maven/
rabbit-milestone
...
{code}
*Work-around #2:*
- restate the hi-jacking repositories inside your {{pom.xml}}, keep the IDs the
same, and then do your own hi-jacking of the URLs inside the repository
definitions, like so:
{code:xml}
...
false
spring-milestone
Spring Milestone
https://artifacts.example.com/repository/maven/
true
spring-snapshot
Spring Snapshot
https://artifacts.example.com/repository/maven/
false
rabbit-milestone
Rabbit Milestone
https://artifacts.example.com/repository/maven/
...
{code}
> Maven Transitive Dependency Resolution Does Not Respect Repository Definition
> -
>
> Key: MNG-6397
> URL: https://issues.apache.org/jira/browse/MNG-6397
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies, POM
>Affects Versions: 3.5.0, 3.5.2, 3.5.3
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /usr/local/share/maven
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
>Reporter: Alan Czajkowski
>Priority: Critical
> Labels: maven
>
> _*Note:* I am trying to do a build behind a firewall which means I cannot
> access the Internet, I can only access my internal Maven repository inside my
> network, so:_
> - _grabbing artifacts from https://artifacts.example.com/repository/maven/
> works fine_
> - _grabbing artifacts from anywhere fails due to firewall restrictions_
> Let's begin:
> My {{pom.xml}} has the following:
> {code:xml}
> ...
>
> ...
>
> org.springframework.boot
> spring-boot-starter-web
> 2.0.0.RELEASE
>
> ...
>
> ...
>
> ...
>
> central
> Public
> https://artifacts.example.com/repository/maven/
>
> true
>
>
> true
>
>
> ...
>
> ...
> {code}
> The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
> {code:java}
> +- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
> | +-
> org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
> | | +-
>
[jira] [Comment Edited] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469261#comment-16469261
]
Alan Czajkowski edited comment on MNG-6397 at 5/9/18 6:37 PM:
--
*Work-around #1:*
- use mirrors inside {{settings.xml}}
{code:xml}
...
mirror-1
Mirror - 1
https://artifacts.example.com/repository/maven/
spring-milestone
mirror-2
Mirror - 2
https://artifacts.example.com/repository/maven/
spring-snapshot
mirror-3
Mirror - 3
https://artifacts.example.com/repository/maven/
rabbit-milestone
...
{code}
*Work-around #2:*
- restate the hi-jacking repositories inside your {{pom.xml}}, keep the
{{}} tags the same, and then do your own hi-jacking of the {{}} tags
inside the repository definitions, like so:
{code:xml}
...
false
spring-milestone
Spring Milestone
https://artifacts.example.com/repository/maven/
true
spring-snapshot
Spring Snapshot
https://artifacts.example.com/repository/maven/
false
rabbit-milestone
Rabbit Milestone
https://artifacts.example.com/repository/maven/
...
{code}
was (Author: alan-czajkowski):
*Work-around #1:*
- use mirrors inside {{settings.xml}}
{code:xml}
...
mirror-1
Mirror - 1
https://artifacts.example.com/repository/maven/
spring-milestone
mirror-2
Mirror - 2
https://artifacts.example.com/repository/maven/
spring-snapshot
mirror-3
Mirror - 3
https://artifacts.example.com/repository/maven/
rabbit-milestone
...
{code}
*Work-around #2:*
- restate the hi-jacking repositories inside your {{pom.xml}}, keep the
{{}} tags the same, and then do your own hi-jacking of the URLs inside the
repository definitions, like so:
{code:xml}
...
false
spring-milestone
Spring Milestone
https://artifacts.example.com/repository/maven/
true
spring-snapshot
Spring Snapshot
https://artifacts.example.com/repository/maven/
false
rabbit-milestone
Rabbit Milestone
https://artifacts.example.com/repository/maven/
...
{code}
> Maven Transitive Dependency Resolution Does Not Respect Repository Definition
> -
>
> Key: MNG-6397
> URL: https://issues.apache.org/jira/browse/MNG-6397
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies, POM
>Affects Versions: 3.5.0, 3.5.2, 3.5.3
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /usr/local/share/maven
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
>Reporter: Alan Czajkowski
>Priority: Critical
> Labels: maven
>
> _*Note:* I am trying to do a build behind a firewall which means I cannot
> access the Internet, I can only access my internal Maven repository inside my
> network, so:_
> - _grabbing artifacts from https://artifacts.example.com/repository/maven/
> works fine_
> - _grabbing artifacts from anywhere fails due to firewall restrictions_
> Let's begin:
> My {{pom.xml}} has the following:
> {code:xml}
> ...
>
> ...
>
> org.springframework.boot
> spring-boot-starter-web
> 2.0.0.RELEASE
>
> ...
>
> ...
>
> ...
>
> central
> Public
> https://artifacts.example.com/repository/maven/
>
> true
>
>
> true
>
>
> ...
>
> ...
> {code}
> The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
> {code:java}
> +- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
> | +-
> org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
> | | +-
>
[jira] [Comment Edited] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469261#comment-16469261
]
Alan Czajkowski edited comment on MNG-6397 at 5/9/18 6:34 PM:
--
*Work-around #1:*
- use mirrors inside {{settings.xml}}
{code:xml}
...
mirror-1
Mirror - 1
https://artifacts.example.com/repository/maven/
spring-milestone
mirror-2
Mirror - 2
https://artifacts.example.com/repository/maven/
spring-snapshot
mirror-3
Mirror - 3
https://artifacts.example.com/repository/maven/
rabbit-milestone
...
{code}
*Work-around #2:*
- restate the hi-jacking repositories inside your {{pom.xml}}, keep the IDs the
same, and then do your own hi-jacking of the URLs inside the repository
definitions, like so:
{code:xml}
...
false
spring-milestone
Spring Milestone
https://artifacts.example.com/repository/maven/
true
spring-snapshot
Spring Snapshot
https://artifacts.example.com/repository/maven/
false
rabbit-milestone
Rabbit Milestone
https://artifacts.example.com/repository/maven/
...
{code}
was (Author: alan-czajkowski):
*Work-around #1:*
- use mirrors inside {{settings.xml}}
{code:xml}
...
mirror-1
Mirror - 1
https://repo.td.com/repository/maven-public/
spring-milestone
mirror-2
Mirror - 2
https://repo.td.com/repository/maven-public/
spring-snapshot
mirror-3
Mirror - 3
https://repo.td.com/repository/maven-public/
rabbit-milestone
...
{code}
*Work-around #2:*
- restate the hi-jacking repositories inside your {{pom.xml}}, keep the IDs the
same, and then do your own hi-jacking of the URLs inside the repository
definitions, like so:
{code:xml}
...
false
spring-milestone
Spring Milestone
https://artifacts.example.com/repository/maven/
true
spring-snapshot
Spring Snapshot
https://artifacts.example.com/repository/maven/
false
rabbit-milestone
Rabbit Milestone
https://artifacts.example.com/repository/maven/
...
{code}
> Maven Transitive Dependency Resolution Does Not Respect Repository Definition
> -
>
> Key: MNG-6397
> URL: https://issues.apache.org/jira/browse/MNG-6397
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies, POM
>Affects Versions: 3.5.0, 3.5.2, 3.5.3
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /usr/local/share/maven
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
>Reporter: Alan Czajkowski
>Priority: Critical
> Labels: maven
>
> _*Note:* I am trying to do a build behind a firewall which means I cannot
> access the Internet, I can only access my internal Maven repository inside my
> network, so:_
> - _grabbing artifacts from https://artifacts.example.com/repository/maven/
> works fine_
> - _grabbing artifacts from anywhere fails due to firewall restrictions_
> Let's begin:
> My {{pom.xml}} has the following:
> {code:xml}
> ...
>
> ...
>
> org.springframework.boot
> spring-boot-starter-web
> 2.0.0.RELEASE
>
> ...
>
> ...
>
> ...
>
> central
> Public
> https://artifacts.example.com/repository/maven/
>
> true
>
>
> true
>
>
> ...
>
> ...
> {code}
> The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
> {code:java}
> +- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
> | +-
> org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
> | | +-
>
[jira] [Comment Edited] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469261#comment-16469261
]
Alan Czajkowski edited comment on MNG-6397 at 5/9/18 6:33 PM:
--
*Work-around #1:*
- use mirrors inside {{settings.xml}}
{code:xml}
...
mirror-1
Mirror - 1
https://repo.td.com/repository/maven-public/
spring-milestone
mirror-2
Mirror - 2
https://repo.td.com/repository/maven-public/
spring-snapshot
mirror-3
Mirror - 3
https://repo.td.com/repository/maven-public/
rabbit-milestone
...
{code}
*Work-around #2:*
- restate the hi-jacking repositories inside your {{pom.xml}}, keep the IDs the
same, and then do your own hi-jacking of the URLs inside the repository
definitions, like so:
{code:xml}
...
false
spring-milestone
Spring Milestone
https://artifacts.example.com/repository/maven/
true
spring-snapshot
Spring Snapshot
https://artifacts.example.com/repository/maven/
false
rabbit-milestone
Rabbit Milestone
https://artifacts.example.com/repository/maven/
...
{code}
was (Author: alan-czajkowski):
aside from using mirrors as a work-around, there is another work-around: you
have restate the hi-jacking repositories inside your {{pom.xml}}, keep the IDs
the same, and then do your own hi-jacking of the URLs inside the repository
definitions, like so:
{code:xml}
...
false
spring-milestone
Spring Milestone
https://artifacts.example.com/repository/maven/
true
spring-snapshot
Spring Snapshot
https://artifacts.example.com/repository/maven/
false
rabbit-milestone
Rabbit Milestone
https://artifacts.example.com/repository/maven/
...
{code}
> Maven Transitive Dependency Resolution Does Not Respect Repository Definition
> -
>
> Key: MNG-6397
> URL: https://issues.apache.org/jira/browse/MNG-6397
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies, POM
>Affects Versions: 3.5.0, 3.5.2, 3.5.3
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /usr/local/share/maven
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
>Reporter: Alan Czajkowski
>Priority: Critical
> Labels: maven
>
> _*Note:* I am trying to do a build behind a firewall which means I cannot
> access the Internet, I can only access my internal Maven repository inside my
> network, so:_
> - _grabbing artifacts from https://artifacts.example.com/repository/maven/
> works fine_
> - _grabbing artifacts from anywhere fails due to firewall restrictions_
> Let's begin:
> My {{pom.xml}} has the following:
> {code:xml}
> ...
>
> ...
>
> org.springframework.boot
> spring-boot-starter-web
> 2.0.0.RELEASE
>
> ...
>
> ...
>
> ...
>
> central
> Public
> https://artifacts.example.com/repository/maven/
>
> true
>
>
> true
>
>
> ...
>
> ...
> {code}
> The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
> {code:java}
> +- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
> | +-
> org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
> | | \-
> com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
> | +-
> org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
> | | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
> | +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
> | | +-
[jira] [Commented] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469261#comment-16469261
]
Alan Czajkowski commented on MNG-6397:
--
aside from using mirrors as a work-around, there is another work-around: you
have restate the hi-jacking repositories inside your {{pom.xml}}, keep the IDs
the same, and then do your own hi-jacking of the URLs inside the repository
definitions, like so:
{code:xml}
...
false
spring-milestone
Spring Milestone
https://artifacts.example.com/repository/maven/
true
spring-snapshot
Spring Snapshot
https://artifacts.example.com/repository/maven/
false
rabbit-milestone
Rabbit Milestone
https://artifacts.example.com/repository/maven/
...
{code}
> Maven Transitive Dependency Resolution Does Not Respect Repository Definition
> -
>
> Key: MNG-6397
> URL: https://issues.apache.org/jira/browse/MNG-6397
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies, POM
>Affects Versions: 3.5.0, 3.5.2, 3.5.3
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /usr/local/share/maven
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
>Reporter: Alan Czajkowski
>Priority: Critical
> Labels: maven
>
> _*Note:* I am trying to do a build behind a firewall which means I cannot
> access the Internet, I can only access my internal Maven repository inside my
> network, so:_
> - _grabbing artifacts from https://artifacts.example.com/repository/maven/
> works fine_
> - _grabbing artifacts from anywhere fails due to firewall restrictions_
> Let's begin:
> My {{pom.xml}} has the following:
> {code:xml}
> ...
>
> ...
>
> org.springframework.boot
> spring-boot-starter-web
> 2.0.0.RELEASE
>
> ...
>
> ...
>
> ...
>
> central
> Public
> https://artifacts.example.com/repository/maven/
>
> true
>
>
> true
>
>
> ...
>
> ...
> {code}
> The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
> {code:java}
> +- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
> | +-
> org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
> | | \-
> com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
> | +-
> org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
> | | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
> | +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
> | | +- javax.validation:validation-api:jar:2.0.1.Final:compile
> | | +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
> | | \- com.fasterxml:classmate:jar:1.3.1:compile
> | \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
> {code}
> How is it that the build fails as such:
> {code:java}
> ...
> Downloading:
> https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://repo.spring.io/snapshot/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://dl.bintray.com/rabbitmq/maven-milestones/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://repo.maven.apache.org/maven2/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> ...
> [ERROR] Failed to execute goal on project maven-multi-module-demo-backend:
> Could not resolve dependencies for project
> com.example.pipe:maven-multi-module-demo-backend:war:1.0.0-SNAPSHOT: Failed
> to collect dependencies at
> org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE ->
> org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Failed to read
> artifact descriptor for
> org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Could not
> transfer artifact
[jira] [Updated] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Czajkowski updated MNG-6397:
-
Description:
_*Note:* I am trying to do a build behind a firewall which means I cannot
access the Internet, I can only access my internal Maven repository inside my
network, so:_
- _grabbing artifacts from https://artifacts.example.com/repository/maven/
works fine_
- _grabbing artifacts from anywhere fails due to firewall restrictions_
Let's begin:
My {{pom.xml}} has the following:
{code:xml}
...
...
org.springframework.boot
spring-boot-starter-web
2.0.0.RELEASE
...
...
...
central
Public
https://artifacts.example.com/repository/maven/
true
true
...
...
{code}
The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
{code:java}
+- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
| +-
org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
| | +- com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
| | +-
com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
| | \-
com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
| +-
org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
| | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
| +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
| | +- javax.validation:validation-api:jar:2.0.1.Final:compile
| | +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
| | \- com.fasterxml:classmate:jar:1.3.1:compile
| \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
{code}
How is it that the build fails as such:
{code:java}
...
Downloading:
https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://repo.spring.io/snapshot/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://dl.bintray.com/rabbitmq/maven-milestones/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://repo.maven.apache.org/maven2/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
...
[ERROR] Failed to execute goal on project maven-multi-module-demo-backend:
Could not resolve dependencies for project
com.example.pipe:maven-multi-module-demo-backend:war:1.0.0-SNAPSHOT: Failed to
collect dependencies at
org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE ->
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Failed to read
artifact descriptor for
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Could not transfer
artifact org.jboss.shrinkwrap:shrinkwrap-bom:pom:1.2.3 from/to spring-milestone
(https://repo.spring.io/milestone): Connection reset -> [Help 1]
...
{code}
when I did not even reference this repo {{spring-milestone
([https://repo.spring.io/milestone])}} anywhere in my {{pom.xml}}?
When you go down the Spring Boot rabbit hole (go into the
{{spring-boot-starter-web}}'s {{pom.xml}} and then traverse up its parent-pom
structure a few jumps) you'll eventually get to a parent-pom
{{spring-boot-dependencies}} with this definition:
{code:xml}
...
false
spring-milestone
Spring Milestone
https://repo.spring.io/milestone
true
spring-snapshot
Spring Snapshot
https://repo.spring.io/snapshot
false
rabbit-milestone
Rabbit Milestone
https://dl.bintray.com/rabbitmq/maven-milestones
...
{code}
How is it that the Maven build does _not_ even attempt to reach out to
[https://artifacts.example.com/repository/maven/] to try to find the missing
dependency {{shrinkwrap-bom}}? and only reaches out to the above repos only and
not the one defined in my own {{pom.xml}}?
*This seems like a transitive dependency resolution bug to me as the Maven
build does not even make a single attempt at trying to get {{shrinkwrap-bom}}
from the {{}} that I have explicitly defined in my {{pom.xml}}. The
(grand)parents of the {{spring-boot-starter-web}} dependency completely hi-jack
the repository list that the build pulls from (this type of hi-jacking should
not be allowed). The {{shrinkwrap-bom}} artifact does exist in
[https://artifacts.example.com/repository/maven/] and can be fetched no problem
if it is explicitly defined in my {{pom.xml}} but defining it explicitly would
be a work-around and I cannot use this
[jira] [Commented] (MEAR-267) assembly.xml contains incorrect references to modules
[
https://issues.apache.org/jira/browse/MEAR-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469250#comment-16469250
]
Karl Heinz Marbaise commented on MEAR-267:
--
Do you have an example project for that so you can attach to this jira issue so
I can take a look
> assembly.xml contains incorrect references to modules
> -
>
> Key: MEAR-267
> URL: https://issues.apache.org/jira/browse/MEAR-267
> Project: Maven Ear Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Leonid Rozenblyum
>Priority: Major
>
> SCENARIO:
> Create a EAR project with maven-ear-plugin 3.0.0
> execute mvn ear:ear
> EXPECTED:
> assembly.xml contains reference to the jar/war equivalent to their physical
> names inside
> the EAR
> (e.g. if the jar is named tryEar-ejb-1.0-SNAPSHOT.jar then assembly.xml
> reference would be:
> {quote}{{}}
> tryEar-ejb-1.0-SNAPSHOT.jar
>
> {quote}
> (this worked in 2.10.1)
> ACTUALLY:
> assembly.xml contains reference
> {quote}
> com.leokom-tryEar-ejb-1.0-SNAPSHOT.jar
>
> {quote}
>
> Due to this difference - JBoss/WildFly cannot deploy the EAR.
> (it's easy to reproduce: you may create a ear project from some standard ones
> from maven-archetypes and change maven-ear-plugin version to 3.0.0).
>
> UPDATE: Sorry, maybe it's a bug in M2E-WTP plugin of Eclipse. I tried this
> scenario in standalone mode without Eclipse - and assembly.xml is consistent
> with the jar files
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MEAR-216) Unable to include dependencies of type test-jar
[
https://issues.apache.org/jira/browse/MEAR-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MEAR-216:
-
Fix Version/s: 3.0.2
> Unable to include dependencies of type test-jar
> ---
>
> Key: MEAR-216
> URL: https://issues.apache.org/jira/browse/MEAR-216
> Project: Maven Ear Plugin
> Issue Type: Improvement
>Affects Versions: 2.10
>Reporter: Maxim Frolov
>Priority: Blocker
> Fix For: 3.0.1, 3.0.2
>
> Attachments: test-jar-in-ear-2.zip, test-jar-in-ear.zip
>
>
> Please implement support for artifacts of type *test-jar*.
> One of the use cases would be to build a test EAR as a mix of production and
> test JARs where the test JARs are used to set up the test data used to test
> the production code.
> Currently including one or more dependencies of type test-jar causes
> *LifecycleExecutionException*:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-ear-plugin:2.10:generate-application-xml
> (default-generate-application-xml) on project suite-systemtests-common-ear:
> Failed to initialize ear modules: Unknown artifact type[test-jar] for
> artifact_id -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-ear-plugin:2.10:generate-application-xml
> (default-generate-application-xml) on project suite-systemtests-common-ear:
> Failed to initialize ear modules
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to
> initialize ear modules
> at
> org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:260)
> at
> org.apache.maven.plugin.ear.GenerateApplicationXmlMojo.execute(GenerateApplicationXmlMojo.java:162)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by: org.apache.maven.plugin.ear.UnknownArtifactTypeException: Unknown
> artifact type[test-jar] for common-domain-impl
> at
> org.apache.maven.plugin.ear.EarModuleFactory.newEarModule(EarModuleFactory.java:88)
> at
> org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:250)
> ... 22 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MEAR-194) Output during creation of Ear is not correct
[
https://issues.apache.org/jira/browse/MEAR-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MEAR-194:
-
Fix Version/s: 3.0.2
> Output during creation of Ear is not correct
>
>
> Key: MEAR-194
> URL: https://issues.apache.org/jira/browse/MEAR-194
> Project: Maven Ear Plugin
> Issue Type: Improvement
>Affects Versions: 2.9.1
>Reporter: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.1, 3.0.2
>
>
> Currently during the creation of the ear the output shows something like this:
> {code}
> [INFO] Building jar: /opt/build/.../xyz-1.0.0-SNAPSHOT.ear
> {code}
> It should be changed into:
> {code}
> [INFO] Building ear: /opt/build/.../xyz-1.0.0-SNAPSHOT.ear
> {code}
> which is more consistent.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MEAR-212) Failed to initialize ear modules: Unknown artifact type[mar] for addressing
[
https://issues.apache.org/jira/browse/MEAR-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MEAR-212:
-
Fix Version/s: 3.0.2
> Failed to initialize ear modules: Unknown artifact type[mar] for addressing
> ---
>
> Key: MEAR-212
> URL: https://issues.apache.org/jira/browse/MEAR-212
> Project: Maven Ear Plugin
> Issue Type: New Feature
>Affects Versions: 2.10
>Reporter: David Hoffer
>Priority: Minor
> Fix For: 3.0.1, 3.0.2
>
>
> I'm trying to generate and ear file but I'm getting the following message:
> Failed to initialize ear modules: Unknown artifact type[mar] for addressing
> (full debug stack trace is below)
> However I don't have any mar artifacts in my dependencies. What I do have is
> a war that has 4 mar files added as resources and I'm making a ear with the
> skinny war feature.
> Why would the ear plugin give this error when it has no nothing to do with
> the mar resources in the war...or perhaps this error has nothing to do with
> those resources, not sure.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-ear-plugin:2.10:generate-application-xml
> (default-generate-application-xml) on project coreservices-ear: Failed to
> initialize ear modules: Unknown artifact type[mar] for addressing -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-ear-plugin:2.10:generate-application-xml
> (default-generate-application-xml) on project coreservices-ear: Failed to
> initialize ear modules
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to
> initialize ear modules
> at
> org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:260)
> at
> org.apache.maven.plugin.ear.GenerateApplicationXmlMojo.execute(GenerateApplicationXmlMojo.java:162)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by: org.apache.maven.plugin.ear.UnknownArtifactTypeException: Unknown
> artifact type[mar] for addressing
> at
> org.apache.maven.plugin.ear.EarModuleFactory.newEarModule(EarModuleFactory.java:88)
> at
> org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:250)
> ... 22 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MDEP-595) Maven 3.5.2 introduces intermittent test-jar dependency failures in multi-module builds
[
https://issues.apache.org/jira/browse/MDEP-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469189#comment-16469189
]
Karl Heinz Marbaise commented on MDEP-595:
--
Hm...this means we can't reproduce the issue..or do you have the old structure
as an example project which causes issue?
> Maven 3.5.2 introduces intermittent test-jar dependency failures in
> multi-module builds
> ---
>
> Key: MDEP-595
> URL: https://issues.apache.org/jira/browse/MDEP-595
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
> Environment: Windows 7 / Server 2012
> Maven 3.5.2
> JDK 1.8
> maven-jar-plugin 2.6
> maven-dependency-plugin 2.10 & 3.0.2
>Reporter: Beirtí Ó'Nunáin
>Priority: Major
> Fix For: waiting-for-feedback
>
>
> This issue never presented in 6 months of running a multi-module build on
> Maven 3.2.5. It began to present in Maven 3.5.2.
> As it's intermittent, will obviously be difficult to reproduce, but here is a
> knocked-down version of our project:
> * parent-aggregator
> ** project_a
> ** project_b
> *** builds jar and test-jar
> Project B has following pom snippet:
> {code:java}
>
> org.apache.maven.plugins
> maven-jar-plugin
>
>
>
> test-jar
>
>
>
>
> {code}
> Project A has a test-jar on Project B. The dependency
> declaration is as follows
> {code:java}
>
> mygroup
> projectB
> ${project.version}
> test-jar
> test
> {code}
> Using Maven 3.2.5, the dependency had been declared using
> tests and this worked fine. Following a
> recommendation on this page:
> https://stackoverflow.com/questions/1725476/maven-test-dependency-in-multi-module-project
> which refers to the previous editions of the guide suggesting classifier, I
> switched to '' but still have the same intermittent issue.
> This page suggests that using 'test-jar' is supported but not ideal:
> https://maven.apache.org/plugins/maven-jar-plugin/examples/create-test-jar.html
> Should we expect multi-module builds to work with test-jar dependencies or
> should we be using a separate 'tests' module instead?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MDEP-595) Maven 3.5.2 introduces intermittent test-jar dependency failures in multi-module builds
[
https://issues.apache.org/jira/browse/MDEP-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MDEP-595:
-
Fix Version/s: waiting-for-feedback
> Maven 3.5.2 introduces intermittent test-jar dependency failures in
> multi-module builds
> ---
>
> Key: MDEP-595
> URL: https://issues.apache.org/jira/browse/MDEP-595
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
> Environment: Windows 7 / Server 2012
> Maven 3.5.2
> JDK 1.8
> maven-jar-plugin 2.6
> maven-dependency-plugin 2.10 & 3.0.2
>Reporter: Beirtí Ó'Nunáin
>Priority: Major
> Fix For: waiting-for-feedback
>
>
> This issue never presented in 6 months of running a multi-module build on
> Maven 3.2.5. It began to present in Maven 3.5.2.
> As it's intermittent, will obviously be difficult to reproduce, but here is a
> knocked-down version of our project:
> * parent-aggregator
> ** project_a
> ** project_b
> *** builds jar and test-jar
> Project B has following pom snippet:
> {code:java}
>
> org.apache.maven.plugins
> maven-jar-plugin
>
>
>
> test-jar
>
>
>
>
> {code}
> Project A has a test-jar on Project B. The dependency
> declaration is as follows
> {code:java}
>
> mygroup
> projectB
> ${project.version}
> test-jar
> test
> {code}
> Using Maven 3.2.5, the dependency had been declared using
> tests and this worked fine. Following a
> recommendation on this page:
> https://stackoverflow.com/questions/1725476/maven-test-dependency-in-multi-module-project
> which refers to the previous editions of the guide suggesting classifier, I
> switched to '' but still have the same intermittent issue.
> This page suggests that using 'test-jar' is supported but not ideal:
> https://maven.apache.org/plugins/maven-jar-plugin/examples/create-test-jar.html
> Should we expect multi-module builds to work with test-jar dependencies or
> should we be using a separate 'tests' module instead?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MDEP-611) Upgrade plexus-archiver to 3.6.0
[ https://issues.apache.org/jira/browse/MDEP-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MDEP-611. Resolution: Fixed Fixed in [ace4e19a2be5764239e1d47f6c2232be6fb7c5d1|https://gitbox.apache.org/repos/asf?p=maven-dependency-plugin.git;a=commitdiff;h=ace4e19a2be5764239e1d47f6c2232be6fb7c5d1] > Upgrade plexus-archiver to 3.6.0 > > > Key: MDEP-611 > URL: https://issues.apache.org/jira/browse/MDEP-611 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.1.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MDEP-82) go-offline / resolve-plugins does not resolve all plugin dependencies
[
https://issues.apache.org/jira/browse/MDEP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468912#comment-16468912
]
John commented on MDEP-82:
--
To narrow this down to versions.
maven = 3.5.2
{code:java}
mvn dependency:go-offline
mvn -o clean install{code}
Fails with missing poms for transitive dependencies of plugins:
{code:java}
--- jacoco-maven-plugin:0.8.0:prepare-agent (default-prepare-agent) @ my-lib ---
[WARNING] The POM for junit:junit:jar:4.8.2 is missing, no dependency
information available
[WARNING] The POM for org.apache.maven.reporting:maven-reporting-impl:jar:2.1
is missing, no dependency information available
[WARNING] The POM for org.jacoco:org.jacoco.agent:jar:runtime:0.8.0 is missing,
no dependency information available
[WARNING] The POM for org.jacoco:org.jacoco.core:jar:0.8.0 is missing, no
dependency information available
[WARNING] The POM for org.jacoco:org.jacoco.report:jar:0.8.0 is missing, no
dependency information available
{code}
1) junit is relied upon _somewhere_ in this build without being explicitly
listed anywhere.
2) the org.jacoco:org.jacoco.* dependencies _are_ listed explicitly by
org.jacoco, however, when resolved, they only pulled the .jar, not the .pom.
This led to the later failures.
But I noticed it was defaulting to using a slightly older
maven-dependency-plugin, 2.8. So i tried:
{code:java}
mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.0:go-offline
{code}
Forcing that version resolved _all_ transitive plugin dependencies properly!
However, I ran into further missing dependencies, specifically with surefire.
After explicitly adding those, I was able to build successfully.
So, there are several layers of dependency resolutions not occurring, depending
on the version of the plugin being used, and how other plugins are being
implemented. Definitely no easy answer here. Our company is committed to
getting this to work at the moment, so I'll probably continue to be bothersome
> go-offline / resolve-plugins does not resolve all plugin dependencies
> -
>
> Key: MDEP-82
> URL: https://issues.apache.org/jira/browse/MDEP-82
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: go-offline, resolve-plugins
>Affects Versions: 2.0-alpha-4
> Environment: Maven 2.0.6
>Reporter: Arne Degenring
>Priority: Major
> Attachments: maven-dependency-plugin-2.3.patch, pom.xml
>
>
> The attached pom.xml is a very simple JAR project, without any direct
> dependencies or plugin dependencies.
> Start with an empty local repository, and run mvn dependency:go-offline on
> it. Some files get downloaded, but not everything that is needed for the
> build. If you run "mvn -o package" afterwards, you end up with the following
> error:
> {noformat}[ERROR] BUILD ERROR
> [INFO]
>
> [INFO] The plugin 'org.apache.maven.plugins:maven-resources-plugin' does not
> exist or no valid version could be found{noformat}
> Afterwards, even "mvn package" without the "-o" parameter does not work any
> longer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MCHANGES-388) Add option to include issues using the -SNAPSHOT suffix for version/milestone
[ https://issues.apache.org/jira/browse/MCHANGES-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468774#comment-16468774 ] Marcelo Riss commented on MCHANGES-388: --- I already have a proposal for a solution for this issue in a forked version of mvn changes plugin at github. > Add option to include issues using the -SNAPSHOT suffix for version/milestone > - > > Key: MCHANGES-388 > URL: https://issues.apache.org/jira/browse/MCHANGES-388 > Project: Maven Changes Plugin > Issue Type: Wish >Reporter: Marcelo Riss >Priority: Minor > > I have a use case where the version id/name at the issue tracking system > (GHE) will have the -SNAPSHOT suffix. Currently, when setting GHE as issue > tracking system and the parameter > *[onlyCurrentVersion|http://maven.apache.org/plugins/maven-changes-plugin/github-report-mojo.html#onlyCurrentVersion]* > to true, the -SNAPSHOT suffix is removed when filtering the issues. My > suggestion is to add a configuration parameter allowing to consider or not > the -SNAPSHOT suffix as the version id/name when searching for issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MCHANGES-388) Add option to include issues using the -SNAPSHOT suffix for version/milestone
[ https://issues.apache.org/jira/browse/MCHANGES-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcelo Riss updated MCHANGES-388: -- Priority: Minor (was: Major) > Add option to include issues using the -SNAPSHOT suffix for version/milestone > - > > Key: MCHANGES-388 > URL: https://issues.apache.org/jira/browse/MCHANGES-388 > Project: Maven Changes Plugin > Issue Type: Wish >Reporter: Marcelo Riss >Priority: Minor > > I have a use case where the version id/name at the issue tracking system > (GHE) will have the -SNAPSHOT suffix. Currently, when setting GHE as issue > tracking system and the parameter > *[onlyCurrentVersion|http://maven.apache.org/plugins/maven-changes-plugin/github-report-mojo.html#onlyCurrentVersion]* > to true, the -SNAPSHOT suffix is removed when filtering the issues. My > suggestion is to add a configuration parameter allowing to consider or not > the -SNAPSHOT suffix as the version id/name when searching for issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MCHANGES-388) Add option to include issues using the -SNAPSHOT suffix for version/milestone
[ https://issues.apache.org/jira/browse/MCHANGES-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcelo Riss updated MCHANGES-388: -- Description: I have a use case where the version id/name at the issue tracking system (GHE) will have the -SNAPSHOT suffix. Currently, when setting GHE as issue tracking system and the parameter *[onlyCurrentVersion|http://maven.apache.org/plugins/maven-changes-plugin/github-report-mojo.html#onlyCurrentVersion]* to true, the -SNAPSHOT suffix is removed when filtering the issues. My suggestion is to add a configuration parameter allowing to consider or not the -SNAPSHOT suffix as the version id/name when searching for issues. > Add option to include issues using the -SNAPSHOT suffix for version/milestone > - > > Key: MCHANGES-388 > URL: https://issues.apache.org/jira/browse/MCHANGES-388 > Project: Maven Changes Plugin > Issue Type: Wish >Reporter: Marcelo Riss >Priority: Major > > I have a use case where the version id/name at the issue tracking system > (GHE) will have the -SNAPSHOT suffix. Currently, when setting GHE as issue > tracking system and the parameter > *[onlyCurrentVersion|http://maven.apache.org/plugins/maven-changes-plugin/github-report-mojo.html#onlyCurrentVersion]* > to true, the -SNAPSHOT suffix is removed when filtering the issues. My > suggestion is to add a configuration parameter allowing to consider or not > the -SNAPSHOT suffix as the version id/name when searching for issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MCHANGES-388) Add option to include issues using the -SNAPSHOT suffix for version/milestone
Marcelo Riss created MCHANGES-388: - Summary: Add option to include issues using the -SNAPSHOT suffix for version/milestone Key: MCHANGES-388 URL: https://issues.apache.org/jira/browse/MCHANGES-388 Project: Maven Changes Plugin Issue Type: Wish Reporter: Marcelo Riss -- This message was sent by Atlassian JIRA (v7.6.3#76005)
