[jira] [Commented] (SUREFIRE-1261) surefire hangs of failed tests and keeps lock on surefirebooter on Windows preventing clean
[
https://issues.apache.org/jira/browse/SUREFIRE-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042553#comment-16042553
]
Valentin Baranov commented on SUREFIRE-1261:
[~tibor17], we have the same problem.
{code:xml}
kill
{code}
didn't help.
Could you please fix this problem or provide some temporary solution?
> surefire hangs of failed tests and keeps lock on surefirebooter on Windows
> preventing clean
> ---
>
> Key: SUREFIRE-1261
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1261
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin, process forking
>Affects Versions: 2.17, 2.19.1
> Environment: Apache Maven 3.3.9
> (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Maven home: C:\project\software\maven
> Java version: 1.8.0_66, vendor: Oracle Corporation
> Java home: C:\project\software\java\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "x86", family: "dos"
>Reporter: Jörg Hohwiller
>Assignee: Tibor Digana
>
> I have Spring-Tests run with surefire in a plain commandline maven build on
> windows. For whatever reason many tests fail with spring initialization
> exception. If I cancel the build in this case ([ctrl][c]) and then restart a
> clean build maven failes to delete the target directory. Using sysinternal
> tools I traced down that a java.exe process is hanging that locks a JAR
> called surefirebooter located in target. This is IMHO the forked process from
> the maven surefire plugin that was not terminated properly when the maven
> process was cancelled.
> You might need to register a shutdown hook in maven-surefire that properly
> cleans up the forked process. But this is just a brute guess...
> http://stackoverflow.com/questions/17465117/maven-surefirebooter
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (SUREFIRE-1384) Add ProviderInfo for JUnit Plattform to enable automatic provider lookup
Benedikt Ritter created SUREFIRE-1384: - Summary: Add ProviderInfo for JUnit Plattform to enable automatic provider lookup Key: SUREFIRE-1384 URL: https://issues.apache.org/jira/browse/SUREFIRE-1384 Project: Maven Surefire Issue Type: Improvement Components: JUnit 5.x support Reporter: Benedikt Ritter Fix For: 3.0-RC1 In order to enable automatic provider lookup for JUnit Plattform/JUnit 5, we need to add the corresponding ProviderInfo implementation to AbstractSurefireMojo. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SUREFIRE-1384) Add ProviderInfo for JUnit Plattform to enable automatic provider lookup
[ https://issues.apache.org/jira/browse/SUREFIRE-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedikt Ritter updated SUREFIRE-1384: -- External issue URL: https://github.com/apache/maven-surefire/pull/153 > Add ProviderInfo for JUnit Plattform to enable automatic provider lookup > > > Key: SUREFIRE-1384 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1384 > Project: Maven Surefire > Issue Type: Improvement > Components: JUnit 5.x support >Reporter: Benedikt Ritter > Fix For: 3.0-RC1 > > > In order to enable automatic provider lookup for JUnit Plattform/JUnit 5, we > need to add the corresponding ProviderInfo implementation to > AbstractSurefireMojo. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SUREFIRE-1384) Add ProviderInfo for JUnit Plattform to enable automatic provider lookup
[ https://issues.apache.org/jira/browse/SUREFIRE-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042643#comment-16042643 ] ASF GitHub Bot commented on SUREFIRE-1384: -- GitHub user britter opened a pull request: https://github.com/apache/maven-surefire/pull/153 SUREFIRE-1384: ProviderInfo for JUnit Plattform (WIP) This is Work in Progress! First take on a JUnitPlattform ProviderInfo, to enable automatic provider lookup. You can merge this pull request into a Git repository by running: $ git pull https://github.com/britter/maven-surefire junitplattform-provider-info Alternatively you can review and apply these changes as the patch at: https://github.com/apache/maven-surefire/pull/153.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #153 commit 890f1cb8b54c5fa612d3191df0057522f6d9f28a Author: Benedikt Ritter Date: 2017-06-08T12:46:04Z SUREFIRE-1384: Start implemeting JUnit Plattform ProviderInfo for automatic provider lookup > Add ProviderInfo for JUnit Plattform to enable automatic provider lookup > > > Key: SUREFIRE-1384 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1384 > Project: Maven Surefire > Issue Type: Improvement > Components: JUnit 5.x support >Reporter: Benedikt Ritter > Fix For: 3.0-RC1 > > > In order to enable automatic provider lookup for JUnit Plattform/JUnit 5, we > need to add the corresponding ProviderInfo implementation to > AbstractSurefireMojo. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SUREFIRE-1384) Add ProviderInfo for JUnit Plattform to enable automatic provider lookup
[ https://issues.apache.org/jira/browse/SUREFIRE-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042648#comment-16042648 ] ASF GitHub Bot commented on SUREFIRE-1384: -- Github user britter commented on the issue: https://github.com/apache/maven-surefire/pull/153 @marcphilipp this may be of interest for you. > Add ProviderInfo for JUnit Plattform to enable automatic provider lookup > > > Key: SUREFIRE-1384 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1384 > Project: Maven Surefire > Issue Type: Improvement > Components: JUnit 5.x support >Reporter: Benedikt Ritter > Fix For: 3.0-RC1 > > > In order to enable automatic provider lookup for JUnit Plattform/JUnit 5, we > need to add the corresponding ProviderInfo implementation to > AbstractSurefireMojo. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SUREFIRE-1384) Add ProviderInfo for JUnit Plattform to enable automatic provider lookup
[ https://issues.apache.org/jira/browse/SUREFIRE-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042667#comment-16042667 ] ASF GitHub Bot commented on SUREFIRE-1384: -- Github user britter commented on the issue: https://github.com/apache/maven-surefire/pull/153 @Tibor17 I'm having problems executing the integration test. When I run `mvn -Dit.test=JUnitPlattformIT verify` with Java 8, I get an error on running the Integration Test project: ``` Caused by: java.lang.NoClassDefFoundError: Lorg/sonatype/aether/RepositorySystemSession; at java.lang.Class.getDeclaredFields0(Native Method) at java.lang.Class.privateGetDeclaredFields(Class.java:2583) at java.lang.Class.getDeclaredFields(Class.java:1916) at com.google.inject.spi.InjectionPoint.getInjectionPoints(InjectionPoint.java:675) at com.google.inject.spi.InjectionPoint.forInstanceMethodsAndFields(InjectionPoint.java:380) at com.google.inject.internal.ConstructorBindingImpl.getInternalDependencies(ConstructorBindingImpl.java:164) at com.google.inject.internal.InjectorImpl.getInternalDependencies(InjectorImpl.java:613) at com.google.inject.internal.InjectorImpl.cleanup(InjectorImpl.java:569) at com.google.inject.internal.InjectorImpl.initializeJitBinding(InjectorImpl.java:555) at com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorImpl.java:884) at com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(InjectorImpl.java:805) at com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl.java:282) at com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImpl.java:214) at com.google.inject.internal.InjectorImpl.getProviderOrThrow(InjectorImpl.java:1006) at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1038) at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1001) at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1051) at org.eclipse.sisu.space.AbstractDeferredClass.get(AbstractDeferredClass.java:48) at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:81) at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:53) at com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:65) at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:115) at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:133) at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:68) at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:63) at com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:45) at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1092) at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012) at org.eclipse.sisu.inject.Guice4$1.get(Guice4.java:162) at org.eclipse.sisu.inject.LazyBeanEntry.getValue(LazyBeanEntry.java:81) at org.eclipse.sisu.plexus.LazyPlexusBean.getValue(LazyPlexusBean.java:51) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:263) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:255) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:519) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:121) ... 21 more Caused by: java.lang.ClassNotFoundException: org.sonatype.aether.RepositorySystemSession at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239) ... 57 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/AetherClassNotFound
[jira] [Commented] (SUREFIRE-1261) surefire hangs of failed tests and keeps lock on surefirebooter on Windows preventing clean
[ https://issues.apache.org/jira/browse/SUREFIRE-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043245#comment-16043245 ] Tibor Digana commented on SUREFIRE-1261: [~Prifiz] [~valyok] I cannot help you if you do not give me relevant data. The mechanism is immediate or kills after 20 seconds. If you kill Maven process and expect immediately released lockout then no way. > surefire hangs of failed tests and keeps lock on surefirebooter on Windows > preventing clean > --- > > Key: SUREFIRE-1261 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1261 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin, process forking >Affects Versions: 2.17, 2.19.1 > Environment: Apache Maven 3.3.9 > (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00) > Maven home: C:\project\software\maven > Java version: 1.8.0_66, vendor: Oracle Corporation > Java home: C:\project\software\java\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "x86", family: "dos" >Reporter: Jörg Hohwiller >Assignee: Tibor Digana > > I have Spring-Tests run with surefire in a plain commandline maven build on > windows. For whatever reason many tests fail with spring initialization > exception. If I cancel the build in this case ([ctrl][c]) and then restart a > clean build maven failes to delete the target directory. Using sysinternal > tools I traced down that a java.exe process is hanging that locks a JAR > called surefirebooter located in target. This is IMHO the forked process from > the maven surefire plugin that was not terminated properly when the maven > process was cancelled. > You might need to register a shutdown hook in maven-surefire that properly > cleans up the forked process. But this is just a brute guess... > http://stackoverflow.com/questions/17465117/maven-surefirebooter -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MDEPLOY-221) deploy generates wrong timestamps in maven-metadata.xml
[
https://issues.apache.org/jira/browse/MDEPLOY-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043573#comment-16043573
]
Guillaume Boué commented on MDEPLOY-221:
[~vvandens] I reproduced the issue clearly when building
[Jspresso|https://github.com/jspresso/jspresso-ce], thanks for this example.
The issue actually stems from the use of {{flexmojos-maven-plugin}} as an
extension. The consequence is that metadatas are getting downloaded / uploaded
twice, and the correct metadata of the first time is getting overwritten by the
second time, sometimes built a second after. You can actually notice the
duplicate download / upload in OP's initial output
{noformat}
[INFO] Downloading:
http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: ...
[INFO] Downloading:
http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
...
[INFO] Uploaded:
http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
(1.9 kB at 59 kB/s)
[INFO] Uploading: ...
[INFO] Uploaded:
http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
(1.9 kB at 43 kB/s)
{noformat}
This is indeed a Maven Core 3.5.0 issue, and does not come from the Deploy
plugin. I will create a MNG issue with a possible fix.
> deploy generates wrong timestamps in maven-metadata.xml
> ---
>
> Key: MDEPLOY-221
> URL: https://issues.apache.org/jira/browse/MDEPLOY-221
> Project: Maven Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy
>Affects Versions: 2.8.2
>Reporter: Roland Illig
>
> When deploying an artifact to a Nexus server, the file {{maven-metadata.xml}}
> can end up with inconsistent timestamps.
> {noformat}
> [INFO] Downloading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> [INFO] Downloaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> (1.9 kB at 24 kB/s)
> [INFO] Downloading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> [INFO] Downloaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> (1.9 kB at 171 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76.jar
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76.jar
> (18 kB at 591 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76.pom
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76.pom
> (2.2 kB at 71 kB/s)
> [INFO] Downloading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> [INFO] Downloaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> (1.2 kB at 92 kB/s)
> [INFO] Downloading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> [INFO] Downloaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> (1.2 kB at 92 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> (1.9 kB at 59 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> (1.9 kB at 43 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> (1.2 kB at 33 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> (1.2 kB at 40 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76-sources.jar
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.
[jira] [Comment Edited] (MDEPLOY-221) deploy generates wrong timestamps in maven-metadata.xml
[
https://issues.apache.org/jira/browse/MDEPLOY-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043573#comment-16043573
]
Guillaume Boué edited comment on MDEPLOY-221 at 6/8/17 11:18 PM:
-
[~vvandens] I reproduced the issue clearly when building
[Jspresso|https://github.com/jspresso/jspresso-ce], thanks for this example.
The issue actually stems from the use of {{flexmojos-maven-plugin}} as an
extension. The consequence is that metadatas are getting downloaded / uploaded
twice, and the correct metadata of the first time is getting merged with the
one produced the second time, sometimes built a second after. You can actually
notice the duplicate download / upload in OP's initial output
{noformat}
[INFO] Downloading:
http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: ...
[INFO] Downloading:
http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
...
[INFO] Uploaded:
http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
(1.9 kB at 59 kB/s)
[INFO] Uploading: ...
[INFO] Uploaded:
http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
(1.9 kB at 43 kB/s)
{noformat}
This is indeed a Maven Core 3.5.0 issue, and does not come from the Deploy
plugin. I will create a MNG issue with a possible fix.
was (Author: gboue):
[~vvandens] I reproduced the issue clearly when building
[Jspresso|https://github.com/jspresso/jspresso-ce], thanks for this example.
The issue actually stems from the use of {{flexmojos-maven-plugin}} as an
extension. The consequence is that metadatas are getting downloaded / uploaded
twice, and the correct metadata of the first time is getting overwritten by the
second time, sometimes built a second after. You can actually notice the
duplicate download / upload in OP's initial output
{noformat}
[INFO] Downloading:
http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: ...
[INFO] Downloading:
http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
...
[INFO] Uploaded:
http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
(1.9 kB at 59 kB/s)
[INFO] Uploading: ...
[INFO] Uploaded:
http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
(1.9 kB at 43 kB/s)
{noformat}
This is indeed a Maven Core 3.5.0 issue, and does not come from the Deploy
plugin. I will create a MNG issue with a possible fix.
> deploy generates wrong timestamps in maven-metadata.xml
> ---
>
> Key: MDEPLOY-221
> URL: https://issues.apache.org/jira/browse/MDEPLOY-221
> Project: Maven Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy
>Affects Versions: 2.8.2
>Reporter: Roland Illig
>
> When deploying an artifact to a Nexus server, the file {{maven-metadata.xml}}
> can end up with inconsistent timestamps.
> {noformat}
> [INFO] Downloading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> [INFO] Downloaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> (1.9 kB at 24 kB/s)
> [INFO] Downloading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> [INFO] Downloaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> (1.9 kB at 171 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76.jar
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76.jar
> (18 kB at 591 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76.pom
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76.pom
> (2.2 kB at 71 kB/s)
> [INFO] Downloading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> [INFO] Downloaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> (1.2 kB at 92 kB/s)
> [INFO] Downloading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> [INFO] Downloaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> (1.2
[jira] [Commented] (MDEPLOY-221) deploy generates wrong timestamps in maven-metadata.xml
[
https://issues.apache.org/jira/browse/MDEPLOY-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043763#comment-16043763
]
jpalacios commented on MDEPLOY-221:
---
[~gboue],
Will you please link the MNG issue here so we can watch it?
Cheers!
> deploy generates wrong timestamps in maven-metadata.xml
> ---
>
> Key: MDEPLOY-221
> URL: https://issues.apache.org/jira/browse/MDEPLOY-221
> Project: Maven Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy
>Affects Versions: 2.8.2
>Reporter: Roland Illig
>
> When deploying an artifact to a Nexus server, the file {{maven-metadata.xml}}
> can end up with inconsistent timestamps.
> {noformat}
> [INFO] Downloading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> [INFO] Downloaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> (1.9 kB at 24 kB/s)
> [INFO] Downloading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> [INFO] Downloaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> (1.9 kB at 171 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76.jar
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76.jar
> (18 kB at 591 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76.pom
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76.pom
> (2.2 kB at 71 kB/s)
> [INFO] Downloading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> [INFO] Downloaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> (1.2 kB at 92 kB/s)
> [INFO] Downloading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> [INFO] Downloaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> (1.2 kB at 92 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> (1.9 kB at 59 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> (1.9 kB at 43 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> (1.2 kB at 33 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> (1.2 kB at 40 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76-sources.jar
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/artifactId-31.0.0-20170510.070327-76-sources.jar
> (12 kB at 386 kB/s)
> [INFO] Downloading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> [INFO] Downloaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> (1.2 kB at 92 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> (1.9 kB at 59 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/31.0.0-SNAPSHOT/maven-metadata.xml
> (1.9 kB at 65 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> [INFO] Uploaded:
> http://nexus-url/content/repositories/snapshots/groupId/artifactId/maven-metadata.xml
> (1.2 kB at 37 kB/s)
> [INFO] Uploading:
> http://nexus-url/content/repositories/snapshots/grou
