[MNG-6694] generated maven-metadata.xml gives wrong snapshot version

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Bug
• Affects Version/s: 3.6.0
• Assignee: Michael Osipov
• Reporter: Rik Schaaf
• Created: 28/Jun/19 13:45
• Updated: 11/Oct/20 18:24
• Resolved: 11/Oct/20 18:22

Description

I build and deploy my maven project today, but when trying to use that deployed version (deployed to nexus 2.14.11-01) the artifact could not be found:

Could not find artifact foo.bar.foo-bar-starter-parent:pom:2.0.0-20190628.113521-15 in snapshots (http://nexus.somesite.nl:8080/nexus/content/repositories/snapshots) and 'parent.relativePath' points at no local POM @ ...

When I looked in nexus, the artifact was actually deployed as: foo-bar-starter-parent-2.0.0-20190628.113520-15.pom.

As you can see, it got deployed under the wrong snapshot number, because the wrong seconds were used.

Here is the maven-metadata for foo-bar-starter-parent

<metadata modelVersion="1.1.0">
	<script id="__gaOptOutExtension"/>
	<groupId>foo.bar</groupId>
	<artifactId>foo-bar-starter-parent</artifactId>
	<version>2.0.0-SNAPSHOT</version>
	<versioning>
		<snapshot>
			<timestamp>20190628.113521</timestamp>
			<buildNumber>15</buildNumber>
		</snapshot>
		<lastUpdated>20190628113521</lastUpdated>
		<snapshotVersions>
			<snapshotVersion>
				<extension>pom</extension>
				<value>2.0.0-20190628.113521-15</value>
				<updated>20190628113521</updated>
			</snapshotVersion>
			<snapshotVersion>
				<classifier>wrapper-assembly-descriptor</classifier>
				<extension>jar</extension>
				<value>2.0.0-20190628.113520-15</value>
				<updated>20190628113521</updated>
			</snapshotVersion>
		</snapshotVersions>
	</versioning>
</metadata>

This metadata file shows that a mix of the right and wrong snapshot numbers is created.

Issue Links

• is related to: MNG-6274 Snapshot timestamps of modules in multimodule build are not aligned
• is superceded by: MNG-6754 Set the same timestamp in multi module builds