[
http://jira.codehaus.org/browse/MEXEC-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=172597#action_172597
]
Milos Kleint commented on MEXEC-25:
-----------------------------------
maybe caused by the fact that ComandLineUtils runs "sh cd <workdir>&& my exec"
and the system input is connected to the wrong process.
see
BourneShell.getExecutionPreamble()
if we run just "java" (or whatever is being executed) as executable in the
Process.exec(), we should be ok.
is shall wrapping that some sort of pre jdk 1.5 workaround?
> exec:exec mojo support interaction with user
> --------------------------------------------
>
> Key: MEXEC-25
> URL: http://jira.codehaus.org/browse/MEXEC-25
> Project: Maven 2.x Exec Plugin
> Issue Type: New Feature
> Components: exec
> Affects Versions: 1.1-beta-1
> Reporter: Jerome Lacoste
>
> It would be nice if the exec mojo would support command line interaction, in
> particular when maven is ran from the command line. Maybe valid as well for
> the java mojo.
> My particular use case is when using asadmin to deploy to a secure glassfish
> install. The first time, the deploy requires accepting the server certificate.
--
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
