Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make org.jacoco:jacoco-maven-plugin compatible to maven 4.x #1480

Closed
joergsesterhenn opened this issue Jun 13, 2023 · 1 comment
Closed

make org.jacoco:jacoco-maven-plugin compatible to maven 4.x #1480

joergsesterhenn opened this issue Jun 13, 2023 · 1 comment
Labels
declined: duplicate ❌ This issue or pull request already exists type: enhancement

Comments

@joergsesterhenn
Copy link

THIS IS A BUG TRACKER ONLY. FOR QUESTIONS PLEASE CHECK FAQ OR USE FORUM:

http://www.jacoco.org/jacoco/trunk/doc/faq.html

https://groups.google.com/forum/?fromgroups=#!forum/jacoco

Please understand that
ISSUES WITHOUT FOLLOWING INFORMATION WILL BE CLOSED WITHOUT COMMENTS!
Thank you for filling feature request!

Scenario

  • JaCoCo version: 0.8.10
  • Operating system: windows
  • Tool integration: Maven
  • Description of your use case: create coverage data for sonarqube

Current Behaviour

when running project using the current version of the above maven-plugin maven 3.9.2 gives a plugin validation error like this:

[WARNING] Plugin validation issues were detected in 1 plugin(s)
[WARNING] 
[WARNING]  * org.jacoco:jacoco-maven-plugin:0.8.10

Wanted Behaviour

make plugin compatible to remove warning

Possible Workarounds

More info (taken from https://maven.apache.org/docs/3.9.2/release-notes.html )

Plugin validation warnings change: they are not littered in console log anymore, but are collected and reported at the build end. Moreover, the validation checks have been extended, more warnings are to be expected if build contains plugins that may not work with upcoming Maven 4. The build end validation report verbosity can be controlled by maven.plugin.validation property values “brief”, “default” and “verbose”. The validation report cannot be turned off, only by not having validation issues in the build, when the report is not shown. See MNG-7712, MNG-7754 and MNG-7767. Almost all of the ASF Maven plugins have been released with fixes to get rid of warnings, updating them is recommended. See Available Plugins page for current plugin versions. For non-ASF plugins, contact plugin maintainers to apply required changes.

@Godin
Copy link
Member

Godin commented Jun 13, 2023

Duplicate of #1435

@Godin Godin marked this as a duplicate of #1435 Jun 13, 2023
@Godin Godin closed this as completed Jun 13, 2023
@Godin Godin added the declined: duplicate ❌ This issue or pull request already exists label Jun 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
declined: duplicate ❌ This issue or pull request already exists type: enhancement
Projects
None yet
Development

No branches or pull requests

2 participants