[
https://issues.jboss.org/browse/JBIDE-15609?page=com.atlassian.jira.plugi...
]
Jiri Peterka commented on JBIDE-15609:
--------------------------------------
Probably false alarm, seems that current comparison method is not reliable since packing
the same content can give slightly different output. As I found this can be caused by data
ordering during packing which is not assured so it can give slightly different results
(and so md5 as well). So packing and comparing md5 is not reliable enough. Better approach
would be to compare unpacked files rather tan pack and compare archives. It try to
implement it soon. So (vwatch.md5check) should not be taken into consideration now since
it only works for some cases.
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.Beta2
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)