Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 332439

Summary: No way to implement custom default interpreter install detection
Product: [Technology] DLTK Reporter: Ivan Inozemtsev <ivan.inozemtsev>
Component: CommonAssignee: dltk.common-inbox <dltk.common-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: major    
Priority: P3 CC: alex.panchenko, ivan.inozemtsev
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:
Attachments:
Description Flags
Patch which fixes an issue none

Description Ivan Inozemtsev CLA 2010-12-13 09:06:14 EST 
Build Identifier: M20100909-0800

JavaRuntime.initializeVMs includes one extra step comparing to ScriptRuntime.initializeInterpreters - if no VMs are installed, it iterates through all VM types and tries to call IVmInstallType.detectInstallLocation. The same should be performed in ScriptRuntime in order to provide an ability of automatic discovering of installed interpreters

Reproducible: Always

Steps to Reproduce:
1. Open ScriptRuntime.initilializeInterpreters
2. Open JavaRuntime.initializeVMs
3. See that there is no way to implement auto-detection
Comment 1 Ivan Inozemtsev CLA 2010-12-13 09:14:38 EST 
Created attachment 185054 [details]
Patch which fixes an issue

This patch adapts corresponding code from JavaRuntime taking into account multi-language nature of DLTK
Comment 2 Alex Panchenko CLA 2010-12-14 05:45:42 EST 
Committed. Thanks