You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2010/11/12 12:53:03 UTC

[jira] Created: (MNG-4895) Plugins depending on 3rd party JARs that contain the Maven API can't be configured/run due to type incompatibilities

Plugins depending on 3rd party JARs that contain the Maven API can't be configured/run due to type incompatibilities
--------------------------------------------------------------------------------------------------------------------

                 Key: MNG-4895
                 URL: http://jira.codehaus.org/browse/MNG-4895
             Project: Maven 2 & 3
          Issue Type: Bug
          Components: Plugins and Lifecycle
    Affects Versions: 3.0, 2.2.1
            Reporter: Benjamin Bentmann


For communication between Maven core and plugins, the classes of the Maven API need to be loaded from the Maven core and not the plugin realm. Maven currently tries to accomplish this by filtering out plugin dependencies based on artifact coordinates. Despite the general maintenance issue when we refactor code/modules, this completely fails with errors like below when plugins depend on 3rd party JARs that contain a (non-relocated) copy of the Maven API as recently seen with Flex.

{noformat}
Caused by: org.codehaus.plexus.component.configurator.ComponentConfigurationException:
Cannot assign configuration entry 'project' to 'class org.apache.maven.project.MavenProject' from '${project}', which is of type class org.apache.maven.project.MavenProject
        at org.codehaus.plexus.component.configurator.converters.AbstractConfigurationConverter.fromExpression(AbstractConfigurationConverter.java:149)
        at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.fromConfiguration(ObjectWithFieldsConverter.java:80)
        at org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:247)
        at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:137)
        at org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent(BasicComponentConfigurator.java:56)
        at org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1357)
{noformat}

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Closed: (MNG-4895) Plugins depending on 3rd party JARs that contain the Maven API can't be configured/run due to type incompatibilities

Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann closed MNG-4895.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0.1
         Assignee: Benjamin Bentmann

Fixed in [r1034880|http://svn.apache.org/viewvc?view=revision&revision=1034880].

> Plugins depending on 3rd party JARs that contain the Maven API can't be configured/run due to type incompatibilities
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4895
>                 URL: http://jira.codehaus.org/browse/MNG-4895
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Plugins and Lifecycle
>    Affects Versions: 2.2.1, 3.0
>            Reporter: Benjamin Bentmann
>            Assignee: Benjamin Bentmann
>             Fix For: 3.0.1
>
>
> For communication between Maven core and plugins, the classes of the Maven API need to be loaded from the Maven core and not the plugin realm. Maven currently tries to accomplish this by filtering out plugin dependencies based on artifact coordinates. Despite the general maintenance issue when we refactor code/modules, this completely fails with errors like below when plugins depend on 3rd party JARs that contain a (non-relocated) copy of the Maven API as recently seen with Flex.
> {noformat}
> Caused by: org.codehaus.plexus.component.configurator.ComponentConfigurationException:
> Cannot assign configuration entry 'project' to 'class org.apache.maven.project.MavenProject' from '${project}', which is of type class org.apache.maven.project.MavenProject
>         at org.codehaus.plexus.component.configurator.converters.AbstractConfigurationConverter.fromExpression(AbstractConfigurationConverter.java:149)
>         at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.fromConfiguration(ObjectWithFieldsConverter.java:80)
>         at org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:247)
>         at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:137)
>         at org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent(BasicComponentConfigurator.java:56)
>         at org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1357)
> {noformat}

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira