You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Igor Fedorenko (JIRA)" <ji...@codehaus.org> on 2011/02/04 21:17:22 UTC
[jira] Created: (MNG-5003) MavenPluginManager serves m2e partially
initialized mojo descriptors in some cases
MavenPluginManager serves m2e partially initialized mojo descriptors in some cases
----------------------------------------------------------------------------------
Key: MNG-5003
URL: http://jira.codehaus.org/browse/MNG-5003
Project: Maven 2 & 3
Issue Type: Bug
Components: Reactor and workspace
Affects Versions: 3.0.2, 3.0.1, 3.0
Reporter: Igor Fedorenko
Not sure if this affect command line maven, but m2e sometimes gets MojoDescriptor instances with null classRealm and implementationClass. Looks like the problem has to do with incomplete plugin descriptor setup when after reused cached plugin realm. I'll try to provide a fix and corresponding unit test.
--
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-5003) MavenPluginManager serves m2e partially
initialized mojo descriptors in some cases
Posted by "Igor Fedorenko (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Fedorenko closed MNG-5003.
-------------------------------
Resolution: Fixed
Fixed. http://svn.apache.org/viewvc?view=revision&revision=1067279
> MavenPluginManager serves m2e partially initialized mojo descriptors in some cases
> ----------------------------------------------------------------------------------
>
> Key: MNG-5003
> URL: http://jira.codehaus.org/browse/MNG-5003
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Reactor and workspace
> Affects Versions: 3.0, 3.0.1, 3.0.2
> Reporter: Igor Fedorenko
> Assignee: Igor Fedorenko
> Fix For: 3.0.3
>
>
> Not sure if this affect command line maven, but m2e sometimes gets MojoDescriptor instances with null classRealm and implementationClass. Looks like the problem has to do with incomplete plugin descriptor setup when after reused cached plugin realm. I'll try to provide a fix and corresponding unit test.
--
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] Updated: (MNG-5003) MavenPluginManager serves m2e partially
initialized mojo descriptors in some cases
Posted by "Igor Fedorenko (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Fedorenko updated MNG-5003:
--------------------------------
Fix Version/s: 3.0.3
Assignee: Igor Fedorenko
> MavenPluginManager serves m2e partially initialized mojo descriptors in some cases
> ----------------------------------------------------------------------------------
>
> Key: MNG-5003
> URL: http://jira.codehaus.org/browse/MNG-5003
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Reactor and workspace
> Affects Versions: 3.0, 3.0.1, 3.0.2
> Reporter: Igor Fedorenko
> Assignee: Igor Fedorenko
> Fix For: 3.0.3
>
>
> Not sure if this affect command line maven, but m2e sometimes gets MojoDescriptor instances with null classRealm and implementationClass. Looks like the problem has to do with incomplete plugin descriptor setup when after reused cached plugin realm. I'll try to provide a fix and corresponding unit test.
--
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