|Re: [tycho-user] framework extension bundle and rt.jar versus tools.jar|
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 http://blog.springsource.org/2009/01/19/exposing-the-boot-classpath-in-osgi/ http://blog.meschberger.ch/2008/10/osgi-framework-extension-as-maven.html I believe there are licensing restrictions for modifying tools.jar and rt.jar, so the framework extension bundle avoids that complication. -----Original Message----- From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Andreas Sewe Sent: Thursday, August 29, 2013 4:09 AM To: tycho-user@xxxxxxxxxxx Subject: Re: [tycho-user] framework extension bundle and rt.jar versus tools.jar Hi Justin, > I have a framework extension bundle project in my reactor, and it > exports packages from rt.jar (like javax.swing.plaf.swing) and > packages from tools.jar (like com.sun.javadoc). FWIW, we describe an alternative to a framework extension bundle on our blog ; we recently came across this technique Bundle-ClassPath: external:$java.home$/../lib/tools.jar Export-Package: com.sun.javadoc, ... and are quite happy with it. Can you please elaborate some more on your framework extension solution? Patrick, a GSoC student, who came up with the above solution for his project might be interested in it. > Is it a compiler classpath problem? That being said, at compile time you still have to use <extraClasspathElements> (also explained in the blog post). Best wishes, Andreas  <http://www.codetrails.com/blog/osgi-ify-your-tools-jar> -- Codetrails UG (haftungsbeschränkt) The knowledge transfer company Robert-Bosch-Str. 7, 64293 Darmstadt Mobile: +49-170-811-3791 http://www.codetrails.com/ Managing Director: Dr. Marcel Bruch Handelsregister: Darmstadt HRB 91940 _______________________________________________ tycho-user mailing list tycho-user@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/tycho-user ---------------------------------------------------------------------- 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