[ 
http://jira.codehaus.org/browse/MPJCOVERAGE-18?page=comments#action_31759 ]
     
Erik Forkalsrud commented on MPJCOVERAGE-18:
--------------------------------------------

I tried the patch and it works pretty well.  However, the additional html files 
it generates don't seem to be linked from the allcallses-frame.html and 
package-frame.html files.  I was able to fix that by using the 
getShortFileName() method on line 187 (CoverageReport.java) and remove the 
if-statement following it, so all classes get listed.  I updated the patch, but 
I havent figured out how to put it in JIRA. (it's at 
http://forkalsrud.org/~erik/JCoveragePatch2.txt for now)


Also, setting up a developer environment for maven plugins turned out to be 
pretty simple.  I did this using eclipse with these steps:

  1 - File->Import...  --  "Checkout Projects from CVS"
  2 - Select: "Create a new repository location"
  3 - Enter values:
         Host            == cvs.apache.org
         Repository Path == /home/cvspublic
         User            == anoncvs
         Connection Type == pserver
  4 - Select: User specified module name: "maven-plugins/jcoverage"
  5 - Select: "Check out as project configured using the New Project Wizard"
  6 - Select: "HEAD" and "Finish"
  7 - Now, go though the regular eclipse project wizard.
      I use MevenIde (http://mevenide.codehaus.org/) to add "Maven Nature" to
      the project and cofigure all jars through the POM Synchronizer
  8 - Go through steps 1-7, again, but this time, check out the module 
      "maven-plugins/plugin-parent"
      (Also, you can "use an existing repoitory location" this time i.e. the
      one you created in step 3)
  9 - Right-click on CoverageReport.java and select: Team->Apply Patch...
      to apply JCoveragePatch.txt
 10 - Go to your eclipse workspace folder where the jcoverage plugin is,
      and type "maven plugin:install" to try out your code changes.


> Inner/anonymous classes report uncomplete
> -----------------------------------------
>
>          Key: MPJCOVERAGE-18
>          URL: http://jira.codehaus.org/browse/MPJCOVERAGE-18
>      Project: maven-jcoverage-plugin
>         Type: Bug
>     Versions: 1.0.8
>     Reporter: Daniel Frey
>     Assignee: Emmanuel Venisse
>      Fix For: 1.0.10
>  Attachments: JCoveragePatch.txt
>
>
> Since I use maven (1.0b8 or so) up to now (1.0) I observe that the JCoverage 
> plugin does produce wrong results for inner/anonymous classes. I.e. I have 
> got a class called ClassOne, which has an anonymouls inner class. The two 
> classes are displayed in the coverage report as ClassOnewith 44% and 
> ClassOne$1 with 0% tested, which is correct. The underlining reference to the 
> html-file is in both cases the same. However, the file displays only the 
> coverage of the inner class, the outer class does not contain any counts, red 
> or green lines. 
>  
> I doublechecked whether the coverage.xml file contains the corresponding 
> values, which it does. So it seems to be a problem of the plugin itself.

-- 
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]

Reply via email to