Maven project support JaCoCo Quarkus report
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 935
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 17
Description
### Description
By default, the JaCoCo extension for Quarkus generates the coverage report (HTML/XML/CSV format) in `target/jacoco-report/`.
Netbeans does not read `target/jacoco-report/jacoco.xml` to display the coverage in the source code or in `Code coverage > Show Report...` (right-click on the maven project).
However, by changing the Quarkus default path via `quarkus.jacoco.report-location=target/site/jacoco` in the `application.properties`, everything seems to work fine in Netbeans.
Here's an example of a simple project: https://github.com/philippefichet/netbeans-example-maven-quarkus-jacoco
I have identified the `java/maven.coverage/src/org/netbeans/modules/maven/coverage/MavenCoverageProvider.java` file which seems to be responsible for finding the `jacoco.xml` file, but I don't feel able to make the most appropriate modification
Could Netbeans be able to detect the report without having to modify the Quarkus default path?
But what about the case where `quarkus.jacoco.report-location` is informed?
PS: Everything works fine with a Gradle project (by default or by changing the `quarkus.jacoco.report-location` in the `application.properties file).
### Use case/motivation
- View code coverage in Netbeans without having to modify the Quarkus `application.properties` file
- View code coverage in Netbeans even if the value of `quarkus.jacoco.report-location` is set in the Quarkus `application.properties` file.
### Related issues
_No response_
### Are you willing to submit a pull request?
No
Contributor guide
Research direction
Start with java/maven.coverage/src/org/netbeans/modules/maven/coverage/MavenCoverageProvider.java and reproduce the issue using the linked Quarkus Maven example. Compare report discovery for target/jacoco-report/ and target/site/jacoco, including a configured quarkus.jacoco.report-location value; done means NetBeans can display coverage without requiring a path change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100