|Re: [cross-project-issues-dev] access to lib/ext|
On 3 Mar 2016, at 13:43, David M Williams wrote:
Others may know "why" it is the case, but one approach is to use a customp2.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 youdon't accidentally change other behavior of the IDE (for example, if therewas 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
Thanks for your answer David. I think this is my backup if the manifest solution fails.
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 adifferent ant runtime can be specified in preferences.
it represents significant user base.
Back to the top