Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 3.0.3
-
Component/s: Plugins and Lifecycle
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
Description
Right now, when determining the target type for a collection item to convert POM configuration to, Maven/Plexus uses some heuristics based on the XML element name and the mojo package name and eventually falls back to String. The current approach requires plugin authors to either put their parameter bean classes into the same package as the mojo or requires users to explicitly use the implementation attribute in the POM. These troubles can be avoided if Maven would recognize the generic type of a parameter declaration List<Bean>, thereby aligning collections with arrays regarding the ease of configuration/use.
Issue Links
- relates to
-
MNG-5027
Problem executing custom surefire implementation in Maven 3.0.3-RC1
-
Activity
Benjamin Bentmann
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Component/s | Plugins and Lifecycle [ 11340 ] | |
| Component/s | Plugin Requests [ 11899 ] |
Benjamin Bentmann
made changes -
| Status | Open [ 1 ] | Closed [ 6 ] |
| Assignee | Benjamin Bentmann [ bentmann ] | |
| Fix Version/s | 3.0.3 [ 17061 ] | |
| Resolution | Fixed [ 1 ] |
Benjamin Bentmann
made changes -