Re: [tycho-user] Handling non-osgi jar files

["Sievers, Jan" <jan.sievers@xxxxxxx>]

semi-sane != sane 

of course all precautions like "you essentially cannot define public API of code you don't own" apply.
Nested jars are a different story - what matters for API is Export-Package (and BSN), whether the package comes from a nested jar or not.

I hope the new "Eclipse Bundle Recipes" proposal
http://eclipse.org/proposals/rt.ebr/
comes up with better ideas.

Jan

-----Original Message-----
From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Max Rydahl Andersen
Sent: Mittwoch, 13. März 2013 17:02
To: Tycho user list
Subject: Re: [tycho-user] Handling non-osgi jar files

On Tue, Mar 12, 2013 at 08:31:07AM +0000, Sievers, Jan wrote:
>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.

*but* if multiple projects does this with their own customzation under the same bundleId names things
gets messy very fast.

this is why I prefer to still use nested jars to avoid polluting the eclipse ecosystem with osgi bundles that 
aren't own by me.

...of course if you add your own custom prefix in front of the bundle all is good - still a mess but a smaller mess ;)
/max

>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.
>
>Regards
>Jan
>
>[1] http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html
>[2] http://wiki.eclipse.org/Tycho/How_Tos/Dependency_on_pom-first_artifacts
>
>-----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
>building.
>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
>http://software.2206966.n2.nabble.com/Good-solution-for-non-osgi-jars-td5098103.html
>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,
>--Thomas
>
>_______________________________________________
>tycho-user mailing list
>tycho-user@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/tycho-user
>_______________________________________________
>tycho-user mailing list
>tycho-user@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user