[
https://issues.jboss.org/browse/JBIDE-9324?page=com.atlassian.jira.plugin...
]
Rob Stryker resolved JBIDE-9324.
--------------------------------
Resolution: Done
Resolving issue for now. If further cleanup is needed on a code level, just target changes
to here.
The class /WebtoolsProjectJBossClasspathContainerInitializer was removed. Other API's
suitable for the purpose already existed such as the ejb3 classpath container.
A proper smoke test to verify nothing has broken would be:
1) create a dynamic web project targeted to a server
2) verify that the java classpath container was added to CP
3) verify that the jboss jars are also added to the CP
4) Create a plain java project
5) Right-click it, go to properties, build path, add library, JBoss EJB3 libraries
6) verify the UI functions as required, and the proper jars are added.
I've tested this already and it works for me, but you never know what can go wrong on
other OS's ;)
Clean up org.jboss.ide.eclipse.as.classpath.core.runtime package
-----------------------------------------------------------------
Key: JBIDE-9324
URL:
https://issues.jboss.org/browse/JBIDE-9324
Project: Tools (JBoss Tools)
Issue Type: Task
Components: JBossAS
Affects Versions: 3.3.0.M2
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.3.0.M3
Workflow is hard to understand, too much delegation, and a class with limited purpose
which can be removed
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira