Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-dev] Tycho doesn't make difference between "natures" of plugins

If you want a plugin/fragment to be packaged as a directory instead of a JAR, add the following directive to your MANIFEST.MF:

Eclipse-BundleShape: dir


On Fri, Feb 13, 2015 at 11:33 AM, Sofiane Lasri <machikoo92500@xxxxxxxxx> wrote:


Until now, we've been using Eclipse PDE to build our RCP targets.

We aim at using Maven/Tycho/Jenkins for continuous integration.

Our applications contain plugins and fragments; when using Eclipse, the RCP target generation process ships plugins & fragments as JAR files, unless the fragment contains only resources (no java code): in that case, PDE ships

those fragments as directories, which is, eventually, what we need (our resource-only fragments contain linux dynamic libraries that depend on each other across the fragments (we use the "rpath" mechanism)).

Tycho doesn't seem to make any difference between the different "natures" of our plugins and ships everything as JARs which is unacceptable for us.

We currently don’t know how to fix this ;  we noticed 2 things:

- All the pom.xml contained in each of our plugins are overwritten with a "eclipse-plugin" packaging directive (maybe another value like « eclipse-fragmentFolder » would be nice to have?)

- The PDE-generated "artifact.xml" file contains a property name "artifact.folder" for each resources-only fragments that the Maven/Tycho generated file does not have

Any idea ? (apart from changing the way our applications are organized ;-)

Thank you very much in advance for your help

Kind regards

tycho-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit


"Legacy code" often differs from its suggested alternative by actually working and scaling.
 - Bjarne Stroustrup

Back to the top