Target alternate WebSphere Installation when run under WebSphere
----------------------------------------------------------------
Key: MWAS-30
URL: http://jira.codehaus.org/browse/MWAS-30
Project: Maven 2.x WebSphere 6 Plugin
Issue Type: New Feature
Environment: AIX, more than one version of WebSphere installed and
running on the one machine.
Reporter: Chris Graham
Assignee: David J. M. Karlsen
Attachments: MWAS30-1.patch
If you are running Maven under a CI tool under WebSphere 6.1, all processes
spawned by the CI tool will automatically inherit the WAS 6.1 environment
variables. That will present a problem if you need to have the
was6-maven-plugin target a different version of WebSphere, eg 6.0.2.
When the was6-maven-plugin calls ws_ant.(sh|bat) it calls setupCmdLine which
initialises most of the variables. There is one variable that points to the
specific instance/node/cluster/cell configuration, WAS_USER_SCRIPT.
If this variable is not removed when calling a WebSphere 6.0.2 ws_ant, when
setupCmdLine is called it will still use the WAS 6.1 one that it inherited when
it was spawned.
This patch provides an extra parameter, alternateScript, that will be run in
preference to ws_ant, thus allow it the ability to perform what ever setup is
necessary. In this case, simply unset the WAS_USER_SCRIPT variable. The script
pointed to by the alternateScript parameter still needs to call ws_ant using
the passed in parameters.
This is in and working when run from Maven called by Hudson running under WAS
6.1 but needing to target WAS 6.0.2.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
