Skip to content

Conversation

@adangel
Copy link
Member

@adangel adangel commented Sep 3, 2021

This PR adds a couple of new goals for creating aggregated reports:

  • aggregate-pmd
  • aggregate-pmd-no-fork
  • aggregate-pmd-check

This fixes MPMD-283

It uses the same logic as the javadoc plugin, e.g. the aggregate* goals create aggregated reports on every level and not just on the top level.

The old mechanism with the property aggregate=true is still preserved, but deprecated.

Following this checklist to help us incorporate your
contribution quickly and easily:

  • Make sure there is a JIRA issue filed
    for the change (usually before you start working on it). Trivial changes like typos do not
    require a JIRA issue. Your pull request should address just this issue, without
    pulling in other changes.
  • Each commit in the pull request should have a meaningful subject line and body.
  • Format the pull request title like [MPMD-XXX] - Subject of the JIRA Ticket,
    where you replace MPMD-XXX with the appropriate JIRA issue. Best practice
    is to use the JIRA issue title in the pull request title and in the first line of the
    commit message.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Run mvn clean verify to make sure basic checks pass. A more thorough check will
    be performed on your pull request automatically.
  • You have run the integration tests successfully (mvn -Prun-its clean verify).

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

@adangel adangel closed this in 5ae53f1 Sep 5, 2021
@adangel adangel deleted the MPMD-283 branch September 5, 2021 18:31
@jira-importer
Copy link

Resolve #616

1 similar comment
@jira-importer
Copy link

Resolve #616

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

Successfully merging this pull request may close these issues.

2 participants