[
https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-19056:
-------------------------------------
Please verify this bug in two steps:
1) Verify that the correct baseline is being compared against (ie, not ~/.m2 folder)
2) Please verify again that if two identical things are being compared, the error does not
show.
I don't know how you currently check for identical units, but even assuming bug 1
shouldn't be there, the build is currently comparing an ~/.m2 cached unit with an
IDENTICAL new build and showing an error. This leads me to believe the comparison is not
accurate and there's a second bug there.
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)