[jira] [Comment Edited] (MDEPLOY-221) deploy generates wrong timestamps in maven-metadata.xml

2017-06-08 Thread JIRA

[ 
https://issues.apache.org/jira/browse/MDEPLOY-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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 kB at 92 kB/s)
> 

[jira] [Comment Edited] (MDEPLOY-221) deploy generates wrong timestamps in maven-metadata.xml

2017-06-06 Thread Vincent Vandenschrick (JIRA)

[ 
https://issues.apache.org/jira/browse/MDEPLOY-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16040154#comment-16040154
 ] 

Vincent Vandenschrick edited comment on MDEPLOY-221 at 6/7/17 4:42 AM:
---

Hi Guillaume,
Unfortunately, it's not fixed. I've just tied the 3.0.0-SNAPSHOT and there is 
still 1 second of difference between the metadata.xml timestamp and the 
deployed file timestamp on certain artifacts. BTW, not sure it is actually 
linked to the deploy plugin since the 2.8.2 works correctly on maven < 3.5.0...

Here are the logs for the failing artifact :

deployment :

Uploading: 
dav:http://repository.jspresso.org/maven2-snapshots/org/jspresso/framework/jspresso-hibernate/4.3-SNAPSHOT/jspresso-hibernate-4.3-20170607.042314-72.jar
Uploaded: 
dav:http://repository.jspresso.org/maven2-snapshots/org/jspresso/framework/jspresso-hibernate/4.3-SNAPSHOT/jspresso-hibernate-4.3-20170607.042314-72.jar
 (78 kB at 76 kB/s)


And the failing build :

[ERROR] Failed to execute goal on project hrsample-core: Could not resolve 
dependencies for project org.jspresso.hrsample:hrsample-core:jar:4.3-SNAPSHOT: 
Could not find artifact 
org.jspresso.framework:jspresso-hibernate:jar:4.3-20170607.042315-72 in 
jspresso-snapshots-repository (http://repository.jspresso.org/maven2-snapshots) 
-> [Help 1]


was (Author: vvandens):
Hi Guillaume,
Unfortunately, it's not fixed. I've just tied the 3.0.0-SNAPSHOT and there is 
still 1 second of difference between the metadata.xml timestamp and the 
deployed file timestamp on certain artifacts. BTW, not sure it is actually 
linked to the deploy plugin since the 2.8.2 works correctly on maven < 3.5.0...

Here are the logs for the failing artifact :

deployment :
{{Uploading: 
dav:http://repository.jspresso.org/maven2-snapshots/org/jspresso/framework/jspresso-hibernate/4.3-SNAPSHOT/jspresso-hibernate-4.3-20170607.042314-72.jar
Uploaded: 
dav:http://repository.jspresso.org/maven2-snapshots/org/jspresso/framework/jspresso-hibernate/4.3-SNAPSHOT/jspresso-hibernate-4.3-20170607.042314-72.jar
 (78 kB at 76 kB/s)}}

And the failing build :
{{[ERROR] Failed to execute goal on project hrsample-core: Could not resolve 
dependencies for project org.jspresso.hrsample:hrsample-core:jar:4.3-SNAPSHOT: 
Could not find artifact 
org.jspresso.framework:jspresso-hibernate:jar:4.3-20170607.042315-72 in 
jspresso-snapshots-repository (http://repository.jspresso.org/maven2-snapshots) 
-> [Help 1]}}

> 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: 
> 

[jira] [Comment Edited] (MDEPLOY-221) deploy generates wrong timestamps in maven-metadata.xml

2017-06-06 Thread Vincent Vandenschrick (JIRA)

[ 
https://issues.apache.org/jira/browse/MDEPLOY-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16040154#comment-16040154
 ] 

Vincent Vandenschrick edited comment on MDEPLOY-221 at 6/7/17 4:40 AM:
---

Hi Guillaume,
Unfortunately, it's not fixed. I've just tied the 3.0.0-SNAPSHOT and there is 
still 1 second of difference between the metadata.xml timestamp and the 
deployed file timestamp on certain artifacts. BTW, not sure it is actually 
linked to the deploy plugin since the 2.8.2 works correctly on maven < 3.5.0...

Here are the logs for the failing artifact :

deployment :
{{
Uploading: 
dav:http://repository.jspresso.org/maven2-snapshots/org/jspresso/framework/jspresso-hibernate/4.3-SNAPSHOT/jspresso-hibernate-4.3-20170607.042314-72.jar
Uploaded: 
dav:http://repository.jspresso.org/maven2-snapshots/org/jspresso/framework/jspresso-hibernate/4.3-SNAPSHOT/jspresso-hibernate-4.3-20170607.042314-72.jar
 (78 kB at 76 kB/s)
}}

And the failing build :
{{
[ERROR] Failed to execute goal on project hrsample-core: Could not resolve 
dependencies for project org.jspresso.hrsample:hrsample-core:jar:4.3-SNAPSHOT: 
Could not find artifact 
org.jspresso.framework:jspresso-hibernate:jar:4.3-20170607.042315-72 in 
jspresso-snapshots-repository (http://repository.jspresso.org/maven2-snapshots) 
-> [Help 1]
}}


was (Author: vvandens):
Hi Guillaume,
Unfortunately, it's not fixed. I've just tied the 3.0.0-SNAPSHOT and there is 
still 1 second of difference between the metadata.xml timestamp and the 
deployed file timestamp on certain artifacts. BTW, not sure it is actually 
linked to the deploy plugin since the 2.8.2 works correctly on maven < 3.5.0...

Here are the logs for the failing artifact :

deployment :
{{monospaced}}
Uploading: 
dav:http://repository.jspresso.org/maven2-snapshots/org/jspresso/framework/jspresso-hibernate/4.3-SNAPSHOT/jspresso-hibernate-4.3-20170607.042314-72.jar
Uploaded: 
dav:http://repository.jspresso.org/maven2-snapshots/org/jspresso/framework/jspresso-hibernate/4.3-SNAPSHOT/jspresso-hibernate-4.3-20170607.042314-72.jar
 (78 kB at 76 kB/s)
{{monospaced}}

And the failing build :
{{monospaced}}
[ERROR] Failed to execute goal on project hrsample-core: Could not resolve 
dependencies for project org.jspresso.hrsample:hrsample-core:jar:4.3-SNAPSHOT: 
Could not find artifact 
org.jspresso.framework:jspresso-hibernate:jar:4.3-20170607.042315-72 in 
jspresso-snapshots-repository (http://repository.jspresso.org/maven2-snapshots) 
-> [Help 1]
{{monospaced}}

> 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: 
> 

[jira] [Comment Edited] (MDEPLOY-221) deploy generates wrong timestamps in maven-metadata.xml

2017-06-06 Thread Vincent Vandenschrick (JIRA)

[ 
https://issues.apache.org/jira/browse/MDEPLOY-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16040154#comment-16040154
 ] 

Vincent Vandenschrick edited comment on MDEPLOY-221 at 6/7/17 4:41 AM:
---

Hi Guillaume,
Unfortunately, it's not fixed. I've just tied the 3.0.0-SNAPSHOT and there is 
still 1 second of difference between the metadata.xml timestamp and the 
deployed file timestamp on certain artifacts. BTW, not sure it is actually 
linked to the deploy plugin since the 2.8.2 works correctly on maven < 3.5.0...

Here are the logs for the failing artifact :

deployment :
{{Uploading: 
dav:http://repository.jspresso.org/maven2-snapshots/org/jspresso/framework/jspresso-hibernate/4.3-SNAPSHOT/jspresso-hibernate-4.3-20170607.042314-72.jar
Uploaded: 
dav:http://repository.jspresso.org/maven2-snapshots/org/jspresso/framework/jspresso-hibernate/4.3-SNAPSHOT/jspresso-hibernate-4.3-20170607.042314-72.jar
 (78 kB at 76 kB/s)}}

And the failing build :
{{[ERROR] Failed to execute goal on project hrsample-core: Could not resolve 
dependencies for project org.jspresso.hrsample:hrsample-core:jar:4.3-SNAPSHOT: 
Could not find artifact 
org.jspresso.framework:jspresso-hibernate:jar:4.3-20170607.042315-72 in 
jspresso-snapshots-repository (http://repository.jspresso.org/maven2-snapshots) 
-> [Help 1]}}


was (Author: vvandens):
Hi Guillaume,
Unfortunately, it's not fixed. I've just tied the 3.0.0-SNAPSHOT and there is 
still 1 second of difference between the metadata.xml timestamp and the 
deployed file timestamp on certain artifacts. BTW, not sure it is actually 
linked to the deploy plugin since the 2.8.2 works correctly on maven < 3.5.0...

Here are the logs for the failing artifact :

deployment :
{{
Uploading: 
dav:http://repository.jspresso.org/maven2-snapshots/org/jspresso/framework/jspresso-hibernate/4.3-SNAPSHOT/jspresso-hibernate-4.3-20170607.042314-72.jar
Uploaded: 
dav:http://repository.jspresso.org/maven2-snapshots/org/jspresso/framework/jspresso-hibernate/4.3-SNAPSHOT/jspresso-hibernate-4.3-20170607.042314-72.jar
 (78 kB at 76 kB/s)
}}

And the failing build :
{{
[ERROR] Failed to execute goal on project hrsample-core: Could not resolve 
dependencies for project org.jspresso.hrsample:hrsample-core:jar:4.3-SNAPSHOT: 
Could not find artifact 
org.jspresso.framework:jspresso-hibernate:jar:4.3-20170607.042315-72 in 
jspresso-snapshots-repository (http://repository.jspresso.org/maven2-snapshots) 
-> [Help 1]
}}

> 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: 
> 

[jira] [Comment Edited] (MDEPLOY-221) deploy generates wrong timestamps in maven-metadata.xml

2017-05-13 Thread Vincent Vandenschrick (JIRA)

[ 
https://issues.apache.org/jira/browse/MDEPLOY-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007908#comment-16007908
 ] 

Vincent Vandenschrick edited comment on MDEPLOY-221 at 5/13/17 6:24 AM:


Same here
- No Nexus
- mvn 3.5.0
- no parallel build nor obfuscation

The same deploy plugin version never had problems with Maven 3.2, so I think 
it's linked to Maven 3.5.0.


was (Author: vvandens):
Same here
- No Nexus
- mvn 3.5.0

> 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: 
>