Using Tycho in a custom Packaging

[pazi146]

Java 17
Tycho version: 4.0.13
Maven: 3.9.9

I am trying to create a custom Packaging based on eclipse-repository to simplify maintenance of our projects (as we use custom deploy, etc.)

As a test I simply copied eclipse-repository from the /META-INF/plexus/components.xml and renamed it to custom-eclipse-repository. It is contained within one of our own plugins and <extensions>true</extensions> is set on that build dependency.

<?xml version="1.0" encoding="UTF-8"?>
<component-set>
    <components>
        <!-- copy of eclipse-repository -->
        <component>
            <role>org.apache.maven.lifecycle.mapping.LifecycleMapping</role>
            <role-hint>custom-eclipse-repository</role-hint>
            <implementation>
                org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping
            </implementation>
            <configuration>
                <lifecycles>
                    <lifecycle>
                        <id>default</id>
                        <phases>
                            <validate>
                                org.eclipse.tycho:tycho-packaging-plugin:4.0.13:build-qualifier-aggregator
                            </validate>
                            <initialize>
                                <!--  P2 publisher application will accumulate the published content in resulting repositories.
                                                The build needs to guarantee that legacy build content is removed from output folder prior to each build.  -->
                                org.apache.maven.plugins:maven-clean-plugin:3.3.2:clean,
                                org.eclipse.tycho:target-platform-configuration:4.0.13:target-platform
                            </initialize>
                            <process-resources>
                                org.apache.maven.plugins:maven-resources-plugin:3.3.1:resources
                            </process-resources>
                            <prepare-package> org.eclipse.tycho:tycho-p2-publisher-plugin:4.0.13:publish-osgi-ee,
                                org.eclipse.tycho:tycho-p2-publisher-plugin:4.0.13:publish-products,
                                org.eclipse.tycho:tycho-p2-publisher-plugin:4.0.13:publish-categories,
                                org.eclipse.tycho:tycho-p2-publisher-plugin:4.0.13:attach-artifacts,
                                org.eclipse.tycho:tycho-p2-repository-plugin:4.0.13:assemble-repository
                            </prepare-package>
                            <package>
                                org.eclipse.tycho:tycho-p2-repository-plugin:4.0.13:archive-repository
                            </package>
                            <install>
                                org.apache.maven.plugins:maven-install-plugin:3.1.1:install,
                                org.eclipse.tycho:tycho-p2-plugin:4.0.13:update-local-index
                            </install>
                            <deploy>
                                org.apache.maven.plugins:maven-deploy-plugin:3.1.1:deploy
                            </deploy>
                        </phases>
                    </lifecycle>
                </lifecycles>
            </configuration>
        </component>
    </components>
</component-set>

When changing the packaging type in the project to the copied one the build no longer completes. No other changes were made to the POM. I get the following error output:

ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-publisher-plugin:4.0.13:publish-products (default-publish-products) on project Test_Project: Publisher failed. Verify your target-platform-configuration and executionEnvironment are suitable for proper resolution: Unable to locate feature 'org.eclipse.equinox.executable'. This feature is required for native product launchers. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-p2-publisher-plugin:4.0.13:publish-products (default-publish-products) on project Test_Project: Publisher failed. Verify your target-platform-configuration and executionEnvironment are suitable for proper resolution
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:333)
    ...
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:314)
Caused by: org.apache.maven.plugin.MojoFailureException: Publisher failed. Verify your target-platform-configuration and executionEnvironment are suitable for proper resolution
    at org.eclipse.tycho.plugins.p2.publisher.AbstractPublishMojo.execute (AbstractPublishMojo.java:41)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:126)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:328)
    ...
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:361)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:314)
Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to locate feature 'org.eclipse.equinox.executable'. This feature is required for native product launchers.
    at org.eclipse.tycho.plugins.p2.publisher.PublishProductMojo.getExpandedLauncherBinaries (PublishProductMojo.java:210)
    at org.eclipse.tycho.plugins.p2.publisher.PublishProductMojo.publishContent (PublishProductMojo.java:139)
    at org.eclipse.tycho.plugins.p2.publisher.AbstractPublishMojo.execute (AbstractPublishMojo.java:38)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:126)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:328)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:316)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:212)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:174)
    at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:75)
    at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:162)
    at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:77)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:568)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:255)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:201)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:361)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:314)
[ERROR] 

• Am I missing something in the plugin where the packaging is defined?
• Or is the configuration incomplete and Tycho uses default values in the background?
• Or is this custom packaging simply not possible with Tycho?

[laeubi]

I am trying to create a custom Packaging based on eclipse-repository to simplify maintenance of our projects (as we use custom deploy, etc.)

I can only recommend not to do that (for multiple reasons) as this does not simplify anything...

So maybe reconsider what exact problem you like to solve that can not be solved with standard maven (e.g. profiles, parents, ...)
If you even already use an extension you can even rewrite the model and inject whatever extra mojos you like (or disable / remove existing ones).

Am I missing something in the plugin where the packaging is defined?
Or is the configuration incomplete and Tycho uses default values in the background?
Or is this custom packaging simply not possible with Tycho?

You likely need to implement a lot more, e.g project-types, artifact handlers and so on.

[pazi146]

I had already suspected this would be the case...

Thank you for the quick answer