Maven30xRuntime.finalizeMojoConfiguration is not processing configurations properly when using new formats provided by sisu

[cvgaviao]

Given that I have the following configuration set for an MojoExecution instance by an unit test:

    <configuration>
       <manifestScope>compile</manifestScope>
       <manifestScope>test</manifestScope>
     </configuration>

This format of configuration is allowed by recent version of eclipse sisu since maven 3.1 under some circunstances. see [1].
The method finalizeMojoConfiguration(MojoExecution mojoExecution) from Maven30xRuntime is not considering it, resulting in a different configuration than expected.

A project that reproduce the problem can be found here [2].

[1] - http://blog.sonatype.com/2011/03/configuring-plugin-goals-in-maven-3/#.VdU-P7M2xC1
[2] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=475588

[cvgaviao]

@ifedorenko,
I identified were the problem is, but couldn't figure out how to fix it.

• First doubt: should we override finalizeMojoConfiguration method on Maven331Runtime class or modify the existent one at Maven30xRuntime?
• Second doubt: the flow of the finalizeMojoConfiguration method is based on mojoDescriptor.getParameters(). The execution configuration items that was set on test (manifestScope) does not appears on mojoDescriptor, but they outer container(manifestScopes). should we evaluate the parameter type ( whether it is a list), then calculate the singular name and compare with the execution configuration provided before add it to the finalConfiguration?