[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-7698) JBT 3.2.0 Beta2 contains invalid org.jdom plugin

[Barry LaFond (JIRA)]

     [ https://jira.jboss.org/browse/JBIDE-7698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Barry LaFond resolved JBIDE-7698.
---------------------------------

    Resolution: Done


Fixed within jbdevstudio-win32-4.0.0.v201012030520R-H26-Beta2

Snjeza

> JBT 3.2.0 Beta2 contains invalid org.jdom plugin
> ------------------------------------------------
>
>                 Key: JBIDE-7698
>                 URL: https://jira.jboss.org/browse/JBIDE-7698
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng
>    Affects Versions: 3.2.0.Beta2
>            Reporter: Snjezana Peco
>            Assignee: Barry LaFond
>            Priority: Blocker
>             Fix For: 3.2.0.Beta2
>
>
> JBT 3.2.0 Beta2 (v20101121-0147-H262-Beta2, for instance) contains the org.jdom plugin that is invalid.
> The plugin is unpacked and contains invalid signed information in the MANIFEST.MF file. Eclipse won't load any classes from the plugin.
> The problem can't always be reproduced because WTP also contains this plugin (valid) and in the case P2 chooses the plugin from WTP, the problem won't happen.
> Steps to reproduce:
> - install WTP to the dropins/wtp folder and JBT to the dropins/jbt folder 
> - start Eclipse with the -clean option (P2 will select org.jdom from the JBT distribution)
> You can also change bundles.info.
> - checkout the o.j.t.ws.ui plugin
> the o.j.t.ws.ui plugin will contain compile errors (DOMBuilder cannot be resolved to a type).
> JBDS 4.0.0 Beta2 includes a valid the org.jdom plugin.
> Solution: removing the org.jdom from JBT or creating a valid the org.jdom plugin.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira