[
https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-19056:
------------------------------------
Sounds like something in vwatch already...
https://github.com/jbdevstudio/jbdevstudio-qa/tree/master/vwatch instead of defining a
single URL baseline, it uses up to N JBDS installs as baselines and can diff
plugin/feature versions, compare MD5 sums, etc.
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
See also JBIDE-19072 and linked/child issues.
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)