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

Centralize Maven reporting plugin configuration #141

Open
DavidWhitlock opened this issue Dec 25, 2015 · 2 comments
Open

Centralize Maven reporting plugin configuration #141

DavidWhitlock opened this issue Dec 25, 2015 · 2 comments

Comments

@DavidWhitlock
Copy link
Collaborator

Currently, there are a lot of duplicate reporting plugin declarations (jxr, jdepend, checkstyle, etc.) in various pom.xml files. As a result, when we update the version or configuration of one of these plugins, we have to modify a number of different places.

It looks like the reporting plugin configuration is inherited from the parent project. So, I should move as many of the configurations to the parent project as I can.

I've already done this with the findbugs, javadoc, and pmd plugins while addressing #44. So, I think it works fine.

@DavidWhitlock DavidWhitlock changed the title Central Maven reporting plugin configuration Centralize Maven reporting plugin configuration Dec 25, 2015
DavidWhitlock added a commit that referenced this issue Dec 25, 2015
…pdate to the latest version. This is related to issue #141.
@DavidWhitlock
Copy link
Collaborator Author

While I'm at it, I should make sure that the results of the integration tests (failsafe plugin) are included in the reports.

@DavidWhitlock
Copy link
Collaborator Author

Hmm. It looks like the surefire and failsafe reports are still not included in the site: http://davidwhitlock.github.io/PortlandStateJava/grader/project-reports.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant