Hi, JEP 220: Modular Run-Time Images describes Java 9 plans to remove extension mechanism. So there will be no lib/ext directory support in Java 9.
Hope this Helps! Thanks & Regards, Sarika From: [email protected] To: [email protected] Date: 03/04/2016 12:25 AM Subject: cross-project-issues-dev Digest, Vol 122, Issue 5 Sent by: [email protected] Send cross-project-issues-dev mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of cross-project-issues-dev digest..." Today's Topics: 1. access to lib/ext (Gorkem Ercan) 2. Re: access to lib/ext (Tom Schindl) 3. Re: access to lib/ext (David M Williams) 4. Re: access to lib/ext (Tom Schindl) 5. Re: access to lib/ext (Tom Schindl) 6. Re: access to lib/ext (Gorkem Ercan) ---------------------------------------------------------------------- Message: 1 Date: Thu, 03 Mar 2016 13:18:32 -0500 From: "Gorkem Ercan" <[email protected]> To: "Cross project issues" <[email protected]> Subject: [cross-project-issues-dev] access to lib/ext Message-ID: <[email protected]> Content-Type: text/plain; charset=utf-8; format=flowed Hi, On JSDT project we are trying to utilize nashorn as runtime for javascript based tool. Nashorn is part of JDK8 and is shipped as nashorn.jar on lib/ext folder of jdk. At the moment, it looks like Eclipse does not have access to the jar files on the lib/ext folder of the JDK. Is this by design? Is there a way for a bundle to get Eclipse runtime give access to lib/ext jars? Thanks, ? Gorkem ------------------------------ Message: 2 Date: Thu, 3 Mar 2016 19:31:27 +0100 From: Tom Schindl <[email protected]> To: Cross project issues <[email protected]> Subject: Re: [cross-project-issues-dev] access to lib/ext Message-ID: <[email protected]> Content-Type: text/plain; charset=utf-8 Equinox by default skips the extension classloader when build your bundle classloader. You have 2 options: A) instruct equinox to delegate to the ext loader which can only be done via commadline params => not an option for an IDE plugin B) ship an adaptor hook => this way eg efxclipse provides access to javafx who is also on the ext classpath Tom Von meinem iPhone gesendet > Am 03.03.2016 um 19:18 schrieb Gorkem Ercan <[email protected]>: > > > Hi, > On JSDT project we are trying to utilize nashorn as runtime for javascript based tool. > Nashorn is part of JDK8 and is shipped as nashorn.jar on lib/ext folder of jdk. > > At the moment, it looks like Eclipse does not have access to the jar files on the lib/ext folder > of the JDK. Is this by design? Is there a way for a bundle to get Eclipse runtime give access to > lib/ext jars? > > Thanks, > ? > Gorkem > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe from this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ------------------------------ Message: 3 Date: Thu, 3 Mar 2016 13:43:36 -0500 From: "David M Williams" <[email protected]> To: Cross project issues <[email protected]> Subject: Re: [cross-project-issues-dev] access to lib/ext Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8" Others may know "why" it is the case, but one approach is to use a custom p2.inf file to add it to the vmargs in eclipse.ini. If you do that, though, be sure you only add that specific jar, so you don't accidentally change other behavior of the IDE (for example, if there was a different version of xalan installed there). And, also, be sure you *remove* the argument when the feature is removed (via unconfigure). Paul Webster has an old blog entry that shows how to do this for a different VM argument, if that helps. http://pweclipse.blogspot.com/2012_02_01_archive.html To play it safe, I would file a "works with" CQ. Ideally, you would have some other "runtime" available or plugable, in case people use a different VM or things change in the future. Or, something like ant does ... where a different ant runtime can be specified in preferences. From: "Gorkem Ercan" <[email protected]> To: "Cross project issues" <[email protected]>, Date: 03/03/2016 01:18 PM Subject: [cross-project-issues-dev] access to lib/ext Sent by: [email protected] Hi, On JSDT project we are trying to utilize nashorn as runtime for javascript based tool. Nashorn is part of JDK8 and is shipped as nashorn.jar on lib/ext folder of jdk. At the moment, it looks like Eclipse does not have access to the jar files on the lib/ext folder of the JDK. Is this by design? Is there a way for a bundle to get Eclipse runtime give access to lib/ext jars? Thanks, ? Gorkem _______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: < https://dev.eclipse.org/mailman/private/cross-project-issues-dev/attachments/20160303/0ddc6d05/attachment.html > ------------------------------ Message: 4 Date: Thu, 3 Mar 2016 19:48:27 +0100 From: Tom Schindl <[email protected]> To: Cross project issues <[email protected]> Subject: Re: [cross-project-issues-dev] access to lib/ext Message-ID: <[email protected]> Content-Type: text/plain; charset=utf-8 Oh and there's C) a equinox specific Manifest header need to look that up but if you query for it there should be a thread on equinox dev where Tom Watson mention the header name In your case c is the best option Tom Von meinem iPhone gesendet > Am 03.03.2016 um 19:31 schrieb Tom Schindl <[email protected]>: > > Equinox by default skips the extension classloader when build your bundle classloader. > > You have 2 options: > A) instruct equinox to delegate to the ext loader which can only be done via commadline params => not an option for an IDE plugin > B) ship an adaptor hook => this way eg efxclipse provides access to javafx who is also on the ext classpath > > Tom > > Von meinem iPhone gesendet > >> Am 03.03.2016 um 19:18 schrieb Gorkem Ercan <[email protected]>: >> >> >> Hi, >> On JSDT project we are trying to utilize nashorn as runtime for javascript based tool. >> Nashorn is part of JDK8 and is shipped as nashorn.jar on lib/ext folder of jdk. >> >> At the moment, it looks like Eclipse does not have access to the jar files on the lib/ext folder >> of the JDK. Is this by design? Is there a way for a bundle to get Eclipse runtime give access to >> lib/ext jars? >> >> Thanks, >> ? >> Gorkem >> _______________________________________________ >> cross-project-issues-dev mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe from this list, visit >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe from this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ------------------------------ Message: 5 Date: Thu, 3 Mar 2016 19:51:10 +0100 From: Tom Schindl <[email protected]> To: Cross project issues <[email protected]> Subject: Re: [cross-project-issues-dev] access to lib/ext Message-ID: <[email protected]> Content-Type: text/plain; charset=utf-8 Doing the work for you https://dev.eclipse.org/mhonarc/lists/equinox-dev/msg07323.html :-) Tom Von meinem iPhone gesendet > Am 03.03.2016 um 19:48 schrieb Tom Schindl <[email protected]>: > > Oh and there's > > C) a equinox specific Manifest header need to look that up but if you query for it there should be a thread on equinox dev where Tom Watson mention the header name > > In your case c is the best option > > Tom > > Von meinem iPhone gesendet > >> Am 03.03.2016 um 19:31 schrieb Tom Schindl <[email protected]>: >> >> Equinox by default skips the extension classloader when build your bundle classloader. >> >> You have 2 options: >> A) instruct equinox to delegate to the ext loader which can only be done via commadline params => not an option for an IDE plugin >> B) ship an adaptor hook => this way eg efxclipse provides access to javafx who is also on the ext classpath >> >> Tom >> >> Von meinem iPhone gesendet >> >>> Am 03.03.2016 um 19:18 schrieb Gorkem Ercan <[email protected]>: >>> >>> >>> Hi, >>> On JSDT project we are trying to utilize nashorn as runtime for javascript based tool. >>> Nashorn is part of JDK8 and is shipped as nashorn.jar on lib/ext folder of jdk. >>> >>> At the moment, it looks like Eclipse does not have access to the jar files on the lib/ext folder >>> of the JDK. Is this by design? Is there a way for a bundle to get Eclipse runtime give access to >>> lib/ext jars? >>> >>> Thanks, >>> ? >>> Gorkem >>> _______________________________________________ >>> cross-project-issues-dev mailing list >>> [email protected] >>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit >>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >> _______________________________________________ >> cross-project-issues-dev mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe from this list, visit >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe from this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ------------------------------ Message: 6 Date: Thu, 03 Mar 2016 13:55:05 -0500 From: "Gorkem Ercan" <[email protected]> To: "Cross project issues" <[email protected]> Subject: Re: [cross-project-issues-dev] access to lib/ext Message-ID: <[email protected]> Content-Type: text/plain; charset=utf-8; format=flowed On 3 Mar 2016, at 13:51, Tom Schindl wrote: > Doing the work for you > https://dev.eclipse.org/mhonarc/lists/equinox-dev/msg07323.html :-) > Yes, you did. Adding one more to my growing beer debt. :) > Tom > > Von meinem iPhone gesendet > >> Am 03.03.2016 um 19:48 schrieb Tom Schindl >> <[email protected]>: >> >> Oh and there's >> >> C) a equinox specific Manifest header need to look that up but if you >> query for it there should be a thread on equinox dev where Tom Watson >> mention the header name >> >> In your case c is the best option >> >> Tom >> >> Von meinem iPhone gesendet >> >>> Am 03.03.2016 um 19:31 schrieb Tom Schindl >>> <[email protected]>: >>> >>> Equinox by default skips the extension classloader when build your >>> bundle classloader. >>> >>> You have 2 options: >>> A) instruct equinox to delegate to the ext loader which can only be >>> done via commadline params => not an option for an IDE plugin >>> B) ship an adaptor hook => this way eg efxclipse provides access to >>> javafx who is also on the ext classpath >>> >>> Tom >>> >>> Von meinem iPhone gesendet >>> >>>> Am 03.03.2016 um 19:18 schrieb Gorkem Ercan >>>> <[email protected]>: >>>> >>>> >>>> Hi, >>>> On JSDT project we are trying to utilize nashorn as runtime for >>>> javascript based tool. >>>> Nashorn is part of JDK8 and is shipped as nashorn.jar on lib/ext >>>> folder of jdk. >>>> >>>> At the moment, it looks like Eclipse does not have access to the >>>> jar files on the lib/ext folder >>>> of the JDK. Is this by design? Is there a way for a bundle to get >>>> Eclipse runtime give access to >>>> lib/ext jars? >>>> >>>> Thanks, >>>> ? >>>> Gorkem >>>> _______________________________________________ >>>> cross-project-issues-dev mailing list >>>> [email protected] >>>> To change your delivery options, retrieve your password, or >>>> unsubscribe from this list, visit >>>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >>> _______________________________________________ >>> cross-project-issues-dev mailing list >>> [email protected] >>> To change your delivery options, retrieve your password, or >>> unsubscribe from this list, visit >>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >> _______________________________________________ >> cross-project-issues-dev mailing list >> [email protected] >> To change your delivery options, retrieve your password, or >> unsubscribe from this list, visit >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or > unsubscribe from this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ------------------------------ _______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev End of cross-project-issues-dev Digest, Vol 122, Issue 5 ********************************************************
_______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
