Bug 488040 - org.eclipse.jdt's samplesExtensionContent.xml references org.eclipse.pde.ui ("Intro tried accessing a NULL bundle" error when PDE not installed)
Summary: org.eclipse.jdt's samplesExtensionContent.xml references org.eclipse.pde.ui (...
Status: CLOSED DUPLICATE of bug 140040
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.5.2   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-18 10:48 EST by EPP Error Reports CLA
Modified: 2016-02-19 04:31 EST (History)
6 users (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-02-18 10:48:21 EST
The following incident was reported via the automated error reporting:

The user(s) left the following comments:
--- Andreas Sewe wrote: ---
Testing the Mars.2 RC4 EPP package for Java Developers. Went to the Welcome page, clicked on Samples > JDT > Java Editor. Nothing (aside from this error) happened.
    


    code:                   0
    plugin:                 org.eclipse.ui.intro_3.4.300.v20141007-1449
    message:                Intro tried accessing a NULL bundle.
    fingerprint:            dfade6d998351f1a7e322053cdb19fed
    exception class:        org.eclipse.epp.logging.aeri.core.util.NoStackTrace
    exception message:      This event was logged without a stack trace. A synthetic stack trace was hence inserted.
    number of children:     0
    
    org.eclipse.epp.logging.aeri.core.util.NoStackTrace: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
    at org.eclipse.ui.internal.intro.impl.util.Log.error(Log.java:75)
    at org.eclipse.ui.internal.intro.impl.model.util.BundleUtil.bundleHasValidState(BundleUtil.java:46)[REQUIRED, TOPMOST]
    at org.eclipse.ui.internal.intro.impl.model.loader.ModelLoaderUtil.createClassInstance(ModelLoaderUtil.java:140)
    at org.eclipse.ui.internal.intro.impl.model.url.IntroURL.runAction(IntroURL.java:275)
    at org.eclipse.ui.internal.intro.impl.model.url.IntroURL.doExecute(IntroURL.java:193)
    at org.eclipse.ui.internal.intro.impl.model.url.IntroURL$1.run(IntroURL.java:144)
    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
    at org.eclipse.ui.internal.intro.impl.model.url.IntroURL.execute(IntroURL.java:141)
    at org.eclipse.ui.internal.intro.impl.presentations.BrowserIntroPartLocationListener.changing(BrowserIntroPartLocationListener.java:130)
    at org.eclipse.swt.browser.IE$7.handleEvent(IE.java:539)
    at org.eclipse.swt.ole.win32.OleEventTable.sendEvent(OleEventTable.java:55)
    at org.eclipse.swt.ole.win32.OleEventSink.notifyListener(OleEventSink.java:152)
    at org.eclipse.swt.ole.win32.OleEventSink.Invoke(OleEventSink.java:120)
    at org.eclipse.swt.ole.win32.OleEventSink.access$1(OleEventSink.java:97)
    at org.eclipse.swt.ole.win32.OleEventSink$1.method6(OleEventSink.java:71)
    at org.eclipse.swt.internal.ole.win32.COMObject.callback6(COMObject.java:119)
    at org.eclipse.swt.internal.win32.OS.DispatchMessageW(OS.java:-2)
    at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2549)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3767)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
    at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
    at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(null:-2)
    at sun.reflect.NativeMethodAccessorImpl.invoke(null:-1)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(null:-1)
    at java.lang.reflect.Method.invoke(null:-1)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
   
  

General Information:

    reported-by:      -
    anonymous-id:     039031f9-affc-4aef-8c18-85649e996477
    eclipse-build-id: 4.5.2.M20160128-1800
    eclipse-product:  org.eclipse.epp.package.java.product
    operating system: Windows7 6.1.0 (x86) - win32
    jre-version:      1.8.0_73-b02

The following plug-ins were present on the execution stack (*):
    1. org.eclipse.core.databinding.observable_1.5.0.v20150422-0725
    2. org.eclipse.core.databinding_1.5.0.v20150422-0725
    3. org.eclipse.core.runtime_3.11.1.v20150903-1804
    4. org.eclipse.e4.ui.workbench_1.3.1.v20160107-1220
    5. org.eclipse.e4.ui.workbench.swt_0.13.0.v20150504-0621
    6. org.eclipse.equinox.app_1.3.300.v20150423-1356
    7. org.eclipse.equinox.launcher_1.3.100.v20150511-1540
    8. org.eclipse.swt_3.104.2.v20160127-0046
    9. org.eclipse.ui_3.107.0.v20150507-1945
    10. org.eclipse.ui.ide.application_1.1.0.v20150422-0725
    11. org.eclipse.ui.ide_3.11.0.v20150825-2158
    12. org.eclipse.ui.intro_3.4.300.v20141007-1449

Please note that:
* Messages, stacktraces, and nested status objects may be shortened.
* Bug fields like status, resolution, and whiteboard are sent
  back to reporters.
