[jbosstools-issues] [JBoss JIRA] (JBIDE-19056) A Mojo to validate a version (compared to baseline)
[
https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen edited comment on JBIDE-19056 at 1/29/15 12:01 PM:
-----------------------------------------------------------------------
Just replicated it on openshift too.
{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.openshift.egit.core: Version have moved backwards for
(org.jboss.tools.openshift.egit.core/2.6.1.Alpha1-v20150129-1651). Baseline has
2.6.100.Alpha1-v20150129-1643) with delta: 0.0.-99 -> [Help 1]{code}
It definitely is looking on *local* filesystem and not *only* in the baseline.
-1 for pushing this in until fixed.
Steps to reproduce:
1) git co master
2) mvn clean verify -DskipTests
3) git co jbosstools-4.2.x
4) updated /pom.xml to use 4.3.0.Alpha1-SNAPSHOT parent
5) mvn clean verify -DskipTests
was (Author: maxandersen):
Just replicated it on openshift too.
{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.openshift.egit.core: Version have moved backwards for
(org.jboss.tools.openshift.egit.core/2.6.1.Alpha1-v20150129-1651). Baseline has
2.6.100.Alpha1-v20150129-1643) with delta: 0.0.-99 -> [Help 1]{code}
It definitely is looking on *local* filesystem and not *only* in the baseline.
-1 for pushing this in until fixed.
A Mojo to validate a version (compared to baseline)
---------------------------------------------------
Key: JBIDE-19056
URL: https://issues.jboss.org/browse/JBIDE-19056
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: build
Affects Versions: 4.2.2.Final
Reporter: Mickael Istria
Assignee: Mickael Istria
Attachments: build.out
We need a mojo that compares a newly-built artifact with other versions of this IU that
we have already released.
Such a mojo would fail is version isn't correct (lower than same one on that stream,
equal to another one already released but with different content...)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)