I ran into this while experimenting with the dependency-maven-plugin.
dependency-maven-plugin has an abstract class (AbstractFromDependenciesMojo)
that, in turn, extends AbstractMojo.  The abstract class defines various
fields which the Maven plugin system is supposed to inject.

I created a separate plugin which declares a dependency in the POM on the
dependency-maven-plugin, and then provided a concrete Mojo extending
AbstractFromDependenciesMojo.  When I run my plugin, all the fields defined
in the abstract class are null.  If I move my concrete Mojo class into the
dependency-maven-plugin directly, without any other changes at all, then all
the fields are set correctly.  Alternatively, if I copy the abstract class
directly in my plugin  (and rename the package to avoid the duplication), it
seems to work.

Is this something I am doing incorrectly, or is this a known issue?

Thanks,
Shash

Reply via email to