[
http://jira.codehaus.org/browse/MNG-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=187488#action_187488
]
Benjamin Bentmann commented on MNG-4162:
----------------------------------------
Olivier, we can't consume the patch as is. The problem is that the Site Plugin
heavily reuses the plugin manager. However, the plugin manager is coded to
support build plugins, i.e. makes certain assumptions about its use. With the
Site Plugin reusing it in its current form, we would for instance end up with
plugin realms for build and report plugins getting crippled and hard to debug
class loading errors during reactor builds.
I'm going to look into refactoring the plugin manager. I envision a little
layering where we have some general-purpose plugin management components on top
of which both the core's plugin manager and the Site Plugin's plugin manager
can easily support build plugins and report plugins, respectively.
> Removal of all reporting logic from the core of Maven
> -----------------------------------------------------
>
> Key: MNG-4162
> URL: http://jira.codehaus.org/browse/MNG-4162
> Project: Maven 2
> Issue Type: Improvement
> Reporter: Jason van Zyl
> Assignee: Benjamin Bentmann
> Fix For: 3.0
>
> Attachments: MNG-4162.patch
>
>
> Any reporting implementation will be implemented as a plugin. Maven will
> provide any information, APIs, and extension points to make this possible.
> But the conflation of building with reporting in the core makes it almost
> impossible for anyone two understand the distinction, makes it impossible to
> have alternate implementations and couple many tools like Doxia directly to
> the core which is unacceptable for Maven 3.x.
--
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
