[jira] [Commented] (MPMD-391) Log what developers care about and not what they don't
[ https://issues.apache.org/jira/browse/MPMD-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851020#comment-17851020 ] Andreas Dangel commented on MPMD-391: - See MNG-5693 > 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 >Priority: Major > > 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)
[jira] [Created] (MPMD-395) Build doesn't fail for invalid CPD format
Andreas Dangel created MPMD-395: --- Summary: Build doesn't fail for invalid CPD format Key: MPMD-395 URL: https://issues.apache.org/jira/browse/MPMD-395 Project: Maven PMD Plugin Issue Type: Bug Components: CPD Affects Versions: 3.22.0 Reporter: Andreas Dangel Assignee: Andreas Dangel See [https://github.com/apache/maven-pmd-plugin/pull/144#issuecomment-2094371392] If an exception occurs while the CPD report is created, the exception is only logged but doesn't fail the build. This means, that build appears to be successful, although it didn't produce all expected build artifacts. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MPMD-394) Bump org.apache.maven.plugins:maven-plugins from 41 to 42
[ https://issues.apache.org/jira/browse/MPMD-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel reassigned MPMD-394: --- Assignee: Andreas Dangel > Bump org.apache.maven.plugins:maven-plugins from 41 to 42 > - > > Key: MPMD-394 > URL: https://issues.apache.org/jira/browse/MPMD-394 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPMD-394) Bump org.apache.maven.plugins:maven-plugins from 41 to 42
[ https://issues.apache.org/jira/browse/MPMD-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel closed MPMD-394. --- Resolution: Fixed Resolved with https://github.com/apache/maven-pmd-plugin/commit/2823fa09871a0d6a4296d3c59f52f0034eb220db > Bump org.apache.maven.plugins:maven-plugins from 41 to 42 > - > > Key: MPMD-394 > URL: https://issues.apache.org/jira/browse/MPMD-394 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade >Reporter: Andreas Dangel >Priority: Major > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPMD-383) PMD should fail when there is a processing error
[
https://issues.apache.org/jira/browse/MPMD-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel updated MPMD-383:
Fix Version/s: waiting-for-feedback
> PMD should fail when there is a processing error
>
>
> Key: MPMD-383
> URL: https://issues.apache.org/jira/browse/MPMD-383
> Project: Maven PMD Plugin
> Issue Type: Improvement
> Components: PMD
>Affects Versions: 3.21.0
>Reporter: Thomas Nikolay
>Priority: Critical
> Fix For: waiting-for-feedback
>
> Attachments: image-2023-07-28-13-34-28-717.png
>
>
> We had the case that PMD can't process some processing error but the build
> does not fail.
>
> {noformat}
> [2023-07-28T10:59:44.102Z] [INFO] --- maven-pmd-plugin:3.20.0:pmd (pmd) @
> mod-config-client-cst ---
> [2023-07-28T10:59:44.692Z] [INFO] PMD version: 6.53.0
> [2023-07-28T10:59:45.672Z] [WARNING] Removed misconfigured rule:
> GK-SAP-ApacheLoggerDeniedRule cause: missing value
> [2023-07-28T10:59:45.672Z] [WARNING] There are 3 PMD processing errors:
> [2023-07-28T10:59:45.672Z] [WARNING]
> /var/lib/hudson-slave/workspace/hmr.MAIN.00-FEATURE-BRANCHES/pos/config/mod-config-client-cst/src/test/java/com/gk_software/cst/client/AppInfoProviderImpl_CST_Test.java:
> PMDException: Error while processing
> /var/lib/hudson-slave/workspace/hmr.MAIN.00-FEATURE-BRANCHES/pos/config/mod-config-client-cst/src/test/java/com/gk_software/cst/client/AppInfoProviderImpl_CST_Test.java
> [2023-07-28T10:59:45.948Z]
> /var/lib/hudson-slave/workspace/hmr.MAIN.00-FEATURE-BRANCHES/pos/config/mod-config-client-cst/src/test/java/com/gk_software/pos/api/model/config/component/client/print/additional_printout/Trigger_CFH_CST_Test.java:
> PMDException: Error while processing
> /var/lib/hudson-slave/workspace/hmr.MAIN.00-FEATURE-BRANCHES/pos/config/mod-config-client-cst/src/test/java/com/gk_software/pos/api/model/config/component/client/print/additional_printout/Trigger_CFH_CST_Test.java
> [2023-07-28T10:59:45.948Z]
> /var/lib/hudson-slave/workspace/hmr.MAIN.00-FEATURE-BRANCHES/pos/config/mod-config-client-cst/src/main/java/com/gk_software/pos/api/model/config/component/client/print/additional_printout/Trigger_CFH_CST.java:
> PMDException: Error while processing
> /var/lib/hudson-slave/workspace/hmr.MAIN.00-FEATURE-BRANCHES/pos/config/mod-config-client-cst/src/main/java/com/gk_software/pos/api/model/config/component/client/print/additional_printout/Trigger_CFH_CST.java
> [2023-07-28T10:59:45.948Z] [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> [2023-07-28T10:59:46.210Z] [INFO]
> [2023-07-28T10:59:46.210Z] [INFO] <<< maven-pmd-plugin:3.20.0:check
> (pmd-check) < :pmd @ mod-config-client-cst <<<
> {noformat}
>
> My expectation would be that the build failed when there a processing errors.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-383) PMD should fail when there is a processing error
[
https://issues.apache.org/jira/browse/MPMD-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838554#comment-17838554
]
Andreas Dangel commented on MPMD-383:
-
What is your setting of parameter {{skipPmdError}} (
[https://maven.apache.org/plugins/maven-pmd-plugin/pmd-mojo.html#skipPmdError]
)? Does it fail your build, if you set this to false?
> PMD should fail when there is a processing error
>
>
> Key: MPMD-383
> URL: https://issues.apache.org/jira/browse/MPMD-383
> Project: Maven PMD Plugin
> Issue Type: Improvement
> Components: PMD
>Affects Versions: 3.21.0
>Reporter: Thomas Nikolay
>Priority: Critical
> Attachments: image-2023-07-28-13-34-28-717.png
>
>
> We had the case that PMD can't process some processing error but the build
> does not fail.
>
> {noformat}
> [2023-07-28T10:59:44.102Z] [INFO] --- maven-pmd-plugin:3.20.0:pmd (pmd) @
> mod-config-client-cst ---
> [2023-07-28T10:59:44.692Z] [INFO] PMD version: 6.53.0
> [2023-07-28T10:59:45.672Z] [WARNING] Removed misconfigured rule:
> GK-SAP-ApacheLoggerDeniedRule cause: missing value
> [2023-07-28T10:59:45.672Z] [WARNING] There are 3 PMD processing errors:
> [2023-07-28T10:59:45.672Z] [WARNING]
> /var/lib/hudson-slave/workspace/hmr.MAIN.00-FEATURE-BRANCHES/pos/config/mod-config-client-cst/src/test/java/com/gk_software/cst/client/AppInfoProviderImpl_CST_Test.java:
> PMDException: Error while processing
> /var/lib/hudson-slave/workspace/hmr.MAIN.00-FEATURE-BRANCHES/pos/config/mod-config-client-cst/src/test/java/com/gk_software/cst/client/AppInfoProviderImpl_CST_Test.java
> [2023-07-28T10:59:45.948Z]
> /var/lib/hudson-slave/workspace/hmr.MAIN.00-FEATURE-BRANCHES/pos/config/mod-config-client-cst/src/test/java/com/gk_software/pos/api/model/config/component/client/print/additional_printout/Trigger_CFH_CST_Test.java:
> PMDException: Error while processing
> /var/lib/hudson-slave/workspace/hmr.MAIN.00-FEATURE-BRANCHES/pos/config/mod-config-client-cst/src/test/java/com/gk_software/pos/api/model/config/component/client/print/additional_printout/Trigger_CFH_CST_Test.java
> [2023-07-28T10:59:45.948Z]
> /var/lib/hudson-slave/workspace/hmr.MAIN.00-FEATURE-BRANCHES/pos/config/mod-config-client-cst/src/main/java/com/gk_software/pos/api/model/config/component/client/print/additional_printout/Trigger_CFH_CST.java:
> PMDException: Error while processing
> /var/lib/hudson-slave/workspace/hmr.MAIN.00-FEATURE-BRANCHES/pos/config/mod-config-client-cst/src/main/java/com/gk_software/pos/api/model/config/component/client/print/additional_printout/Trigger_CFH_CST.java
> [2023-07-28T10:59:45.948Z] [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> [2023-07-28T10:59:46.210Z] [INFO]
> [2023-07-28T10:59:46.210Z] [INFO] <<< maven-pmd-plugin:3.20.0:check
> (pmd-check) < :pmd @ mod-config-client-cst <<<
> {noformat}
>
> My expectation would be that the build failed when there a processing errors.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (MPMD-379) Upgrade to use PMD 7.0.0 by default
[ https://issues.apache.org/jira/browse/MPMD-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel resolved MPMD-379. - Resolution: Fixed Resolved with https://github.com/apache/maven-pmd-plugin/commit/89a7cdb594c3b28beafb44d6c0251bc7a4bbd71e > Upgrade to use PMD 7.0.0 by default > --- > > Key: MPMD-379 > URL: https://issues.apache.org/jira/browse/MPMD-379 > Project: Maven PMD Plugin > Issue Type: Improvement > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: next-release > > > Add support for the new major version of PMD. > This gives support for analyzing Java 21 code. > The upgrade from PMD 6 to PMD 7 is a major upgrade, that might impact > end-users, if they use custom rulesets (see > [https://maven.apache.org/plugins/maven-pmd-plugin/examples/usingRuleSets.html]) > or if they override the dependencies to upgrade PMD at runtime and currently > use PMD 6.x (see > [https://maven.apache.org/plugins/maven-pmd-plugin/examples/upgrading-PMD-at-runtime.html]). > > Most likely, end-users have to review their rulesets and migrate them to PMD > 7. Rules might have been renamed or replaced. See > [https://docs.pmd-code.org/latest/pmd_release_notes_pmd7.html] and > [https://docs.pmd-code.org/latest/pmd_userdocs_migrating_to_pmd7.html] . > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPMD-379) Upgrade to use PMD 7.0.0 by default
[ https://issues.apache.org/jira/browse/MPMD-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel closed MPMD-379. --- > Upgrade to use PMD 7.0.0 by default > --- > > Key: MPMD-379 > URL: https://issues.apache.org/jira/browse/MPMD-379 > Project: Maven PMD Plugin > Issue Type: Improvement > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: next-release > > > Add support for the new major version of PMD. > This gives support for analyzing Java 21 code. > The upgrade from PMD 6 to PMD 7 is a major upgrade, that might impact > end-users, if they use custom rulesets (see > [https://maven.apache.org/plugins/maven-pmd-plugin/examples/usingRuleSets.html]) > or if they override the dependencies to upgrade PMD at runtime and currently > use PMD 6.x (see > [https://maven.apache.org/plugins/maven-pmd-plugin/examples/upgrading-PMD-at-runtime.html]). > > Most likely, end-users have to review their rulesets and migrate them to PMD > 7. Rules might have been renamed or replaced. See > [https://docs.pmd-code.org/latest/pmd_release_notes_pmd7.html] and > [https://docs.pmd-code.org/latest/pmd_userdocs_migrating_to_pmd7.html] . > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPMD-393) Upgrade commons-io:commons-io to 2.16.1
[ https://issues.apache.org/jira/browse/MPMD-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-393: Summary: Upgrade commons-io:commons-io to 2.16.1 (was: Upgrade commons-io:commons-io to 2.16.0) > Upgrade commons-io:commons-io to 2.16.1 > --- > > Key: MPMD-393 > URL: https://issues.apache.org/jira/browse/MPMD-393 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPMD-394) Bump org.apache.maven.plugins:maven-plugins from 41 to 42
[ https://issues.apache.org/jira/browse/MPMD-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-394: Summary: Bump org.apache.maven.plugins:maven-plugins from 41 to 42 (was: Upgrade to Parent 42) > Bump org.apache.maven.plugins:maven-plugins from 41 to 42 > - > > Key: MPMD-394 > URL: https://issues.apache.org/jira/browse/MPMD-394 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade >Reporter: Andreas Dangel >Priority: Major > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPMD-394) Upgrade to Parent 42
Andreas Dangel created MPMD-394: --- Summary: Upgrade to Parent 42 Key: MPMD-394 URL: https://issues.apache.org/jira/browse/MPMD-394 Project: Maven PMD Plugin Issue Type: Dependency upgrade Reporter: Andreas Dangel Fix For: next-release -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPMD-379) Upgrade to use PMD 7.0.0 by default
[
https://issues.apache.org/jira/browse/MPMD-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel updated MPMD-379:
Description:
Add support for the new major version of PMD.
This gives support for analyzing Java 21 code.
The upgrade from PMD 6 to PMD 7 is a major upgrade, that might impact
end-users, if they use custom rulesets (see
[https://maven.apache.org/plugins/maven-pmd-plugin/examples/usingRuleSets.html])
or if they override the dependencies to upgrade PMD at runtime and currently
use PMD 6.x (see
[https://maven.apache.org/plugins/maven-pmd-plugin/examples/upgrading-PMD-at-runtime.html]).
Most likely, end-users have to review their rulesets and migrate them to PMD 7.
Rules might have been renamed or replaced. See
[https://docs.pmd-code.org/latest/pmd_release_notes_pmd7.html] and
[https://docs.pmd-code.org/latest/pmd_userdocs_migrating_to_pmd7.html] .
was:
Add support for the new major version of PMD.
This has some non-backward compatible changes. Upgrading m-pmd-p to PMD 7 most
likely means, that only PMD 7 will be supported onwards (no backwards
compatibility supported).
wip branch: [https://github.com/apache/maven-pmd-plugin/compare/master...pmd7]
A snapshot version that is compatible with the current 7.0.0 release candidates
is available here as version {*}3.21.1-pmd-7-SNAPSHOT{*}:
{code:java}
apache.snapshots
Apache Snapshot Repository
https://repository.apache.org/snapshots
false
true
{code}
> Upgrade to use PMD 7.0.0 by default
> ---
>
> Key: MPMD-379
> URL: https://issues.apache.org/jira/browse/MPMD-379
> Project: Maven PMD Plugin
> Issue Type: Improvement
> Components: CPD, PMD
>Reporter: Andreas Dangel
>Assignee: Andreas Dangel
>Priority: Major
>
> Add support for the new major version of PMD.
> This gives support for analyzing Java 21 code.
> The upgrade from PMD 6 to PMD 7 is a major upgrade, that might impact
> end-users, if they use custom rulesets (see
> [https://maven.apache.org/plugins/maven-pmd-plugin/examples/usingRuleSets.html])
> or if they override the dependencies to upgrade PMD at runtime and currently
> use PMD 6.x (see
> [https://maven.apache.org/plugins/maven-pmd-plugin/examples/upgrading-PMD-at-runtime.html]).
>
> Most likely, end-users have to review their rulesets and migrate them to PMD
> 7. Rules might have been renamed or replaced. See
> [https://docs.pmd-code.org/latest/pmd_release_notes_pmd7.html] and
> [https://docs.pmd-code.org/latest/pmd_userdocs_migrating_to_pmd7.html] .
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MPMD-379) Upgrade to use PMD 7.0.0 by default
[
https://issues.apache.org/jira/browse/MPMD-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel updated MPMD-379:
Summary: Upgrade to use PMD 7.0.0 by default (was: Support PMD 7.0.0)
> Upgrade to use PMD 7.0.0 by default
> ---
>
> Key: MPMD-379
> URL: https://issues.apache.org/jira/browse/MPMD-379
> Project: Maven PMD Plugin
> Issue Type: Improvement
> Components: CPD, PMD
>Reporter: Andreas Dangel
>Assignee: Andreas Dangel
>Priority: Major
>
> Add support for the new major version of PMD.
> This has some non-backward compatible changes. Upgrading m-pmd-p to PMD 7
> most likely means, that only PMD 7 will be supported onwards (no backwards
> compatibility supported).
> wip branch: [https://github.com/apache/maven-pmd-plugin/compare/master...pmd7]
>
> A snapshot version that is compatible with the current 7.0.0 release
> candidates is available here as version {*}3.21.1-pmd-7-SNAPSHOT{*}:
> {code:java}
>
> apache.snapshots
> Apache Snapshot Repository
> https://repository.apache.org/snapshots
>
> false
>
>
> true
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-391) Log what developers care about and not what they don't
[ https://issues.apache.org/jira/browse/MPMD-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17811355#comment-17811355 ] Andreas Dangel commented on MPMD-391: - To see, why the build failed, the property [printFailingErrors|https://maven.apache.org/plugins/maven-pmd-plugin/check-mojo.html#printFailingErrors] can be set - which is by default disabled (not sure why). This however just adds more output and doesn't remove unnecessary clutter... > 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 >Priority: Major > > 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)
[jira] [Commented] (MPMD-379) Support PMD 7.0.0
[
https://issues.apache.org/jira/browse/MPMD-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17808218#comment-17808218
]
Andreas Dangel commented on MPMD-379:
-
[~chonton] In order to use PMD 7.0.0-rc4 (and later) with maven-pmd-plugin,
please follow the instructions at [pmd/pmd#4478
(comment)|https://github.com/pmd/pmd/discussions/4478#discussioncomment-7607566]
> Support PMD 7.0.0
> -
>
> Key: MPMD-379
> URL: https://issues.apache.org/jira/browse/MPMD-379
> Project: Maven PMD Plugin
> Issue Type: Improvement
> Components: CPD, PMD
>Reporter: Andreas Dangel
>Assignee: Andreas Dangel
>Priority: Major
>
> Add support for the new major version of PMD.
> This has some non-backward compatible changes. Upgrading m-pmd-p to PMD 7
> most likely means, that only PMD 7 will be supported onwards (no backwards
> compatibility supported).
> wip branch: [https://github.com/apache/maven-pmd-plugin/compare/master...pmd7]
>
> A snapshot version that is compatible with the current 7.0.0 release
> candidates is available here as version {*}3.21.1-pmd-7-SNAPSHOT{*}:
> {code:java}
>
> apache.snapshots
> Apache Snapshot Repository
> https://repository.apache.org/snapshots
>
> false
>
>
> true
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MPMD-371) Using two ruleset files with same name in different directories
[
https://issues.apache.org/jira/browse/MPMD-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel closed MPMD-371.
---
Resolution: Fixed
> Using two ruleset files with same name in different directories
> ---
>
> Key: MPMD-371
> URL: https://issues.apache.org/jira/browse/MPMD-371
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.20.0
>Reporter: Bruno Harbulot
>Priority: Major
> Fix For: 3.21.1
>
>
> It is not possible to rely on two ruleset files that share the same filename
> (but are located in different directories).
> Here is an sample configuration for a multi-module project where there is a
> common {{pmd-ruleset.xml}} file in the parent project and a
> {{pmd-ruleset.xml}} file in each sub-module. (This is not limited to
> multi-module projects, it could be any configuration where the same filename
> is used in different directories.)
>
> {code:java}
>
> org.apache.maven.plugins
> maven-pmd-plugin
> ${pmd-maven-plugin.version}
>
>
> ${project.basedir}/pmd-ruleset.xml
> ${project-root.basedir}/pmd-ruleset.xml
>
>
> {code}
>
> The files specified in the {{}} elements are copied into
> {{{}${project.build.directory}/pmd/rulesets{}}}, but only the actual filename
> is taken into account during the copy, so the second copy overwrites the
> first.
> This seems to be due to the implementation of
> {{PmdReport.resolveRulesets(...)}} and {{PmdReport.getLocationTemp(...)}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MPMD-371) Using two ruleset files with same name in different directories
[
https://issues.apache.org/jira/browse/MPMD-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel updated MPMD-371:
Fix Version/s: 3.21.1
> Using two ruleset files with same name in different directories
> ---
>
> Key: MPMD-371
> URL: https://issues.apache.org/jira/browse/MPMD-371
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.20.0
>Reporter: Bruno Harbulot
>Priority: Major
> Fix For: 3.21.1
>
>
> It is not possible to rely on two ruleset files that share the same filename
> (but are located in different directories).
> Here is an sample configuration for a multi-module project where there is a
> common {{pmd-ruleset.xml}} file in the parent project and a
> {{pmd-ruleset.xml}} file in each sub-module. (This is not limited to
> multi-module projects, it could be any configuration where the same filename
> is used in different directories.)
>
> {code:java}
>
> org.apache.maven.plugins
> maven-pmd-plugin
> ${pmd-maven-plugin.version}
>
>
> ${project.basedir}/pmd-ruleset.xml
> ${project-root.basedir}/pmd-ruleset.xml
>
>
> {code}
>
> The files specified in the {{}} elements are copied into
> {{{}${project.build.directory}/pmd/rulesets{}}}, but only the actual filename
> is taken into account during the copy, so the second copy overwrites the
> first.
> This seems to be due to the implementation of
> {{PmdReport.resolveRulesets(...)}} and {{PmdReport.getLocationTemp(...)}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MNG-7795) IllegalArgumentException: 'other' has different root during plugin validation
Andreas Dangel created MNG-7795:
---
Summary: IllegalArgumentException: 'other' has different root
during plugin validation
Key: MNG-7795
URL: https://issues.apache.org/jira/browse/MNG-7795
Project: Maven
Issue Type: Bug
Components: Core
Affects Versions: 3.9.2
Reporter: Andreas Dangel
Assignee: Andreas Dangel
Fix For: 3.9.3
This bug happens under Windows only and is the reason, why one IT
(MPMD-323-ruleset-basedir-jgitver) is failing for m-pmd-p with the following
exception:
{code:java}
java.lang.IllegalArgumentException: 'other' has different root
at sun.nio.fs.WindowsPath.relativize (WindowsPath.java:404)
at sun.nio.fs.WindowsPath.relativize (WindowsPath.java:42)
at
org.apache.maven.plugin.internal.DefaultPluginValidationManager.pluginOccurrence
(DefaultPluginValidationManager.java:224)
at
org.apache.maven.plugin.internal.DefaultPluginValidationManager.reportPluginValidationIssue
(DefaultPluginValidationManager.java:111)
at
org.apache.maven.plugin.internal.PlexusContainerDefaultDependenciesValidator.doValidate
(PlexusContainerDefaultDependenciesValidator.java:49)
at
org.apache.maven.plugin.internal.AbstractMavenPluginDependenciesValidator.validate
(AbstractMavenPluginDependenciesValidator.java:50)
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo
(DefaultMavenPluginManager.java:560)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:114)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:342)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:330)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:175)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
(MojoExecutor.java:76)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:163)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:160)
at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions
(MojoExecutor.java:462)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:325)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:175)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
(MojoExecutor.java:76)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:163)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:160)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:105)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:73)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:53)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:118)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:910)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:566)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:283)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:226)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:407)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:348)
{code}
E.g. see GitHub Actions:
[https://github.com/apache/maven-pmd-plugin/actions/runs/5024694265]
(unfortunately without a stack trace)
This IT uses the extension
[jgitver-maven-plugin|https://github.com/jgitver/jgitver-maven-plugin], which
creates a temporary pom file for the current project with the new
[jira] [Commented] (MPMD-379) Support PMD 7.0.0
[
https://issues.apache.org/jira/browse/MPMD-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17725010#comment-17725010
]
Andreas Dangel commented on MPMD-379:
-
This is currently needed in two cases: When toolchain is used, then PMD is not
invoked within the current JVM process, but a new one is spawned. This is, what
Executor#setupLogLevel is responsible for - recreating the environment, that
maven cli already provided, in the new process.
The other case is the parameter {{showPmdLog}} - if this is true, then any
slf4j log message from within PMD should show up as usual. But if this is set
to false, then we want to silence out any PMD logging. Since this parameter can
be true for one module and false for another, the log levels needs to switch at
runtime if no toolchain is in use. This is what Executor#setupPmdLogging is
doing.
We could however decide, to remove this parameter and keep the logging enabled
all the time. That would make it easier. Are there any best practices on how to
deal with logs from third-party-libs (in that case, PMD is a 3rd-party lib to
maven)? If one wanted to silence out the logging from PMD, then one could
change maven's simplelogger.properties (or provide equivalent system properties
via MAVEN_OPTS).
> Support PMD 7.0.0
> -
>
> Key: MPMD-379
> URL: https://issues.apache.org/jira/browse/MPMD-379
> Project: Maven PMD Plugin
> Issue Type: Improvement
> Components: CPD, PMD
>Reporter: Andreas Dangel
>Assignee: Andreas Dangel
>Priority: Major
>
> Add support for the new major version of PMD.
> This has some non-backward compatible changes. Upgrading m-pmd-p to PMD 7
> most likely means, that only PMD 7 will be supported onwards (no backwards
> compatibility supported).
> wip branch: [https://github.com/apache/maven-pmd-plugin/compare/master...pmd7]
>
> A snapshot version that is compatible with the current 7.0.0 release
> candidates is available here as version {*}3.21.1-pmd-7-SNAPSHOT{*}:
> {code:java}
>
> apache.snapshots
> Apache Snapshot Repository
> https://repository.apache.org/snapshots
>
> false
>
>
> true
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MPMD-379) Support PMD 7.0.0
[
https://issues.apache.org/jira/browse/MPMD-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel updated MPMD-379:
Description:
Add support for the new major version of PMD.
This has some non-backward compatible changes. Upgrading m-pmd-p to PMD 7 most
likely means, that only PMD 7 will be supported onwards (no backwards
compatibility supported).
wip branch: [https://github.com/apache/maven-pmd-plugin/compare/master...pmd7]
A snapshot version that is compatible with the current 7.0.0 release candidates
is available here as version {*}3.21.1-pmd-7-SNAPSHOT{*}:
{code:java}
apache.snapshots
Apache Snapshot Repository
https://repository.apache.org/snapshots
false
true
{code}
was:
Add support for the new major version of PMD.
This has some non-backward compatible changes. Upgrading m-pmd-p to PMD 7 most
likely means, that only PMD 7 will be supported onwards (no backwards
compatibility supported).
wip branch: https://github.com/apache/maven-pmd-plugin/compare/master...pmd7
> Support PMD 7.0.0
> -
>
> Key: MPMD-379
> URL: https://issues.apache.org/jira/browse/MPMD-379
> Project: Maven PMD Plugin
> Issue Type: Improvement
> Components: CPD, PMD
>Reporter: Andreas Dangel
>Assignee: Andreas Dangel
>Priority: Major
>
> Add support for the new major version of PMD.
> This has some non-backward compatible changes. Upgrading m-pmd-p to PMD 7
> most likely means, that only PMD 7 will be supported onwards (no backwards
> compatibility supported).
> wip branch: [https://github.com/apache/maven-pmd-plugin/compare/master...pmd7]
>
> A snapshot version that is compatible with the current 7.0.0 release
> candidates is available here as version {*}3.21.1-pmd-7-SNAPSHOT{*}:
> {code:java}
>
> apache.snapshots
> Apache Snapshot Repository
> https://repository.apache.org/snapshots
>
> false
>
>
> true
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MPMD-379) Support PMD 7.0.0
[ https://issues.apache.org/jira/browse/MPMD-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-379: Fix Version/s: (was: 3.21.1) > Support PMD 7.0.0 > - > > Key: MPMD-379 > URL: https://issues.apache.org/jira/browse/MPMD-379 > Project: Maven PMD Plugin > Issue Type: Improvement > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > > Add support for the new major version of PMD. > This has some non-backward compatible changes. Upgrading m-pmd-p to PMD 7 > most likely means, that only PMD 7 will be supported onwards (no backwards > compatibility supported). > wip branch: https://github.com/apache/maven-pmd-plugin/compare/master...pmd7 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPMD-367) Verify / ubuntu-latest jdk-11-temurin 3.9.1 broken at head in MPMD-270-325-JDK11
[
https://issues.apache.org/jira/browse/MPMD-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel updated MPMD-367:
Fix Version/s: 3.21.0
> Verify / ubuntu-latest jdk-11-temurin 3.9.1 broken at head in
> MPMD-270-325-JDK11
>
>
> Key: MPMD-367
> URL: https://issues.apache.org/jira/browse/MPMD-367
> Project: Maven PMD Plugin
> Issue Type: Task
>Reporter: Elliotte Rusty Harold
>Assignee: Elliotte Rusty Harold
>Priority: Major
> Fix For: 3.21.0
>
>
> Problem seems to be that this test produces a WARNING on this platform (and
> only this platform?) that fails the build
> {noformat}
> 317 kB at 5.4 MB/s)
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 2 source files to
> /home/runner/work/maven-pmd-plugin/maven-pmd-plugin/target/it/MPMD-270-325-JDK11/target/classes
> [INFO]
> [INFO] --- resources:3.3.0:testResources (default-testResources) @
> MPMD-270-325-JDK11 ---
> [INFO] skip non existing resourceDirectory
> /home/runner/work/maven-pmd-plugin/maven-pmd-plugin/target/it/MPMD-270-325-JDK11/src/test/resources
> [INFO]
> [INFO] --- compiler:3.8.0:testCompile (default-testCompile) @
> MPMD-270-325-JDK11 ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- surefire:3.0.0:test (default-test) @ MPMD-270-325-JDK11 ---
> [INFO] No tests to run.
> [INFO]
> [INFO] --- jar:3.3.0:jar (default-jar) @ MPMD-270-325-JDK11 ---
> [INFO] Building jar:
> /home/runner/work/maven-pmd-plugin/maven-pmd-plugin/target/it/MPMD-270-325-JDK11/target/MPMD-270-325-JDK11-1.0-SNAPSHOT.jar
> [INFO]
> [INFO] >>> pmd:3.21.0-SNAPSHOT:check (default) > :pmd @ MPMD-270-325-JDK11 >>>
> [INFO]
> [INFO] --- pmd:3.21.0-SNAPSHOT:pmd (pmd) @ MPMD-270-325-JDK11 ---
> [WARNING] Parameter \'localRepository\' is deprecated core expression; Avoid
> use of ArtifactRepository type. If you need access to local repository,
> switch to \'${repositorySystemSession}\' expression and get LRM from it
> instead.
> [INFO] PMD version: 6.55.0
> [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> [INFO]
> [INFO] <<< pmd:3.21.0-SNAPSHOT:check (default) < :pmd @ MPMD-270-325-JDK11 <<<
> [INFO]
> [INFO]
> [INFO] --- pmd:3.21.0-SNAPSHOT:check (default) @ MPMD-270-325-JDK11 ---
> [INFO] PMD version: 6.55.0
> [INFO] PMD Failure: com.mycompany.app.Foo:26 Rule:UnusedFormalParameter
> Priority:3 Avoid unused constructor parameters such as \'foo\'..
> [INFO]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MPMD-366) Update parent pom to 39
[ https://issues.apache.org/jira/browse/MPMD-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-366: Fix Version/s: 3.21.0 > Update parent pom to 39 > --- > > Key: MPMD-366 > URL: https://issues.apache.org/jira/browse/MPMD-366 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Major > Fix For: 3.21.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPMD-379) Support PMD 7.0.0
Andreas Dangel created MPMD-379: --- Summary: Support PMD 7.0.0 Key: MPMD-379 URL: https://issues.apache.org/jira/browse/MPMD-379 Project: Maven PMD Plugin Issue Type: Improvement Components: CPD, PMD Reporter: Andreas Dangel Assignee: Andreas Dangel Fix For: 3.21.1 Add support for the new major version of PMD. This has some non-backward compatible changes. Upgrading m-pmd-p to PMD 7 most likely means, that only PMD 7 will be supported onwards (no backwards compatibility supported). wip branch: https://github.com/apache/maven-pmd-plugin/compare/master...pmd7 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPMD-365) Support Java 20
[ https://issues.apache.org/jira/browse/MPMD-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel closed MPMD-365. --- Resolution: Fixed > Support Java 20 > --- > > Key: MPMD-365 > URL: https://issues.apache.org/jira/browse/MPMD-365 > Project: Maven PMD Plugin > Issue Type: New Feature > Components: PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.21.0 > > > With the PMD version 6.55.0, Java 20 is supported. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPMD-365) Support Java 20
[ https://issues.apache.org/jira/browse/MPMD-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17696145#comment-17696145 ] Andreas Dangel commented on MPMD-365: - Fixed: [https://gitbox.apache.org/repos/asf?p=maven-pmd-plugin.git;a=commit;h=c8782ca85d9c12dc1138292d091cf3dda53461ac] > Support Java 20 > --- > > Key: MPMD-365 > URL: https://issues.apache.org/jira/browse/MPMD-365 > Project: Maven PMD Plugin > Issue Type: New Feature > Components: PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.21.0 > > > With the PMD version 6.55.0, Java 20 is supported. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPMD-365) Support Java 20
[ https://issues.apache.org/jira/browse/MPMD-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-365: Fix Version/s: 3.21.0 (was: 3.18.0) > Support Java 20 > --- > > Key: MPMD-365 > URL: https://issues.apache.org/jira/browse/MPMD-365 > Project: Maven PMD Plugin > Issue Type: New Feature > Components: PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.21.0 > > > With the PMD version 6.55.0, Java 20 is supported. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPMD-364) Upgrade to PMD 6.55.0
[ https://issues.apache.org/jira/browse/MPMD-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-364: Summary: Upgrade to PMD 6.55.0 (was: Upgrade to PMD 6.54.0) > Upgrade to PMD 6.55.0 > - > > Key: MPMD-364 > URL: https://issues.apache.org/jira/browse/MPMD-364 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.21.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPMD-365) Support Java 20
Andreas Dangel created MPMD-365: --- Summary: Support Java 20 Key: MPMD-365 URL: https://issues.apache.org/jira/browse/MPMD-365 Project: Maven PMD Plugin Issue Type: New Feature Components: PMD Reporter: Andreas Dangel Assignee: Andreas Dangel Fix For: 3.18.0 With the next PMD version 6.48.0, Java 19 is supported. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPMD-365) Support Java 20
[ https://issues.apache.org/jira/browse/MPMD-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-365: Description: With the PMD version 6.55.0, Java 20 is supported. (was: With the next PMD version 6.48.0, Java 19 is supported.) > Support Java 20 > --- > > Key: MPMD-365 > URL: https://issues.apache.org/jira/browse/MPMD-365 > Project: Maven PMD Plugin > Issue Type: New Feature > Components: PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.18.0 > > > With the PMD version 6.55.0, Java 20 is supported. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPMD-364) Upgrade to PMD 6.54.0
[ https://issues.apache.org/jira/browse/MPMD-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel closed MPMD-364. --- > Upgrade to PMD 6.54.0 > - > > Key: MPMD-364 > URL: https://issues.apache.org/jira/browse/MPMD-364 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.21.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (MPMD-364) Upgrade to PMD 6.54.0
[ https://issues.apache.org/jira/browse/MPMD-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel resolved MPMD-364. - Resolution: Fixed > Upgrade to PMD 6.54.0 > - > > Key: MPMD-364 > URL: https://issues.apache.org/jira/browse/MPMD-364 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPMD-364) Upgrade to PMD 6.54.0
[ https://issues.apache.org/jira/browse/MPMD-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17681602#comment-17681602 ] Andreas Dangel commented on MPMD-364: - Hi [~michael-o] , could you please set the fixed version to 3.21.0? Thanks! > Upgrade to PMD 6.54.0 > - > > Key: MPMD-364 > URL: https://issues.apache.org/jira/browse/MPMD-364 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPMD-364) Upgrade to PMD 6.54.0
[ https://issues.apache.org/jira/browse/MPMD-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17681601#comment-17681601 ] Andreas Dangel commented on MPMD-364: - Fixed with https://gitbox.apache.org/repos/asf?p=maven-pmd-plugin.git;a=commit;h=5826c8805c31e0089b999646037c1e730305d3e9 > Upgrade to PMD 6.54.0 > - > > Key: MPMD-364 > URL: https://issues.apache.org/jira/browse/MPMD-364 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPMD-364) Upgrade to PMD 6.54.0
[
https://issues.apache.org/jira/browse/MPMD-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17681598#comment-17681598
]
Andreas Dangel commented on MPMD-364:
-
{quote}This seems like a never ending story...{quote}
Yes, but a new PMD version doesn't necessarily mean that a new m-pmd-p version
is required. It's just better to keep the dependency updated to be prepared,
when the next m-pmd-p version is released.
> Upgrade to PMD 6.54.0
> -
>
> Key: MPMD-364
> URL: https://issues.apache.org/jira/browse/MPMD-364
> Project: Maven PMD Plugin
> Issue Type: Dependency upgrade
> Components: CPD, PMD
>Reporter: Andreas Dangel
>Assignee: Andreas Dangel
>Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MPMD-364) Upgrade to PMD 6.54.0
[ https://issues.apache.org/jira/browse/MPMD-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-364: Fix Version/s: (was: 3.20.0) > Upgrade to PMD 6.54.0 > - > > Key: MPMD-364 > URL: https://issues.apache.org/jira/browse/MPMD-364 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPMD-364) Upgrade to PMD 6.54.0
Andreas Dangel created MPMD-364: --- Summary: Upgrade to PMD 6.54.0 Key: MPMD-364 URL: https://issues.apache.org/jira/browse/MPMD-364 Project: Maven PMD Plugin Issue Type: Dependency upgrade Components: CPD, PMD Reporter: Andreas Dangel Assignee: Andreas Dangel Fix For: 3.20.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPMD-360) Upgrade to PMD 6.53.0
[ https://issues.apache.org/jira/browse/MPMD-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel closed MPMD-360. --- Resolution: Fixed > Upgrade to PMD 6.53.0 > - > > Key: MPMD-360 > URL: https://issues.apache.org/jira/browse/MPMD-360 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.20.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPMD-360) Upgrade to PMD 6.53.0
Andreas Dangel created MPMD-360: --- Summary: Upgrade to PMD 6.53.0 Key: MPMD-360 URL: https://issues.apache.org/jira/browse/MPMD-360 Project: Maven PMD Plugin Issue Type: Dependency upgrade Components: CPD, PMD Reporter: Andreas Dangel Assignee: Andreas Dangel Fix For: 3.20.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPMD-358) Upgrade to PMD 6.52.0
[ https://issues.apache.org/jira/browse/MPMD-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel closed MPMD-358. --- > Upgrade to PMD 6.52.0 > - > > Key: MPMD-358 > URL: https://issues.apache.org/jira/browse/MPMD-358 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.20.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (MPMD-358) Upgrade to PMD 6.52.0
[ https://issues.apache.org/jira/browse/MPMD-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel resolved MPMD-358. - Resolution: Fixed > Upgrade to PMD 6.52.0 > - > > Key: MPMD-358 > URL: https://issues.apache.org/jira/browse/MPMD-358 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.20.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPMD-359) Bump maven-plugins from 37 to 38
Andreas Dangel created MPMD-359: --- Summary: Bump maven-plugins from 37 to 38 Key: MPMD-359 URL: https://issues.apache.org/jira/browse/MPMD-359 Project: Maven PMD Plugin Issue Type: Dependency upgrade Components: CPD, PMD Reporter: Andreas Dangel See https://github.com/apache/maven-pmd-plugin/pull/103 and infos about code style changes: https://lists.apache.org/thread/14n13z4sh3twy5qgp5f487f1z0s5pc4s Also note: "The parent POM raises the minimum JDK requirement to JDK 1.8." -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPMD-358) Upgrade to PMD 6.52.0
Andreas Dangel created MPMD-358: --- Summary: Upgrade to PMD 6.52.0 Key: MPMD-358 URL: https://issues.apache.org/jira/browse/MPMD-358 Project: Maven PMD Plugin Issue Type: Dependency upgrade Components: CPD, PMD Reporter: Andreas Dangel Assignee: Andreas Dangel Fix For: 3.20.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (MPMD-335) Aggregate mode doesn't use additional repositories
[
https://issues.apache.org/jira/browse/MPMD-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel resolved MPMD-335.
-
Resolution: Fixed
> Aggregate mode doesn't use additional repositories
> --
>
> Key: MPMD-335
> URL: https://issues.apache.org/jira/browse/MPMD-335
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.15.0, 3.16.0, 3.17.0, 3.18.0, 3.19.0
>Reporter: Andre Kalamandeen
>Assignee: Andreas Dangel
>Priority: Major
> Fix For: 3.20.0
>
> Attachments: MPMD-335-aggregate-private-repo.zip
>
>
> I've tried to upgrade PMD to 3.16.0 and noticed that when building it tries
> to get artifacts from the default maven repository instead of the repository
> configured in the project.
> This causes issues with the build as certain artifacts are only available in
> the custom repository.
>
> The build error:
> {code:java}
> Execution pmd of goal org.apache.maven.plugins:maven-pmd-plugin:3.16.0:pmd
> failed: org.apache.maven.reporting.MavenReportException:
> org.eclipse.aether.resolution.DependencyResolutionException: The following
> artifacts could not be resolved: [REMOVED]: Failure to find [REMOVED] in
> https://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MPMD-335) Aggregate mode doesn't use additional repositories
[
https://issues.apache.org/jira/browse/MPMD-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel closed MPMD-335.
---
> Aggregate mode doesn't use additional repositories
> --
>
> Key: MPMD-335
> URL: https://issues.apache.org/jira/browse/MPMD-335
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.15.0, 3.16.0, 3.17.0, 3.18.0, 3.19.0
>Reporter: Andre Kalamandeen
>Assignee: Andreas Dangel
>Priority: Major
> Fix For: 3.20.0
>
> Attachments: MPMD-335-aggregate-private-repo.zip
>
>
> I've tried to upgrade PMD to 3.16.0 and noticed that when building it tries
> to get artifacts from the default maven repository instead of the repository
> configured in the project.
> This causes issues with the build as certain artifacts are only available in
> the custom repository.
>
> The build error:
> {code:java}
> Execution pmd of goal org.apache.maven.plugins:maven-pmd-plugin:3.16.0:pmd
> failed: org.apache.maven.reporting.MavenReportException:
> org.eclipse.aether.resolution.DependencyResolutionException: The following
> artifacts could not be resolved: [REMOVED]: Failure to find [REMOVED] in
> https://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MPMD-335) Aggregate mode doesn't use additional repositories
[
https://issues.apache.org/jira/browse/MPMD-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel updated MPMD-335:
Summary: Aggregate mode doesn't use additional repositories (was: PMD
3.15.0 and 3.16.0 do not use project repository)
> Aggregate mode doesn't use additional repositories
> --
>
> Key: MPMD-335
> URL: https://issues.apache.org/jira/browse/MPMD-335
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.15.0, 3.16.0, 3.17.0, 3.18.0, 3.19.0
>Reporter: Andre Kalamandeen
>Assignee: Andreas Dangel
>Priority: Major
> Fix For: 3.20.0
>
> Attachments: MPMD-335-aggregate-private-repo.zip
>
>
> I've tried to upgrade PMD to 3.16.0 and noticed that when building it tries
> to get artifacts from the default maven repository instead of the repository
> configured in the project.
> This causes issues with the build as certain artifacts are only available in
> the custom repository.
>
> The build error:
> {code:java}
> Execution pmd of goal org.apache.maven.plugins:maven-pmd-plugin:3.16.0:pmd
> failed: org.apache.maven.reporting.MavenReportException:
> org.eclipse.aether.resolution.DependencyResolutionException: The following
> artifacts could not be resolved: [REMOVED]: Failure to find [REMOVED] in
> https://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-335) PMD 3.15.0 and 3.16.0 do not use project repository
[
https://issues.apache.org/jira/browse/MPMD-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635289#comment-17635289
]
Andreas Dangel commented on MPMD-335:
-
It's not reproducible by the way with the new "aggregate-pmd-check" goal,
because this one triggers the phase "test-compile", which downloads the
dependency. Then when the m-pmd-p is executed, the dependency is already there
in the local repo.
> PMD 3.15.0 and 3.16.0 do not use project repository
> ---
>
> Key: MPMD-335
> URL: https://issues.apache.org/jira/browse/MPMD-335
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.15.0, 3.16.0, 3.17.0, 3.18.0, 3.19.0
>Reporter: Andre Kalamandeen
>Assignee: Andreas Dangel
>Priority: Major
> Fix For: 3.20.0
>
> Attachments: MPMD-335-aggregate-private-repo.zip
>
>
> I've tried to upgrade PMD to 3.16.0 and noticed that when building it tries
> to get artifacts from the default maven repository instead of the repository
> configured in the project.
> This causes issues with the build as certain artifacts are only available in
> the custom repository.
>
> The build error:
> {code:java}
> Execution pmd of goal org.apache.maven.plugins:maven-pmd-plugin:3.16.0:pmd
> failed: org.apache.maven.reporting.MavenReportException:
> org.eclipse.aether.resolution.DependencyResolutionException: The following
> artifacts could not be resolved: [REMOVED]: Failure to find [REMOVED] in
> https://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MPMD-335) PMD 3.15.0 and 3.16.0 do not use project repository
[
https://issues.apache.org/jira/browse/MPMD-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel updated MPMD-335:
Affects Version/s: 3.19.0
3.18.0
3.17.0
3.16.0
> PMD 3.15.0 and 3.16.0 do not use project repository
> ---
>
> Key: MPMD-335
> URL: https://issues.apache.org/jira/browse/MPMD-335
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.15.0, 3.16.0, 3.17.0, 3.18.0, 3.19.0
>Reporter: Andre Kalamandeen
>Assignee: Andreas Dangel
>Priority: Major
> Fix For: 3.20.0
>
> Attachments: MPMD-335-aggregate-private-repo.zip
>
>
> I've tried to upgrade PMD to 3.16.0 and noticed that when building it tries
> to get artifacts from the default maven repository instead of the repository
> configured in the project.
> This causes issues with the build as certain artifacts are only available in
> the custom repository.
>
> The build error:
> {code:java}
> Execution pmd of goal org.apache.maven.plugins:maven-pmd-plugin:3.16.0:pmd
> failed: org.apache.maven.reporting.MavenReportException:
> org.eclipse.aether.resolution.DependencyResolutionException: The following
> artifacts could not be resolved: [REMOVED]: Failure to find [REMOVED] in
> https://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MPMD-335) PMD 3.15.0 and 3.16.0 do not use project repository
[
https://issues.apache.org/jira/browse/MPMD-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel updated MPMD-335:
Affects Version/s: 3.15.0
> PMD 3.15.0 and 3.16.0 do not use project repository
> ---
>
> Key: MPMD-335
> URL: https://issues.apache.org/jira/browse/MPMD-335
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.15.0
>Reporter: Andre Kalamandeen
>Assignee: Andreas Dangel
>Priority: Major
> Fix For: 3.20.0
>
> Attachments: MPMD-335-aggregate-private-repo.zip
>
>
> I've tried to upgrade PMD to 3.16.0 and noticed that when building it tries
> to get artifacts from the default maven repository instead of the repository
> configured in the project.
> This causes issues with the build as certain artifacts are only available in
> the custom repository.
>
> The build error:
> {code:java}
> Execution pmd of goal org.apache.maven.plugins:maven-pmd-plugin:3.16.0:pmd
> failed: org.apache.maven.reporting.MavenReportException:
> org.eclipse.aether.resolution.DependencyResolutionException: The following
> artifacts could not be resolved: [REMOVED]: Failure to find [REMOVED] in
> https://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MPMD-335) PMD 3.15.0 and 3.16.0 do not use project repository
[
https://issues.apache.org/jira/browse/MPMD-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel updated MPMD-335:
Component/s: PMD
> PMD 3.15.0 and 3.16.0 do not use project repository
> ---
>
> Key: MPMD-335
> URL: https://issues.apache.org/jira/browse/MPMD-335
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Reporter: Andre Kalamandeen
>Assignee: Andreas Dangel
>Priority: Major
> Fix For: 3.20.0
>
> Attachments: MPMD-335-aggregate-private-repo.zip
>
>
> I've tried to upgrade PMD to 3.16.0 and noticed that when building it tries
> to get artifacts from the default maven repository instead of the repository
> configured in the project.
> This causes issues with the build as certain artifacts are only available in
> the custom repository.
>
> The build error:
> {code:java}
> Execution pmd of goal org.apache.maven.plugins:maven-pmd-plugin:3.16.0:pmd
> failed: org.apache.maven.reporting.MavenReportException:
> org.eclipse.aether.resolution.DependencyResolutionException: The following
> artifacts could not be resolved: [REMOVED]: Failure to find [REMOVED] in
> https://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MPMD-335) PMD 3.15.0 and 3.16.0 do not use project repository
[
https://issues.apache.org/jira/browse/MPMD-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel updated MPMD-335:
Fix Version/s: 3.20.0
> PMD 3.15.0 and 3.16.0 do not use project repository
> ---
>
> Key: MPMD-335
> URL: https://issues.apache.org/jira/browse/MPMD-335
> Project: Maven PMD Plugin
> Issue Type: Bug
>Reporter: Andre Kalamandeen
>Assignee: Andreas Dangel
>Priority: Major
> Fix For: 3.20.0
>
> Attachments: MPMD-335-aggregate-private-repo.zip
>
>
> I've tried to upgrade PMD to 3.16.0 and noticed that when building it tries
> to get artifacts from the default maven repository instead of the repository
> configured in the project.
> This causes issues with the build as certain artifacts are only available in
> the custom repository.
>
> The build error:
> {code:java}
> Execution pmd of goal org.apache.maven.plugins:maven-pmd-plugin:3.16.0:pmd
> failed: org.apache.maven.reporting.MavenReportException:
> org.eclipse.aether.resolution.DependencyResolutionException: The following
> artifacts could not be resolved: [REMOVED]: Failure to find [REMOVED] in
> https://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MPMD-335) PMD 3.15.0 and 3.16.0 do not use project repository
[
https://issues.apache.org/jira/browse/MPMD-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17632730#comment-17632730
]
Andreas Dangel edited comment on MPMD-335 at 11/12/22 7:07 PM:
---
I was able to create a reproducer project (see
[^MPMD-335-aggregate-private-repo.zip] ).
The full stack trace is (in case somebody is searching on the internets):
{code}
Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not
find artifact
org.apache.maven.plugins.pmd.it.mpmd335:dependency1:jar:1.0.0-SNAPSHOT
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
(DefaultArtifactResolver.java:415)
at
org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
(DefaultArtifactResolver.java:229)
at
org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies
(DefaultRepositorySystem.java:340)
at
org.apache.maven.shared.transfer.dependencies.resolve.internal.Maven31DependencyResolver.resolveDependencies
(Maven31DependencyResolver.java:216)
at
org.apache.maven.shared.transfer.dependencies.resolve.internal.Maven31DependencyResolver.resolveDependencies
(Maven31DependencyResolver.java:198)
at
org.apache.maven.shared.transfer.dependencies.resolve.internal.DefaultDependencyResolver.resolveDependencies
(DefaultDependencyResolver.java:60)
at org.apache.maven.plugins.pmd.PmdReport.determineAuxClasspath
(PmdReport.java:556)
at org.apache.maven.plugins.pmd.PmdReport.executePmd (PmdReport.java:363)
at org.apache.maven.plugins.pmd.PmdReport.canGenerateReport
(PmdReport.java:315)
at org.apache.maven.reporting.AbstractMavenReport.execute
(AbstractMavenReport.java:143)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:370)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:351)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:215)
{code}
It's happening when determining the auxclasspath for the projects
was (Author: adangel):
I was able to create a reproducer project (see
[^MPMD-335-aggregate-private-repo.zip] ).
The full stack trace is (in case somebody is searching on the internets):
{code}
Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not
find artifact
org.apache.maven.plugins.pmd.it.mpmd335:dependency1:jar:1.0.0-SNAPSHOT
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
(DefaultArtifactResolver.java:415)
at
org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
(DefaultArtifactResolver.java:229)
at
org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies
(DefaultRepositorySystem.java:340)
at
org.apache.maven.shared.transfer.dependencies.resolve.internal.Maven31DependencyResolver.resolveDependencies
(Maven31DependencyResolver.java:216)
at
org.apache.maven.shared.transfer.dependencies.resolve.internal.Maven31DependencyResolver.resolveDependencies
(Maven31DependencyResolver.java:198)
at
org.apache.maven.shared.transfer.dependencies.resolve.internal.DefaultDependencyResolver.resolveDependencies
(DefaultDependencyResolver.java:60)
at org.apache.maven.plugins.pmd.PmdReport.determineAuxClasspath
(PmdReport.java:556)
at org.apache.maven.plugins.pmd.PmdReport.executePmd (PmdReport.java:363)
at org.apache.maven.plugins.pmd.PmdReport.canGenerateReport
(PmdReport.java:315)
at org.apache.maven.reporting.AbstractMavenReport.execute
(AbstractMavenReport.java:143)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:370)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:351)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:215)
{code}
> PMD 3.15.0 and 3.16.0 do not use project repository
> ---
>
> Key: MPMD-335
> URL: https://issues.apache.org/jira/browse/MPMD-335
> Project: Maven PMD Plugin
> Issue Type: Bug
>Reporter: Andre Kalamandeen
>Assignee: Andreas Dangel
>Priority: Major
> Attachments: MPMD-335-aggregate-private-repo.zip
>
>
> I've tried to upgrade PMD to 3.16.0 and noticed that when building it tries
> to get artifacts from the default maven repository instead of the repository
> configured in the project.
> This causes issues with the build as certain artifacts are only available in
> the custom repository.
>
> The build error:
> {code:java}
> Execution pmd of goal
[jira] [Commented] (MPMD-335) PMD 3.15.0 and 3.16.0 do not use project repository
[
https://issues.apache.org/jira/browse/MPMD-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17632730#comment-17632730
]
Andreas Dangel commented on MPMD-335:
-
I was able to create a reproducer project (see
[^MPMD-335-aggregate-private-repo.zip] ).
The full stack trace is (in case somebody is searching on the internets):
{code}
Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not
find artifact
org.apache.maven.plugins.pmd.it.mpmd335:dependency1:jar:1.0.0-SNAPSHOT
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
(DefaultArtifactResolver.java:415)
at
org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
(DefaultArtifactResolver.java:229)
at
org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies
(DefaultRepositorySystem.java:340)
at
org.apache.maven.shared.transfer.dependencies.resolve.internal.Maven31DependencyResolver.resolveDependencies
(Maven31DependencyResolver.java:216)
at
org.apache.maven.shared.transfer.dependencies.resolve.internal.Maven31DependencyResolver.resolveDependencies
(Maven31DependencyResolver.java:198)
at
org.apache.maven.shared.transfer.dependencies.resolve.internal.DefaultDependencyResolver.resolveDependencies
(DefaultDependencyResolver.java:60)
at org.apache.maven.plugins.pmd.PmdReport.determineAuxClasspath
(PmdReport.java:556)
at org.apache.maven.plugins.pmd.PmdReport.executePmd (PmdReport.java:363)
at org.apache.maven.plugins.pmd.PmdReport.canGenerateReport
(PmdReport.java:315)
at org.apache.maven.reporting.AbstractMavenReport.execute
(AbstractMavenReport.java:143)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:370)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:351)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:215)
{code}
> PMD 3.15.0 and 3.16.0 do not use project repository
> ---
>
> Key: MPMD-335
> URL: https://issues.apache.org/jira/browse/MPMD-335
> Project: Maven PMD Plugin
> Issue Type: Bug
>Reporter: Andre Kalamandeen
>Assignee: Andreas Dangel
>Priority: Major
> Attachments: MPMD-335-aggregate-private-repo.zip
>
>
> I've tried to upgrade PMD to 3.16.0 and noticed that when building it tries
> to get artifacts from the default maven repository instead of the repository
> configured in the project.
> This causes issues with the build as certain artifacts are only available in
> the custom repository.
>
> The build error:
> {code:java}
> Execution pmd of goal org.apache.maven.plugins:maven-pmd-plugin:3.16.0:pmd
> failed: org.apache.maven.reporting.MavenReportException:
> org.eclipse.aether.resolution.DependencyResolutionException: The following
> artifacts could not be resolved: [REMOVED]: Failure to find [REMOVED] in
> https://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MPMD-335) PMD 3.15.0 and 3.16.0 do not use project repository
[
https://issues.apache.org/jira/browse/MPMD-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel updated MPMD-335:
Attachment: MPMD-335-aggregate-private-repo.zip
> PMD 3.15.0 and 3.16.0 do not use project repository
> ---
>
> Key: MPMD-335
> URL: https://issues.apache.org/jira/browse/MPMD-335
> Project: Maven PMD Plugin
> Issue Type: Bug
>Reporter: Andre Kalamandeen
>Assignee: Andreas Dangel
>Priority: Major
> Attachments: MPMD-335-aggregate-private-repo.zip
>
>
> I've tried to upgrade PMD to 3.16.0 and noticed that when building it tries
> to get artifacts from the default maven repository instead of the repository
> configured in the project.
> This causes issues with the build as certain artifacts are only available in
> the custom repository.
>
> The build error:
> {code:java}
> Execution pmd of goal org.apache.maven.plugins:maven-pmd-plugin:3.16.0:pmd
> failed: org.apache.maven.reporting.MavenReportException:
> org.eclipse.aether.resolution.DependencyResolutionException: The following
> artifacts could not be resolved: [REMOVED]: Failure to find [REMOVED] in
> https://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (MPMD-335) PMD 3.15.0 and 3.16.0 do not use project repository
[
https://issues.apache.org/jira/browse/MPMD-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel reopened MPMD-335:
-
Assignee: Andreas Dangel
> PMD 3.15.0 and 3.16.0 do not use project repository
> ---
>
> Key: MPMD-335
> URL: https://issues.apache.org/jira/browse/MPMD-335
> Project: Maven PMD Plugin
> Issue Type: Bug
>Reporter: Andre Kalamandeen
>Assignee: Andreas Dangel
>Priority: Major
> Attachments: MPMD-335-aggregate-private-repo.zip
>
>
> I've tried to upgrade PMD to 3.16.0 and noticed that when building it tries
> to get artifacts from the default maven repository instead of the repository
> configured in the project.
> This causes issues with the build as certain artifacts are only available in
> the custom repository.
>
> The build error:
> {code:java}
> Execution pmd of goal org.apache.maven.plugins:maven-pmd-plugin:3.16.0:pmd
> failed: org.apache.maven.reporting.MavenReportException:
> org.eclipse.aether.resolution.DependencyResolutionException: The following
> artifacts could not be resolved: [REMOVED]: Failure to find [REMOVED] in
> https://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MPMD-357) Upgrade to PMD 6.51.0
[ https://issues.apache.org/jira/browse/MPMD-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel closed MPMD-357. --- > Upgrade to PMD 6.51.0 > - > > Key: MPMD-357 > URL: https://issues.apache.org/jira/browse/MPMD-357 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.20.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (MPMD-357) Upgrade to PMD 6.51.0
[ https://issues.apache.org/jira/browse/MPMD-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel resolved MPMD-357. - Resolution: Fixed > Upgrade to PMD 6.51.0 > - > > Key: MPMD-357 > URL: https://issues.apache.org/jira/browse/MPMD-357 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.20.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPMD-356) Upgrade to PMD 6.50.0
[ https://issues.apache.org/jira/browse/MPMD-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel closed MPMD-356. --- > Upgrade to PMD 6.50.0 > - > > Key: MPMD-356 > URL: https://issues.apache.org/jira/browse/MPMD-356 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.20.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPMD-357) Upgrade to PMD 6.51.0
Andreas Dangel created MPMD-357: --- Summary: Upgrade to PMD 6.51.0 Key: MPMD-357 URL: https://issues.apache.org/jira/browse/MPMD-357 Project: Maven PMD Plugin Issue Type: Dependency upgrade Components: CPD, PMD Reporter: Andreas Dangel Assignee: Andreas Dangel Fix For: 3.20.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (MPMD-356) Upgrade to PMD 6.50.0
[ https://issues.apache.org/jira/browse/MPMD-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel resolved MPMD-356. - Resolution: Fixed > Upgrade to PMD 6.50.0 > - > > Key: MPMD-356 > URL: https://issues.apache.org/jira/browse/MPMD-356 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.20.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPMD-356) Upgrade to PMD 6.50.0
[ https://issues.apache.org/jira/browse/MPMD-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-356: Fix Version/s: 3.20.0 (was: 3.19.0) > Upgrade to PMD 6.50.0 > - > > Key: MPMD-356 > URL: https://issues.apache.org/jira/browse/MPMD-356 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.20.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPMD-356) Upgrade to PMD 6.50.0
Andreas Dangel created MPMD-356: --- Summary: Upgrade to PMD 6.50.0 Key: MPMD-356 URL: https://issues.apache.org/jira/browse/MPMD-356 Project: Maven PMD Plugin Issue Type: Dependency upgrade Components: CPD, PMD Reporter: Andreas Dangel Assignee: Andreas Dangel Fix For: 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (MPMD-354) Upgrade to PMD 6.49.0
[ https://issues.apache.org/jira/browse/MPMD-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel resolved MPMD-354. - Fix Version/s: 3.19.0 Resolution: Fixed > Upgrade to PMD 6.49.0 > - > > Key: MPMD-354 > URL: https://issues.apache.org/jira/browse/MPMD-354 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPMD-353) API incompatibility with jansi after upgrading m-shared-utils
[
https://issues.apache.org/jira/browse/MPMD-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel closed MPMD-353.
---
> API incompatibility with jansi after upgrading m-shared-utils
> -
>
> Key: MPMD-353
> URL: https://issues.apache.org/jira/browse/MPMD-353
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.18.0
>Reporter: Piotr Zygielo
>Assignee: Andreas Dangel
>Priority: Major
> Fix For: 3.19.0
>
>
> Affected maven versions:
> * 3.5.3
> * 3.6.3
> *Not* affected maven versions:
> * 3.2.5
> * 3.3.9
> * 3.8.6 (latest)
> {code:bash}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd (pmd) on project
> UnnecessaryFullyQualifiedName: Execution pmd of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd:
> java.lang.NoSuchMethodError:
> org.fusesource.jansi.AnsiConsole.out()Lorg/fusesource/jansi/AnsiPrintStream;
> Error: -
> Error: realm = plugin>org.apache.maven.plugins:maven-pmd-plugin:3.18.0
> Error: strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> Error: urls[0] =
> file:/home/runner/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.jar
> Error: urls[1] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-core/6.48.0/pmd-core-6.48.0.jar
> Error: urls[2] =
> file:/home/runner/.m2/repository/org/antlr/antlr4-runtime/4.7.2/antlr4-runtime-4.7.2.jar
> Error: urls[3] =
> file:/home/runner/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
> Error: urls[4] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
> Error: urls[5] =
> file:/home/runner/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
> Error: urls[6] =
> file:/home/runner/.m2/repository/com/google/code/gson/gson/2.8.9/gson-2.8.9.jar
> Error: urls[7] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
> Error: urls[8] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-java/6.48.0/pmd-java-6.48.0.jar
> Error: urls[9] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar
> Error: urls[10] =
> file:/home/runner/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> Error: urls[11] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> Error: urls[12] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> Error: urls[13] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> Error: urls[14] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> Error: urls[15] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> Error: urls[16] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.1.1/plexus-component-annotations-2.1.1.jar
> Error: urls[17] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.3.1/maven-common-artifact-filters-3.3.1.jar
> Error: urls[18] =
> file:/home/runner/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
> Error: urls[19] =
> file:/home/runner/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
> Error: urls[20] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-javascript/6.48.0/pmd-javascript-6.48.0.jar
> Error: urls[21] =
> file:/home/runner/.m2/repository/org/mozilla/rhino/1.7.14/rhino-1.7.14.jar
> Error: urls[22] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-jsp/6.48.0/pmd-jsp-6.48.0.jar
> Error: urls[23] =
> file:/home/runner/.m2/repository/org/slf4j/jul-to-slf4j/1.7.36/jul-to-slf4j-1.7.36.jar
> Error: urls[24] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.11.1/doxia-sink-api-1.11.1.jar
> Error: urls[25] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.11.1/doxia-logging-api-1.11.1.jar
> Error: urls[26] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.11.1/doxia-decoration-model-1.11.1.jar
> Error: urls[27] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.11.1/doxia-site-renderer-1.11.1.jar
> Error: urls[28] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-core/1.11.1/doxia-core-1.11.1.jar
> Error: urls[29] =
[jira] [Updated] (MPMD-353) API incompatibility with jansi after upgrading m-shared-utils
[
https://issues.apache.org/jira/browse/MPMD-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel updated MPMD-353:
Fix Version/s: 3.19.0
> API incompatibility with jansi after upgrading m-shared-utils
> -
>
> Key: MPMD-353
> URL: https://issues.apache.org/jira/browse/MPMD-353
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.18.0
>Reporter: Piotr Zygielo
>Assignee: Andreas Dangel
>Priority: Major
> Fix For: 3.19.0
>
>
> Affected maven versions:
> * 3.5.3
> * 3.6.3
> *Not* affected maven versions:
> * 3.2.5
> * 3.3.9
> * 3.8.6 (latest)
> {code:bash}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd (pmd) on project
> UnnecessaryFullyQualifiedName: Execution pmd of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd:
> java.lang.NoSuchMethodError:
> org.fusesource.jansi.AnsiConsole.out()Lorg/fusesource/jansi/AnsiPrintStream;
> Error: -
> Error: realm = plugin>org.apache.maven.plugins:maven-pmd-plugin:3.18.0
> Error: strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> Error: urls[0] =
> file:/home/runner/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.jar
> Error: urls[1] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-core/6.48.0/pmd-core-6.48.0.jar
> Error: urls[2] =
> file:/home/runner/.m2/repository/org/antlr/antlr4-runtime/4.7.2/antlr4-runtime-4.7.2.jar
> Error: urls[3] =
> file:/home/runner/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
> Error: urls[4] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
> Error: urls[5] =
> file:/home/runner/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
> Error: urls[6] =
> file:/home/runner/.m2/repository/com/google/code/gson/gson/2.8.9/gson-2.8.9.jar
> Error: urls[7] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
> Error: urls[8] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-java/6.48.0/pmd-java-6.48.0.jar
> Error: urls[9] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar
> Error: urls[10] =
> file:/home/runner/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> Error: urls[11] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> Error: urls[12] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> Error: urls[13] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> Error: urls[14] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> Error: urls[15] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> Error: urls[16] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.1.1/plexus-component-annotations-2.1.1.jar
> Error: urls[17] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.3.1/maven-common-artifact-filters-3.3.1.jar
> Error: urls[18] =
> file:/home/runner/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
> Error: urls[19] =
> file:/home/runner/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
> Error: urls[20] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-javascript/6.48.0/pmd-javascript-6.48.0.jar
> Error: urls[21] =
> file:/home/runner/.m2/repository/org/mozilla/rhino/1.7.14/rhino-1.7.14.jar
> Error: urls[22] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-jsp/6.48.0/pmd-jsp-6.48.0.jar
> Error: urls[23] =
> file:/home/runner/.m2/repository/org/slf4j/jul-to-slf4j/1.7.36/jul-to-slf4j-1.7.36.jar
> Error: urls[24] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.11.1/doxia-sink-api-1.11.1.jar
> Error: urls[25] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.11.1/doxia-logging-api-1.11.1.jar
> Error: urls[26] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.11.1/doxia-decoration-model-1.11.1.jar
> Error: urls[27] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.11.1/doxia-site-renderer-1.11.1.jar
> Error: urls[28] =
>
[jira] [Closed] (MPMD-354) Upgrade to PMD 6.49.0
[ https://issues.apache.org/jira/browse/MPMD-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel closed MPMD-354. --- > Upgrade to PMD 6.49.0 > - > > Key: MPMD-354 > URL: https://issues.apache.org/jira/browse/MPMD-354 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPMD-354) Upgrade to PMD 6.49.0
[ https://issues.apache.org/jira/browse/MPMD-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598778#comment-17598778 ] Andreas Dangel commented on MPMD-354: - Fixed with: https://gitbox.apache.org/repos/asf?p=maven-pmd-plugin.git;a=commit;h=ebd3579da3099ab558e4414029ae2149eebc4178 > Upgrade to PMD 6.49.0 > - > > Key: MPMD-354 > URL: https://issues.apache.org/jira/browse/MPMD-354 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (MPMD-353) API incompatibility with jansi after upgrading m-shared-utils
[
https://issues.apache.org/jira/browse/MPMD-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel resolved MPMD-353.
-
Resolution: Fixed
> API incompatibility with jansi after upgrading m-shared-utils
> -
>
> Key: MPMD-353
> URL: https://issues.apache.org/jira/browse/MPMD-353
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.18.0
>Reporter: Piotr Zygielo
>Assignee: Andreas Dangel
>Priority: Major
>
> Affected maven versions:
> * 3.5.3
> * 3.6.3
> *Not* affected maven versions:
> * 3.2.5
> * 3.3.9
> * 3.8.6 (latest)
> {code:bash}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd (pmd) on project
> UnnecessaryFullyQualifiedName: Execution pmd of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd:
> java.lang.NoSuchMethodError:
> org.fusesource.jansi.AnsiConsole.out()Lorg/fusesource/jansi/AnsiPrintStream;
> Error: -
> Error: realm = plugin>org.apache.maven.plugins:maven-pmd-plugin:3.18.0
> Error: strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> Error: urls[0] =
> file:/home/runner/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.jar
> Error: urls[1] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-core/6.48.0/pmd-core-6.48.0.jar
> Error: urls[2] =
> file:/home/runner/.m2/repository/org/antlr/antlr4-runtime/4.7.2/antlr4-runtime-4.7.2.jar
> Error: urls[3] =
> file:/home/runner/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
> Error: urls[4] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
> Error: urls[5] =
> file:/home/runner/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
> Error: urls[6] =
> file:/home/runner/.m2/repository/com/google/code/gson/gson/2.8.9/gson-2.8.9.jar
> Error: urls[7] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
> Error: urls[8] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-java/6.48.0/pmd-java-6.48.0.jar
> Error: urls[9] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar
> Error: urls[10] =
> file:/home/runner/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> Error: urls[11] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> Error: urls[12] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> Error: urls[13] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> Error: urls[14] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> Error: urls[15] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> Error: urls[16] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.1.1/plexus-component-annotations-2.1.1.jar
> Error: urls[17] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.3.1/maven-common-artifact-filters-3.3.1.jar
> Error: urls[18] =
> file:/home/runner/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
> Error: urls[19] =
> file:/home/runner/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
> Error: urls[20] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-javascript/6.48.0/pmd-javascript-6.48.0.jar
> Error: urls[21] =
> file:/home/runner/.m2/repository/org/mozilla/rhino/1.7.14/rhino-1.7.14.jar
> Error: urls[22] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-jsp/6.48.0/pmd-jsp-6.48.0.jar
> Error: urls[23] =
> file:/home/runner/.m2/repository/org/slf4j/jul-to-slf4j/1.7.36/jul-to-slf4j-1.7.36.jar
> Error: urls[24] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.11.1/doxia-sink-api-1.11.1.jar
> Error: urls[25] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.11.1/doxia-logging-api-1.11.1.jar
> Error: urls[26] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.11.1/doxia-decoration-model-1.11.1.jar
> Error: urls[27] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.11.1/doxia-site-renderer-1.11.1.jar
> Error: urls[28] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-core/1.11.1/doxia-core-1.11.1.jar
> Error: urls[29] =
>
[jira] [Commented] (MPMD-353) API incompatibility with jansi after upgrading m-shared-utils
[
https://issues.apache.org/jira/browse/MPMD-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598771#comment-17598771
]
Andreas Dangel commented on MPMD-353:
-
Fixed with:
https://gitbox.apache.org/repos/asf?p=maven-pmd-plugin.git;a=commit;h=7b4c330399faa65b8800b6a3dfd9d60a661178b8
> API incompatibility with jansi after upgrading m-shared-utils
> -
>
> Key: MPMD-353
> URL: https://issues.apache.org/jira/browse/MPMD-353
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.18.0
>Reporter: Piotr Zygielo
>Assignee: Andreas Dangel
>Priority: Major
>
> Affected maven versions:
> * 3.5.3
> * 3.6.3
> *Not* affected maven versions:
> * 3.2.5
> * 3.3.9
> * 3.8.6 (latest)
> {code:bash}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd (pmd) on project
> UnnecessaryFullyQualifiedName: Execution pmd of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd:
> java.lang.NoSuchMethodError:
> org.fusesource.jansi.AnsiConsole.out()Lorg/fusesource/jansi/AnsiPrintStream;
> Error: -
> Error: realm = plugin>org.apache.maven.plugins:maven-pmd-plugin:3.18.0
> Error: strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> Error: urls[0] =
> file:/home/runner/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.jar
> Error: urls[1] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-core/6.48.0/pmd-core-6.48.0.jar
> Error: urls[2] =
> file:/home/runner/.m2/repository/org/antlr/antlr4-runtime/4.7.2/antlr4-runtime-4.7.2.jar
> Error: urls[3] =
> file:/home/runner/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
> Error: urls[4] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
> Error: urls[5] =
> file:/home/runner/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
> Error: urls[6] =
> file:/home/runner/.m2/repository/com/google/code/gson/gson/2.8.9/gson-2.8.9.jar
> Error: urls[7] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
> Error: urls[8] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-java/6.48.0/pmd-java-6.48.0.jar
> Error: urls[9] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar
> Error: urls[10] =
> file:/home/runner/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> Error: urls[11] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> Error: urls[12] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> Error: urls[13] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> Error: urls[14] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> Error: urls[15] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> Error: urls[16] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.1.1/plexus-component-annotations-2.1.1.jar
> Error: urls[17] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.3.1/maven-common-artifact-filters-3.3.1.jar
> Error: urls[18] =
> file:/home/runner/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
> Error: urls[19] =
> file:/home/runner/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
> Error: urls[20] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-javascript/6.48.0/pmd-javascript-6.48.0.jar
> Error: urls[21] =
> file:/home/runner/.m2/repository/org/mozilla/rhino/1.7.14/rhino-1.7.14.jar
> Error: urls[22] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-jsp/6.48.0/pmd-jsp-6.48.0.jar
> Error: urls[23] =
> file:/home/runner/.m2/repository/org/slf4j/jul-to-slf4j/1.7.36/jul-to-slf4j-1.7.36.jar
> Error: urls[24] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.11.1/doxia-sink-api-1.11.1.jar
> Error: urls[25] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.11.1/doxia-logging-api-1.11.1.jar
> Error: urls[26] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.11.1/doxia-decoration-model-1.11.1.jar
> Error: urls[27] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.11.1/doxia-site-renderer-1.11.1.jar
>
[jira] [Updated] (MPMD-354) Upgrade to PMD 6.49.0
[ https://issues.apache.org/jira/browse/MPMD-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-354: Fix Version/s: (was: 3.18.0) > Upgrade to PMD 6.49.0 > - > > Key: MPMD-354 > URL: https://issues.apache.org/jira/browse/MPMD-354 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPMD-354) Upgrade to PMD 6.49.0
Andreas Dangel created MPMD-354: --- Summary: Upgrade to PMD 6.49.0 Key: MPMD-354 URL: https://issues.apache.org/jira/browse/MPMD-354 Project: Maven PMD Plugin Issue Type: Dependency upgrade Components: CPD, PMD Reporter: Andreas Dangel Assignee: Andreas Dangel Fix For: 3.18.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPMD-353) API incompatibility with jansi after upgrading m-shared-utils
[
https://issues.apache.org/jira/browse/MPMD-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel updated MPMD-353:
Description:
Affected maven versions:
* 3.5.3
* 3.6.3
*Not* affected maven versions:
* 3.2.5
* 3.3.9
* 3.8.6 (latest)
{code:bash}
Error: Failed to execute goal
org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd (pmd) on project
UnnecessaryFullyQualifiedName: Execution pmd of goal
org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd:
java.lang.NoSuchMethodError:
org.fusesource.jansi.AnsiConsole.out()Lorg/fusesource/jansi/AnsiPrintStream;
Error: -
Error: realm = plugin>org.apache.maven.plugins:maven-pmd-plugin:3.18.0
Error: strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
Error: urls[0] =
file:/home/runner/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.jar
Error: urls[1] =
file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-core/6.48.0/pmd-core-6.48.0.jar
Error: urls[2] =
file:/home/runner/.m2/repository/org/antlr/antlr4-runtime/4.7.2/antlr4-runtime-4.7.2.jar
Error: urls[3] =
file:/home/runner/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
Error: urls[4] =
file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
Error: urls[5] =
file:/home/runner/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
Error: urls[6] =
file:/home/runner/.m2/repository/com/google/code/gson/gson/2.8.9/gson-2.8.9.jar
Error: urls[7] =
file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
Error: urls[8] =
file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-java/6.48.0/pmd-java-6.48.0.jar
Error: urls[9] =
file:/home/runner/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar
Error: urls[10] =
file:/home/runner/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
Error: urls[11] =
file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
Error: urls[12] =
file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
Error: urls[13] =
file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
Error: urls[14] =
file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
Error: urls[15] =
file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
Error: urls[16] =
file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.1.1/plexus-component-annotations-2.1.1.jar
Error: urls[17] =
file:/home/runner/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.3.1/maven-common-artifact-filters-3.3.1.jar
Error: urls[18] =
file:/home/runner/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
Error: urls[19] =
file:/home/runner/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
Error: urls[20] =
file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-javascript/6.48.0/pmd-javascript-6.48.0.jar
Error: urls[21] =
file:/home/runner/.m2/repository/org/mozilla/rhino/1.7.14/rhino-1.7.14.jar
Error: urls[22] =
file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-jsp/6.48.0/pmd-jsp-6.48.0.jar
Error: urls[23] =
file:/home/runner/.m2/repository/org/slf4j/jul-to-slf4j/1.7.36/jul-to-slf4j-1.7.36.jar
Error: urls[24] =
file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.11.1/doxia-sink-api-1.11.1.jar
Error: urls[25] =
file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.11.1/doxia-logging-api-1.11.1.jar
Error: urls[26] =
file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.11.1/doxia-decoration-model-1.11.1.jar
Error: urls[27] =
file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.11.1/doxia-site-renderer-1.11.1.jar
Error: urls[28] =
file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-core/1.11.1/doxia-core-1.11.1.jar
Error: urls[29] =
file:/home/runner/.m2/repository/org/apache/commons/commons-text/1.3/commons-text-1.3.jar
Error: urls[30] =
file:/home/runner/.m2/repository/org/apache/httpcomponents/httpcore/4.4.14/httpcore-4.4.14.jar
Error: urls[31] =
file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-skin-model/1.11.1/doxia-skin-model-1.11.1.jar
Error: urls[32] =
file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.11.1/doxia-module-xhtml-1.11.1.jar
Error: urls[33] =
file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml5/1.11.1/doxia-module-xhtml5-1.11.1.jar
Error: urls[34] =
[jira] [Commented] (MPMD-353) API incompatibility with jansi after upgrading m-shared-utils
[
https://issues.apache.org/jira/browse/MPMD-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17585359#comment-17585359
]
Andreas Dangel commented on MPMD-353:
-
I've tested the original suggestion
{quote}Maybe not call method MessageUtils.setColorEnabled from pmd?
{quote}
and it turns out, that this method call doesn't seem to be necessary at all.
I've tested various combinations (toolchain and debug logging) and always got
correctly colorized log output. If I remember correctly, I had the problem when
executing PMD through toolchain, that maven logging was colorized, but the log
output produced by PMD run via toolchain wasn't - but I couldn't reproduce the
problem now.
I've created a PR -> [https://github.com/apache/maven-pmd-plugin/pull/91]
Let's see, if the CI builds turns green again
->
[https://ci-maven.apache.org/blue/organizations/jenkins/Maven%2Fmaven-box%2Fmaven-pmd-plugin/detail/MPMD-353/1/pipeline]
[~michael-o] Would this "bug" justify a 3.18.1 version or should it go into a
future 3.19.0? Please create the version in JIRA, thanks!
Only old maven versions would are affected...
> API incompatibility with jansi after upgrading m-shared-utils
> -
>
> Key: MPMD-353
> URL: https://issues.apache.org/jira/browse/MPMD-353
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.18.0
>Reporter: Piotr Zygielo
>Assignee: Andreas Dangel
>Priority: Major
>
> {code:bash}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd (pmd) on project
> UnnecessaryFullyQualifiedName: Execution pmd of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd:
> java.lang.NoSuchMethodError:
> org.fusesource.jansi.AnsiConsole.out()Lorg/fusesource/jansi/AnsiPrintStream;
> Error: -
> Error: realm = plugin>org.apache.maven.plugins:maven-pmd-plugin:3.18.0
> Error: strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> Error: urls[0] =
> file:/home/runner/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.jar
> Error: urls[1] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-core/6.48.0/pmd-core-6.48.0.jar
> Error: urls[2] =
> file:/home/runner/.m2/repository/org/antlr/antlr4-runtime/4.7.2/antlr4-runtime-4.7.2.jar
> Error: urls[3] =
> file:/home/runner/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
> Error: urls[4] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
> Error: urls[5] =
> file:/home/runner/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
> Error: urls[6] =
> file:/home/runner/.m2/repository/com/google/code/gson/gson/2.8.9/gson-2.8.9.jar
> Error: urls[7] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
> Error: urls[8] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-java/6.48.0/pmd-java-6.48.0.jar
> Error: urls[9] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar
> Error: urls[10] =
> file:/home/runner/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> Error: urls[11] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> Error: urls[12] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> Error: urls[13] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> Error: urls[14] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> Error: urls[15] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> Error: urls[16] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.1.1/plexus-component-annotations-2.1.1.jar
> Error: urls[17] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.3.1/maven-common-artifact-filters-3.3.1.jar
> Error: urls[18] =
> file:/home/runner/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
> Error: urls[19] =
> file:/home/runner/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
> Error: urls[20] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-javascript/6.48.0/pmd-javascript-6.48.0.jar
> Error: urls[21] =
> file:/home/runner/.m2/repository/org/mozilla/rhino/1.7.14/rhino-1.7.14.jar
> Error: urls[22] =
>
[jira] [Updated] (MPMD-353) API incompatibility with jansi after upgrading m-shared-utils
[
https://issues.apache.org/jira/browse/MPMD-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel updated MPMD-353:
Summary: API incompatibility with jansi after upgrading m-shared-utils
(was: An API incompatibility was encountered while executing
org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd)
> API incompatibility with jansi after upgrading m-shared-utils
> -
>
> Key: MPMD-353
> URL: https://issues.apache.org/jira/browse/MPMD-353
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.18.0
>Reporter: Piotr Zygielo
>Priority: Major
>
> {code:bash}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd (pmd) on project
> UnnecessaryFullyQualifiedName: Execution pmd of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd:
> java.lang.NoSuchMethodError:
> org.fusesource.jansi.AnsiConsole.out()Lorg/fusesource/jansi/AnsiPrintStream;
> Error: -
> Error: realm = plugin>org.apache.maven.plugins:maven-pmd-plugin:3.18.0
> Error: strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> Error: urls[0] =
> file:/home/runner/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.jar
> Error: urls[1] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-core/6.48.0/pmd-core-6.48.0.jar
> Error: urls[2] =
> file:/home/runner/.m2/repository/org/antlr/antlr4-runtime/4.7.2/antlr4-runtime-4.7.2.jar
> Error: urls[3] =
> file:/home/runner/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
> Error: urls[4] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
> Error: urls[5] =
> file:/home/runner/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
> Error: urls[6] =
> file:/home/runner/.m2/repository/com/google/code/gson/gson/2.8.9/gson-2.8.9.jar
> Error: urls[7] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
> Error: urls[8] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-java/6.48.0/pmd-java-6.48.0.jar
> Error: urls[9] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar
> Error: urls[10] =
> file:/home/runner/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> Error: urls[11] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> Error: urls[12] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> Error: urls[13] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> Error: urls[14] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> Error: urls[15] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> Error: urls[16] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.1.1/plexus-component-annotations-2.1.1.jar
> Error: urls[17] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.3.1/maven-common-artifact-filters-3.3.1.jar
> Error: urls[18] =
> file:/home/runner/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
> Error: urls[19] =
> file:/home/runner/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
> Error: urls[20] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-javascript/6.48.0/pmd-javascript-6.48.0.jar
> Error: urls[21] =
> file:/home/runner/.m2/repository/org/mozilla/rhino/1.7.14/rhino-1.7.14.jar
> Error: urls[22] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-jsp/6.48.0/pmd-jsp-6.48.0.jar
> Error: urls[23] =
> file:/home/runner/.m2/repository/org/slf4j/jul-to-slf4j/1.7.36/jul-to-slf4j-1.7.36.jar
> Error: urls[24] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.11.1/doxia-sink-api-1.11.1.jar
> Error: urls[25] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.11.1/doxia-logging-api-1.11.1.jar
> Error: urls[26] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.11.1/doxia-decoration-model-1.11.1.jar
> Error: urls[27] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.11.1/doxia-site-renderer-1.11.1.jar
> Error: urls[28] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-core/1.11.1/doxia-core-1.11.1.jar
> Error:
[jira] [Assigned] (MPMD-353) API incompatibility with jansi after upgrading m-shared-utils
[
https://issues.apache.org/jira/browse/MPMD-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel reassigned MPMD-353:
---
Assignee: Andreas Dangel
> API incompatibility with jansi after upgrading m-shared-utils
> -
>
> Key: MPMD-353
> URL: https://issues.apache.org/jira/browse/MPMD-353
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.18.0
>Reporter: Piotr Zygielo
>Assignee: Andreas Dangel
>Priority: Major
>
> {code:bash}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd (pmd) on project
> UnnecessaryFullyQualifiedName: Execution pmd of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd:
> java.lang.NoSuchMethodError:
> org.fusesource.jansi.AnsiConsole.out()Lorg/fusesource/jansi/AnsiPrintStream;
> Error: -
> Error: realm = plugin>org.apache.maven.plugins:maven-pmd-plugin:3.18.0
> Error: strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> Error: urls[0] =
> file:/home/runner/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.jar
> Error: urls[1] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-core/6.48.0/pmd-core-6.48.0.jar
> Error: urls[2] =
> file:/home/runner/.m2/repository/org/antlr/antlr4-runtime/4.7.2/antlr4-runtime-4.7.2.jar
> Error: urls[3] =
> file:/home/runner/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
> Error: urls[4] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
> Error: urls[5] =
> file:/home/runner/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
> Error: urls[6] =
> file:/home/runner/.m2/repository/com/google/code/gson/gson/2.8.9/gson-2.8.9.jar
> Error: urls[7] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
> Error: urls[8] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-java/6.48.0/pmd-java-6.48.0.jar
> Error: urls[9] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar
> Error: urls[10] =
> file:/home/runner/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> Error: urls[11] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> Error: urls[12] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> Error: urls[13] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> Error: urls[14] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> Error: urls[15] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> Error: urls[16] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.1.1/plexus-component-annotations-2.1.1.jar
> Error: urls[17] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.3.1/maven-common-artifact-filters-3.3.1.jar
> Error: urls[18] =
> file:/home/runner/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
> Error: urls[19] =
> file:/home/runner/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
> Error: urls[20] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-javascript/6.48.0/pmd-javascript-6.48.0.jar
> Error: urls[21] =
> file:/home/runner/.m2/repository/org/mozilla/rhino/1.7.14/rhino-1.7.14.jar
> Error: urls[22] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-jsp/6.48.0/pmd-jsp-6.48.0.jar
> Error: urls[23] =
> file:/home/runner/.m2/repository/org/slf4j/jul-to-slf4j/1.7.36/jul-to-slf4j-1.7.36.jar
> Error: urls[24] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.11.1/doxia-sink-api-1.11.1.jar
> Error: urls[25] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.11.1/doxia-logging-api-1.11.1.jar
> Error: urls[26] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.11.1/doxia-decoration-model-1.11.1.jar
> Error: urls[27] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.11.1/doxia-site-renderer-1.11.1.jar
> Error: urls[28] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-core/1.11.1/doxia-core-1.11.1.jar
> Error: urls[29] =
> file:/home/runner/.m2/repository/org/apache/commons/commons-text/1.3/commons-text-1.3.jar
> Error: urls[30] =
[jira] [Commented] (MPMD-353) An API incompatibility was encountered while executing org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd
[
https://issues.apache.org/jira/browse/MPMD-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584412#comment-17584412
]
Andreas Dangel commented on MPMD-353:
-
I added that in case PMD is executed via toolchain - then it's executed in a
separate process and I tried to setup the logging as before. Not calling
{{MessageUtils.setColorEnabled}} would only result in monochrome log output
when running PMD with a configured toolchain... only an aesthetic issue.
The problem appears only with maven 3.6.3 - this ships with jansi 1.17.1.
Maven Shared Utils 3.3.4 is compiled against jansi 2.2.0 (as an optional
dependency).
Would it be an option to catch this MethodNotFoundError and ignore it? As
described above, it should only have the effect, that logging from PMD might be
monochrome - but would only affect maven 3.6.x users...
> An API incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd
> ---
>
> Key: MPMD-353
> URL: https://issues.apache.org/jira/browse/MPMD-353
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.18.0
>Reporter: Piotr Zygielo
>Priority: Major
>
> {code:bash}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd (pmd) on project
> UnnecessaryFullyQualifiedName: Execution pmd of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd:
> java.lang.NoSuchMethodError:
> org.fusesource.jansi.AnsiConsole.out()Lorg/fusesource/jansi/AnsiPrintStream;
> Error: -
> Error: realm = plugin>org.apache.maven.plugins:maven-pmd-plugin:3.18.0
> Error: strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> Error: urls[0] =
> file:/home/runner/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.jar
> Error: urls[1] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-core/6.48.0/pmd-core-6.48.0.jar
> Error: urls[2] =
> file:/home/runner/.m2/repository/org/antlr/antlr4-runtime/4.7.2/antlr4-runtime-4.7.2.jar
> Error: urls[3] =
> file:/home/runner/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
> Error: urls[4] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
> Error: urls[5] =
> file:/home/runner/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
> Error: urls[6] =
> file:/home/runner/.m2/repository/com/google/code/gson/gson/2.8.9/gson-2.8.9.jar
> Error: urls[7] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
> Error: urls[8] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-java/6.48.0/pmd-java-6.48.0.jar
> Error: urls[9] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar
> Error: urls[10] =
> file:/home/runner/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> Error: urls[11] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> Error: urls[12] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> Error: urls[13] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> Error: urls[14] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> Error: urls[15] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> Error: urls[16] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.1.1/plexus-component-annotations-2.1.1.jar
> Error: urls[17] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.3.1/maven-common-artifact-filters-3.3.1.jar
> Error: urls[18] =
> file:/home/runner/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
> Error: urls[19] =
> file:/home/runner/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
> Error: urls[20] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-javascript/6.48.0/pmd-javascript-6.48.0.jar
> Error: urls[21] =
> file:/home/runner/.m2/repository/org/mozilla/rhino/1.7.14/rhino-1.7.14.jar
> Error: urls[22] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-jsp/6.48.0/pmd-jsp-6.48.0.jar
> Error: urls[23] =
> file:/home/runner/.m2/repository/org/slf4j/jul-to-slf4j/1.7.36/jul-to-slf4j-1.7.36.jar
> Error: urls[24] =
>
[jira] [Closed] (MPMD-348) Support Java 19
[ https://issues.apache.org/jira/browse/MPMD-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel closed MPMD-348. --- Resolution: Fixed Fixed: https://gitbox.apache.org/repos/asf?p=maven-pmd-plugin.git;a=commit;h=2ecd5788286c80b12136cb7e86a6ff1795c53e23 > Support Java 19 > --- > > Key: MPMD-348 > URL: https://issues.apache.org/jira/browse/MPMD-348 > Project: Maven PMD Plugin > Issue Type: New Feature > Components: PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.18.0 > > > With the next PMD version 6.48.0, Java 19 is supported. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPMD-348) Support Java 19
[ https://issues.apache.org/jira/browse/MPMD-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-348: Fix Version/s: 3.18.0 (was: 3.17.0) > Support Java 19 > --- > > Key: MPMD-348 > URL: https://issues.apache.org/jira/browse/MPMD-348 > Project: Maven PMD Plugin > Issue Type: New Feature > Components: PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.18.0 > > > With the next PMD version 6.48.0, Java 19 is supported. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPMD-347) Upgrade to PMD 6.48.0
[ https://issues.apache.org/jira/browse/MPMD-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel closed MPMD-347. --- Resolution: Fixed Fixed: https://gitbox.apache.org/repos/asf?p=maven-pmd-plugin.git;a=commit;h=10d345c3588fad71df9f7e5bf505e1ece2817c74 > Upgrade to PMD 6.48.0 > - > > Key: MPMD-347 > URL: https://issues.apache.org/jira/browse/MPMD-347 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.18.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPMD-348) Support Java 19
[ https://issues.apache.org/jira/browse/MPMD-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-348: Description: With the next PMD version 6.48.0, Java 19 is supported. (was: With the next PMD version 6.49.0, Java 19 is supported.) > Support Java 19 > --- > > Key: MPMD-348 > URL: https://issues.apache.org/jira/browse/MPMD-348 > Project: Maven PMD Plugin > Issue Type: New Feature > Components: PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.17.0 > > > With the next PMD version 6.48.0, Java 19 is supported. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPMD-348) Support Java 19
[ https://issues.apache.org/jira/browse/MPMD-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-348: Description: With the next PMD version 6.49.0, Java 19 is supported. (was: With the next PMD version 6.44.0, Java 18 will be supported.) > Support Java 19 > --- > > Key: MPMD-348 > URL: https://issues.apache.org/jira/browse/MPMD-348 > Project: Maven PMD Plugin > Issue Type: New Feature > Components: PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.17.0 > > > With the next PMD version 6.49.0, Java 19 is supported. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPMD-348) Support Java 19
Andreas Dangel created MPMD-348: --- Summary: Support Java 19 Key: MPMD-348 URL: https://issues.apache.org/jira/browse/MPMD-348 Project: Maven PMD Plugin Issue Type: New Feature Components: PMD Reporter: Andreas Dangel Assignee: Andreas Dangel Fix For: 3.17.0 With the next PMD version 6.44.0, Java 18 will be supported. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPMD-347) Upgrade to PMD 6.48.0
Andreas Dangel created MPMD-347: --- Summary: Upgrade to PMD 6.48.0 Key: MPMD-347 URL: https://issues.apache.org/jira/browse/MPMD-347 Project: Maven PMD Plugin Issue Type: Dependency upgrade Components: CPD, PMD Reporter: Andreas Dangel Assignee: Andreas Dangel Fix For: 3.18.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPMD-346) Source encoding is not applied in PmdExecutor
[ https://issues.apache.org/jira/browse/MPMD-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel closed MPMD-346. --- Resolution: Duplicate > Source encoding is not applied in PmdExecutor > - > > Key: MPMD-346 > URL: https://issues.apache.org/jira/browse/MPMD-346 > Project: Maven PMD Plugin > Issue Type: Bug > Components: PMD >Reporter: Sérgio Siegrist >Priority: Major > Labels: encoding > > `PmdExecutor` is missing: > configuration.setSourceEncoding( request.getSourceEncoding() ); > Hence, source files are being processed with the system default encoding, > instead of the configured one. > Note: `CpdExecutor` is not missing that. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPMD-345) Upgrade to PMD 6.47.0
[ https://issues.apache.org/jira/browse/MPMD-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel closed MPMD-345. --- Resolution: Fixed > Upgrade to PMD 6.47.0 > - > > Key: MPMD-345 > URL: https://issues.apache.org/jira/browse/MPMD-345 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.18.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPMD-345) Upgrade to PMD 6.47.0
Andreas Dangel created MPMD-345: --- Summary: Upgrade to PMD 6.47.0 Key: MPMD-345 URL: https://issues.apache.org/jira/browse/MPMD-345 Project: Maven PMD Plugin Issue Type: Dependency upgrade Components: CPD, PMD Reporter: Andreas Dangel Assignee: Andreas Dangel Fix For: 3.17.0 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (MPMD-345) Upgrade to PMD 6.47.0
[ https://issues.apache.org/jira/browse/MPMD-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-345: Fix Version/s: 3.18.0 (was: 3.17.0) > Upgrade to PMD 6.47.0 > - > > Key: MPMD-345 > URL: https://issues.apache.org/jira/browse/MPMD-345 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.18.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (MPMD-344) Properties verbose and printFailingErrors are overlapping
Andreas Dangel created MPMD-344:
---
Summary: Properties verbose and printFailingErrors are overlapping
Key: MPMD-344
URL: https://issues.apache.org/jira/browse/MPMD-344
Project: Maven PMD Plugin
Issue Type: Bug
Components: PMD
Reporter: Andreas Dangel
The two properties {{verbose}} and {{printFailingErrors}} do almost the same:
* verbose: Print details of check failures to build output. - this includes
also violations that are only warnings and do not fail the build
* printFailingErrors: Print details of errors that cause build failure - this
only includes violations that fail the build
If both options are enabled, then the violations the fail the build are printed
twice.
The options should be handled more logically: If "verbose=true", then
printFailingErrors can be ignored. If "verbose=false", then only print the
failing errors if "printFailingErrors=true". That way, always the correct stuff
should be printed.
Also the properties description (javadoc) should be improved with a better
explanation.
Original issue reported here: https://github.com/pmd/pmd/issues/4001
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Closed] (MPMD-336) Replace deprecated calls to PMD
[ https://issues.apache.org/jira/browse/MPMD-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel closed MPMD-336. --- Resolution: Fixed > Replace deprecated calls to PMD > --- > > Key: MPMD-336 > URL: https://issues.apache.org/jira/browse/MPMD-336 > Project: Maven PMD Plugin > Issue Type: Task >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.17.0 > > > * configuration.prependClasspath > * Use PmdAnalysis instead of PMD.processFiles > * Use Report.filterViolations instead of creating a new Report instance -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MPMD-336) Replace deprecated calls to PMD
[ https://issues.apache.org/jira/browse/MPMD-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17544503#comment-17544503 ] Andreas Dangel commented on MPMD-336: - https://gitbox.apache.org/repos/asf?p=maven-pmd-plugin.git;a=commit;h=f26bec9283e0e0857f48deb8f2945bb807129407 > Replace deprecated calls to PMD > --- > > Key: MPMD-336 > URL: https://issues.apache.org/jira/browse/MPMD-336 > Project: Maven PMD Plugin > Issue Type: Task >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.17.0 > > > * configuration.prependClasspath > * Use PmdAnalysis instead of PMD.processFiles > * Use Report.filterViolations instead of creating a new Report instance -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Closed] (MPMD-343) Upgrade to PMD 6.46.0
[ https://issues.apache.org/jira/browse/MPMD-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel closed MPMD-343. --- Resolution: Fixed > Upgrade to PMD 6.46.0 > - > > Key: MPMD-343 > URL: https://issues.apache.org/jira/browse/MPMD-343 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.17.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MPMD-343) Upgrade to PMD 6.46.0
[ https://issues.apache.org/jira/browse/MPMD-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17544501#comment-17544501 ] Andreas Dangel commented on MPMD-343: - Updated to PMD 6.46.0: https://gitbox.apache.org/repos/asf?p=maven-pmd-plugin.git;a=commit;h=027bf252a306a95b5ef2f42bd55430dfdd74ea0e > Upgrade to PMD 6.46.0 > - > > Key: MPMD-343 > URL: https://issues.apache.org/jira/browse/MPMD-343 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.17.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (MPMD-343) Upgrade to PMD 6.46.0
Andreas Dangel created MPMD-343: --- Summary: Upgrade to PMD 6.46.0 Key: MPMD-343 URL: https://issues.apache.org/jira/browse/MPMD-343 Project: Maven PMD Plugin Issue Type: Dependency upgrade Components: CPD, PMD Reporter: Andreas Dangel Assignee: Andreas Dangel Fix For: 3.17.0 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (MPMD-337) Upgrade Maven Parent to 36
[ https://issues.apache.org/jira/browse/MPMD-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-337: Fix Version/s: 3.17.0 > Upgrade Maven Parent to 36 > -- > > Key: MPMD-337 > URL: https://issues.apache.org/jira/browse/MPMD-337 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.17.0 > > > [https://github.com/apache/maven-parent/releases/tag/maven-parent-36] > [https://github.com/apache/maven-apache-parent/releases/tag/apache-26] > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (MPMD-337) Upgrade Maven Parent to 36
[ https://issues.apache.org/jira/browse/MPMD-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-337: Description: [https://github.com/apache/maven-parent/releases/tag/maven-parent-36] [https://github.com/apache/maven-apache-parent/releases/tag/apache-26] was:https://github.com/apache/maven-parent/releases/tag/maven-parent-36 > Upgrade Maven Parent to 36 > -- > > Key: MPMD-337 > URL: https://issues.apache.org/jira/browse/MPMD-337 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > > [https://github.com/apache/maven-parent/releases/tag/maven-parent-36] > [https://github.com/apache/maven-apache-parent/releases/tag/apache-26] > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (MPMD-337) Upgrade Maven Parent to 36
[ https://issues.apache.org/jira/browse/MPMD-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-337: Description: https://github.com/apache/maven-parent/releases/tag/maven-parent-36 > Upgrade Maven Parent to 36 > -- > > Key: MPMD-337 > URL: https://issues.apache.org/jira/browse/MPMD-337 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > > https://github.com/apache/maven-parent/releases/tag/maven-parent-36 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (MPMD-337) Upgrade Maven Parent to 36
Andreas Dangel created MPMD-337: --- Summary: Upgrade Maven Parent to 36 Key: MPMD-337 URL: https://issues.apache.org/jira/browse/MPMD-337 Project: Maven PMD Plugin Issue Type: Dependency upgrade Reporter: Andreas Dangel Assignee: Andreas Dangel -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (MPMD-336) Replace deprecated calls to PMD
[ https://issues.apache.org/jira/browse/MPMD-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-336: Description: * configuration.prependClasspath * Use PmdAnalysis instead of PMD.processFiles * Use Report.filterViolations instead of creating a new Report instance > Replace deprecated calls to PMD > --- > > Key: MPMD-336 > URL: https://issues.apache.org/jira/browse/MPMD-336 > Project: Maven PMD Plugin > Issue Type: Task >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.17.0 > > > * configuration.prependClasspath > * Use PmdAnalysis instead of PMD.processFiles > * Use Report.filterViolations instead of creating a new Report instance -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (MPMD-336) Replace deprecated calls to PMD
Andreas Dangel created MPMD-336: --- Summary: Replace deprecated calls to PMD Key: MPMD-336 URL: https://issues.apache.org/jira/browse/MPMD-336 Project: Maven PMD Plugin Issue Type: Task Reporter: Andreas Dangel Assignee: Andreas Dangel Fix For: 3.17.0 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MPMD-329) Upgrade to PMD 6.45.0
[ https://issues.apache.org/jira/browse/MPMD-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17530365#comment-17530365 ] Andreas Dangel commented on MPMD-329: - Updated to PMD 6.45.0: https://gitbox.apache.org/repos/asf?p=maven-pmd-plugin.git;a=commit;h=0e8f29d228bc232f6aba51faa7bdcb910a99e666 > Upgrade to PMD 6.45.0 > - > > Key: MPMD-329 > URL: https://issues.apache.org/jira/browse/MPMD-329 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.17.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
