When you don't specify the value in the POM you are *effectively*[1]
specifying ${demoName}
So what you have done is disabled configuration via the CLI.
[1] I say *effectively* because if you did configure that and the property
was undefined then that explicit configuration would evaluate to the
Hi,
I am facing an issue I really did not expect, where a plugins
parameters in the POM take precedence over CLI –Dparam=value parameter values.
My plugin takes a string parameter:
@Mojo(name = "showValue", requiresProject = true, aggregator = true,
defaultPhase = LifecyclePhase.PACKAGE, threa
