You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Allen (JIRA)" <ji...@codehaus.org> on 2006/05/16 21:18:41 UTC
[jira] Created: (MCLOVER-37) clover does not work with site:run
clover does not work with site:run
----------------------------------
Key: MCLOVER-37
URL: http://jira.codehaus.org/browse/MCLOVER-37
Project: Maven 2.x Clover Plugin
Type: Bug
Versions: 2.1
Reporter: John Allen
Priority: Minor
Don't know if this is by design or a known issue and it's probably a big ask but i thought i'd mention it
--
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: (MCLOVER-37) clover does not work with site:run
Posted by "John Allen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCLOVER-37?page=comments#action_65566 ]
John Allen commented on MCLOVER-37:
-----------------------------------
Hi Brett,
So the issue with site:run goes beyond the report simply being dependent upon a pre-site mojo being run?
The assumption that reports will be run as part of the site phase means that site:stage and any other future site:mojos that invoke reports will not work as the site phase is not actually being invoked. Am I correct in this? And if I am I don't think this is a healthy way to go in the development of reports, to me its an unenforcable and error prone coupling.
> clover does not work with site:run
> ----------------------------------
>
> Key: MCLOVER-37
> URL: http://jira.codehaus.org/browse/MCLOVER-37
> Project: Maven 2.x Clover Plugin
> Type: Bug
> Versions: 2.1
> Reporter: John Allen
> Assignee: Vincent Massol
> Priority: Minor
>
>
> Don't know if this is by design or a known issue and it's probably a big ask but i thought i'd mention it
--
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: (MCLOVER-37) clover does not work with site:run
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCLOVER-37?page=comments#action_65527 ]
Brett Porter commented on MCLOVER-37:
-------------------------------------
it's a documented limitation of site:run. External reports do will not currently link correctly. Probably by 2.0 - I think it's already in the MSITE JIRA.
> clover does not work with site:run
> ----------------------------------
>
> Key: MCLOVER-37
> URL: http://jira.codehaus.org/browse/MCLOVER-37
> Project: Maven 2.x Clover Plugin
> Type: Bug
> Versions: 2.1
> Reporter: John Allen
> Assignee: Vincent Massol
> Priority: Minor
>
>
> Don't know if this is by design or a known issue and it's probably a big ask but i thought i'd mention it
--
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: (MCLOVER-37) clover does not work with site:run
Posted by "Julien HENRY (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCLOVER-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91684 ]
Julien HENRY commented on MCLOVER-37:
-------------------------------------
Can you please give me the link to the related maven-site-plugin issue? I still have the problem with site:stage.
> clover does not work with site:run
> ----------------------------------
>
> Key: MCLOVER-37
> URL: http://jira.codehaus.org/browse/MCLOVER-37
> Project: Maven 2.x Clover Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: John Allen
> Assigned To: Vincent Massol
> Priority: Minor
>
> Don't know if this is by design or a known issue and it's probably a big ask but i thought i'd mention it
--
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: (MCLOVER-37) clover does not work with site:run
Posted by "John Allen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCLOVER-37?page=comments#action_65524 ]
John Allen commented on MCLOVER-37:
-----------------------------------
Hi Vincent,
The site plugin has 3 Mojos which generate a site
http://maven.apache.org/plugins/maven-site-plugin/plugin-info.html
site:site Generates the project site.
site:run Start the site up, rendering documents as requested for fast editing.
site:stage Generate and then staging a site in specific directory.
Thus one can not assume that reports will be as part of the site phase.
There is no nice solution to this beyond fixing the core issue that prevented you from performing the required activities from the report forked instrumentation and test lifecycle.
May be we could separate out the two aspects of the system, the old behaviour which worked well and abided by the standard maven report appraoch (of being self contained) and this new stuff, maybe under a different name.
In regards to output, say for site:stage or even site:site you simply get the 'there is no clover database, not generating report' because the instrumentation mojo hasnt been run becuase site:stage != site.
> clover does not work with site:run
> ----------------------------------
>
> Key: MCLOVER-37
> URL: http://jira.codehaus.org/browse/MCLOVER-37
> Project: Maven 2.x Clover Plugin
> Type: Bug
> Versions: 2.1
> Reporter: John Allen
> Assignee: Vincent Massol
> Priority: Minor
>
>
> Don't know if this is by design or a known issue and it's probably a big ask but i thought i'd mention it
--
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: (MCLOVER-37) clover does not work with site:run
Posted by "Vincent Massol (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCLOVER-37?page=comments#action_65517 ]
Vincent Massol commented on MCLOVER-37:
---------------------------------------
What is site:run?
Could you provide the console output you're getting?
> clover does not work with site:run
> ----------------------------------
>
> Key: MCLOVER-37
> URL: http://jira.codehaus.org/browse/MCLOVER-37
> Project: Maven 2.x Clover Plugin
> Type: Bug
> Versions: 2.1
> Reporter: John Allen
> Priority: Minor
>
>
> Don't know if this is by design or a known issue and it's probably a big ask but i thought i'd mention it
--
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: (MCLOVER-37) clover does not work with site:run
Posted by "Vincent Massol (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCLOVER-37?page=all ]
Vincent Massol closed MCLOVER-37:
---------------------------------
Resolution: Won't Fix
Not an issue with the clover plugin. Brett said it's a documented limitation of the site:run mojo which doesn't currently support external reports.
> clover does not work with site:run
> ----------------------------------
>
> Key: MCLOVER-37
> URL: http://jira.codehaus.org/browse/MCLOVER-37
> Project: Maven 2.x Clover Plugin
> Type: Bug
> Versions: 2.1
> Reporter: John Allen
> Assignee: Vincent Massol
> Priority: Minor
>
>
> Don't know if this is by design or a known issue and it's probably a big ask but i thought i'd mention it
--
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