Thanks Igor and Alejandro,
So adding the m2e-tycho plugin worked. If I add the profile as suggested to create the MANIFEST.MF in the root path, the launch config will show up as expected and up-to-date.....
...unfortunately in this case when launching I will receive errors for my DS-services (which are generated by the maven-scr-plugin) like:
!ENTRY com.xyz.servlet.discovery 4 0 2013-07-16 00:07:41.520!MESSAGE Component descriptor entry 'OSGI-INF/com.xyz.servlet.discovery.impl.DiscoveryMessageBodyWriter.xml' not found
The OSGI-INF is located in target/classes. I tried copying it to the next to the META-INF as well, but this give me just other creepy errors (something like: The path com.xyz.servlet.discovery was not found but was in target/classes/com.xyz.servlet.discovery).
Anyhow you already helped me a lot. Thanks to everyone :)
Date: Mon, 15 Jul 2013 11:39:34 -0400From: Alejandro.Endo@xxxxxxxxxxx
To: Maven Integration for Eclipse users mailing list <m2e-users@xxxxxxxxxxx>
Subject: Re: [m2e-users] Problem with M2E and OSGi runtime launch config
Content-Type: text/plain; charset=US-ASCII
It does work with OSGi Framework launchers. We use them every day.
Two tricks are1) Install the Tycho Configurator
2) configure the MBP to put the manifest in the place PDE expects it andthe plugin.xml if you use extension points
This is the profile I created to configure everything for PDE
<id>in-eclipse</id> <!-- activated only when running in m2e (eclipse) -->
<manifestLocation>META-INF</manifestLocation> <!-- PDE expects it in the root of the project -->
<resource> <!-- pde (project root) -->
<resource> <!-- normal (output dir
, /target/classes) --> <directory>src/main/resources</
Alejandro Endo | Software Designer/Concepteur de logiciels
From: Igor Fedorenko <igor@xxxxxxxxxxxxxx>
Date: 2013-07-14 09:00 AMSubject: Re: [m2e-users] Problem with M2E and OSGi runtime launch config
Sent by: m2e-users-bounces@xxxxxxxxxxx
For projects that use maven-bundle-plugin (m-b-p for short), m2e-tycho,
despite the name, will execute m-b-p to generate bundle manifest as partof eclipse workspace build. It will also make projects using m-b-p
visible to PDE tools, launch configuration in particular, so you can addthese projects to the list of bundles enabled in the launch configuration.
I only use this with "Eclipse Application" and "JUnit Plug-in Test" and
do not know if it works with "OSGi Framework" launch configurations.
Theoretically, you should not need to change anything in your pom.xmlfiles, but due to some PDE bugs I did not care to debug you have to
change location of generated bundle manifest to META-INF/manifest.mf. Iusually do this in pom profile activated by m2e.version property, so
regular command line build works as is. I also lock version qualifier'.qualifier' (or any constant string, really) in the same profile to
avoid unnecessary workspace builds.--