[MCOMPILER-16] ability to separate compilation parameters for different compilers / create a compilation configuration object

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Auto Closed
• Assignee: Unassigned
• Reporter: Brett Porter
• Created: 14/Nov/05 22:08
• Updated: 06/Sep/15 20:50
• Resolved: 06/Sep/15 20:50

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