#13 Wrong version check in release packaging

2.0.0
closed-fixed
nobody
None
5
2011-03-24
2011-03-24
No

When packaging releases problems might occur, due to a incorrect comparison of artifact SNAPSHOT versions, where the full timestamp of the snapshot artifact is being compared to only the base version of the dependency added in the POM.

For example:

"1.0.0-20110322.163103-112 != 1.0.0-SNAPSHOT"

Both version strings here come from the same SNAPSHOT version of the dependency, but the internal format in Maven provides the version either throught "getVersion()" or "getBaseVersion()".

This may cause an error when packaging releases and can be recognized by the following error output in the console:


[INFO] ------------------------------------------------------------------------
[INFO] T E S T - R U N N E R
[INFO] ------------------------------------------------------------------------
[ERROR] Version mismatch for xxx_lib: [xxx_lib:erlang-otp:1.0.0-SNAPSHOT:compile, xxx_core:erlang-otp:1.0.0-SNAPSHOT:compile, xxx_driver:erlang-otp:1.0.0-SNAPSHOT:compile] != {xxx_core=1.0.0-SNAPSHOT, tv=2.1.4.6, stdlib=1.17.1, mnesia=4.4.15, xxx_lib=1.0.0-SNAPSHOT, gs=1.5.13, sasl=2.1.9.2, kernel=2.14.1, xxx_driver=1.0.0-SNAPSHOT}
...
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Checking dependencies failed, see previous output for detailed description.
[INFO] ------------------------------------------------------------------------

Discussion

  • Olle Törnström

    Resolved in the development trunk 2.1.0-SNAPSHOT.

     
  • Olle Törnström

    • status: open --> open-fixed
     
  • Olle Törnström

    • status: open-fixed --> closed-fixed
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks