[
https://jira.codehaus.org/browse/MDEPLOY-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276649#comment-276649
]
Stephen Connolly commented on MDEPLOY-97:
-----------------------------------------
Be interesting to know if the user changed maven version between sc-69-SNAPSHOT
and sc-70-SNAPSHOT.
OTOH this issue has not been updated in over 2 years, so is this still a bug?
> the <buildNumber> always be 1 on maven-metadata.xml
> ---------------------------------------------------
>
> Key: MDEPLOY-97
> URL: https://jira.codehaus.org/browse/MDEPLOY-97
> Project: Maven 2.x Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy
> Affects Versions: 2.4
> Environment: unix, jdk 1.5
> Reporter: Michael Meng
> Labels: scrub-review-started
> Attachments: buildnumber.JPG, clear.doc, goodone.JPG
>
>
> We have setup a project build on cruise control, whose version is SNAPSHOT
> (in my case is 70-SNAPSHOT), however, the build result files look fine, but
> the build number always be 1, what is the problem ?
> You may compare the 2 pic, you will see the difference. the right pic is what
> we expect. it has the build number 54,55, 56, 57,,,,
> while the left pic's build number always be 1
> in the maven-metadata.xml the buildNumber always 1, no matter how many times
> you build it.
> <buildNumber>1</buildNumber>
> <metadata>
> <groupId>ubhsc</groupId>
> <artifactId>sc</artifactId>
> <version>70-SNAPSHOT</version>
> - <versioning>
> - <snapshot>
> <timestamp>20090320.170754</timestamp>
> <buildNumber>1</buildNumber>
> </snapshot>
> <lastUpdated>20090320170754</lastUpdated>
> </versioning>
> </metadata>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
