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 bits given so
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
Benjamin Bentmann wrote:
Costin Caraivan wrote:
By the way, this works when I move the configuration section in the
root
of the plugin.
We have a (passing) IT [0] to test execution configuration which
includes a Map parameter so I wonder how do you invoke your mojo in the
first
Hello,
I have a plugin with the following configuration:
configuration
featureId
groupIdcom.axway.md/groupId
artifactIdcom.axway.md/artifactId
version${project.version}/version
typezip/type
/featureId
pluginsUnpackFolderaoleu/pluginsUnpackFolder
featuresUnpackFolderaoleu/featuresUnpackFolder
Costin Caraivan wrote:
Hello,
I have a plugin with the following configuration:
configuration
featureId
groupIdcom.axway.md/groupId
artifactIdcom.axway.md/artifactId
version${project.version}/version
typezip/type
/featureId
pluginsUnpackFolderaoleu/pluginsUnpackFolder
Costin Caraivan wrote:
By the way, this works when I move the configuration section in the root
of the plugin.
We have a (passing) IT [0] to test execution configuration which
includes a Map parameter so I wonder how do you invoke your mojo in the
first place? From the command line? Per
