facebook

Validation preferences not persisting upon eclipse shutdown.

  1. MyEclipse IDE
  2.  > 
  3. General Development
Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #213163 Reply

    meagle
    Member

    I just upgraded to MyEclipse 3.8.1. First I unistalled my old beta version of MyEclipse, then installed 3.8.1. I immediately went to the MyEclipse validation preferences (Window -> Preferences -> MyEclipse -> Validation) and “Deselect All”. I clicked “Apply”, and then “OK”. I shut down eclipse, get a stacktrace in the .log, and when I restart eclipse, my validation preferences have not been persisted and they have reverted back to their default values. The stacktrace I referred to is as follows:

    !MESSAGE The class "com.ibm.wtp.common.ui.UITesterImpl" cannot be loaded because the system is shutting down and the plug-in "com.ibm.wtp.common.ui" has already been stopped.
    !STACK 0
    java.lang.ClassNotFoundException: The class "com.ibm.wtp.common.ui.UITesterImpl" cannot be loaded because the system is shutting down and the plug-in "com.ibm.wtp.common.ui" has already been stopped.
        at org.eclipse.core.runtime.adaptor.EclipseClassLoader.shouldActivateFor(EclipseClassLoader.java:147)
        at org.eclipse.core.runtime.adaptor.EclipseClassLoader.findLocalClass(EclipseClassLoader.java:62)
        at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:371)
        at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:402)
        at org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.loadClass(AbstractClassLoader.java:93)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(BundleLoader.java:307)
        at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:336)
        at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1313)
        at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:131)
        at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:124)
        at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:113)
        at com.ibm.wtp.common.UIContextDetermination$UITesterRegistryReader.readElement(UIContextDetermination.java:153)
        at com.ibm.wtp.common.RegistryReader.internalReadElement(RegistryReader.java:61)
        at com.ibm.wtp.common.RegistryReader.readRegistry(RegistryReader.java:99)
        at com.ibm.wtp.common.UIContextDetermination.getCurrentContext(UIContextDetermination.java:69)
        at com.ibm.etools.validate.internal.EventManager.isHeadless(Unknown Source)
        at com.ibm.etools.validate.internal.EventManager.shutdown(Unknown Source)
        at com.ibm.etools.validate.plugin.ValidationPlugin.shutdown(Unknown Source)
        at org.eclipse.core.internal.compatibility.PluginActivator.stop(PluginActivator.java:74)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:994)
        at java.security.AccessController.doPrivileged(Native Method)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:990)
        at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:502)
        at org.eclipse.osgi.framework.internal.core.AbstractBundle.stop(AbstractBundle.java:437)
        at org.eclipse.core.runtime.adaptor.BundleStopper.basicStopBundles(BundleStopper.java:75)
        at org.eclipse.core.runtime.adaptor.BundleStopper.stopBundles(BundleStopper.java:62)
        at org.eclipse.core.runtime.adaptor.EclipseAdaptor.frameworkStopping(EclipseAdaptor.java:551)
        at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:457)
        at org.eclipse.osgi.framework.internal.core.SystemBundle$1.run(SystemBundle.java:182)
        at java.lang.Thread.run(Unknown Source)

    I have made other preference changes such as adding line numbers to the editors, and the changes persist. It seems to be fairly issolated to validation preferences. Immediate assistance would be appreciated because I cannot use MyEclipse with validation enabled due to the know bug about jsp validation and out of memory errors.

    Thanks You,
    Chad Westfall

    #213180 Reply

    Scott Anderson
    Participant

    Chad,

    We’ve got a problem report on the JSP validation setting not being persisted globally and we plan to resolve it shortly. The current workaround is to override the global setting at the project level by going to the Package Explorer, right clicking and selecting Properties > MyEclipse-Validation. From that page you can choose to override the global settings and turn of whichever validators you like there. These are persisted properly and are not affected by this bug. Also, please note that even with JSP validation turned off, you can still choose to validate a file or two by right-clicking on the JSP file in the Package Explorer and selecting Validate JSP File. Sorry for the inconvenience while we work on this issue.

Viewing 2 posts - 1 through 2 (of 2 total)
Reply To: Validation preferences not persisting upon eclipse shutdown.

You must be logged in to post in the forum log in