[
http://jira.codehaus.org/browse/MEXEC-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138364#action_138364
]
Glen Mazza commented on MEXEC-50:
---------------------------------
This is not necessary...for a running mvn exec:exec, if I want to see the
classpath used, all I need to do is temporarily break it by placing in
<argument>-safsdfas</argument> or whatever in the arguments section--it will
then give me that classpath that was used. This issue can be closed (although
perhaps documentation on this could be given.)
> Give us a debugging option to see the results of the <classpath/> command
> under <arguments/>
> --------------------------------------------------------------------------------------------
>
> Key: MEXEC-50
> URL: http://jira.codehaus.org/browse/MEXEC-50
> Project: Maven 2.x Exec Plugin
> Issue Type: Wish
> Components: exec
> Affects Versions: future
> Reporter: Glen Mazza
> Priority: Minor
>
> It would be nice if there were some option to output the exec command that
> was run, in particular for java executions that include the full classpath
> used.
> When I do mvn exec:exec -e, while executing the Java command, I get a nice
> debugging output if there is an error in the running of the application. In
> that output, I see the full java command run, including the full classpath
> created by the <classpath/> command.
> But, if there is no error, I can't see the classpath that was generated.
> Giving us such an option to see the output classpath helps in debugging
> between exec's that work and those that don't.
> Thanks,
> Glen
--
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
