Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] m2e-users Digest, Vol 54, Issue 8

OSGi DS generally work with m2e-tycho and "Eclipse Application" launch
configurations but I don't know anything about maven-scr-plugin so can't
tell if there is anything special about it.


On 2013-07-16 2:12 AM, Philipp Marx wrote:
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 4 0 2013-07-16 00:07:41.520!MESSAGE
Component descriptor entry
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 was not found but
was in target/classes/

Anyhow you already helped me a lot. Thanks to everyone :)


Message: 1
Date: Mon, 15 Jul 2013 11:39:34 -0400
From: Alejandro.Endo@xxxxxxxxxxx <mailto:Alejandro.Endo@xxxxxxxxxxx>
To: Maven Integration for Eclipse users mailing list
         <m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>>
Subject: Re: [m2e-users] Problem with M2E and OSGi runtime launch


Content-Type: text/plain; charset=US-ASCII

It does work with OSGi Framework launchers. We use them every day.

Two tricks are
1) Install the Tycho Configurator
2) configure the MBP to put the manifest in the place PDE expects it and
the plugin.xml if you use extension points

This is the profile I created to configure everything for PDE

                         <!-- activated only when running in m2e
(eclipse) -->



manifestLocation> <!-- PDE expects it in the root of the project -->
                                                 <!-- pde (project root) -->



                                                 <!-- normal (output dir
, /target/classes) -->


Alejandro Endo | Software Designer/Concepteur de logiciels

From:   Igor Fedorenko <igor@xxxxxxxxxxxxxx <mailto:igor@xxxxxxxxxxxxxx>>
To: m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>,
Date:   2013-07-14 09:00 AM
Subject:        Re: [m2e-users] Problem with M2E and OSGi runtime launch
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 part
of eclipse workspace build. It will also make projects using m-b-p
visible to PDE tools, launch configuration in particular, so you can add
these 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.xml
files, but due to some PDE bugs I did not care to debug you have to
change location of generated bundle manifest to META-INF/ I
usually 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.


m2e-users mailing list

Back to the top