1:29 p.m.
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
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
1:19 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7698) JBT 3.2.0 Beta2 contains invalid org.jdom plugin
[
https://jira.jboss.org/browse/JBIDE-7698?page=com.atlassian.jira.plugin.s...
]
Max Andersen commented on JBIDE-7698:
-------------------------------------
what is dragging in that org.jdom plugin ?
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
1:19 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7698) JBT 3.2.0 Beta2 contains invalid org.jdom plugin
[
https://jira.jboss.org/browse/JBIDE-7698?page=com.atlassian.jira.plugin.s...
]
Max Andersen updated JBIDE-7698:
--------------------------------
Fix Version/s: 3.2.0.Beta2
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
1:21 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7698) JBT 3.2.0 Beta2 contains invalid org.jdom plugin
[
https://jira.jboss.org/browse/JBIDE-7698?page=com.atlassian.jira.plugin.s...
]
Max Andersen updated JBIDE-7698:
--------------------------------
Description:
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.
was:
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.
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
3:46 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7698) JBT 3.2.0 Beta2 contains invalid org.jdom plugin
[
https://jira.jboss.org/browse/JBIDE-7698?page=com.atlassian.jira.plugin.s...
]
Snjezana Peco commented on JBIDE-7698:
--------------------------------------
It contains unpacked Orbit's org.jdom plugin. Since Orbit's plugin is signed,
unpacking it creates an invalid plugin.
The plugin needs to be removed because WTP contains the correct plugin.
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
3:14 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7698) JBT 3.2.0 Beta2 contains invalid org.jdom plugin
[
https://jira.jboss.org/browse/JBIDE-7698?page=com.atlassian.jira.plugin.s...
]
Snjezana Peco commented on JBIDE-7698:
--------------------------------------
In my previous message, I have mentioned that the problem isn't in JBDS, but in JBoss
Tools build.
I have created JBoss Tools locally. It doesn't contain the org.jdom plugin.
The invalid org.jdom plugin is placed in Teiid Designer 7.1 (the
teiid_designer_7.1_v20100830.zip archive).
Not sure who to assign this issue to. So I am assigning it back to you :) .
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: Snjezana Peco
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
3:57 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7698) JBT 3.2.0 Beta2 contains invalid org.jdom plugin
[
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
9:11 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7698) JBT 3.2.0 Beta2 contains invalid org.jdom plugin
[
https://jira.jboss.org/browse/JBIDE-7698?page=com.atlassian.jira.plugin.s...
]
Max Andersen updated JBIDE-7698:
--------------------------------
Assignee: Barry LaFond (was: Nick Boldt)
Priority: Blocker (was: Major)
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
9:11 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7698) JBT 3.2.0 Beta2 contains invalid org.jdom plugin
[
https://jira.jboss.org/browse/JBIDE-7698?page=com.atlassian.jira.plugin.s...
]
Nick Boldt commented on JBIDE-7698:
-----------------------------------
Our target platform currently contains these on which you can depend. If you need
something newer, let me know:
./features/org.jdom.feature_1.0.0.v201005080400.jar
./plugins/org.jdom_1.0.0.v201005080400.jar
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
5:05 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7698) JBT 3.2.0 Beta2 contains invalid org.jdom plugin
[
https://jira.jboss.org/browse/JBIDE-7698?page=com.atlassian.jira.plugin.s...
]
Nick Boldt commented on JBIDE-7698:
-----------------------------------
I believe
http://hudson.qa.jboss.com/hudson/job/devstudio-4.0_stable_branch.uberbui...
will contain this fix.
http://reports.qa.atl.jboss.com/binaries/RHDS/builds/nightly/4.0.0.Beta2/ (look for H23
build or later)
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
5:11 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7698) JBT 3.2.0 Beta2 contains invalid org.jdom plugin
[
https://jira.jboss.org/browse/JBIDE-7698?page=com.atlassian.jira.plugin.s...
]
Barry LaFond commented on JBIDE-7698:
-------------------------------------
I changed the 2 offending feature.xml's to "require" org.jdom instead of
including it.
Installed a Designer-Only update zip into Eclipse and Designer worked ok.
Need to re-test/install as above to verify?
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
12:43 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-7698) JBT 3.2.0 Beta2 contains invalid org.jdom plugin
[
https://jira.jboss.org/browse/JBIDE-7698?page=com.atlassian.jira.plugin.s...
]
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
11:30 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-7698) JBT 3.2.0 Beta2 contains invalid org.jdom plugin
[
https://jira.jboss.org/browse/JBIDE-7698?page=com.atlassian.jira.plugin.s...
]
Jiri Peterka closed JBIDE-7698.
-------------------------------
Seems ok, verified in JBDS 4.0.0.beta2 h33, Fedora 14-64b
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: Jiri Peterka
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
5052
days inactive
5068
days old
jbosstools-issues@lists.jboss.org
12 comments
5 participants
participants (5)
-
Barry LaFond (JIRA) -
Jiri Peterka (JIRA)
-
Max Andersen (JIRA)
-
Nick Boldt (JIRA)
-
Snjezana Peco (JIRA)