[
https://issues.apache.org/jira/browse/MPMD-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863627#comment-17863627
]
ASF GitHub Bot commented on MPMD-391:
-------------------------------------
michael-o opened a new pull request, #156:
URL: https://github.com/apache/maven-pmd-plugin/pull/156
Following this checklist to help us incorporate your
contribution quickly and easily:
- [ ] Make sure there is a [JIRA
issue](https://issues.apache.org/jira/browse/MPMD) 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](https://www.apache.org/licenses/icla.pdf) 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](http://www.apache.org/licenses/LICENSE-2.0)
you have to acknowledge this by using the following check-box.
- [ ] I hereby declare this contribution to be licenced under the [Apache
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
- [ ] In any other case, please file an [Apache Individual Contributor
License Agreement](https://www.apache.org/licenses/icla.pdf).
> Log what developers care about and not what they don't
> ------------------------------------------------------
>
> Key: MPMD-391
> URL: https://issues.apache.org/jira/browse/MPMD-391
> Project: Maven PMD Plugin
> Issue Type: Improvement
> Reporter: Elliotte Rusty Harold
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 3.23.1
>
>
> Here's output from a recent PMD plugin run that failed:
> [INFO] >>> maven-pmd-plugin:3.21.2:check (default-cli) > :pmd @ commons-io >>>
> [INFO]
> [INFO] --- maven-pmd-plugin:3.21.2:pmd (pmd) @ commons-io ---
> [INFO] PMD version: 6.55.0
> [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> [INFO]
> [INFO] <<< maven-pmd-plugin:3.21.2:check (default-cli) < :pmd @ commons-io <<<
> [INFO]
> [INFO]
> [INFO] --- maven-pmd-plugin:3.21.2:check (default-cli) @ commons-io ---
> [INFO] PMD version: 6.55.0
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 05:22 min
> [INFO] Finished at: 2024-01-14T14:11:30Z
> [INFO]
> ------------------------------------------------------------------------
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.21.2:check (default-cli) on
> project commons-io: You have 1 PMD violation. For more details see:
> /home/runner/work/commons-io/commons-io/target/pmd.xml -> [Help 1]
> Error:
> Error: To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> Error: Re-run Maven using the -X switch to enable full debug logging.
> Error:
> Error: For more information about the errors and possible solutions, please
> read the following articles:
> Error: [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> Error: Process completed with exit code 1.
> Things I don't care about that are printed:
> * PMD version
> * Doxia skin
> * Blank lines
> * Total time
> * Timestamp when it finished
> * Generic information about Mojo failures
> * Exit code from Mojo
> The one thing I care about:
> * The actual error that caused the failure
> Everything in the first list can be hidden in some random log file no one
> will ever look at. Everything in the second list should be front and center.
> Instead Maven gets this exactly backwards,
--
This message was sent by Atlassian Jira
(v8.20.10#820010)