Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[Dltk-dev] Bug when reading library nodes from the org.eclipse.dltk.launching.interpreterInstalls extension point

Hi,

There is a problem when reading library nodes from the
org.eclipse.dltk.launching.interpreterInstalls extension point.

The library paths are resolved against the "home" directory specified
in the interpreterInstall element. The method
ScriptRuntime.addInterpreterExtensions() has the following code:

		IPath libPath = homePath..append(substitute(libPathStr));
		locations[j] = new LibraryLocation(libPath);

which passes a local file path only (without the local environment ID)
to the LibraryLocation constructor. This make the constructor fail
because this expects also the environment ID to be present in the
libPath. Therefore the Assert fails in the constructor code:

	public LibraryLocation(IPath libraryPath) {
		Assert.isLegal(EnvironmentPathUtils.isFull(libraryPath));
		...


PS: The logic of the UI also break if interpreter installs are
contributed through this extension point because the extension point
provides a directory and the UI (AbstractInterpreterDialog) expects
files. This is related to my previous post/bug.


Regards,
Gabriel


Back to the top