[
http://jira.codehaus.org/browse/MRM-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=216547#action_216547
]
Maria Odea Ching commented on MRM-1353:
---------------------------------------
After doing some investigation and writing a test case for this, the problem is
that the metadata being read in the upload action is the project-level metadata
and not the artifact level metadata. So everytime a snapshot artifact is
uploaded, when the metadata is updated, it is always getting a null
snapshotVersion object (because this does not exist in the project-level
metadata) thereby the build number is always set to 1.
> Build number is always 1 for SNAPSHOT artifacts uploaded via web upload form
> ----------------------------------------------------------------------------
>
> Key: MRM-1353
> URL: http://jira.codehaus.org/browse/MRM-1353
> Project: Archiva
> Issue Type: Bug
> Components: Web Interface
> Affects Versions: 1.3
> Reporter: Maria Odea Ching
> Assignee: Maria Odea Ching
> Fix For: 1.3.1
>
> Attachments: MRM-1353-in-trunk.png
>
>
> The metadata always shows <buildNumber>1</buildNumber> even if the value of
> <lastUpdated> is correct.
> Directory list for test SNAPSHOT artifact uploaded twice shows:
> archiva-consumers-1.3.1-20100303.101055-1.jar
> archiva-consumers-1.3.1-20100303.101055-1.pom
> archiva-consumers-1.3.1-20100303.101055-1.pom.md5
> archiva-consumers-1.3.1-20100303.101055-1.pom.sha1
> archiva-consumers-1.3.1-20100303.101108-1.jar
> archiva-consumers-1.3.1-20100303.101108-1.pom
> archiva-consumers-1.3.1-20100303.101108-1.pom.md5
> archiva-consumers-1.3.1-20100303.101108-1.pom.sha1
> maven-metadata.xml
> maven-metadata.xml.md5
> maven-metadata.xml.sha1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
