WebSphere container should set the PATH properly by itself

Description

While working with WebSphere and WebLogic, I ran in the same problem over again, that I have multiple versions installed of both, yet need to add version specific environment variables while running them with Cargo. Both of them need for example their native libraries on PATH.

In case of WebSphere we already have a a rather exhaustive check (40+ lines of code) just to see if the PATH contains a value, instead of setting it.

Both implementations of JvmLauncher underlying executors (Ant Task Java and java.lang.ProcessBuilder) support setting environment variables, which makes it easy to add the functionality to JvmLauncher without too big of an impact.

Status

Assignee

Savas Ali Tokmen

Reporter

Savas Ali Tokmen

Components

Fix versions

Priority

Major
Configure