Discussion:
Feature based product throws a runtime error
(too old to reply)
Youngeun Cho
2018-10-23 11:09:42 UTC
Permalink
Hi,

I am following the tycho tutorial at vogella
<http://www.vogella.com/tutorials/EclipseTycho/article.html>.

The tutorial provides RCP product building instructions in chapter 9.

Chapter Summary:

1. Create plug-in project(prjA) using the `Eclipse 4 RCP Application
Template`

2. Create general project(prjB) for the maven build.

3. Move the generated .product file from prjA, to prjB.

(I do not understand why this step is necessary.)

4. Enter ID, make pom.xml

5. Select feature-based

6. Configure start-level, build.

The build finishes without errors, but when I run the generated binary,

I get the following stack trace:

!SESSION 2018-10-23 18:05:38.742
-----------------------------------------------
eclipse.buildId=unknown
java.version=1.8.0_172
java.vendor=Oracle Corporation
BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_KR
Framework arguments: -clearPersistedState -keyring
/Users/upoque/.eclipse_keyring
Command-line arguments: -os macosx -ws cocoa -arch x86_64
-clearPersistedState -keyring /Users/upoque/.eclipse_keyring

!ENTRY org.eclipse.equinox.app 0 0 2018-10-23 18:05:40.561
!MESSAGE Product org.rubis.oscar.rcp.product could not be found.

!ENTRY org.eclipse.osgi 4 0 2018-10-23 18:05:41.392
!MESSAGE Application error
!STACK 1
java.lang.NullPointerException
at
org.eclipse.emf.common.util.URI$URIPool$PlatformAccessUnit.setValue(URI.java:865)
at org.eclipse.emf.common.util.URI$URIPool.intern(URI.java:1949)
at
org.eclipse.emf.common.util.URI.createPlatformPluginURI(URI.java:2718)
at
org.eclipse.e4.ui.internal.workbench.swt.E4Application.determineApplicationModelURI(E4Application.java:408)
at
org.eclipse.e4.ui.internal.workbench.swt.E4Application.loadApplicationModel(E4Application.java:349)
at
org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:253)
at
org.eclipse.e4.ui.internal.workbench.swt.E4Application.start(E4Application.java:149)
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:388)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
at org.eclipse.equinox.launcher.Main.run(Main.java:1499)


However, when I build the product based on plug-ins(rather than
feature-based), I get no errors.

Why do I get this error, and how can I fix this?

Thank you.
Young

Continue reading on narkive:
Loading...