[jbosstools-issues] [JBoss JIRA] (JBIDE-15609) versionwatch should ignore when there's a folder & jar which are identical

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-15609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968664#comment-12968664 ] 

Nick Boldt commented on JBIDE-15609:
------------------------------------

It's not valid. This situation only occurs when we take an old plugin which is is configured to be installed as a folder, and attempt to compare it to a plugin installed as a jar. Because you can't diff a folder w/ a file, I zip the folder plugin so it can be compared to newer versions of the same plugin as a jar.

But the result is that for some older plugins, you have org.foo_x.y.z/ and org.foo_x.yz..jar. I suppose we could DELETE the folder once it's been jarred, which would also avoid this situation.

> 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)