[ https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19056: ---------------------------------------- I gave a first shot to such mojo, which is accessible in https://github.com/mickaelistria/jbosstools-maven-plugins/tree/JBIDE-19056 Then it can be set on any module producing p2 installable unit to compare versions with baseline. {code:xml} <plugin> <groupId>org.jboss.tools.tycho-plugins</groupId> <artifactId>repository-utils</artifactId> <version>0.22.1-SNAPSHOT</version> <executions> <execution> <goals> <goal>compare-version-with-baselines</goal> </goals> <phase>verify</phase> <configuration> <baselines> <repo>http://download.jboss.org/jbosstools/updates/stable/luna</repo... </baselines> </configuration> </execution> </executions> </plugin> {code} For example, when this is set and we're trying to build org.jboss.tools.usage bundle from master, build fails with {code} [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:compare-version-with-baselines (default) on project org.jboss.tools.usage: Version of 'org.jboss.tools.usage/2.0.0.Alpha1-v20150123-1146) must be bigger than baseline one (2.0.1.Final-v20141209-0333-B84) -> [Help 1] {code} I believe this should definitely make us less error-prone with version management. CC [~nickboldt] [~jpeterka] [~mmalina] [~maxandersen] [~fbricon] -- This message was sent by Atlassian JIRA (v6.3.11#6341)