[
http://jira.codehaus.org/browse/MWAS-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=170784#action_170784
]
Chris Graham commented on MWAS-30:
----------------------------------
{quote}
bq. This issue has not come about because we have different versions on the
one box. It has come about because we have multiple versions on the one box.
In this case the best solution would be to use multiple maven profiles.
{quote}
On the contary, just how do you think that profiles would address this issue?
The issue here is that because we're running from a WAS 6.1 process, it has all
of the WAS 6.1 environment variables set. One if them is the WAS_USER_SCRIPT,
which is designed to allow custom setup for specific profiles.
The issue here is that if this particular variable is set, when
setupCmdLine.sh|bat is called (which is called by basically all shell or batch
files, and ws_ant is one of them) then *NO* initialization takes place.
The issue then is that you are trying to setup and use a different WPS (or base
WAS for that matter) version than what has already been initialised.
The only means to reinitialize the environment is to remove the WAS_USER_SCRIPT
variable.
So, as all of this happens when the was6-maven-plugin calls ws_ant or ws_ant.sh
or ws_ant.bat, we have left maven's control and passed it to the shell/batch
script.
How would use of profiles fix this?
-Chris
> 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, WAS-30-unset-was-env.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
