[
https://issues.jboss.org/browse/JBIDE-15609?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-15609:
------------------------------------
Is there a commandline flag for that? Can you update the jobs to disable that check?
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
(Both jobs are blue, it's just that the report contents could be optimized.)
Currently, the only red boxes for JBDS 8.0.0.Beta2 are for freemarker, which we're not
currently building anyway.
http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc...
Oh, and looking at the above jobs, I realized that changes in JBIDE-16871 mean the latest
installers aren't being tested. Here's a PR to fix that:
https://github.com/jbdevstudio/jbdevstudio-qa/pull/13
versionwatch should ignore when there's a folder & jar which
are identical
--------------------------------------------------------------------------
Key: JBIDE-15609
URL:
https://issues.jboss.org/browse/JBIDE-15609
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, qa
Affects Versions: 4.1.1.Alpha2
Reporter: Nick Boldt
Assignee: Jiri Peterka
Fix For: 4.2.0.Beta3
A while ago I added a facility to jar up feature and plugin folders so they could have
their md5 sums compared.
Now, the vwatch tool complains when there's a folder and a jar present.
Two possible solutions to this come to mind:
a) ignore this - do not report as *{color:red}a problem{color}*
b) whenever a folder is jarred up, delete the source folder, so the above condition
cannot occur
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)