[
https://jira.jboss.org/browse/JBIDE-7698?page=com.atlassian.jira.plugin.s...
]
Snjezana Peco commented on JBIDE-7698:
--------------------------------------
In the meantime I have found what the problem is.
Namely, org.teiid.designer.feature and org.teiid.designer.runtime.feature include
org.jdom. They should require this plugin instead of including it.
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: Nick Boldt
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