Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 332439 - No way to implement custom default interpreter install detection
Summary: No way to implement custom default interpreter install detection
Status: RESOLVED FIXED
Alias: None
Product: DLTK
Classification: Technology
Component: Common (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: dltk.common-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-13 09:06 EST by Ivan Inozemtsev CLA
Modified: 2010-12-14 05:45 EST (History)
2 users (show)

See Also:

Attachments
Patch which fixes an issue (7.67 KB, patch)
2010-12-13 09:14 EST, Ivan Inozemtsev CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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