-
I have a Tycho pomless product build. The products are generated without problems. The product definition declares a custom launcher name. This works, i.e. Tycho creates the product for all platforms using the custom launcher name. The MacOS artifacts are packaged as Also it looks like all other platforms don't use a root folder whereas MacOS artifacts are the only ones using |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 7 replies
-
You can use all configuration options in your configurator-pom to customize this e.g. but I think the name of the folders (e.g. |
Beta Was this translation helpful? Give feedback.
-
we just use this:
buchen/fix-info-plist-maven-plugin: Small Maven plugin to "fix" the
Info.plist file generated by p2 during a Tycho product build.
<https://github.com/buchen/fix-info-plist-maven-plugin>
servoy-eclipse/com.servoy.eclipse.product/pom.xml at master ·
Servoy/servoy-eclipse
<https://github.com/Servoy/servoy-eclipse/blob/master/com.servoy.eclipse.product/pom.xml#L175>
that works fine our app is really Servoy.app not Eclipse.app
…On Thu, 7 Nov 2024 at 16:12, Gunnar Wagenknecht ***@***.***> wrote:
I have a Tycho pomless product build. The products are generated without
problems. The product definition declares a custom launcher name. This
works, i.e. Tycho creates the product for all platforms using the custom
launcher name.
However, the MacOS artifacts are packaged as Eclipse.app app bundles. Is
it possible to disable this in a pomless Tycho build or modify the app
bundle name to something else?
—
Reply to this email directly, view it on GitHub
<#4424>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAY7MHDKAZOO2YGTVW2N6DDZ7N7NVAVCNFSM6AAAAABRLN2P7GVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZXGQ2DANZYG4>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
Yes you can configure it in the
pluginManagement
section of the parent. There you can of course also use a property (that then can be overwritten inbuild.properties
withpom.model.property.myRootFolder = foo
this is quite common to use and make pomless more configurable.