maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <>
Subject [jira] Closed: (MNG-4479) [regression] Project-level plugin dependencies ignored for direct CLI invocation if plugin key uses properties
Date Mon, 07 Dec 2009 00:12:55 GMT


Benjamin Bentmann closed MNG-4479.

       Resolution: Fixed
    Fix Version/s: 3.0-alpha-2

The problem is related to interpolation. As such a workaround is to use a constant value for
the group-/artifactId of the plugin, i.e. your test project passes if you replace {{<groupId>${project.groupId}</groupId>}}
with {{<groupId>mavenbugs</groupId>}} in the plugin declaration.

> [regression] Project-level plugin dependencies ignored for direct CLI invocation if plugin
key uses properties
> --------------------------------------------------------------------------------------------------------------
>                 Key: MNG-4479
>                 URL:
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Class Loading, Dependencies, Plugins and Lifecycle
>    Affects Versions: 2.1.0-M1, 2.1.0, 2.2.0, 2.2.1
>            Reporter: Laird Nelson
>            Assignee: Benjamin Bentmann
>             Fix For: 3.0-alpha-2
>         Attachments:
> I have a plugin that makes use of the implementation attribute in its configuration.
 That is, one of its parameters is a plexus tag that specifies an implementation class to
> The implementation class comes from a jar that is the plugin's dependency, but that dependency
is included as part of the plugin configuration, not as part of the stock plugin.
> This setup works fine when I bind the plugin's configuration via an execution to a normal
phase (generate-sources as it happens).
> When I bind the plugin's configuration to the default-cli execution, plexus cannot configure
the component, claiming that the classname it encounters in the "implementation" attribute
cannot be found (even though, again, if I bind it to the generate-sources phase instead, via
another execution, same configuration, everything works fine.
> I tried to debug this using mvn -X, but the output was totally baffling; sorry.  My raw
take is that it looks like dependency resolution in the default-cli execution is somehow performed
differently than when the plugin is run bound to a phase.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message