[
https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-19056:
------------------------------------
Tested w/ older Forge in master:
{code}
cd jbosstools-forge; mvn clean install
[INFO] org.jboss.tools.aesh.runtime ...................... FAILURE [16.725s]
[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.aesh.runtime: Version of
'org.jboss.tools.aesh.runtime/1.3.53.Alpha1-v20150128-1904) must be bigger than
baseline one (1.3.53.Final-v20150113-1315-B85) -> [Help 1]
{code}
Then run again after updating to latest in master:
{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.aesh.runtime: Unless artifacts are identical, version
of 'org.jboss.tools.aesh.runtime' must have bigger x.y.z than what's available
in baseline (2.0.0.Alpha1-v20150128-1908) -> [Help 1]
{code}
So.. Forge is still broken, despite JBIDE-19077 being now resolved, with these changes:
https://github.com/jbosstools/jbosstools-forge/commit/d671d50805e18348658...
Is that a problem w/ the mojo or with Forge?
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
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)