Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 324670 - Environment variables in Modisco Run Configurations
Summary: Environment variables in Modisco Run Configurations
Status: CLOSED WONTFIX
Alias: None
Product: MoDisco
Classification: Modeling
Component: Infrastructure (show other bugs)
Version: 0.9.0   Edit
Hardware: PC Windows XP
: P2 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Nicolas Bros CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-07 12:22 EDT by Missing name CLA
Modified: 2011-01-11 04:58 EST (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Missing name CLA 2010-09-07 12:22:58 EDT
it is not possible to set Environment variables in Modisco Run Configurations
Comment 1 Gabriel BARBIER CLA 2010-09-10 11:02:21 EDT
Hello Tony,
Did you mean "to use environment variables" instead of "to set environment variables" ?

Gabriel
Comment 2 Missing name CLA 2010-09-10 11:13:30 EDT
Hi Gabriel,

i would like to set environment variables and use them as i can do in Java Application Launch Configuration.

i would like to have the Java Application Launch Configuration Environment Tab in Modisco Discoverer Launch Configuration.
Comment 3 Gregoire Dupe CLA 2010-10-06 10:54:57 EDT
Moving back to P2 because this is an enhancement request.
Comment 4 Nicolas Bros CLA 2010-10-19 04:59:31 EDT
Since discoverers are launched in the same process as the rest of Eclipse, I don't think modifying the environment is possible, without risking conflicts.

Why would you need to change the environment anyway? If you need to pass parameters to discoverers, they should probably be declared as a DiscoveryParameter.
Comment 5 Fabien Giquel CLA 2010-12-14 09:03:46 EST
Hi Tony, 

to go further, we need a description for your use case .

As Nicolas said, the Modisco launch config does not launch a new JVM process. Uility for setting/overriding an environment variable is not obvious, and will require to set back the original value at the end of the discovery.

Setting the bug as "WONTFIX". Will reopen it if you, or someone else, brings some explanation to the need.
Comment 6 Hugo Bruneliere CLA 2011-01-11 04:58:20 EST
Currently not a bug.