Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Handling non-osgi jar files

we have used maven-bundle-plugin [1]
with Embed-Dependency directive (-> no nested jars)

IMHO the only semi-sane way to generate OSGi MANIFESTs based on 3rd party binaries.

build your OSGi wrappers in a separate ("orbit"-like) reactor and then use pomDependencies=consider to consume them[2].
For convenience in PDE you may also build an eclipse-repository out of these.



-----Original Message-----
From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Thomas Johnsson
Sent: Dienstag, 12. März 2013 09:19
To: tycho-user@xxxxxxxxxxx
Subject: [tycho-user] Handling non-osgi jar files

I'm in the process of tycho-ifying an eclipse plugin project. It has 3rd 
party non osgi jar files residing in lib directories in of subprojects, 
and included in the classpath.
Maven/Tycho is able to build this, and the jar files get included in the 
built plugins, just as a pde build would.

But: in a proper mavenised and tycho-ified project one would not have 
these local lib directories. Instead, the jar files and their versions 
would be specified in pom files, and plucked from a maven repo when 
Similarly, one would like such jar files from maven repo made available 
in the eclipse plugin project.

So what is the state-of-the-art when it comes to building plugins that 
include non-osgi jars? I googled this, and found
but that was almost 3 years ago, hopefully the situation has improved.

PS In some lucky cases one can find bundle-ified versions at Maven 
central, but unfortunately not all.

Thanks in advance,

tycho-user mailing list

Back to the top