| 'No product definitions found' in tycho build [message #1856902] |
Sun, 08 January 2023 17:03  |
|
Hello, I have a simple set of projects to create an RCP product, built by tycho-3.0.1 and using JavaSE-18. The projects' structure:
targetplatform: eclipse 4.26.0 (2022-12), junit.jupiter and swtbot (eclipse-target-definition)
ui: Application.e4xmi, GUI classes, .product file and product extension in plugin.xml (eclipse-plugin)
feature: references ui plugin (eclipse-feature)
repository: category.xml with feature (eclipse-repository)
ui.tests: swtbot fragment (eclipse-test-plugin)
The build completes but there's no executable created. Checking the console output, I see:
[INFO] --- tycho-p2-director-plugin:3.0.1:materialize-products (materialize-products) @ ca.footeware.e4.application.ui ---
[INFO] No product definitions found. Nothing to do.
I've verified that synchronizing the product updates the extension. The pom has the standard p2-director snippet:
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-p2-director-plugin</artifactId>
<version>${tycho.version}</version>
<executions>
<execution>
<id>materialize-products</id>
<goals>
<goal>materialize-products</goal>
</goals>
</execution>
<execution>
<id>archive-products</id>
<goals>
<goal>archive-products</goal>
</goals>
</execution>
</executions>
</plugin>
What am I missing or doing wrong?
[Updated on: Mon, 09 January 2023 17:24] Report message to a moderator |
|
|
| Re: 'No product definitions found' in tycho build [message #1856928 is a reply to message #1856902] |
Mon, 09 January 2023 19:20  |
|
Progress update:
I eventually moved the .product and its splash.bmp to its own .product project, with eclipse-repository packaging. Building works and generates a feature repository and a trio of executables. Running the built executable works but running the product inside eclipse (Eclipse Application launcher specifying the product) causes the following non-fatal error:
!SESSION 2023-01-09 14:16:29.426 -----------------------------------------------
eclipse.buildId=unknown
java.version=19.0.1
java.vendor=Private Build
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_CA
Framework arguments: -product ca.footeware.e4.application.ui.product -clearPersistedState
Command-line arguments: -product ca.footeware.e4.application.ui.product -data /home/craig/eclipse-workspace/../runtime-ca.footeware.e4.application.product -dev file:/home/craig/eclipse-workspace/.metadata/.plugins/org.eclipse.pde.core/ca.footeware.e4.application.product-RUN/dev.properties -os linux -ws gtk -arch x86_64 -consoleLog -clearPersistedState
!ENTRY org.eclipse.e4.ui.workbench 4 0 2023-01-09 14:16:31.182
!MESSAGE Unable to resolve plug-in "ca.footeware.e4.application.product".
!STACK 0
java.io.IOException: Unable to resolve plug-in "ca.footeware.e4.application.product".
at org.eclipse.core.internal.runtime.PlatformURLPluginConnection.parse(PlatformURLPluginConnection.java:64)
at org.eclipse.core.internal.runtime.PlatformURLPluginConnection.resolve(PlatformURLPluginConnection.java:73)
at org.eclipse.core.internal.boot.PlatformURLHandler.openConnection(PlatformURLHandler.java:69)
at org.eclipse.osgi.internal.url.URLStreamHandlerProxy.openConnection(URLStreamHandlerProxy.java:123)
at java.base/java.net.URL.openConnection(URL.java:1095)
at org.eclipse.core.internal.runtime.PlatformURLConverter.resolve(PlatformURLConverter.java:46)
at org.eclipse.core.runtime.FileLocator.resolve(FileLocator.java:288)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.initializeStyling(PartRenderingEngine.java:1373)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1050)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1046)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)
at org.eclipse.e4.ui.internal.workbench.swt.E4Application.start(E4Application.java:168)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:136)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:402)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.base/java.lang.reflect.Method.invoke(Method.java:578)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:596)
at org.eclipse.equinox.launcher.Main.run(Main.java:1467)
at org.eclipse.equinox.launcher.Main.main(Main.java:1440)
Any ideas how to get rid of that?
|
|
|
Powered by
FUDForum. Page generated in 0.03153 seconds
] 
Search
Help
Register
Login
Home
