Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] framework extension bundle and rt.jar versus tools.jar

Right, I posted a reply with how I modified the tycho-compiler classpath to include tools.jar.

I hadn't read the blog you linked but it is titled "osgi-ify-your-tools-jar" so I assumed that meant modifying the manifest in tools.jar. 

-----Original Message-----
From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Andreas Sewe
Sent: Thursday, August 29, 2013 9:30 AM
To: tycho-user@xxxxxxxxxxx
Subject: Re: [tycho-user] framework extension bundle and rt.jar versus tools.jar

Hi Justin,

> I've been told by multiple people in the Eclipse and Tycho community 
> that the extension bundle is the Correct way to expose these packages, 
> with these two blog posts being referred to
> -osgi/
> tml

thank you for the pointers. Very interesting.

There is a one crucial difference, though. The framework extension mechanism can only be used to expose things which are on the JVM's boot classpath (like sun.misc.Unsafe) but which are not considered to be part of the execution environment (like java.*).

The tools.jar, however, resides rarely (never?) on the JVM's boot classpath. So, as far as I can tell, the framework extension mechanism doesn't apply to it. Hope that explains the difference.

So, for rt.jar, frameworke extensions fit the bill nicely, but for tools.jar you need another workaround.

> I believe there are licensing restrictions for modifying tools.jar and rt.jar, so the framework extension bundle avoids that complication.

Yes, I am aware of these restrictions. In fact, the solution presented in [1] does *not* require repackaging of the tools.jar.

Best wishes,


[1] <>

Codetrails UG (haftungsbeschränkt)
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Mobile: +49-170-811-3791

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
tycho-user mailing list

This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient.  Any review, use, distribution, or disclosure by others is strictly prohibited.  If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.

Back to the top