* The list of present bundles and their respective versions was
  calculated by package naming heuristics. This may or may not reflect reality.

Other Resources:
* Report: https://dev.eclipse.org/recommenders/committers/confess/#/problems/56ba97d1e4b0ffc093b76603  
* Manual: https://dev.eclipse.org/recommenders/community/confess/#/guide


Thank you for your assistance.
Your friendly error-reports-inbox.

This bug was created on behalf of andreas.sewe@xxxxxxxxxxxx.
Comment 1 Andreas Sewe CLA 2016-02-18 10:51:29 EST
FWIW, the standard behavior seems to be to open a dialog "The samples are currently not installed. Do you want to download samples from eclipse.org?"
Comment 2 Andreas Sewe CLA 2016-02-18 10:58:54 EST
(In reply to Andreas Sewe from comment #1)
> FWIW, the standard behavior seems to be to open a dialog "The samples are
> currently not installed. Do you want to download samples from eclipse.org?"

Tested this with the Mars.2 RC4 SDK [1]. That works. So this seems to be a packaging issue. Moving to EPP.

[1] <http://download.eclipse.org/eclipse/downloads/drops4/M-4.5.2RC4-201602121500/>
Comment 3 Brian de Alwis CLA 2016-02-18 11:03:46 EST
I can reproduce in my 'classic' SDK runtime.
Comment 4 Andreas Sewe CLA 2016-02-18 11:08:58 EST
(In reply to Brian de Alwis from comment #3)
> I can reproduce in my 'classic' SDK runtime.

Hi Brian. Just to be you mean using on of the SDK downloads offered by the platform team [1] (because I can't). Or do you mean using a specific EPP package?

[1] <http://download.eclipse.org/eclipse/downloads/>
Comment 5 Brian de Alwis CLA 2016-02-18 11:41:21 EST
Sorry, I mis-read the title — I thought you were getting an NPE, which I was getting too (from  an SDK I-build).  But that NPE has gone away with a fresh workspace; I think it was spurious as I've been having some problems with some errant bundle opening too many files.
Comment 6 Andreas Sewe CLA 2016-02-18 13:11:04 EST
(In reply to Andreas Sewe from comment #2)
> (In reply to Andreas Sewe from comment #1)
> > FWIW, the standard behavior seems to be to open a dialog "The samples are
> > currently not installed. Do you want to download samples from eclipse.org?"
> 
> Tested this with the Mars.2 RC4 SDK [1]. That works. So this seems to be a
> packaging issue. Moving to EPP.

Tested with with further EPP packages:

- Java Developers: error
- Java EE Developers: works
- RCP/RAP Developers: works
- C/C++ Developers: n/a (no samples)
Comment 7 Andreas Sewe CLA 2016-02-19 03:20:40 EST
(In reply to Andreas Sewe from comment #6)
> Tested with with further EPP packages:
> 
> - Java Developers: error

FYI, this error already exists in Mars.1 and Mars.2 RC3.
Comment 8 Markus Knauer CLA 2016-02-19 03:46:58 EST
(In reply to Andreas Sewe from comment #7)
> FYI, this error already exists in Mars.1 and Mars.2 RC3.

Yes, my feeling is that this is not a regression, instead it sound like a category of errors that have been there (unreported) for a long time.
Comment 9 Andreas Sewe CLA 2016-02-19 04:05:30 EST
Debugged a bit:

The intro URL in question is

  http://org.eclipse.ui.intro/runAction?pluginId=org.eclipse.pde.ui&class=org.eclipse.pde.internal.ui.samples.ShowSampleAction&id=org.eclipse.sdk.samples.javaeditor

so it is looking for the org.eclipse.pde.ui bundle, which doesn't (and shouldn't) exist in the Java package.
Comment 10 Andreas Sewe CLA 2016-02-19 04:13:12 EST
(In reply to Andreas Sewe from comment #9)
> Debugged a bit:
> 
> The intro URL in question is
> 
>  
> http://org.eclipse.ui.intro/runAction?pluginId=org.eclipse.pde.ui&class=org.
> eclipse.pde.internal.ui.samples.ShowSampleAction&id=org.eclipse.sdk.samples.
> javaeditor
> 
> so it is looking for the org.eclipse.pde.ui bundle, which doesn't (and
> shouldn't) exist in the Java package.

The above URL is contributed by the org.eclipse.jdt bundle (which seems to be JDT's branding plugin). The reference to a bundle outside the JDT feature itself looks like a JDT bug to me. Will reassign to the JDT team.
Comment 11 Dani Megert CLA 2016-02-19 04:31:10 EST
(In reply to Markus Knauer from comment #8)
> (In reply to Andreas Sewe from comment #7)
> > FYI, this error already exists in Mars.1 and Mars.2 RC3.
> 
> Yes, my feeling is that this is not a regression, instead it sound like a
> category of errors that have been there (unreported) for a long time.

It's like that for more than 10 years.

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