[jira] Commented: (MNG-1621) Explain system scope for dependencies
[ http://jira.codehaus.org/browse/MNG-1621?page=comments#action_51344 ] Julien Kirch commented on MNG-1621: --- small typos : * "depedency" instead of "dependency" * Each of the scopes affects -> no s > Explain system scope for dependencies > - > > Key: MNG-1621 > URL: http://jira.codehaus.org/browse/MNG-1621 > Project: Maven 2 > Type: Improvement > Components: documentation - guides > Reporter: Boris Boehlen > Assignee: Jason van Zyl > Priority: Minor > Attachments: introduction-to-dependency-mechanism.apt.patch > > > The documentation under the URL > "guides/introduction/introduction-to-dependency-mechanism.html" should > explain the system scope. > I'll propose a patch which updates the guide accordingly. The table > describing the relationships between the different scope is NOT updated by > the patch. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPCLOVER-35) projects that don't have clover data does not produce reports
[ http://jira.codehaus.org/browse/MPCLOVER-35?page=comments#action_40243 ] Julien Kirch commented on MPCLOVER-35: -- As a consequences, when we have no test case the clover report is generated and the link to it added to the site (linking to a page with no usable data at all, changing the MPCLOVER-21 bahavior), if the report generation is not a requesdite, would it be possible to at least remove the link ? > projects that don't have clover data does not produce reports > - > > Key: MPCLOVER-35 > URL: http://jira.codehaus.org/browse/MPCLOVER-35 > Project: maven-clover-plugin > Type: Bug > Versions: 1.8 > Reporter: Eric Lapierre > Assignee: Vincent Massol > Fix For: 1.9 > Attachments: clover_patch.zip > > > Some projects have java code but does not have any testcases, so the coverage > is 0% and the number of line is != 0. However, because there was no coverage > data collected, no clover report is generated. > We therefore don't see the number of line of java code in the dashboard > report when there are no junit testcases for that project. > Clover provides a flag to generate the reports even though there is not > coverage data. > alwaysReport="true" -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPCLOVER-39) Sources file should not be instrumented when no test file is present
Sources file should not be instrumented when no test file is present Key: MPCLOVER-39 URL: http://jira.codehaus.org/browse/MPCLOVER-39 Project: maven-clover-plugin Type: Improvement Versions: 1.9 Environment: mavan 1.0.1 clover plugin 1.9 Reporter: Julien Kirch I have a project with no test file (it's a set of test classes we want to reuse and NO we don't test the tests) when building the project's site : ***snip [javac] loaded from: C:\maven-1.0.1\repository\clover\jars\clover-1.3.6.jar [javac] 30 day Evaluation Version distributed via the Maven Jar Repository. [javac] Clover is not free. You have 30 days to evaluate it. After this, please visit http://www.cenqua.com to obtain a licensed version of Clover [javac] No coverage database 'C:\yourNameHere\target\clover\database\clover_coverage.db' found. Creating a fresh one. [javac] Clover all over. Instrumented 80 file. ***snip as there's no test to execute, clovering the source is a pure loss of time, the plugin should check 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPCLOVER-38) Error in clover plugin v1.9
Error in clover plugin v1.9 --- Key: MPCLOVER-38 URL: http://jira.codehaus.org/browse/MPCLOVER-38 Project: maven-clover-plugin Type: Bug Versions: 1.9 Environment: maven 1.0.1 clover plugin 1.9 Reporter: Julien Kirch maven clean java:compile clover -Dmaven.test.skip=true BUILD FAILED File.. c:\maven-1.0.1\cache\maven-clover-plugin-1.9\plugin.jelly Element... maven:set Line.. 226 Column 42 You must define an attribute called 'value' for this tag. Total time: 5 seconds Finished at: Tue May 24 09:03:13 CEST 2005 -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPPMD-15) Upgrade pmd version to 3.0
Upgrade pmd version to 3.0 -- Key: MPPMD-15 URL: http://jira.codehaus.org/browse/MPPMD-15 Project: maven-pmd-plugin Type: Improvement Versions: 1.6 Reporter: Julien Kirch Current mpd version is 1.9, please update to 3.0, new version includes the usual stuff (new rules, optimizations and so on) API didn't changed, only dependency version change seems to be required. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
