[
http://jira.jboss.com/jira/browse/JBIDE-322?page=comments#action_12372360 ]
R Firoz commented on JBIDE-322:
-------------------------------
I actually ran the update manager to download the plugin and install it so I had to
exclude ' org.jboss.ide.eclipse.ejb3.feature 1.0.2.GA' from the update in order to
go ahead with the plugin installation. So my question is more in line with what happens if
I exclude this component from plugin. I have ran my application and am able to debug. What
I am trying to understand is the side effects of excluding a component from the plugin.
Thanks,
RF
Unused plugin dependency in org.jboss.ide.eclipse.ejb3.wizards.ui on
org.eclipse.jdt.source
--------------------------------------------------------------------------------------------
Key: JBIDE-322
URL:
http://jira.jboss.com/jira/browse/JBIDE-322
Project: JBoss Tools
Issue Type: Bug
Components: ejb3
Affects Versions: 1.5 Final
Reporter: Francois Granade
Assigned To: Marshall Culpepper
Priority: Minor
Fix For: 2.0.0.Alpha
The plugin org.jboss.ide.eclipse.ejb3.wizards.ui declare a dependency on
org.eclipse.jdt.source. You can see that in the Manifest file:
http://fisheye.labs.jboss.com/viewrep/JBoss/jbosside/ejb3/plugins/org.jbo...
Unless I'm mistaken, this dependency is not needed (why would the wizard have a
dependency on JDT source code ???)
It's innocuous, but this causes an error to appear in Eclipse error log.
Also, for us at
http://www.easyeclipse.org, it means that we have to patch the manifest
when we build it. It's small, but useless
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira