[ https://jira.jboss.org/jira/browse/JBIDE-4258?page=com.atlassian.jira.plu... ] Florian Beckmann updated JBIDE-4258: ------------------------------------ Summary: No Visual Editor - XULRunner feature disabled when re-adding extension point (was: No Visual Editor - XULRunner feature disabled) Workaround Description: Unpack eclipse archive and start over with a fresh install, which is annoying when using extension points to manage ( alot of) plugins. Environment: eclipse.buildId=M20090211-1700 java.version=1.6.0_11 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=de_DE Command-line arguments: -os linux -ws gtk -arch x86 -clean -data /home/u1/workspace was:Debian Linux, Kernel 2.6.26, Eclipse Ganymede SR2 Affects Version/s: 3.0.0.GA Description: I installed JBoss-Tools (tried it with 3.0.0.GA and nightly, 3.1.0 Alpha) into an extension point using the old update manager. With a fresh eclipse install everything works fine. But moving the extension-point folder away and re-add it later leaves the XULRunner-feature with status Disabled: The feature is not configured properly. No plug-in: "org.mozilla.xpcom" included at runtime (even though it's there!) In the error log I got the messages: ClassLoaderUtil:activate: Cannot find required plugin org.jboss.tools.jsf.ui ClassLoaderUtil:activate: Cannot find required plugin org.jboss.tools.jst.web.ui To be sure it's not related to other plugins I removed all other extension points leaving just jbosstools. I think it is maybe related to https://jira.jboss.org/jira/browse/JBIDE-3543 (different OS though). was: I installed JBoss-Tools Nightly (3.1.0 Alpha) into an extension point using the old update manager. With a fresh install everything works fine. But moving the extension-point folder away and re-add it later leaves the XULRunner-feature with Status Disabled: No plug-in: "org.mozilla.xpcom" included at runtime - even though it's there! Complexity: Low Workaround: [Workaround Exists] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-4258?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-4258: --------------------------------------- Component/s: UpStream -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-4258?page=com.atlassian.jira.plu... ] Max Rydahl Andersen resolved JBIDE-4258. ---------------------------------------- Fix Version/s: 3.1.0.M1 Resolution: Done Fixed upstream, so as long as you use Eclipse 3.5M7 it works. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira