[
https://issues.jboss.org/browse/JBIDE-15481?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-15481:
-------------------------------
Attachment: jbide15481.png
Pretty sure we don't need a new mojo for this. We can just use the existing "do
some install" then "run vwatch against two folders" approach we already
have.
Results will look like this, except won't have com.jboss.* in them:
http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc...
New job would simply be a copy of the existing vwatch job but with a different initial
step to do the install:
!jbide15481.png!
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
Attachments: jbide15481.png
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)