[
http://jira.codehaus.org/browse/MWAS-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=170775#action_170775
]
Chris Graham commented on MWAS-30:
----------------------------------
bq. It might be more feasible just to add "websphereVersion" parameter, instead
of complicating things with alternate scripts. Depending on this parameter the
plugin could decide whether to add "-nonput" argument or not. It also might be
useful if any other differencies would be found.
It is not a *version* difference, it is a *platform* difference. The same
revision of Process Server (in this case 6.0.2.4) on windows does not have the
parameter, but it does not fail it it is supplied. The same version on AIX,
however, terminates with an error message.
bq. Btw, having the same version of WS on every environment including
development, CI and production is the most common practice (and the best one).
I am well aware of that, and we do have the same versions across all 10
environments (except when we are rolling out patches - cann't do them all at
once).
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.
Well, LPAR actually. This LPAR, has:
WPS 6.0.2.4, which includes ??? of ESB and an underlying version 6.0.2.31 of
WAS.
WAS 6.1.0.15, and
Portal ????
In this case, Hudson requires Java 1.5 to run, so it is installed in a Cluster
under WAS 6.1. But when I am generating Process Server and normal J2EE ears for
WPS, it needs to target the 6.0.2.4 WPS code - especially for deployments.
-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
