|Programmatically Installing Execution Environments, Adding them to Project Build Paths [message #1431519]
||Thu, 25 September 2014 20:12
| Evan Beisheim
Registered: September 2014
I would like to programmatically insert my custom execution environment as an added library in the Lua build path of my project, so that the users of our Eclipse application don't have to. The following code does exactly what I want:|
LuaExecutionEnvironment ee = LuaExecutionEnvironmentManager.installLuaExecutionEnvironment("path/to/ee.zip");
List<IPath> eePath = LuaExecutionEnvironmentBuildpathUtil.getExecutionEnvironmentBuildPath(ee);
IBuildpathEntry e = DLTKCore.newLibraryEntry(eePath.get(0), IAccessRule.EMPTY_RULES, new IBuildpathAttribute, BuildpathEntry.INCLUDE_ALL, BuildpathEntry.EXCLUDE_NONE, false, true);
project.setRawBuildpath(entrylist.toArray(new IBuildpathEntry[entrylist.size()]), null);
However the calls to installLuaExecutionEnvironment and getExecutionEnvironmentBuildPath are not API and give 'Discouraged Access' warnings. I'm wondering if there are other ways to install EE's and get their build paths without using private API's.
I know there is an extension point, executionEnvironment, but Eclipse isn't finding the schema when I try to open it and I don't know how to use it. Can it help me with custom EEs?
Powered by FUDForum
. Page generated in 0.01888 seconds