You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2009/05/16 16:43:44 UTC
[jira] Created: (MNG-4162) Removal of all reporting logic from the
core of Maven
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
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
[jira] Commented: (MNG-4162) Removal of all reporting logic from
the core of Maven
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=242123#action_242123 ]
Dennis Lundberg commented on MNG-4162:
--------------------------------------
Christopher, the Site Plugin for Maven 3 has a built-in converter, that is able to read the <reporting> section of a POM and convert it into the new model used in Maven 3. So it is possible to use <reporting> with Maven 3. Read more on the Site Plugin 3.x site:
http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/maven-3.html
> Removal of all reporting logic from the core of Maven
> -----------------------------------------------------
>
> Key: MNG-4162
> URL: http://jira.codehaus.org/browse/MNG-4162
> Project: Maven 2 & 3
> Issue Type: Improvement
> Reporter: Jason van Zyl
> Assignee: Benjamin Bentmann
> Fix For: 3.0-beta-1
>
> 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
[jira] Commented: (MNG-4162) Removal of all reporting logic from
the core of Maven
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=186003#action_186003 ]
Olivier Lamy commented on MNG-4162:
-----------------------------------
So it looks to works fine now.
Please review core branches.
Note no huge hack has been added only new methods.
Please review before merging.
Thanks
> 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
> Fix For: 3.0
>
>
> 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
[jira] Commented: (MNG-4162) Removal of all reporting logic from
the core of Maven
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MNG-4162) Removal of all reporting logic from
the core of Maven
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198358#action_198358 ]
Jason van Zyl commented on MNG-4162:
------------------------------------
This is all done isn't it, the site plugin just doesn't work 100% right?
> 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-alpha-5
>
> 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
[jira] Closed: (MNG-4162) Removal of all reporting logic from the
core of Maven
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-4162.
----------------------------------
Resolution: Fixed
The converter of the <reporting> section is finished and the new Site Plugin is flipped over to use its own configuration, ITs look good.
> Removal of all reporting logic from the core of Maven
> -----------------------------------------------------
>
> Key: MNG-4162
> URL: http://jira.codehaus.org/browse/MNG-4162
> Project: Maven 2 & 3
> Issue Type: Improvement
> Reporter: Jason van Zyl
> Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-8
>
> 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
[jira] Updated: (MNG-4162) Removal of all reporting logic from the
core of Maven
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl updated MNG-4162:
-------------------------------
Fix Version/s: (was: 3.0)
3.0-alpha-3
> 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-alpha-3
>
> 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
[jira] Commented: (MNG-4162) Removal of all reporting logic from
the core of Maven
Posted by "Christopher Hunt (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=242017#action_242017 ]
Christopher Hunt commented on MNG-4162:
---------------------------------------
Am I correct in assuming that the 2.x reporting section of a pom file is completely incompatible with Maven 3? This has been my observation at least, and I suspect that it will impact on the uptake of Maven 3. I understand the motivation in factoring out the report plugin from core, but I would favour deprecation of the reporting section in the pom over removal in order to have Maven 3 become widely adopted.
> Removal of all reporting logic from the core of Maven
> -----------------------------------------------------
>
> Key: MNG-4162
> URL: http://jira.codehaus.org/browse/MNG-4162
> Project: Maven 2 & 3
> Issue Type: Improvement
> Reporter: Jason van Zyl
> Assignee: Benjamin Bentmann
> Fix For: 3.0-beta-1
>
> 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
[jira] Updated: (MNG-4162) Removal of all reporting logic from the
core of Maven
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl updated MNG-4162:
-------------------------------
Fix Version/s: 3.0
> 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
> Fix For: 3.0
>
>
> 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
[jira] Commented: (MNG-4162) Removal of all reporting logic from
the core of Maven
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185792#action_185792 ]
Olivier Lamy commented on MNG-4162:
-----------------------------------
The approach used creating for each report plugin : creating a new ClassRealm with parent maven-site-plugin-realm with parent core realm.
Following imported from maven-site-plugin realm :
- org.apache.maven.reporting.MavenReport
- org.codehaus.doxia.sink.Sink
- org.apache.maven.doxia.sink.Sink
- org.apache.maven.doxia.sink.SinkEventAttributes
Note need to add org.apache.maven.artifact.manager.WagonConfigurationException in compat.
So I now have the famous issue with :
{code}
... 15 more
Caused by: java.lang.NoSuchMethodError: org.codehaus.plexus.PlexusContainer.getLoggerManager()Lorg/codehaus/plexus/logging/LoggerManager;
at org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:222)
at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:90)
at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:145)
... 19 more
{code}
> 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
> Fix For: 3.0
>
>
> 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
[jira] Commented: (MNG-4162) Removal of all reporting logic from
the core of Maven
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185780#action_185780 ]
Olivier Lamy commented on MNG-4162:
-----------------------------------
I have commit stuff in core branch.
No big chance only new methods and some move from private to public.
No objections to merge to trunk ?
> 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
> Fix For: 3.0
>
>
> 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
[jira] Commented: (MNG-4162) Removal of all reporting logic from
the core of Maven
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198367#action_198367 ]
Olivier Lamy commented on MNG-4162:
-----------------------------------
I have to review the its and understand the failures. (https://grid.sonatype.org/ci/view/Maven%203.0.x/job/maven-site-plugin-3.x/).
It looks something has changed (in classworld I think) and now some reporting plugins breaks.
But I haven't yet investigated.
> 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-alpha-5
>
> 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
[jira] Updated: (MNG-4162) Removal of all reporting logic from the
core of Maven
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy updated MNG-4162:
------------------------------
Attachment: MNG-4162.patch
merge from branch MNG-4162
> 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
> 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
[jira] Commented: (MNG-4162) Removal of all reporting logic from
the core of Maven
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=188696#action_188696 ]
Olivier Lamy commented on MNG-4162:
-----------------------------------
first part of this working. Currently only for "simple" report plugins.
Now we have to work with complicated report plugins which fork lifecycle (surefire report, cobertura).
> 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
[jira] Commented: (MNG-4162) Removal of all reporting logic from
the core of Maven
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185579#action_185579 ]
Olivier Lamy commented on MNG-4162:
-----------------------------------
branches started :
- core : https://svn.apache.org/repos/asf/maven/components/branches/MNG-4162/
- site plugin : https://svn.apache.org/repos/asf/maven/plugins/branches/maven-site-plugin-3.x
> 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
> Fix For: 3.0
>
>
> 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
[jira] Commented: (MNG-4162) Removal of all reporting logic from
the core of Maven
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185990#action_185990 ]
Olivier Lamy commented on MNG-4162:
-----------------------------------
note [rev 800978|http://svn.apache.org/viewvc?view=rev&revision=800978] is needed for be able to use maven-project-info-reports-plugin.
> 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
> Fix For: 3.0
>
>
> 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
[jira] (MNG-4162) Removal of all reporting logic from the core of
Maven
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MNG-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy updated MNG-4162:
-------------------------------
Description: 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 to 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. (was: 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.)
> Removal of all reporting logic from the core of Maven
> -----------------------------------------------------
>
> Key: MNG-4162
> URL: https://jira.codehaus.org/browse/MNG-4162
> Project: Maven 2 & 3
> Issue Type: Improvement
> Reporter: Jason van Zyl
> Assignee: Benjamin Bentmann
> Fix For: 3.0-beta-1
>
> 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 to 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, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira