Hi Justin, it looks like it works if the two classes are inside the same project, but not if B inherits from a class in another plugin...
It looks like a bug... or can anyone see any reason for it? Ste On Wed, Jan 6, 2010 at 10:25 PM, Justin Edelson <justinedel...@gmail.com> wrote: > Are A and B in the same JAR file? If so, this should work. If you look at > just about any core plugin, it depends upon this working. For example: > > http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-install-plugin/src/main/java/org/apache/maven/plugin/install/InstallMojo.java > > extends > http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-install-plugin/src/main/java/org/apache/maven/plugin/install/AbstractInstallMojo.java > > Justin > > On Wed, Jan 6, 2010 at 3:54 PM, Stefano Fornari > <stefano.forn...@gmail.com>wrote: > >> Hi All, >> I am developing a mojo A and I would like to extend it with a subclass >> mojo B. I declared the project property in A and when the mojo >> executes, the property is correctly set. I expected the same behaviour >> for B, but it looks like it does not work. If I do not declare the >> project field in B, the maven project object is not set. >> Is this the normal behaviour? Is there a way to inherit mojo >> configuration parameters? >> >> Thanks in advance. >> >> -- >> Ste >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> > -- Ste --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
