[jira] [Commented] (SUREFIRE-1302) Surefire does not wait long enough for the forked VM and assumes it to be dead
[
https://issues.apache.org/jira/browse/SUREFIRE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102553#comment-16102553
]
Hudson commented on SUREFIRE-1302:
--
SUCCESS: Integrated in Jenkins build maven-surefire-dev #19 (See
[https://builds.apache.org/job/maven-surefire-dev/19/])
[SUREFIRE-1302] Surefire does not wait long enough for the forked VM and
(tibor17:
[http://git-wip-us.apache.org/repos/asf/?p=maven-surefire.git=commit=fec3dfedc359ae57c5928f98a7b1c43bad89bc5a])
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/report/FileReporterUtils.java
* (add)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/PpidChecker.java
* (add)
surefire-api/src/test/java/org/apache/maven/surefire/util/ReflectionUtilsTest.java
* (edit) maven-failsafe-plugin/pom.xml
* (edit) surefire-api/pom.xml
* (edit) maven-surefire-plugin/pom.xml
* (edit)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/ForkedBooter.java
* (edit)
surefire-booter/src/test/java/org/apache/maven/surefire/booter/JUnit4SuiteTest.java
* (edit) surefire-api/src/test/java/org/apache/maven/JUnit4SuiteTest.java
* (edit) surefire-booter/pom.xml
* (edit) pom.xml
* (add)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/Platform.java
* (edit)
surefire-api/src/main/java/org/apache/maven/surefire/util/ReflectionUtils.java
* (edit)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/BooterConstants.java
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/SurefireProperties.java
* (edit) maven-surefire-plugin/src/site/apt/examples/shutdown.apt.vm
* (delete)
surefire-api/src/test/java/org/apache/maven/surefire/util/internal/SystemUtilsTest.java
* (add)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/ProcessInfo.java
* (edit)
maven-surefire-common/src/test/java/org/apache/maven/plugin/surefire/booterclient/BooterDeserializerStartupConfigurationTest.java
* (edit)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/BooterDeserializer.java
* (edit)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/PropertiesWrapper.java
* (edit)
surefire-api/src/main/java/org/apache/maven/surefire/booter/CommandReader.java
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/ForkConfiguration.java
* (edit) maven-surefire-common/pom.xml
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/ForkStarter.java
* (add)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/SystemUtils.java
* (add)
surefire-booter/src/test/java/org/apache/maven/surefire/booter/SystemUtilsTest.java
* (delete)
surefire-api/src/main/java/org/apache/maven/surefire/util/internal/SystemUtils.java
* (add)
surefire-booter/src/test/java/org/apache/maven/surefire/booter/PpidCheckerTest.java
* (edit)
surefire-booter/src/test/java/org/apache/maven/surefire/booter/NewClassLoaderRunner.java
* (edit)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/Classpath.java
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java
* (edit)
maven-surefire-common/src/test/java/org/apache/maven/plugin/surefire/booterclient/ForkConfigurationTest.java
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/BooterSerializer.java
* (edit)
maven-surefire-common/src/test/java/org/apache/maven/plugin/surefire/booterclient/BooterDeserializerProviderConfigurationTest.java
* (edit)
maven-surefire-common/src/test/java/org/apache/maven/plugin/surefire/report/DefaultReporterFactoryTest.java
* (edit) maven-surefire-report-plugin/pom.xml
* (edit)
surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/jiras/Surefire1295AttributeJvmCrashesToTestsIT.java
> Surefire does not wait long enough for the forked VM and assumes it to be dead
> --
>
> Key: SUREFIRE-1302
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1302
> Project: Maven Surefire
> Issue Type: Request
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Yuriy Zaplavnov
>Assignee: Tibor Digana
> Fix For: 2.20.1
>
> Attachments: 2017-05-18T05-48-08_685-jvmRun1.dumpstream,
> surefire-gclog.log, surefire-logs,
> surefire-tests-terminated-master-aa9330316038f6b46316ce36ff40714ffc7cf299.zip,
> tests_log_01.txt, tests_log_02.txt
>
>
> This issue happens because surefire kills the forked container if it times
> out waiting for the 'ping'.
> In org.apache.maven.surefire.booter.ForkedBooter class there is hardcoded
> constant PING_TIMEOUT_IN_SECONDS = 20 which is used in the following method:
> {code}
> private static ScheduledFuture
[jira] [Assigned] (MDEP-559) Java 9 bytecode cannot be parsed
[
https://issues.apache.org/jira/browse/MDEP-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte reassigned MDEP-559:
---
Assignee: Robert Scholte
> Java 9 bytecode cannot be parsed
>
>
> Key: MDEP-559
> URL: https://issues.apache.org/jira/browse/MDEP-559
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 3.0.0
> Environment: Apache Maven 3.3.9
> (NON-CANONICAL_2015-11-23T13:17:27+03:00_root; 2015-11-23T21:17:27+11:00)
> Maven home: /opt/maven
> Java version: 9-ea, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-9-jdk
> Default locale: en_AU, platform encoding: UTF-8
> OS name: "linux", version: "4.9.11-1-arch", arch: "amd64", family: "unix"
>Reporter: Ben Alex
>Assignee: Robert Scholte
>
> Attempting to run analyze-only against source compiled with Java 9 results in:
> {noformat}
> [INFO] --- maven-dependency-plugin:3.0.0:analyze-only (config-dependency) @
> lmdbjava ---
> [DEBUG] Configuring mojo
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only from
> plugin realm
> ClassRealm[plugin>org.apache.maven.plugins:maven-dependency-plugin:3.0.0,
> parent: jdk.internal.loader.ClassLoaders$AppClassLoader@3b764bce]
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only' with
> basic configurator -->
> [DEBUG] (f) analyzer = default
> [DEBUG] (f) baseDir = /home/bpa/projects/lmdbjava
> [DEBUG] (f) failOnWarning = true
> [DEBUG] (f) ignoreNonCompile = false
> [DEBUG] (f) outputDirectory = /home/bpa/projects/lmdbjava/target
> [DEBUG] (f) outputXML = false
> [DEBUG] (f) project = MavenProject: org.lmdbjava:lmdbjava:0.0.6-SNAPSHOT @
> /home/bpa/projects/lmdbjava/dependency-reduced-pom.xml
> [DEBUG] (f) scriptableFlag = $$%%%
> [DEBUG] (f) scriptableOutput = false
> [DEBUG] (f) skip = false
> [DEBUG] (f) usedDependencies = [org.lmdbjava:lmdbjava-native-linux-x86_64,
> org.lmdbjava:lmdbjava-native-windows-x86_64,
> org.lmdbjava:lmdbjava-native-osx-x86_64]
> [DEBUG] (f) verbose = false
> [DEBUG] -- end configuration --
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 7.256 s
> [INFO] Finished at: 2017-03-17T17:32:20+11:00
> [INFO] Final Memory: 40M/132M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only
> (config-dependency) on project lmdbjava: Execution config-dependency of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only failed.
> IllegalArgumentException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only
> (config-dependency) on project lmdbjava: Execution config-dependency of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only failed.
> 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
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:547)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
>
[jira] [Assigned] (MENFORCER-275) Enforcer plugin breaks with JDK 9
[ https://issues.apache.org/jira/browse/MENFORCER-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reassigned MENFORCER-275: Assignee: Guillaume Boué > Enforcer plugin breaks with JDK 9 > - > > Key: MENFORCER-275 > URL: https://issues.apache.org/jira/browse/MENFORCER-275 > Project: Maven Enforcer Plugin > Issue Type: Bug > Components: Plugin >Affects Versions: 1.4.1 >Reporter: Ismaël Mejía >Assignee: Guillaume Boué > > I am trying to make Apache Beam work on Java 9. I found that the enforcer > plugin was not working as expected. A simple execution of mvn > enforcer:display-info fails, and also the execution of the plugin to enforce > fails. > I am using Maven 3.5 and Oracle Java 9+175. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MENFORCER-275) Enforcer plugin breaks with JDK 9
[ https://issues.apache.org/jira/browse/MENFORCER-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MENFORCER-275: - Fix Version/s: (was: 3.0.0) > Enforcer plugin breaks with JDK 9 > - > > Key: MENFORCER-275 > URL: https://issues.apache.org/jira/browse/MENFORCER-275 > Project: Maven Enforcer Plugin > Issue Type: Bug > Components: Plugin >Affects Versions: 1.4.1 >Reporter: Ismaël Mejía > > I am trying to make Apache Beam work on Java 9. I found that the enforcer > plugin was not working as expected. A simple execution of mvn > enforcer:display-info fails, and also the execution of the plugin to enforce > fails. > I am using Maven 3.5 and Oracle Java 9+175. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (MENFORCER-254) version 1.4.1 cause extra-enforcer-rules ITs failures
[ https://issues.apache.org/jira/browse/MENFORCER-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reassigned MENFORCER-254: Assignee: Karl Heinz Marbaise > version 1.4.1 cause extra-enforcer-rules ITs failures > - > > Key: MENFORCER-254 > URL: https://issues.apache.org/jira/browse/MENFORCER-254 > Project: Maven Enforcer Plugin > Issue Type: Bug >Affects Versions: 1.4.1 >Reporter: Hervé Boutemy >Assignee: Karl Heinz Marbaise >Priority: Blocker > Attachments: pom.xml > > > when building extra-enforcer-rules > http://www.mojohaus.org/extra-enforcer-rules/ with 1.4.1, some ITs fail: no > issue with 1.4 or any other release -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MENFORCER-254) version 1.4.1 cause extra-enforcer-rules ITs failures
[ https://issues.apache.org/jira/browse/MENFORCER-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MENFORCER-254: - Fix Version/s: (was: 3.0.0) > version 1.4.1 cause extra-enforcer-rules ITs failures > - > > Key: MENFORCER-254 > URL: https://issues.apache.org/jira/browse/MENFORCER-254 > Project: Maven Enforcer Plugin > Issue Type: Bug >Affects Versions: 1.4.1 >Reporter: Hervé Boutemy >Priority: Blocker > Attachments: pom.xml > > > when building extra-enforcer-rules > http://www.mojohaus.org/extra-enforcer-rules/ with 1.4.1, some ITs fail: no > issue with 1.4 or any other release -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MDEP-573) "purge-local-repository -Dinclude" does not work as described
[ https://issues.apache.org/jira/browse/MDEP-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MDEP-573: Fix Version/s: (was: next-release) 3.0.2 > "purge-local-repository -Dinclude" does not work as described > - > > Key: MDEP-573 > URL: https://issues.apache.org/jira/browse/MDEP-573 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: purge-local-repository >Affects Versions: 3.0.0, 3.0.1 > Environment: Win 7, 64 Bit, JDK 8u92, MVN 3.5.0, MDEP 3.0.1 >Reporter: Markus Karg >Assignee: Guillaume Boué > Fix For: 3.0.2 > > > When I run _mvn generate-sources_ on a POM which binds the goal > _purge-local-repository_ to that phase, then MDEP correctly purges and > re-resolves the all dependencies of all submodules. > When I instead run _mvn dependency:purge-local-repository_ then the reactor > *skips* all submodules. > This in rather annoying and surprising, because nowhere in the public > description of MDEP is told that invoking _dependency:purge-local-repository_ > at the command line as the sole goal will effectively *skip submodules* of > the POM. > If this is not intended, this bug should get fixed. > If this is intended, then the documentation of this goal should clearly tell > that. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MDEP-571) JDK9: Issue with list goal fails with java.lang.NoSuchMethodException
[
https://issues.apache.org/jira/browse/MDEP-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MDEP-571:
Fix Version/s: (was: next-release)
3.0.2
> JDK9: Issue with list goal fails with java.lang.NoSuchMethodException
> -
>
> Key: MDEP-571
> URL: https://issues.apache.org/jira/browse/MDEP-571
> Project: Maven Dependency Plugin
> Issue Type: Bug
>Affects Versions: 3.0.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /usr/local/maven
> Java version: 9-ea, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.9.0_ea+174.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.11.6", arch: "x86_64", family: "mac"
>Reporter: Karl Heinz Marbaise
>Assignee: Guillaume Boué
>Priority: Blocker
> Fix For: 3.0.2
>
>
> Calling:
> {{mvn org.apache.maven.plugins:maven-dependency-plugin:3.0.1:list}}
> Fails with the following:
> {code}
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] parent
> [INFO] domain
> [INFO] service-client
> [INFO] webgui
> [INFO] service
> [INFO] app
> [INFO] appasm
> [INFO] shade
> [INFO] assembly
> [INFO]
> [INFO]
>
> [INFO] Building parent 3.4.6-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-dependency-plugin:3.0.1:list (default-cli) @ parent ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO]none
> [INFO]
> [INFO]
> [INFO]
>
> [INFO] Building domain 3.4.6-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-dependency-plugin:3.0.1:list (default-cli) @ domain ---
> java.lang.NoSuchMethodException:
> jdk.internal.module.ModuleReferenceImpl.descriptor()
> at java.base/java.lang.Class.getDeclaredMethod(Class.java:2451)
> at
> org.apache.maven.plugins.dependency.utils.DependencyStatusSets.getModuleDescriptor(DependencyStatusSets.java:272)
> at
> org.apache.maven.plugins.dependency.utils.DependencyStatusSets.buildArtifactListOutput(DependencyStatusSets.java:227)
> at
> org.apache.maven.plugins.dependency.utils.DependencyStatusSets.getOutput(DependencyStatusSets.java:165)
> at
> org.apache.maven.plugins.dependency.resolvers.ResolveDependenciesMojo.doExecute(ResolveDependenciesMojo.java:90)
> at
> org.apache.maven.plugins.dependency.AbstractDependencyMojo.execute(AbstractDependencyMojo.java:143)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> 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:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
>
[jira] [Updated] (MDEP-564) NPE on maven 3.5.0
[
https://issues.apache.org/jira/browse/MDEP-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MDEP-564:
Description:
When using get goal on maven 3.5.0 getting NPE.
Works fine on maven 3.3.9
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:3.0.0:get (default-cli) on
project standalone-pom: Execution default-cli of goal
org.apache.maven.plugins:maven-dependency-plugin:3.0.0:get failed.:
NullPointerException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:3.0.0:get (default-cli) on
project standalone-pom: Execution default-cli of goal
org.apache.maven.plugins:maven-dependency-plugin:3.0.0:get failed.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
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:309)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
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: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)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
default-cli of goal org.apache.maven.plugins:maven-dependency-plugin:3.0.0:get
failed.
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 20 more
Caused by: java.lang.NullPointerException
at
org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:370)
at
org.apache.maven.shared.dependencies.resolve.internal.Maven31DependencyResolver.resolveDependencies(Maven31DependencyResolver.java:227)
at
org.apache.maven.shared.dependencies.resolve.internal.Maven31DependencyResolver.resolveDependencies(Maven31DependencyResolver.java:90)
at
org.apache.maven.shared.dependencies.resolve.internal.DefaultDependencyResolver.resolveDependencies(DefaultDependencyResolver.java:81)
at org.apache.maven.plugins.dependency.GetMojo.execute(GetMojo.java:226)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
... 21 more
{noformat}
was:
When using get goal on maven 3.5.0 getting NPE.
Works fine on maven 3.3.9
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:3.0.0:get (default-cli) on
project standalone-pom: Execution default-cli of goal
org.apache.maven.plugins:maven-dependency-plugin:3.0.0:get failed.:
NullPointerException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:3.0.0:get (default-cli) on
project standalone-pom: Execution default-cli of goal
org.apache.maven.plugins:maven-dependency-plugin:3.0.0:get failed.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
at
[jira] [Comment Edited] (MENFORCER-248) Upgrading maven-enforcer-plugin to 1.4.1 breaks maven-assembly-plugin
[ https://issues.apache.org/jira/browse/MENFORCER-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101967#comment-16101967 ] Brian Brooks edited comment on MENFORCER-248 at 7/26/17 5:29 PM: - [~khmarbaise] We got bit by bug MENFORCER-248 as well when trying to upgrade to maven-enforcer-plugin 1.4.1 and maven-assembly-plugin 3.0.0. I see in https://issues.apache.org/jira/browse/MENFORCER-248?focusedCommentId=15169367=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15169367 that you said upgrading would fix this issue. Which upgraded components resolve MENFORCER-248? was (Author: bbrooks): [~khmarbaise] We got bit by bug MENFORCER-248 as well when trying to upgrade to maven-enforcer-plugin 1.4.1 and maven-assembly-plugin 3.0.0. I see in https://issues.apache.org/jira/browse/MENFORCER-248?focusedCommentId=15169367=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15169367 that you said upgraded would fix this issue. Which upgraded components resolve MENFORCER-248? > Upgrading maven-enforcer-plugin to 1.4.1 breaks maven-assembly-plugin > - > > Key: MENFORCER-248 > URL: https://issues.apache.org/jira/browse/MENFORCER-248 > Project: Maven Enforcer Plugin > Issue Type: Bug > Components: Plugin >Reporter: Blazej Checinski >Assignee: Karl Heinz Marbaise > Fix For: 1.4.1 > > Attachments: extjars.xml, pom.xml > > > After upgrading m-e-p from 1.4 to 1.4.1 the maven-assembly-plugin generates > the following error: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-assembly-plugin:2.4:single (assemble) on > project extjars: Execution assemble of goal > org.apache.maven.plugins:maven-assembly-plugin:2.4:single failed. > NullPointerException -> [Help 1] > Downgrading to m-e-p 1.4 makes the assembly work again. > Sample pom & assembly that expose the error attached. > When called via: > mvn -Dplugins.maven-enforcer-plugin.version=1.4 > a zip file is generated as expected, when called via > mvn -Dplugins.maven-enforcer-plugin.version=1.4.1 > (or without argument) you will get the NPE. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MENFORCER-248) Upgrading maven-enforcer-plugin to 1.4.1 breaks maven-assembly-plugin
[ https://issues.apache.org/jira/browse/MENFORCER-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101967#comment-16101967 ] Brian Brooks commented on MENFORCER-248: [~khmarbaise] We got bit by bug MENFORCER-248 as well when trying to upgrade to maven-enforcer-plugin 1.4.1 and maven-assembly-plugin 3.0.0. I see in https://issues.apache.org/jira/browse/MENFORCER-248?focusedCommentId=15169367=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15169367 that you said upgraded would fix this issue. Which upgraded components resolve MENFORCER-248? > Upgrading maven-enforcer-plugin to 1.4.1 breaks maven-assembly-plugin > - > > Key: MENFORCER-248 > URL: https://issues.apache.org/jira/browse/MENFORCER-248 > Project: Maven Enforcer Plugin > Issue Type: Bug > Components: Plugin >Reporter: Blazej Checinski >Assignee: Karl Heinz Marbaise > Fix For: 1.4.1 > > Attachments: extjars.xml, pom.xml > > > After upgrading m-e-p from 1.4 to 1.4.1 the maven-assembly-plugin generates > the following error: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-assembly-plugin:2.4:single (assemble) on > project extjars: Execution assemble of goal > org.apache.maven.plugins:maven-assembly-plugin:2.4:single failed. > NullPointerException -> [Help 1] > Downgrading to m-e-p 1.4 makes the assembly work again. > Sample pom & assembly that expose the error attached. > When called via: > mvn -Dplugins.maven-enforcer-plugin.version=1.4 > a zip file is generated as expected, when called via > mvn -Dplugins.maven-enforcer-plugin.version=1.4.1 > (or without argument) you will get the NPE. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MNG-6255) Maven script cannot parse jvm.config with CRLF
[
https://issues.apache.org/jira/browse/MNG-6255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101926#comment-16101926
]
ASF GitHub Bot commented on MNG-6255:
-
Github user grkvlt commented on the issue:
https://github.com/apache/maven-integration-testing/pull/24
Removed *CR* test
> Maven script cannot parse jvm.config with CRLF
> --
>
> Key: MNG-6255
> URL: https://issues.apache.org/jira/browse/MNG-6255
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.5.0
> Environment: Windows 7 with MINGW64 environment via Git for Windows
> 0.1.1 including GNU coreutils and bash 4.4.12
>Reporter: Andrew Kennedy
>
> A project with a {{.mvn/jvm.config}} file that has *CRLF* line endings will
> not parse it correctly. The script uses the {{tr}} command to change *LF* to
> space, but this leaves *CR* behind. For example, with the {{jvm.config}} file
> containing the text {{-Xmx1024m -Xms512m}} followed by *CRLF*, the following
> error message is printed:
> {code}
> $ mvn install
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> Invalid initial heap size: -Xms512m
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (MNG-6264) java.lang.ArrayIndexOutOfBoundsException: 92772 -> http://cwiki.apache.org/confluence/display/MAVEN/InternalErrorException
Francisco Acevedo created MNG-6264:
--
Summary: java.lang.ArrayIndexOutOfBoundsException: 92772 ->
http://cwiki.apache.org/confluence/display/MAVEN/InternalErrorException
Key: MNG-6264
URL: https://issues.apache.org/jira/browse/MNG-6264
Project: Maven
Issue Type: Bug
Reporter: Francisco Acevedo
Attachments: debug.log, mdp-ws.zip
Executing {code:java}mvnw.cmd -e -X > debug.log{code} in project attached
(mdp-ws.zip).
File debug.log is attached as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (MJAR-240) maven-jar-plugin index.html - bad links in left column Examples section
Brian Brooks created MJAR-240:
-
Summary: maven-jar-plugin index.html - bad links in left column
Examples section
Key: MJAR-240
URL: https://issues.apache.org/jira/browse/MJAR-240
Project: Maven JAR Plugin
Issue Type: Bug
Components: site
Reporter: Brian Brooks
Priority: Trivial
At the site https://maven.apache.org/plugins/maven-jar-plugin/index.html in the
leftColumn div there are some bad links
# In leftColumn {{Creating an Executable JAR File}}
{code}
Creating an Executable JAR File
{code}
# In leftColumn {{Using Your Own Manifest File}}. Clicking on that hyperlink
results in an HTTP 404 error.
{code}
Using Your Own Manifest File
{code}
# in [Usage|https://maven.apache.org/plugins/maven-jar-plugin/index.html#Usage]
section hyperlink {{plugin's wiki page}}
{code}
http://docs.codehaus.org/display/MAVENUSER/JAR+Plugin;>plugin's wiki
page
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (MNG-6263) Parallel dependency download fails
[
https://issues.apache.org/jira/browse/MNG-6263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Chystoprudov closed MNG-6263.
Resolution: Cannot Reproduce
Looks like issue was related to internal Maven proxy. When pointed directly to
repo1.maven.org issue can't be reproduced
> Parallel dependency download fails
> --
>
> Key: MNG-6263
> URL: https://issues.apache.org/jira/browse/MNG-6263
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.0
> Environment: Mac OS
>Reporter: Alexey Chystoprudov
>
> If execute Maven build with empty repository in several terminal consoles
> some of the runs were failed because of dependency download fail. Issue is
> not reproduced at Maven 3.2.5
> Generated test project
> {code}
> mvn archetype:generate -B -DarchetypeGroupId=com.atlassian.bamboo
> -DarchetypeArtifactId=bamboo-specs-archetype -DarchetypeVersion=6.0.2
> -DgroupId=com.atlassian.bamboo -DartifactId=bamboo-specs-tutorial
> -Dversion=1.0.0-SNAPSHOT -Dpackage=tutorial -Dtemplate=minimal
> cd bamboo-specs-tutorial
> {code}
> Then opened 5 consoles and started command in all of them
> {code}
> mvn -Dmaven.repo.local=remove-me -Ppublish-specs -Dspecs.yamlDir=output/1
> -Dspecs.useRest=false -Dspecs.rs.vcsLocationId=1 -Dspecs.rs.branch=master
> -Dspecs.rs.revision=
> {code}
> Parameter specs.yamlDir was different for every console to avoid overwrite of
> generated file
> Then cleaned up local repo and execute the same 5 times.
> {code}
> ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-
> plugin:3.5.1:compile (default-compile) on project bamboo-specs-tutorial:
> Execution default-
> compile of goal org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile
> failed: Plugin
> org.apache.maven.plugins:maven-compiler-plugin:3.5.1 or one of its
> dependencies could not
> be resolved: Failed to collect dependencies at
> org.apache.maven.plugins:maven-compiler-
> plugin:jar:3.5.1 -> org.apache.maven:maven-core:jar:3.0 ->
> org.apache.maven:maven-settings-
> builder:jar:3.0: Failed to read artifact descriptor for
> org.apache.maven:maven-settings-
> builder:jar:3.0: Could not transfer artifact
> org.apache.maven:maven-settings-builder:pom:3.0
> from/to maven-atlassian-com
> (https://packages.atlassian.com/maven/repository/internal):
> /Users/alexeychystoprudov/temp/bamboo-specs-tutorial/remove-
> me/org/apache/maven/maven-settings-builder/3.0/maven-settings-builder-3.0.pom.part
> (No
> such file or directory) -> [Help 1]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (MNG-6263) Parallel dependency download fails
[
https://issues.apache.org/jira/browse/MNG-6263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Chystoprudov updated MNG-6263:
-
Description:
If execute Maven build with empty repository in several terminal consoles some
of the runs were failed because of dependency download fail. Issue is not
reproduced at Maven 3.2.5
Generated test project
mvn archetype:generate -B -DarchetypeGroupId=com.atlassian.bamboo
-DarchetypeArtifactId=bamboo-specs-archetype -DarchetypeVersion=6.0.2
-DgroupId=com.atlassian.bamboo -DartifactId=bamboo-specs-tutorial
-Dversion=1.0.0-SNAPSHOT -Dpackage=tutorial -Dtemplate=minimal
cd bamboo-specs-tutorial
Then opened 5 consoles and started command in all of them
mvn -Dmaven.repo.local=remove-me -Ppublish-specs -Dspecs.yamlDir=output/1
-Dspecs.useRest=false -Dspecs.rs.vcsLocationId=1 -Dspecs.rs.branch=master
-Dspecs.rs.revision=
Parameter specs.yamlDir was different for every console to avoid overwrite of
generated file
Then cleaned up local repo and execute the same 5 times.
{code}
ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-
plugin:3.5.1:compile (default-compile) on project bamboo-specs-tutorial:
Execution default-
compile of goal org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile
failed: Plugin
org.apache.maven.plugins:maven-compiler-plugin:3.5.1 or one of its
dependencies could not
be resolved: Failed to collect dependencies at
org.apache.maven.plugins:maven-compiler-
plugin:jar:3.5.1 -> org.apache.maven:maven-core:jar:3.0 ->
org.apache.maven:maven-settings-
builder:jar:3.0: Failed to read artifact descriptor for
org.apache.maven:maven-settings-
builder:jar:3.0: Could not transfer artifact
org.apache.maven:maven-settings-builder:pom:3.0
from/to maven-atlassian-com
(https://packages.atlassian.com/maven/repository/internal):
/Users/alexeychystoprudov/temp/bamboo-specs-tutorial/remove-
me/org/apache/maven/maven-settings-builder/3.0/maven-settings-builder-3.0.pom.part
(No
such file or directory) -> [Help 1]
{code}
was:
If execute Maven build with empty repository in several terminal consoles some
of the runs were failed because of dependency download fail. Issue is not
reproduced at Maven 3.2.5
{code}
ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-
plugin:3.5.1:compile (default-compile) on project bamboo-specs-tutorial:
Execution default-
compile of goal org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile
failed: Plugin
org.apache.maven.plugins:maven-compiler-plugin:3.5.1 or one of its
dependencies could not
be resolved: Failed to collect dependencies at
org.apache.maven.plugins:maven-compiler-
plugin:jar:3.5.1 -> org.apache.maven:maven-core:jar:3.0 ->
org.apache.maven:maven-settings-
builder:jar:3.0: Failed to read artifact descriptor for
org.apache.maven:maven-settings-
builder:jar:3.0: Could not transfer artifact
org.apache.maven:maven-settings-builder:pom:3.0
from/to maven-atlassian-com
(https://packages.atlassian.com/maven/repository/internal):
/Users/alexeychystoprudov/temp/bamboo-specs-tutorial/remove-
me/org/apache/maven/maven-settings-builder/3.0/maven-settings-builder-3.0.pom.part
(No
such file or directory) -> [Help 1]
{code}
> Parallel dependency download fails
> --
>
> Key: MNG-6263
> URL: https://issues.apache.org/jira/browse/MNG-6263
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.0
> Environment: Mac OS
>Reporter: Alexey Chystoprudov
>
> If execute Maven build with empty repository in several terminal consoles
> some of the runs were failed because of dependency download fail. Issue is
> not reproduced at Maven 3.2.5
> Generated test project
> mvn archetype:generate -B -DarchetypeGroupId=com.atlassian.bamboo
> -DarchetypeArtifactId=bamboo-specs-archetype -DarchetypeVersion=6.0.2
> -DgroupId=com.atlassian.bamboo -DartifactId=bamboo-specs-tutorial
> -Dversion=1.0.0-SNAPSHOT -Dpackage=tutorial -Dtemplate=minimal
> cd bamboo-specs-tutorial
> Then opened 5 consoles and started command in all of them
> mvn -Dmaven.repo.local=remove-me -Ppublish-specs -Dspecs.yamlDir=output/1
> -Dspecs.useRest=false -Dspecs.rs.vcsLocationId=1 -Dspecs.rs.branch=master
> -Dspecs.rs.revision=
> Parameter specs.yamlDir was different for every console to avoid overwrite of
> generated file
> Then cleaned up local repo and execute the same 5 times.
> {code}
> ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-
> plugin:3.5.1:compile (default-compile) on project bamboo-specs-tutorial:
> Execution default-
> compile of goal org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile
> failed: Plugin
> org.apache.maven.plugins:maven-compiler-plugin:3.5.1 or one of its
> dependencies could not
> be resolved: Failed to collect dependencies at
>
[jira] [Updated] (MNG-6263) Parallel dependency download fails
[
https://issues.apache.org/jira/browse/MNG-6263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Chystoprudov updated MNG-6263:
-
Description:
If execute Maven build with empty repository in several terminal consoles some
of the runs were failed because of dependency download fail. Issue is not
reproduced at Maven 3.2.5
Generated test project
{code}
mvn archetype:generate -B -DarchetypeGroupId=com.atlassian.bamboo
-DarchetypeArtifactId=bamboo-specs-archetype -DarchetypeVersion=6.0.2
-DgroupId=com.atlassian.bamboo -DartifactId=bamboo-specs-tutorial
-Dversion=1.0.0-SNAPSHOT -Dpackage=tutorial -Dtemplate=minimal
cd bamboo-specs-tutorial
{code}
Then opened 5 consoles and started command in all of them
{code}
mvn -Dmaven.repo.local=remove-me -Ppublish-specs -Dspecs.yamlDir=output/1
-Dspecs.useRest=false -Dspecs.rs.vcsLocationId=1 -Dspecs.rs.branch=master
-Dspecs.rs.revision=
{code}
Parameter specs.yamlDir was different for every console to avoid overwrite of
generated file
Then cleaned up local repo and execute the same 5 times.
{code}
ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-
plugin:3.5.1:compile (default-compile) on project bamboo-specs-tutorial:
Execution default-
compile of goal org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile
failed: Plugin
org.apache.maven.plugins:maven-compiler-plugin:3.5.1 or one of its
dependencies could not
be resolved: Failed to collect dependencies at
org.apache.maven.plugins:maven-compiler-
plugin:jar:3.5.1 -> org.apache.maven:maven-core:jar:3.0 ->
org.apache.maven:maven-settings-
builder:jar:3.0: Failed to read artifact descriptor for
org.apache.maven:maven-settings-
builder:jar:3.0: Could not transfer artifact
org.apache.maven:maven-settings-builder:pom:3.0
from/to maven-atlassian-com
(https://packages.atlassian.com/maven/repository/internal):
/Users/alexeychystoprudov/temp/bamboo-specs-tutorial/remove-
me/org/apache/maven/maven-settings-builder/3.0/maven-settings-builder-3.0.pom.part
(No
such file or directory) -> [Help 1]
{code}
was:
If execute Maven build with empty repository in several terminal consoles some
of the runs were failed because of dependency download fail. Issue is not
reproduced at Maven 3.2.5
Generated test project
mvn archetype:generate -B -DarchetypeGroupId=com.atlassian.bamboo
-DarchetypeArtifactId=bamboo-specs-archetype -DarchetypeVersion=6.0.2
-DgroupId=com.atlassian.bamboo -DartifactId=bamboo-specs-tutorial
-Dversion=1.0.0-SNAPSHOT -Dpackage=tutorial -Dtemplate=minimal
cd bamboo-specs-tutorial
Then opened 5 consoles and started command in all of them
mvn -Dmaven.repo.local=remove-me -Ppublish-specs -Dspecs.yamlDir=output/1
-Dspecs.useRest=false -Dspecs.rs.vcsLocationId=1 -Dspecs.rs.branch=master
-Dspecs.rs.revision=
Parameter specs.yamlDir was different for every console to avoid overwrite of
generated file
Then cleaned up local repo and execute the same 5 times.
{code}
ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-
plugin:3.5.1:compile (default-compile) on project bamboo-specs-tutorial:
Execution default-
compile of goal org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile
failed: Plugin
org.apache.maven.plugins:maven-compiler-plugin:3.5.1 or one of its
dependencies could not
be resolved: Failed to collect dependencies at
org.apache.maven.plugins:maven-compiler-
plugin:jar:3.5.1 -> org.apache.maven:maven-core:jar:3.0 ->
org.apache.maven:maven-settings-
builder:jar:3.0: Failed to read artifact descriptor for
org.apache.maven:maven-settings-
builder:jar:3.0: Could not transfer artifact
org.apache.maven:maven-settings-builder:pom:3.0
from/to maven-atlassian-com
(https://packages.atlassian.com/maven/repository/internal):
/Users/alexeychystoprudov/temp/bamboo-specs-tutorial/remove-
me/org/apache/maven/maven-settings-builder/3.0/maven-settings-builder-3.0.pom.part
(No
such file or directory) -> [Help 1]
{code}
> Parallel dependency download fails
> --
>
> Key: MNG-6263
> URL: https://issues.apache.org/jira/browse/MNG-6263
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.0
> Environment: Mac OS
>Reporter: Alexey Chystoprudov
>
> If execute Maven build with empty repository in several terminal consoles
> some of the runs were failed because of dependency download fail. Issue is
> not reproduced at Maven 3.2.5
> Generated test project
> {code}
> mvn archetype:generate -B -DarchetypeGroupId=com.atlassian.bamboo
> -DarchetypeArtifactId=bamboo-specs-archetype -DarchetypeVersion=6.0.2
> -DgroupId=com.atlassian.bamboo -DartifactId=bamboo-specs-tutorial
> -Dversion=1.0.0-SNAPSHOT -Dpackage=tutorial -Dtemplate=minimal
> cd bamboo-specs-tutorial
> {code}
> Then opened 5 consoles and started command in all of them
> {code}
> mvn
[jira] [Created] (MNG-6263) Parallel dependency download fails
Alexey Chystoprudov created MNG-6263:
Summary: Parallel dependency download fails
Key: MNG-6263
URL: https://issues.apache.org/jira/browse/MNG-6263
Project: Maven
Issue Type: Bug
Affects Versions: 3.5.0
Environment: Mac OS
Reporter: Alexey Chystoprudov
If execute Maven build with empty repository in several terminal consoles some
of the runs were failed because of dependency download fail. Issue is not
reproduced at Maven 3.2.5
{code}
ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-
plugin:3.5.1:compile (default-compile) on project bamboo-specs-tutorial:
Execution default-
compile of goal org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile
failed: Plugin
org.apache.maven.plugins:maven-compiler-plugin:3.5.1 or one of its
dependencies could not
be resolved: Failed to collect dependencies at
org.apache.maven.plugins:maven-compiler-
plugin:jar:3.5.1 -> org.apache.maven:maven-core:jar:3.0 ->
org.apache.maven:maven-settings-
builder:jar:3.0: Failed to read artifact descriptor for
org.apache.maven:maven-settings-
builder:jar:3.0: Could not transfer artifact
org.apache.maven:maven-settings-builder:pom:3.0
from/to maven-atlassian-com
(https://packages.atlassian.com/maven/repository/internal):
/Users/alexeychystoprudov/temp/bamboo-specs-tutorial/remove-
me/org/apache/maven/maven-settings-builder/3.0/maven-settings-builder-3.0.pom.part
(No
such file or directory) -> [Help 1]
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (SUREFIRE-1302) Surefire does not wait long enough for the forked VM and assumes it to be dead
[
https://issues.apache.org/jira/browse/SUREFIRE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-1302.
--
Resolution: Fixed
https://git1-us-west.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=f1f4718e519bdee7ab53b91b34714adce3e39c34
> Surefire does not wait long enough for the forked VM and assumes it to be dead
> --
>
> Key: SUREFIRE-1302
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1302
> Project: Maven Surefire
> Issue Type: Request
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Yuriy Zaplavnov
>Assignee: Tibor Digana
> Fix For: 2.20.1
>
> Attachments: 2017-05-18T05-48-08_685-jvmRun1.dumpstream,
> surefire-gclog.log, surefire-logs,
> surefire-tests-terminated-master-aa9330316038f6b46316ce36ff40714ffc7cf299.zip,
> tests_log_01.txt, tests_log_02.txt
>
>
> This issue happens because surefire kills the forked container if it times
> out waiting for the 'ping'.
> In org.apache.maven.surefire.booter.ForkedBooter class there is hardcoded
> constant PING_TIMEOUT_IN_SECONDS = 20 which is used in the following method:
> {code}
> private static ScheduledFuture listenToShutdownCommands( CommandReader
> reader )
> {
> reader.addShutdownListener( createExitHandler( reader ) );
> AtomicBoolean pingDone = new AtomicBoolean( true );
> reader.addNoopListener( createPingHandler( pingDone ) );
> return JVM_TERMINATOR.scheduleAtFixedRate( createPingJob( pingDone,
> reader ),
>0,PING_TIMEOUT_IN_SECONDS,
> SECONDS );
> }
> {code}
> to create ScheduledFuture.
> In some of the cases the forked container might respond a bit later than it's
> expected and surefire kills it
> {code}
> private static Runnable createPingJob( final AtomicBoolean pingDone, final
> CommandReader reader )
> {
> return new Runnable()
> {
> public void run()
> {
> boolean hasPing = pingDone.getAndSet( false );
> if ( !hasPing )
> {
> exit( 1, KILL, reader, true );
> }
> }
> };
> }
> {code}
> As long as we need to terminate it anyway, It would be really helpful if the
> problem could be solved making the PING_TIMEOUT_IN_SECONDS configurable with
> the ability to specify the value from maven-surefire-plugin.
> It would help to configure this timeout based on needs and factors of the
> projects where surefire runs.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1398) TestNG test fails when both JUnitCore provider and TestNG provider are on classpath
[
https://issues.apache.org/jira/browse/SUREFIRE-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101289#comment-16101289
]
ASF GitHub Bot commented on SUREFIRE-1398:
--
Github user MatousJobanek commented on the issue:
https://github.com/apache/maven-surefire/pull/160
Sorry, I didn't notice that the parameter is used also in other cases.
I changed the commit to set the `threadCount` only when it is a positive
value also in case of JUnit - in the same way as it is done in case of TestNG
> TestNG test fails when both JUnitCore provider and TestNG provider are on
> classpath
> ---
>
> Key: SUREFIRE-1398
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1398
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin, TestNG support
>Affects Versions: 2.20
>Reporter: Matous Jobanek
>
> When both JUnitCore and TestNG providers are on classpath:
> {code:xml}
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.20
>
>
> org.apache.maven.surefire
> surefire-junit47
> 2.20
>
>
> org.apache.maven.surefire
> surefire-testng
> 2.20
>
>
>
> {code}
> then the TestNG execution fails with a message:
> {noformat}
> Configuring TestNG with: TestNG60Configurator
> Cannot use a threadCount parameter less than 1; 1 > 0
> Usage: [options] The XML suite files to run
> Options:
> -configfailurepolicy
>Configuration failure policy (skip or continue)
> -d
>Output directory
> -dataproviderthreadcount
>Number of threads to use when running data providers
> -excludegroups
>Comma-separated list of group names to exclude
> -groups
>Comma-separated list of group names to be run
> -junit
>JUnit mode
>Default: false
> -listener
>List of .class files or list of class names implementing ITestListener
> or
>ISuiteListener
> -methods
>Comma separated of test methods
>Default: []
> -methodselectors
>List of .class files or list of class names implementing
> IMethodSelector
> -mixed
>Mixed mode - autodetect the type of current test and run it with
>appropriate runner
>Default: false
> -objectfactory
>List of .class files or list of class names implementing
>ITestRunnerFactory
> -parallel
>Parallel mode (methods, tests or classes)
>Possible Values: [tests, methods, classes, instances, none, true,
> false]
> -port
>The port
> -reporter
>Extended configuration for custom report listener
> -suitename
>Default name of test suite, if not specified in suite definition file
> or
>source code
> -suitethreadpoolsize
>Size of the thread pool to use to run suites
>Default: 1
> -testclass
>The list of test classes
> -testjar
>A jar file containing the tests
> -testname
>Default name of test, if not specified in suitedefinition file or
> source
>code
> -testnames
>The list of test names to run
> -testrunfactory, -testRunFactory
>The factory used to create tests
> -threadcount
>Number of threads to use when running tests in parallel
> -usedefaultlisteners
>Whether to use the default listeners
>Default: true
> -log, -verbose
>Level of verbosity
> -xmlpathinjar
>The full path to the xml file inside the jar file (only valid if
> -testjar
>was specified)
>Default: testng.xml
> {noformat}
> The same behavior occurs when instead of these two providers I use my own
> dynamic provider and delegate the execution to the TestNG provider.
> The cause of the behavior is a combination of the method
> [convertJunitCoreParameters()|https://github.com/apache/maven-surefire/blob/master/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java#L1289]
> and the TestNG provider.
> The method is called for
> [JunitCoreProvider|https://github.com/apache/maven-surefire/blob/master/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java#L2696]
> and sets the thread count to the current value (no matter if it is set or
> not). In case that it is not set, then the value is 0, which causes the
> before mentioned failure when {{TestNGProvider}} is being executed.
> The same in case of
>
[jira] [Commented] (SUREFIRE-1302) Surefire does not wait long enough for the forked VM and assumes it to be dead
[
https://issues.apache.org/jira/browse/SUREFIRE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101259#comment-16101259
]
Hudson commented on SUREFIRE-1302:
--
SUCCESS: Integrated in Jenkins build maven-surefire #1722 (See
[https://builds.apache.org/job/maven-surefire/1722/])
[SUREFIRE-1302] Surefire does not wait long enough for the forked VM and
(tibor17:
[http://git-wip-us.apache.org/repos/asf/?p=maven-surefire.git=commit=f1f4718e519bdee7ab53b91b34714adce3e39c34])
* (edit)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/Classpath.java
* (edit) maven-surefire-common/pom.xml
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/report/FileReporterUtils.java
* (delete)
surefire-api/src/main/java/org/apache/maven/surefire/util/internal/SystemUtils.java
* (edit)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/ForkedBooter.java
* (add)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/ProcessInfo.java
* (edit) maven-surefire-plugin/pom.xml
* (edit) surefire-api/pom.xml
* (add)
surefire-booter/src/test/java/org/apache/maven/surefire/booter/SystemUtilsTest.java
* (edit)
maven-surefire-common/src/test/java/org/apache/maven/plugin/surefire/booterclient/BooterDeserializerStartupConfigurationTest.java
* (add)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/SystemUtils.java
* (edit)
maven-surefire-common/src/test/java/org/apache/maven/plugin/surefire/booterclient/BooterDeserializerProviderConfigurationTest.java
* (edit)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/BooterDeserializer.java
* (edit) pom.xml
* (edit)
surefire-api/src/main/java/org/apache/maven/surefire/booter/CommandReader.java
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/ForkConfiguration.java
* (edit)
surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/jiras/Surefire1295AttributeJvmCrashesToTestsIT.java
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/ForkStarter.java
* (edit)
surefire-booter/src/test/java/org/apache/maven/surefire/booter/NewClassLoaderRunner.java
* (edit) maven-surefire-report-plugin/pom.xml
* (add)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/PpidChecker.java
* (add)
surefire-api/src/test/java/org/apache/maven/surefire/util/ReflectionUtilsTest.java
* (delete)
surefire-api/src/test/java/org/apache/maven/surefire/util/internal/SystemUtilsTest.java
* (edit)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/PropertiesWrapper.java
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/SurefireProperties.java
* (edit)
maven-surefire-common/src/test/java/org/apache/maven/plugin/surefire/report/DefaultReporterFactoryTest.java
* (edit)
maven-surefire-common/src/test/java/org/apache/maven/plugin/surefire/booterclient/ForkConfigurationTest.java
* (edit) surefire-booter/pom.xml
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java
* (edit)
surefire-api/src/main/java/org/apache/maven/surefire/util/ReflectionUtils.java
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/BooterSerializer.java
* (add)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/Platform.java
* (edit)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/BooterConstants.java
* (add)
surefire-booter/src/test/java/org/apache/maven/surefire/booter/PpidCheckerTest.java
* (edit) maven-failsafe-plugin/pom.xml
* (edit) maven-surefire-plugin/src/site/apt/examples/shutdown.apt.vm
* (edit) surefire-api/src/test/java/org/apache/maven/JUnit4SuiteTest.java
* (edit)
surefire-booter/src/test/java/org/apache/maven/surefire/booter/JUnit4SuiteTest.java
> Surefire does not wait long enough for the forked VM and assumes it to be dead
> --
>
> Key: SUREFIRE-1302
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1302
> Project: Maven Surefire
> Issue Type: Request
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Yuriy Zaplavnov
>Assignee: Tibor Digana
> Fix For: 2.20.1
>
> Attachments: 2017-05-18T05-48-08_685-jvmRun1.dumpstream,
> surefire-gclog.log, surefire-logs,
> surefire-tests-terminated-master-aa9330316038f6b46316ce36ff40714ffc7cf299.zip,
> tests_log_01.txt, tests_log_02.txt
>
>
> This issue happens because surefire kills the forked container if it times
> out waiting for the 'ping'.
> In org.apache.maven.surefire.booter.ForkedBooter class there is hardcoded
> constant PING_TIMEOUT_IN_SECONDS = 20 which is used in the following method:
> {code}
> private static ScheduledFuture
