Benjamin Bentmann wrote:
>
> Costin Caraivan wrote:
>
>> The invocation is from the pom.xml, inside a profile. So execution bound
>> to
>> a build lifecycle.
>
> Then consider to drop an example project in JIRA so we can have closer
> look and something to reproduce the issue. From the few bi
Costin Caraivan wrote:
The invocation is from the pom.xml, inside a profile. So execution bound to
a build lifecycle.
Then consider to drop an example project in JIRA so we can have closer
look and something to reproduce the issue. From the few bits given so
far, I have no idea what might be
Benjamin Bentmann wrote:
>
> Costin Caraivan wrote:
>
>> By the way, this works when I move the section in the
>> root
>> of the plugin.
>
> We have a (passing) IT [0] to test configuration which
> includes a Map parameter so I wonder how do you invoke your mojo in the
> first place? From
Costin Caraivan wrote:
By the way, this works when I move the section in the root
of the plugin.
We have a (passing) IT [0] to test configuration which
includes a Map parameter so I wonder how do you invoke your mojo in the
first place? From the command line? Per configurations have
by d
Costin Caraivan wrote:
>
> Hello,
>
> I have a plugin with the following configuration:
>
>
> com.axway.md
> com.axway.md
> ${project.version}
> zip
>
> aoleu
> aoleu
>
> This is inside an execution of my plugin.
>
> In my Mojo I have this:
> /**
> * @parameter
> * @required
Hello,
I have a plugin with the following configuration:
com.axway.md
com.axway.md
${project.version}
zip
aoleu
aoleu
This is inside an execution of my plugin.
In my Mojo I have this:
/**
* @parameter
* @required
*/
private Map featureId;
However, the featureId comes
