[
http://jira.codehaus.org/browse/MNG-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-5012.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0.3
Assignee: Benjamin Bentmann
Done in [r1070102|http://svn.apache.org/viewvc?view=revision&revision=1070102].
> Allow to configure array-typed plugin parameters from expressions yielding
> collections and vice versa
> -----------------------------------------------------------------------------------------------------
>
> Key: MNG-5012
> URL: http://jira.codehaus.org/browse/MNG-5012
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Plugins and Lifecycle
> Affects Versions: 3.0.2
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Priority: Minor
> Fix For: 3.0.3
>
>
> The distinction between arrays and collections is often times more a low-tech
> thingy than anything else, conceptually, both types are useful to hold zero
> or more items. As such it would be nice if plugin authors can freely choose
> which type works best for their plugin parameters. E.g. many Maven APIs
> provide collections yet arrays currently render the nicer plugin docs
> (component type mentioned). Currently, this is not possible:
> {code:java}
> /** @parameter default-value="${project.compileSourceRoots}" */
> String[] sourceRoots;
> {code}
--
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
