-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Automate jpeek analisys with maven plugin #274
Comments
@paulodamaso/z this project will fix the problem faster if you donate a few dollars to it; just click here and pay via Stripe, it's very fast, convenient and appreciated; thanks a lot! |
@paulodamaso I like the idea |
@0crat assign me |
@paulodamaso/z this job was assigned to you 5days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please. |
For #274: jPeek maven plugin setup
The user @paulodamaso/z resigned from #274, please stop working. Reason for job resignation: It is older than 10 days, see §8 |
@paulodamaso I'm not sure why 0crat assigned me this, maybe you should refuse then out it |
@0crat refuse |
@paulodamaso The user @victornoel/z resigned from #274, please stop working. Reason for job resignation: Order was cancelled |
@0crat out |
@paulodamaso Job |
jpeek
should provide an maven plugin so we could run it automatically on each build.Proposed features:
jpeek-maven-plugin
to be configured on projectpom.xml
file, and will collect metrics on maven builds (similar toqulice-maven-plugin
), saving it from some directory on build pathjpeek-maven-plugin
will allow to set target values from cohesion metrics and will check report files generated on execution. Build can be configured to fail when target values are not metqulice
/checkstyle
/PMD
plugins;The text was updated successfully, but these errors were encountered: