|Re: Tycho build fails missing org.eclipse.equinox.executable.feature.group 0.0.0 [message #1752546 is a reply to message #1749322]
||Wed, 25 January 2017 01:27
| Patrik Suzzi
Registered: February 2018
Tycho resolves dependencies against p2 repositories (remote or local). It uses the information in plugin.xml. The dependencies are declared in MANIFEST.MF|
Anything that is a plugin dependency should come from a p2 repository, or from a plug-in project included in the build (so the maven reactor can satisfy the dependencies).
If you use specific Java libraries, I suggest you add them to the bundle classpath: in the plugin.xml, Runtime tab, Classpath section. (verify they are included in the build).
If you use native libraries, I suggest you put them in the base folder of your project and ensure you have a task that copies those natives under the path where Maven is building (by default maven builds under the /target directory).
To fully understand the Tycho build, the best resource is the "Tycho demo tutorial," by J.Sievers. Download it; start reading the index.html; and follow the tutorial until the end. Once done, it will be easy to understand how to modify the tutorial to achieve a Tycho build for your plugin, product, or set of products.
- here is the link: https://github.com/jsievers/tycho-demo
If you need other pointers, please see also:
- for Theory: https://www.eclipsecon.org/na2014/sites/default/files/slides/Tycho%20Tutorial%20-%20Introduction.pdf
- extensive reference/tutorial: http://www.vogella.com/tutorials/EclipseTycho/article.html
If you have other doubts, please try to summarize and formalize them, and respond on this thread.
Ing. Patrik Suzzi
Consultant Software Engineer,
Eclipse Platform Committer
|Re: Tycho build fails missing org.eclipse.equinox.executable.feature.group 0.0.0 [message #1773540 is a reply to message #1773533]
||Fri, 29 September 2017 05:56
| Dirk Fauth
Registered: July 2012
Your problem is not POM-first vs. MANIFEST-first ... your problem is the definition of a target platform and that PDE uses p2 and things are sometimes inconsistent.|
The basic idea of Tycho is to reduce the amount of configuration work for the automated build. As an Eclipse RCP developer you typically specify a Target Platform and define the dependencies of your plugins/bundles manually at development time. This is how it works with PDE. As you have done this already, there should be no need to do this again for building. So for Eclipse RCP development with PDE, Tycho is a perfect match. That comes even more to play when you consider pom-less Tycho.
In other scenarios, day using bndtools for example, Tycho doesn't fit well.
So there is a clear strategy. When using PDE for creating OSGi bundles, use Tycho as you will have the most benefit out of it. If you are using other tools like bndtools, use different approaches as there a MANIFEST-first approach will not work. (BTW you are referring to a 5 year old post, and the world has evolved since then).
But yes, the names shown by Tycho errors and the ones shown in the target editor are not the same. I switched to using a text based editor for target definitions a while ago. Started with https://github.com/mbarbero/fr.obeo.releng.targetplatform and in Oxygen you could use the Generic Text Editor. Both support code completion.
'org.eclipse.equinox.executable.feature.group' is also known as 'Eclipse Platform Launcher Executables'.
I have written a getting started with Eclipse 4 blog some years ago: https://blog.codecentric.de/en/2015/02/eclipse-rcp-cookbook-basic-recipe/
Probably not up-to-date in detail, but that part should be covered.
We have written a migration guide that should help: https://jaxenter.de/tutorial-so-portieren-sie-eclipse-3-anwendungen-auf-eclipse-4-39492
Unfortunately not yet translated to English.
In GitHub you can find sources for a simple migration scenario that might be also helpful: https://github.com/fipro78/e4-cookbook-migration-guide
Hope that helps
Powered by FUDForum
. Page generated in 0.06833 seconds