Maven 1.x JCoverage Plugin

jcoverage fails when compile.src.set != pom.build.sourceDirectory

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 1.0.5
  • Labels:
    None
  • Number of attachments :
    0

Description

java.io.FileNotFoundException: /home/tplbuild/cruisecontrol/checkout/tr3/java/retriever/target/docs/jcoverage/au/com/tradingroom/retriever/capitaladjustment/package-frame.html (No such file or directory)
at java.io.FileOutputStream.open(Native Method)

I believe this occurs because the capitaladjustment package has its source in target/jaxb (generated code).

Possibly the best (only?) solution in the plugin is to use the compile.src.set path instead of the source directory, if jcoverage supports it.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Emmanuel Venisse added a comment -

OK, I'll fix this. JCoverage report tag doesn't support multiple source directory, so, I'll copy all dirs in one and use it for report.

Show
Emmanuel Venisse added a comment - OK, I'll fix this. JCoverage report tag doesn't support multiple source directory, so, I'll copy all dirs in one and use it for report.
Hide
Permalink
Matthias Kerkhoff added a comment -

We have stumbled into a related issue. Our project structure is
like this:

root/
project
project.xml
maven.xml
src
java
target
test

We are not able to use the jcoverage report. The problem
seems to be that we have changed our maven.junit.dir to
target/test and (at least) the jcoverage report seems to
be unable to handle such scenarios.
During jcoverage:report the plugin tries to access a file
root/project/jcoverage.ser. This file does not exist there.
It is actually present target/jcoverage.

Shall I open a separate issue on that?

Show
Matthias Kerkhoff added a comment - We have stumbled into a related issue. Our project structure is like this: root/ project project.xml maven.xml src java target test We are not able to use the jcoverage report. The problem seems to be that we have changed our maven.junit.dir to target/test and (at least) the jcoverage report seems to be unable to handle such scenarios. During jcoverage:report the plugin tries to access a file root/project/jcoverage.ser. This file does not exist there. It is actually present target/jcoverage. Shall I open a separate issue on that?
Hide
Permalink
Brett Porter added a comment -

done

Show
Brett Porter added a comment - done

People

  • Assignee:
    Brett Porter
    Reporter:
    Brett Porter
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: