[
https://jira.codehaus.org/browse/MEXEC-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=283506#comment-283506
]
daniel carter commented on MEXEC-59:
------------------------------------
A comment has been added to the examples but the best place to document a
parameter is in the documentation for that parameter. i.e.
mvn exec:help -Ddetail=true -Dgoal=java
should explain the difference as should
http://mojo.codehaus.org/exec-maven-plugin/java-mojo.html#commandlineArgs
> Difference between <arguments> and <commandLineArgs> is not documented
> ----------------------------------------------------------------------
>
> Key: MEXEC-59
> URL: https://jira.codehaus.org/browse/MEXEC-59
> Project: Maven 2.x Exec Plugin
> Issue Type: Bug
> Components: java
> Reporter: Trevor Harmon
> Assignee: Jerome Lacoste
> Priority: Minor
> Fix For: 1.1.1
>
>
> The exec:java goal has two seemingly identical elements: <arguments> and
> <commandLineArgs>. The difference between them is not documented.
> Simone Gianni made the following observations on the Maven Users List:
> - If commandLineArgs is specified, it will be used as is, except for
> replacing %classpath with proper classpath using dependencies
> - Otherwise if the property exec.args is specified, it will be used
> - Otherwise the list of <argument> and <classpath> will be parsed and used
> So, yes, they both (and the exec.args also) serve the same purpose, but
> commandLineArgs is taken more or less literaly, as well as exec.args, while
> the <arguments> element offer a more "formal" way of specifying parameters
> and calculating classpaths.
> These differences should be explained in the exec:java documentation.
--
This message is automatically generated by JIRA.
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
