[
http://jira.codehaus.org/browse/MOJO-995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129957#action_129957
]
Peter Ineson commented on MOJO-995:
-----------------------------------
I was wondering if "noExit" flag has been renamed to "continueOnFailure",
though currently it does not set the "-noExit" parameter when calling the
Weblogic deployer.
It would also be nice to add parameter expressions for the debug and verbose
options, just so they can be set from the command line.
One thing I have been pondering is if a change to the remote option is required
too. Currently when a remote deployment is requested then the Weblogic deployer
is called with the '-upload' parameter set, it may be better to include the
'-remote' parameter too (for correction for path names when deploying to a
remote server).
> Patch for Additional deployment parameters, notably -noExit
> -----------------------------------------------------------
>
> Key: MOJO-995
> URL: http://jira.codehaus.org/browse/MOJO-995
> Project: Mojo
> Issue Type: Improvement
> Components: weblogic
> Environment: You name it!
> Reporter: Peter Ineson
> Assignee: Jon Osborn
> Attachments: patch_extraDeploymentParameters.txt
>
>
> Attached is a patch that adds support for passing some of the extra
> parameters to the Weblogic deployer
> (http://e-docs.bea.com/wls/docs92/deployment/wldeployer.html#wp1010461). All
> the new parameters are common arguments which effect all the deployment tasks
> (deploy, undeploy, stop start etc). The extra parameters are;
> 1) -noExit (-Dweblogic.noExit).
> 2) -debug (-Dweblogic.debug).
> 3) -verbose (-Dweblogic.verbose).
> 4) -timeout (-Dweblogic.timeout).
> The -noExit parameter is of particular note for Weblogic 9.2 users (probably
> other versions too). The deployer performs a System.exit() even if the
> deployment was successful (not as per documentation ), as a result the maven
> build never completes. It was of particular annoyance to me as the
> application I am building is made up of 4 deployments, each one was having to
> be deployed individually as separate builds, rather than as a group in a
> single build.
> Cheers
> Peter
--
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
