Bug 494358 - Update can create broken combination of OTDT with original jdt.core
Summary: Update can create broken combination of OTDT with original jdt.core
Status: RESOLVED WORKSFORME
Alias: None
Product: Objectteams
Classification: Tools
Component: Releng (show other bugs)
Version: 2.4   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 2.5 RC   Edit
Assignee: Stephan Herrmann CLA
QA Contact:
URL:
Whiteboard: what installation steps lead to the c...
Keywords: needinfo
: 468105 473196 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-05-23 18:37 EDT by EPP Error Reports CLA
Modified: 2016-05-31 06:38 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description EPP Error Reports CLA 2016-05-23 18:37:48 EDT
The following problem was reported via the automated error reporting:

Message: The proxied delegate for 'org.eclipse.objectteams.otdt.internal.ui.callinmarkers.UpdateRulerAction' could not be loaded
java.lang.ClassNotFoundException: org.eclipse.objectteams.otdt.core.IOTJavaElement cannot be found by org.eclipse.objectteams.otdt.ui_2.2.0.201305210612
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:439)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344)
    at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
    at java.lang.ClassLoader.loadClass(null:-1)
    at org.eclipse.objectteams.otdt.ui.OTDTUIPlugin.registerAdapter(OTDTUIPlugin.java:165)
    at org.eclipse.objectteams.otdt.ui.OTDTUIPlugin.start(OTDTUIPlugin.java:122)
    at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:771)
    at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
    at java.security.AccessController.doPrivileged(null:-2)
    at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:764)
    at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:721)
    at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:941)
    at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:318)
    at org.eclipse.osgi.container.Module.doStart(Module.java:571)
    at org.eclipse.osgi.container.Module.start(Module.java:439)
    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:454)
    at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
    at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:531)
    at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:324)
    at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:327)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:402)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344)
    at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
    at java.lang.ClassLoader.loadClass(null:-1)
    at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:573)
    at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174)
    at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
    at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
    at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
    at org.eclipse.ui.internal.handlers.ActionDelegateHandlerProxy.loadDelegate(ActionDelegateHandlerProxy.java:589)
    at org.eclipse.ui.internal.handlers.ActionDelegateHandlerProxy.execute(ActionDelegateHandlerProxy.java:270)
    at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
    at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
    at org.eclipse.ui.actions.ContributedAction.runWithEvent(ContributedAction.java:193)
    at org.eclipse.ui.texteditor.AbstractTextEditor$14.triggerAction(AbstractTextEditor.java:3082)
    at org.eclipse.ui.texteditor.AbstractTextEditor$14.access$1(AbstractTextEditor.java:3065)
    at org.eclipse.ui.texteditor.AbstractTextEditor$15.run(AbstractTextEditor.java:3096)
    at org.eclipse.ui.texteditor.AbstractTextEditor$14.mouseUp(AbstractTextEditor.java:3100)
    at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)



Operating Systems:
| Windows | 6.1.0 | 10.0.0 |


The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/559719cbe4b08735226b8b5e for the latest data.

Thank you for your assistance.
 Your friendly error-reports-inbox.
Comment 1 Stephan Herrmann CLA 2016-05-23 18:41:38 EDT
Originally, I saw in the linked aeri record, that jdt.core was in version 3.11.2.v20160128-0629, despite that fact that some OTDT components (org.eclipse.objectteams.otdt.ui) where installed.

I *guess* that this situation could occur, when updating jdt, say from 3.11.1 to 3.11.2 where no corresponding OTDT update is available, hence overwriting the presiously installed org.eclipse.jdt.core_3.11.1.v_OTDT_r241_201509081206

=> OTDT should never skip any (micro) release.
Comment 2 Stephan Herrmann CLA 2016-05-23 18:44:43 EDT
*** Bug 468105 has been marked as a duplicate of this bug. ***
Comment 3 Stephan Herrmann CLA 2016-05-26 18:16:12 EDT
*** Bug 473196 has been marked as a duplicate of this bug. ***
Comment 4 Stephan Herrmann CLA 2016-05-31 06:26:07 EDT
(In reply to Stephan Herrmann from comment #1)
> I *guess* that this situation could occur, when updating jdt, say from
> 3.11.1 to 3.11.2 where no corresponding OTDT update is available, hence
> overwriting the presiously installed
> org.eclipse.jdt.core_3.11.1.v_OTDT_r241_201509081206

I tried reproducing by
- installing Eclipse SDK 4.5.1
- adding Object Teams 2.4.1 from the mars/201510021000 repo
- check for updates

=> Updating SDK to 4.5.2 & OT to 2.4.2

I was not able to create the inconsistent configuration using this approach.
Comment 5 Stephan Herrmann CLA 2016-05-31 06:38:34 EDT
I tried a few more scenarios but even for a non-package install (i.e., plain SDK) we already have the mars repo registered and any check for updates will find OTDT 2.4.2 from there. That's one of the reasons, why Object Teams is on the SimRel train to begin with.

I'm closing as WORKSFORME, until s.o. can provide the installation steps that lead to the situation where we have OTDT installed, but org.eclipse.jdt.core has a non-OT version (no "v_OTDT_" segment in the qualifier of the plugin version).