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

["David M Williams" <david_williams@xxxxxxxxxx>]

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"
<gorkem.ercan@xxxxxxxxx>
To:      
 "Cross project
issues" <cross-project-issues-dev@xxxxxxxxxxx>, 
Date:      
 03/03/2016 01:18 PM
Subject:    
   [cross-project-issues-dev]
access to lib/ext
Sent by:    
   cross-project-issues-dev-bounces@xxxxxxxxxxx

---

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