|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [mojo-dev] [jira] (MRPM-118) Build failure: date rol... Graham Leggett (JIRA)
- [mojo-dev] [jira] (MRPM-118) Build failure: dat... Graham Leggett (JIRA)
- [mojo-dev] [jira] (MRPM-118) Build failure: dat... Graham Leggett (JIRA)
- [mojo-dev] [jira] (MRPM-118) Build failure: dat... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MRPM-118) Build failure: dat... Graham Leggett (JIRA)
- [mojo-dev] [jira] (MRPM-118) Build failure: dat... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MRPM-118) Build failure: dat... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MRPM-118) Build failure: dat... Graham Leggett (JIRA)
- [mojo-dev] [jira] (MRPM-118) Build failure: dat... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MRPM-118) Build failure: dat... Graham Leggett (JIRA)

The cause of this problem is that the version number of the RPM is calculated a total of three times, the first time by VersionMojo placing the result in the environment, and then a subsequent two times by AbstractRPMMojo, ignoring the original version placed in the environment.
Because the version number so calculated contains a timestamp with a one second resolution, the version number changes between the first and third invocations, and the build fails as the name of the artifact has changed.
Patch to fix this to follow.