[
https://issues.jboss.org/browse/JBIDE-15481?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-15481:
----------------------------------------
I'm currently thinking about writing a simple Maven Mojo that would take as input some
baselines (last releases of JBT or JBDS), and that will as part of the 'verify'
step, compare the versions of newly built repo with baseline one, with the following rules
:
* version in new repo must be >= to latest version found in baseline
* if x.y.z is the same as the bundle in baseline, then qualifier must be the same (case
when we re-use a module we didn't need to rebuild)
* if x.y.z.qualifier are equals, then bundles must be exactly the same (check file
signature)
I believe this would rather be part of the aggregation build.
setup of vwatch for jboss tools installations
---------------------------------------------
Key: JBIDE-15481
URL:
https://issues.jboss.org/browse/JBIDE-15481
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: build
Reporter: Max Rydahl Andersen
Fix For: 4.2.x
use the install robot and then run versionwatch aginst JBoss Tools install with all of
central content installed.
usecases:
* find missing/weird versions
* duplicate components
* get list of potential unnecessary plugins in TP
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)