You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Vincent Siveton (JIRA)" <ji...@codehaus.org> on 2007/11/03 11:15:10 UTC

[jira] Created: (MPIR-74) Move logic inside AbstractProjectInfoReport to maven-reporting-impl

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

        

[jira] Commented: (MPIR-74) Move logic inside AbstractProjectInfoReport to maven-reporting-impl

Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MPIR-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113011 ] 

Dennis Lundberg commented on MPIR-74:
-------------------------------------

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.

> 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

        

[jira] Commented: (MPIR-74) Move logic inside AbstractProjectInfoReport to maven-reporting-impl

Posted by "Vincent Siveton (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MPIR-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113012 ] 

Vincent Siveton commented on MPIR-74:
-------------------------------------

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
{noformat}
        getSink().head();
        getSink().text( "REPORT NAME" );
        getSink().head_();
{noformat}


> 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

        

[jira] Commented: (MNG-3346) Move logic inside AbstractProjectInfoReport to maven-reporting-impl

Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122692 ] 

Dennis Lundberg commented on MNG-3346:
--------------------------------------

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?

> Move logic inside AbstractProjectInfoReport to maven-reporting-impl
> -------------------------------------------------------------------
>
>                 Key: MNG-3346
>                 URL: http://jira.codehaus.org/browse/MNG-3346
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Plugin API
>    Affects Versions: 2.0.8
>            Reporter: Vincent Siveton
>            Priority: Blocker
>
> 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

        

[jira] Updated: (MNG-3346) Move logic inside AbstractProjectInfoReport to maven-reporting-impl

Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Lundberg updated MNG-3346:
---------------------------------

    Component/s: Plugin API

> Move logic inside AbstractProjectInfoReport to maven-reporting-impl
> -------------------------------------------------------------------
>
>                 Key: MNG-3346
>                 URL: http://jira.codehaus.org/browse/MNG-3346
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Plugin API
>    Affects Versions: 2.0.8
>            Reporter: Vincent Siveton
>            Priority: Blocker
>
> 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

        

[jira] Commented: (MNG-3346) Move logic inside AbstractProjectInfoReport to maven-reporting-impl

Posted by "Vincent Siveton (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120954 ] 

Vincent Siveton commented on MNG-3346:
--------------------------------------

first step in r614398

> Move logic inside AbstractProjectInfoReport to maven-reporting-impl
> -------------------------------------------------------------------
>
>                 Key: MNG-3346
>                 URL: http://jira.codehaus.org/browse/MNG-3346
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Plugin API
>    Affects Versions: 2.0.8
>            Reporter: Vincent Siveton
>            Priority: Blocker
>
> 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

        

[jira] Moved: (MNG-3346) Move logic inside AbstractProjectInfoReport to maven-reporting-impl

Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Lundberg moved MPIR-74 to MNG-3346:
------------------------------------------

    Affects Version/s:     (was: 2.1)
                       2.0.8
        Fix Version/s:     (was: 2.1)
                  Key: MNG-3346  (was: MPIR-74)
              Project: Maven 2  (was: Maven 2.x Project Info Reports Plugin)

> Move logic inside AbstractProjectInfoReport to maven-reporting-impl
> -------------------------------------------------------------------
>
>                 Key: MNG-3346
>                 URL: http://jira.codehaus.org/browse/MNG-3346
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Plugin API
>    Affects Versions: 2.0.8
>            Reporter: Vincent Siveton
>            Priority: Blocker
>
> 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

        

[jira] Moved: (MSHARED-31) Move logic inside AbstractProjectInfoReport to maven-reporting-impl

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MSHARED-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter moved MNG-3346 to MSHARED-31:
------------------------------------------

    Affects Version/s:     (was: 2.0.8)
          Component/s:     (was: Plugin API)
                       maven-reporting-impl
                  Key: MSHARED-31  (was: MNG-3346)
              Project: Maven Shared Components  (was: Maven 2)

> Move logic inside AbstractProjectInfoReport to maven-reporting-impl
> -------------------------------------------------------------------
>
>                 Key: MSHARED-31
>                 URL: http://jira.codehaus.org/browse/MSHARED-31
>             Project: Maven Shared Components
>          Issue Type: Improvement
>          Components: maven-reporting-impl
>            Reporter: Vincent Siveton
>            Priority: Blocker
>
> 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

        

[jira] Commented: (MPIR-74) Move logic inside AbstractProjectInfoReport to maven-reporting-impl

Posted by "Vincent Siveton (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MPIR-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113009 ] 

Vincent Siveton commented on MPIR-74:
-------------------------------------

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

> 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

        

[jira] Commented: (MPIR-74) Move logic inside AbstractProjectInfoReport to maven-reporting-impl

Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MPIR-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112992 ] 

Dennis Lundberg commented on MPIR-74:
-------------------------------------

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.

> 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

        

[jira] Commented: (MPIR-74) Move logic inside AbstractProjectInfoReport to maven-reporting-impl

Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
    [ 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