Re: [cross-project-issues-dev] access to lib/ext

[Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx>]

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 <tom.schindl@xxxxxxxxxxxxxxx>:
> 
> 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 <gorkem.ercan@xxxxxxxxx>:
>> 
>> 
>> 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
>> cross-project-issues-dev@xxxxxxxxxxx
>> 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
> cross-project-issues-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev