Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 358025 - WindowsBuilder Installation errors
Summary: WindowsBuilder Installation errors
Status: CLOSED DUPLICATE of bug 228247
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: WindowBuilder (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-18 10:36 EDT by Jonathan Camilleri CLA
Modified: 2021-06-04 16:45 EDT (History)
3 users (show)

See Also:

Attachments
Log file (349.30 KB, application/octet-stream)
2011-09-18 10:37 EDT, Jonathan Camilleri CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan Camilleri CLA 2011-09-18 10:36:50 EDT 
Build Identifier: M20110210-1200

The attached errors were noted after installing WindowsBuilder.  
!ENTRY org.eclipse.equinox.registry 4 0 2011-09-18 15:59:55.906
!MESSAGE Error notifying registry change listener.
!SUBENTRY 1 org.eclipse.equinox.registry 4 0 2011-09-18 15:59:55.906
!MESSAGE Error notifying registry change listener.
!STACK 0
org.eclipse.core.runtime.InvalidRegistryObjectException: Invalid registry object
	at org.eclipse.core.internal.registry.TemporaryObjectManager.getObject(TemporaryObjectManager.java:98)
	at org.eclipse.core.internal.registry.BaseExtensionPointHandle.getExtensionPoint(BaseExtensionPointHandle.java:106)
	at org.eclipse.core.internal.registry.BaseExtensionPointHandle.getContributor(BaseExtensionPointHandle.java:45)
	at org.eclipse.core.internal.registry.BaseExtensionPointHandle.getNamespace(BaseExtensionPointHandle.java:37)
	at org.eclipse.ui.internal.PopupMenuExtender.registryChanged(PopupMenuExtender.java:520)
	at org.eclipse.core.internal.registry.ExtensionRegistry$2.run(ExtensionRegistry.java:921)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.core.internal.registry.ExtensionRegistry.processChangeEvent(ExtensionRegistry.java:919)
	at org.eclipse.core.runtime.spi.RegistryStrategy.processChangeEvent(RegistryStrategy.java:260)
	at org.eclipse.core.internal.registry.osgi.ExtensionEventDispatcherJob.run(ExtensionEventDispatcherJob.java:50)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

file:///C:/Documents%20and%20Settings/Jon/workspace/.metadata/.plugins/org.eclipse.ui.workbench/log

I did not restart when prompted to install Windows Builder, since there was an option to 'Apply Changes' accepting the risk that there might be errors.  

If there are errors that inhibit functionality they should be removed from the options available, in my opinion.
Windows Builder information at http://www.eclipse.org/windowbuilder/support.php.

Reproducible: Didn't try
Comment 1 Jonathan Camilleri CLA 2011-09-18 10:37:55 EDT 
Created attachment 203551 [details]
Log file
Comment 2 Curtis Windatt CLA 2011-09-19 09:37:02 EDT 
Moving to WindowBuilder as this does not demonstrate a bug in PDE. I suspect that this is caused by using the apply changes option.  The extension point framework does not handle changes at runtime and needs to restart.  However, the install is handled by p2 which has no way of knowing whether the units it installed require a restart or not.  Note that some plug-ins may function fine without restart depending on what extension points they use.
Comment 3 Eric Clayberg CLA 2011-09-20 10:45:40 EDT 
This is a well known Eclipse issue that has nothing to do with WindowBuilder.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=228247

Bottom line: never use "Apply Changes". Always restart after installing anything significant.

*** This bug has been marked as a duplicate of bug 228247 ***