Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: backlog
-
Labels:None
-
Number of attachments :
Description
I think we should introduce a compilation configuration object (and deprecate but not remove the old parameters) in the compiler plugin. This can have a base class that is extended by the different compiler types.
I'm not sure if the Maven processing does enough just yet to be able to set a specific field with the right type without setting implementation="" however, and we should also be able to make the object a fullly-fledged component (with expressions and default values, as long as it is in the same source tree).
Issue Links
- is depended upon by
-
MCOMPILER-15
ability to have different test compilation parameters to general compilation parameters
-
- is related to
-
MNG-1567
improvements to complex mojo configuration
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link | This issue is depended upon by MNG-1565 [ MNG-1565 ] |
| Component/s | maven-compiler-plugin [ 11806 ] | |
| Type | Improvement [ 4 ] | Bug [ 1 ] |
| Key | MNG-1566 | MCOMPILER-16 |
| Workflow | Maven [ 42055 ] | jira [ 44069 ] |
| Project | Maven 2 [ 10500 ] | Maven 2.x Compiler Plugin [ 11130 ] |
| Workflow | jira [ 44069 ] | Maven [ 44705 ] |
| Fix Version/s | 2.1 [ 12304 ] |
| Workflow | Maven [ 44705 ] | Maven New [ 51788 ] |
| Fix Version/s | 2.1 [ 12304 ] | |
| Fix Version/s | 2.2 [ 16097 ] |
| Fix Version/s | 2.3 [ 16208 ] | |
| Fix Version/s | 2.2 [ 16097 ] |
| Fix Version/s | backlog [ 18455 ] | |
| Fix Version/s | 2.4 [ 16208 ] |