[
http://jira.codehaus.org/browse/MPIR-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113131
]
Dennis Lundberg commented on MPIR-74:
-------------------------------------
But this has no effect on maven-project-info-reports-plugin. That is an issue
for the reporting-api and reporting-implementation. I still don't see why this
should hold up the release of MPIR. Other reporting plugins do not extend
classes from MPIR. It is only when the reporting-api/reporting-implementation
upgrades to doxia-1.0-alpha-9 that this would have any effect on other
reporting plugins.
> Move logic inside AbstractProjectInfoReport to maven-reporting-impl
> -------------------------------------------------------------------
>
> Key: MPIR-74
> URL: http://jira.codehaus.org/browse/MPIR-74
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Improvement
> Affects Versions: 2.1
> Reporter: Vincent Siveton
> Priority: Blocker
> Fix For: 2.1
>
>
> Due to doxia:1.0-alpha-9, the following methods need to be a part of
> maven-reporting-impl:
> private File getSkinArtifactFile();
> public void execute();
> So, it should be more easy to create a new report plugin.
--
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
