[MCOMPILER-15] ability to have different test compilation parameters to general compilation parameters

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0.2
• Assignee: Olle Jonsson
• Reporter: Brett Porter
• Created: 14/Nov/05 22:02
• Updated: 31/Dec/09 08:22
• Resolved: 31/Dec/09 08:22

Description

when we stopped doing per goal compilation because of its verbosity, we decided anything that had a different meaning in different mojos within a plugin would need a different parameter name. The compiler plugin slipped through this - specifically the compilation parameters for tests.

What we probably want is to be able to specify the test parameters separately, defaulting to the normal compilation parameters, and then the general defaults.

I think this should depend on us first splitting the compilation parameters into a separate component however so that they can be different depending on whether it is a java compiler, c# compiler, etc.

Issue Links

• depends upon: MCOMPILER-16 ability to separate compilation parameters for different compilers / create a compilation configuration object
• duplicates: MCOMPILER-83 add separate configuration for test compiler
• is related to: MNG-3203 maven should execute compiler:compile and :test-compile in separate executions, to allow separate configuration