#2 versioning issues

1.0
open
Jorge Simões
build fails (2)
2014-07-25
2014-06-27
munterberger
No

Maven builds fail, because of different reference versions between parent project and sub-modules

e.g. in extraction-manager POM (https://opensourceprojects.eu/p/timbus/context-population/extraction-manager) the extractors-core dependency is referenced by version 0.0.2-RELEASE

<dependency>
    <groupId>net.timbusproject.extractors</groupId>
    <artifactId>extractors-core</artifactId>
    <version>0.0.2-RELEASE</version>
    <scope>provided</scope>
</dependency>

but in extractors-core POM itself (https://opensourceprojects.eu/p/timbus/context-population/extractors-core) it is defined as version 0.0.3-RELEASE

<groupId>net.timbusproject.extractors</groupId>
<artifactId>extractors-core</artifactId>
<version>0.0.3-RELEASE</version>
<packaging>bundle</packaging>
<name>Context Population Framework</name>
    <url>http://www.timbusproject.net/</url>

Discussion

  • Jorge Simões
    Jorge Simões
    2014-07-25

    You have to roll back to commit hash 642d901 to get 0.0.2-RELEASE:

    git checkout 642d901 && mvn clean install

     
    Link

  • Rudolf Mayer
    Rudolf Mayer
    2014-07-25

    I would consider that a workaround, and not a proper long-term solution.

    I would expect that if you check out the projects at any time in point, there shouldn't be any additional work to be done to just make them compile properly.

    So, either 0.0.2-RELEASE (and any other future version other modules depend on) should be available via a maven repository, or the dependencies of all the submodules should always be synchronised to the versions currently available.

     
    Link