[MPLUGIN-163] Mojo parameters defined in abstract-mojo class not set, when concrete/abstract mojo class in different JARs

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.5.1
• Component/s: maven-plugin-tools-java

Environment

Maven-2.0.2 (also in Maven-2.0.1)

Win-XP/Pro - Cygwin

$ java -version
java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode, sharing)

• Assignee: Benjamin Bentmann
• Reporter: Shash Chatterjee
• Created: 18/Jan/06 16:32
• Updated: 18/Dec/09 04:25
• Resolved: 18/Dec/09 04:25

Description

Have an abstract mojo class, which extends AbstractMojo. This abstract class defines some mojo parameters with expressions to set default values.

Have a concrete class, in the same project (JAR) and package, which simply extends the abstract mojo class. This works fine, in that the parameter values are initialized correctly.

Have an identical concrete class, but this time in a different project which defines a Maven dependency on the previous JAR. This time the parameters defined in the abstract class are not initialized correctly. Whether this second concrete mojo is in the same Java package as the abstract class, or not, does not seem to make a difference.

I have attached a ZIP file which demonstrates the problem. Included are three very simple Maven modules, all created with "mvn archetype:create". The first project, "testplugin-one" contains an abstract and a concrete Mojo class. The second project, "testplugin-two" contains just a concrete Mojo class. The third project "testplugin-driver" contains a POM that invokes the two mojos: the first time the parameters have values, the second time they are null.

Issue Links

• duplicates: MPLUGIN-56 Inter-plugin Mojo inheritance