Are you saying that we can't release maven-pir-plugin 2.1 until this is fixed? Otherwise I would like to push this issue to the next release.

The main goal of this issue was how to create a new MavenReport (which extends AbstractMavenReport) with new Doxia dependency. The main pb that I found is how to use the correct sink.
If you release MPIRP like this, I guess that we need to copy and paste these methods in all reports which will be bumped to Doxia:1.0-alpha-9

Do you mean reports within the maven-pir-plugin or other reports?

This plugin builds and runs fine as it is now, with doxia 1.0-alpha-9. I don't see what the problem is.

The main pb is not in the MPIR (works fine) but in all report pending plugins. We need to extract this logic somewhere to avoid copy/paste.

Just try to create a new report plugin with doxia:1.0-alpha-9 and specify the following content

        getSink().head();
        getSink().text( "REPORT NAME" );
        getSink().head_();

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.

first step in r614398

I think that I understand the problem now. Would you mind having a look over at MCHANGES-88 and see if it is this problem that we're hitting there?