Tycho-Build: How to suppress additional executable artifact?

[Dani-Hub]

Hi, we are in the process of migrating our classic PDE build by the tycho build (Thanks to everyone who has helped us so far!). This works now basically, but we noticed that after a successful build besides the wanted <product>.zip there is also an additional artifact <product>.executable.zip uploaded, which contains the two executable files without the plugins and features folders. Is it possible to suppress the generation of this extra artifact or at least possible to prevent its upload when maven performs the deploy step?

[laeubi]

I think you need to supply an example I'm not aware of that being the default in Tycho.

[Dani-Hub]

Great suggestion @sratz - it works like a charm! Nonetheless I'm wondering why there exists no official customization of this part, since binding to a non-existing phase looks like a somehow hacky approach to me.

[laeubi]

This is common practice in maven, but this:

1. do not attach anything, in wich case it would be simpler to skip the deploy goal if you don't want to deploy anything and the goal has even a skip parameter: https://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#skip
2. It does not explain why you get <product>.executable.zip I never seen this before and it looks wrong.

[Dani-Hub]

Well we certainly want to deploy something, but only one thing. @sratz before/after picture essentially demonstrates what we want to realize.

[sratz]

2. It does not explain why you get <product>.executable.zip I never seen this before and it looks wrong.

Hmm, I can't remember this ever having been different.

Just checked some old deployments of our product using Tycho 0.18.0 way back which also behaved like this.

Also some random product deployment of an Eclipse product:
https://repo.eclipse.org/content/repositories/ptp-releases/org/eclipse/remote/org.eclipse.remote.proxy.server.product/1.0.0/

I think whatever is being attached to the project is being deployed.

[laeubi]

I think whatever is being attached to the project is being deployed.

Just because it was always wrong does not make it right ;-)

I can't think about any case where it is useful and this should simply never be attached.