maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mostafa shahdadi <mostafa.shahd...@icloud.com.INVALID>
Subject Re: [jira] [Commented] (MNG-6694) generated maven-metadata.xml gives wrong snapshot version
Date Sun, 14 Jul 2019 11:31:40 GMT


Sent from my iPad

> On Jul 14, 2019, at 15:57, Michael Osipov (JIRA) <jira@apache.org> wrote:
> 
> 
>    [ https://issues.apache.org/jira/browse/MNG-6694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16884108#comment-16884108
] 
> 
> Michael Osipov commented on MNG-6694:
> -------------------------------------
> 
> 3.0.0-M1 *is* a release version. 
> 
>> generated maven-metadata.xml gives wrong snapshot version
>> ---------------------------------------------------------
>> 
>>                Key: MNG-6694
>>                URL: https://issues.apache.org/jira/browse/MNG-6694
>>            Project: Maven
>>         Issue Type: Bug
>>   Affects Versions: 3.6.0
>>           Reporter: Rik Schaaf
>>           Priority: Major
>> 
>> 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:
>> {code}
>> 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 @ ...
>> {code}
>> 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
>> {code:xml}
>> <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>
>> {code}
>> This metadata file shows that a mix of the right and wrong snapshot numbers is created.
> 
> 
> 
> --
> This message was sent by Atlassian JIRA
> (v7.6.14#76016)


Mime
View raw message