[jira] [Comment Edited] (MPMD-404) Upgrade to PMD 7.5.0
[ https://issues.apache.org/jira/browse/MPMD-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880253#comment-17880253 ] Piotr Zygielo edited comment on MPMD-404 at 9/9/24 11:03 AM: - I based my expectation on 3.25.0 with PMD not being updated to 7.4.0 then. I suppose - IF there is newer PMD by the next plugin release, it will will be possible to update again (like [https://github.com/apache/maven-pmd-plugin/pulls?q=is%3Apr+MPMD-393+is%3Aclosed]). was (Author: pzygielo): I based my expectation on 3.25.0 with PMD not being updated to 7.4.0 then. I suppose - IF there is 7.100 by the next plugin release, it will will be possible to update again (like https://github.com/apache/maven-pmd-plugin/pulls?q=is%3Apr+MPMD-393+is%3Aclosed). > Upgrade to PMD 7.5.0 > > > Key: MPMD-404 > URL: https://issues.apache.org/jira/browse/MPMD-404 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade >Reporter: Piotr Zygielo >Assignee: Michael Osipov >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (MPMD-404) Upgrade to PMD 7.5.0
[ https://issues.apache.org/jira/browse/MPMD-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880253#comment-17880253 ] Piotr Zygielo edited comment on MPMD-404 at 9/9/24 10:20 AM: - I based my expectation on 3.25.0 with PMD not being updated to 7.4.0 then. I suppose - IF there is 7.100 by the next plugin release, it will will be possible to update again (like https://github.com/apache/maven-pmd-plugin/pulls?q=is%3Apr+MPMD-393+is%3Aclosed). was (Author: pzygielo): I based my expectation on 3.25.0 with PMD not being updated to 7.4.0 then. I suppose - IF there is 7.100 by the next plugin release, it will will be possible to update again. > Upgrade to PMD 7.5.0 > > > Key: MPMD-404 > URL: https://issues.apache.org/jira/browse/MPMD-404 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade >Reporter: Piotr Zygielo >Assignee: Michael Osipov >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPMD-404) Upgrade to PMD 7.5.0
Piotr Zygielo created MPMD-404: -- Summary: Upgrade to PMD 7.5.0 Key: MPMD-404 URL: https://issues.apache.org/jira/browse/MPMD-404 Project: Maven PMD Plugin Issue Type: Dependency upgrade Reporter: Piotr Zygielo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPMD-403) Standalone :pmd goal cannot be executed for 'skin cannot be null'
[
https://issues.apache.org/jira/browse/MPMD-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880140#comment-17880140
]
Piotr Zygielo commented on MPMD-403:
Now, that you patiently repeated it, I can see that in {{m-jar-p}} (that I so
fixated on for no reason truly), with the help of {{{}help:effective-pom{}}},
there is {{version.maven-fluido-skin}} defined indeed.
Thank you.
> Standalone :pmd goal cannot be executed for 'skin cannot be null'
> -
>
> Key: MPMD-403
> URL: https://issues.apache.org/jira/browse/MPMD-403
> Project: Maven PMD Plugin
> Issue Type: Wish
> Components: PMD
>Affects Versions: 3.25.0
> Environment: Apache Maven 3.9.9
> (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Java version: 21.0.4
>Reporter: Piotr Zygielo
>Assignee: Michael Osipov
>Priority: Minor
>
> For example with project that has no {{m-pmd-p}} configured:
> {code:java}
> $ git init maven-jar-plugin
> $ cd maven-jar-plugin
> $ git remote add origin https://github.com/apache/maven-jar-plugin
> $ git fetch origin --depth=1 be27b5f35a8ca911a459d992c9c8f106084bf525
> $ git checkout be27b5f35a8ca911a459d992c9c8f106084bf525
> {code}
> previously (3.24.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.24.0:pmd
> ...
> [INFO] --- pmd:3.24.0:pmd (default-cli) @ maven-jar-plugin ---
> [WARNING] Unable to locate Source XRef to link to - DISABLED
> [INFO] PMD version: 7.3.0
> [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 7.372 s
> [INFO] Finished at: 2024-09-07T15:04:57+02:00
> [INFO]
>
> {code}
> while now (3.25.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 7.802 s
> [INFO] Finished at: 2024-09-07T15:08:59+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd (default-cli) on project
> maven-jar-plugin: Execution default-cli of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd failed: skin cannot be
> null -> [Help 1]
> {code}
>
> {code:java}
> # first bad commit: [c31b29af9835652db9ab0b9e919c8e14bc4efabf] [MPMD-389]
> Upgrade to Doxia 2.0.0 Milestone Stack
> {code}
>
> After checking {{site.xml}} there ({{m-jar-p}}), and adding {{}} it's
> fine to use 3.25.0.
> Thus changing the type and priority.
> Feel free to close as invalid. I'm sorry for the noise.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-403) Standalone :pmd goal cannot be executed for 'skin cannot be null'
[
https://issues.apache.org/jira/browse/MPMD-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880110#comment-17880110
]
Piotr Zygielo commented on MPMD-403:
To clarify: Currently standalone {{:pmd}} does not work in 3.25.0, and there is
no need to have issue for this in MPMD. Right?
> Standalone :pmd goal cannot be executed for 'skin cannot be null'
> -
>
> Key: MPMD-403
> URL: https://issues.apache.org/jira/browse/MPMD-403
> Project: Maven PMD Plugin
> Issue Type: Wish
> Components: PMD
>Affects Versions: 3.25.0
> Environment: Apache Maven 3.9.9
> (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Java version: 21.0.4
>Reporter: Piotr Zygielo
>Assignee: Michael Osipov
>Priority: Minor
>
> For example with project that has no {{m-pmd-p}} configured:
> {code:java}
> $ git init maven-jar-plugin
> $ cd maven-jar-plugin
> $ git remote add origin https://github.com/apache/maven-jar-plugin
> $ git fetch origin --depth=1 be27b5f35a8ca911a459d992c9c8f106084bf525
> $ git checkout be27b5f35a8ca911a459d992c9c8f106084bf525
> {code}
> previously (3.24.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.24.0:pmd
> ...
> [INFO] --- pmd:3.24.0:pmd (default-cli) @ maven-jar-plugin ---
> [WARNING] Unable to locate Source XRef to link to - DISABLED
> [INFO] PMD version: 7.3.0
> [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 7.372 s
> [INFO] Finished at: 2024-09-07T15:04:57+02:00
> [INFO]
>
> {code}
> while now (3.25.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 7.802 s
> [INFO] Finished at: 2024-09-07T15:08:59+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd (default-cli) on project
> maven-jar-plugin: Execution default-cli of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd failed: skin cannot be
> null -> [Help 1]
> {code}
>
> {code:java}
> # first bad commit: [c31b29af9835652db9ab0b9e919c8e14bc4efabf] [MPMD-389]
> Upgrade to Doxia 2.0.0 Milestone Stack
> {code}
>
> After checking {{site.xml}} there ({{m-jar-p}}), and adding {{}} it's
> fine to use 3.25.0.
> Thus changing the type and priority.
> Feel free to close as invalid. I'm sorry for the noise.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-403) Standalone :pmd goal cannot be executed for 'skin cannot be null'
[
https://issues.apache.org/jira/browse/MPMD-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880105#comment-17880105
]
Piotr Zygielo commented on MPMD-403:
{quote}So all is good and the failure is correct.
{quote}
Everything is correct, only goal cannot be executed.
> Standalone :pmd goal cannot be executed for 'skin cannot be null'
> -
>
> Key: MPMD-403
> URL: https://issues.apache.org/jira/browse/MPMD-403
> Project: Maven PMD Plugin
> Issue Type: Wish
> Components: PMD
>Affects Versions: 3.25.0
> Environment: Apache Maven 3.9.9
> (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Java version: 21.0.4
>Reporter: Piotr Zygielo
>Assignee: Michael Osipov
>Priority: Minor
>
> For example with project that has no {{m-pmd-p}} configured:
> {code:java}
> $ git init maven-jar-plugin
> $ cd maven-jar-plugin
> $ git remote add origin https://github.com/apache/maven-jar-plugin
> $ git fetch origin --depth=1 be27b5f35a8ca911a459d992c9c8f106084bf525
> $ git checkout be27b5f35a8ca911a459d992c9c8f106084bf525
> {code}
> previously (3.24.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.24.0:pmd
> ...
> [INFO] --- pmd:3.24.0:pmd (default-cli) @ maven-jar-plugin ---
> [WARNING] Unable to locate Source XRef to link to - DISABLED
> [INFO] PMD version: 7.3.0
> [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 7.372 s
> [INFO] Finished at: 2024-09-07T15:04:57+02:00
> [INFO]
>
> {code}
> while now (3.25.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 7.802 s
> [INFO] Finished at: 2024-09-07T15:08:59+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd (default-cli) on project
> maven-jar-plugin: Execution default-cli of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd failed: skin cannot be
> null -> [Help 1]
> {code}
>
> {code:java}
> # first bad commit: [c31b29af9835652db9ab0b9e919c8e14bc4efabf] [MPMD-389]
> Upgrade to Doxia 2.0.0 Milestone Stack
> {code}
>
> After checking {{site.xml}} there ({{m-jar-p}}), and adding {{}} it's
> fine to use 3.25.0.
> Thus changing the type and priority.
> Feel free to close as invalid. I'm sorry for the noise.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MPMD-403) Standalone :pmd goal cannot be executed for 'skin cannot be null'
[
https://issues.apache.org/jira/browse/MPMD-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880104#comment-17880104
]
Piotr Zygielo edited comment on MPMD-403 at 9/8/24 8:47 AM:
-Yes, it's the failure due to contents of the existing {{{}site.xml{}}}.-
was (Author: pzygielo):
Yes, it's the failure due to contents of the existing {{{}site.xml{}}}.
> Standalone :pmd goal cannot be executed for 'skin cannot be null'
> -
>
> Key: MPMD-403
> URL: https://issues.apache.org/jira/browse/MPMD-403
> Project: Maven PMD Plugin
> Issue Type: Wish
> Components: PMD
>Affects Versions: 3.25.0
> Environment: Apache Maven 3.9.9
> (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Java version: 21.0.4
>Reporter: Piotr Zygielo
>Assignee: Michael Osipov
>Priority: Minor
>
> For example with project that has no {{m-pmd-p}} configured:
> {code:java}
> $ git init maven-jar-plugin
> $ cd maven-jar-plugin
> $ git remote add origin https://github.com/apache/maven-jar-plugin
> $ git fetch origin --depth=1 be27b5f35a8ca911a459d992c9c8f106084bf525
> $ git checkout be27b5f35a8ca911a459d992c9c8f106084bf525
> {code}
> previously (3.24.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.24.0:pmd
> ...
> [INFO] --- pmd:3.24.0:pmd (default-cli) @ maven-jar-plugin ---
> [WARNING] Unable to locate Source XRef to link to - DISABLED
> [INFO] PMD version: 7.3.0
> [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 7.372 s
> [INFO] Finished at: 2024-09-07T15:04:57+02:00
> [INFO]
>
> {code}
> while now (3.25.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 7.802 s
> [INFO] Finished at: 2024-09-07T15:08:59+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd (default-cli) on project
> maven-jar-plugin: Execution default-cli of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd failed: skin cannot be
> null -> [Help 1]
> {code}
>
> {code:java}
> # first bad commit: [c31b29af9835652db9ab0b9e919c8e14bc4efabf] [MPMD-389]
> Upgrade to Doxia 2.0.0 Milestone Stack
> {code}
>
> After checking {{site.xml}} there ({{m-jar-p}}), and adding {{}} it's
> fine to use 3.25.0.
> Thus changing the type and priority.
> Feel free to close as invalid. I'm sorry for the noise.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-403) Standalone :pmd goal cannot be executed for 'skin cannot be null'
[
https://issues.apache.org/jira/browse/MPMD-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880104#comment-17880104
]
Piotr Zygielo commented on MPMD-403:
Yes, it's the failure due to contents of the existing {{{}site.xml{}}}.
> Standalone :pmd goal cannot be executed for 'skin cannot be null'
> -
>
> Key: MPMD-403
> URL: https://issues.apache.org/jira/browse/MPMD-403
> Project: Maven PMD Plugin
> Issue Type: Wish
> Components: PMD
>Affects Versions: 3.25.0
> Environment: Apache Maven 3.9.9
> (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Java version: 21.0.4
>Reporter: Piotr Zygielo
>Assignee: Michael Osipov
>Priority: Minor
>
> For example with project that has no {{m-pmd-p}} configured:
> {code:java}
> $ git init maven-jar-plugin
> $ cd maven-jar-plugin
> $ git remote add origin https://github.com/apache/maven-jar-plugin
> $ git fetch origin --depth=1 be27b5f35a8ca911a459d992c9c8f106084bf525
> $ git checkout be27b5f35a8ca911a459d992c9c8f106084bf525
> {code}
> previously (3.24.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.24.0:pmd
> ...
> [INFO] --- pmd:3.24.0:pmd (default-cli) @ maven-jar-plugin ---
> [WARNING] Unable to locate Source XRef to link to - DISABLED
> [INFO] PMD version: 7.3.0
> [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 7.372 s
> [INFO] Finished at: 2024-09-07T15:04:57+02:00
> [INFO]
>
> {code}
> while now (3.25.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 7.802 s
> [INFO] Finished at: 2024-09-07T15:08:59+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd (default-cli) on project
> maven-jar-plugin: Execution default-cli of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd failed: skin cannot be
> null -> [Help 1]
> {code}
>
> {code:java}
> # first bad commit: [c31b29af9835652db9ab0b9e919c8e14bc4efabf] [MPMD-389]
> Upgrade to Doxia 2.0.0 Milestone Stack
> {code}
>
> After checking {{site.xml}} there ({{m-jar-p}}), and adding {{}} it's
> fine to use 3.25.0.
> Thus changing the type and priority.
> Feel free to close as invalid. I'm sorry for the noise.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MPMD-403) Standalone :pmd goal cannot be executed for 'skin cannot be null'
[
https://issues.apache.org/jira/browse/MPMD-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880098#comment-17880098
]
Piotr Zygielo edited comment on MPMD-403 at 9/8/24 8:44 AM:
[~michael-o]: On empty repo and with everything re-fetched from central I'm
getting the same failure as you, indeed.
(Still, setting {{output.format}} helps.)
was (Author: pzygielo):
[~michael-o]: On empty repo and with everything re-fetched from central I'm
getting the same failure as you, indeed.
> Standalone :pmd goal cannot be executed for 'skin cannot be null'
> -
>
> Key: MPMD-403
> URL: https://issues.apache.org/jira/browse/MPMD-403
> Project: Maven PMD Plugin
> Issue Type: Wish
> Components: PMD
>Affects Versions: 3.25.0
> Environment: Apache Maven 3.9.9
> (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Java version: 21.0.4
>Reporter: Piotr Zygielo
>Assignee: Michael Osipov
>Priority: Minor
>
> For example with project that has no {{m-pmd-p}} configured:
> {code:java}
> $ git init maven-jar-plugin
> $ cd maven-jar-plugin
> $ git remote add origin https://github.com/apache/maven-jar-plugin
> $ git fetch origin --depth=1 be27b5f35a8ca911a459d992c9c8f106084bf525
> $ git checkout be27b5f35a8ca911a459d992c9c8f106084bf525
> {code}
> previously (3.24.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.24.0:pmd
> ...
> [INFO] --- pmd:3.24.0:pmd (default-cli) @ maven-jar-plugin ---
> [WARNING] Unable to locate Source XRef to link to - DISABLED
> [INFO] PMD version: 7.3.0
> [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 7.372 s
> [INFO] Finished at: 2024-09-07T15:04:57+02:00
> [INFO]
>
> {code}
> while now (3.25.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 7.802 s
> [INFO] Finished at: 2024-09-07T15:08:59+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd (default-cli) on project
> maven-jar-plugin: Execution default-cli of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd failed: skin cannot be
> null -> [Help 1]
> {code}
>
> {code:java}
> # first bad commit: [c31b29af9835652db9ab0b9e919c8e14bc4efabf] [MPMD-389]
> Upgrade to Doxia 2.0.0 Milestone Stack
> {code}
>
> After checking {{site.xml}} there ({{m-jar-p}}), and adding {{}} it's
> fine to use 3.25.0.
> Thus changing the type and priority.
> Feel free to close as invalid. I'm sorry for the noise.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-403) Standalone :pmd goal cannot be executed for 'skin cannot be null'
[
https://issues.apache.org/jira/browse/MPMD-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880071#comment-17880071
]
Piotr Zygielo commented on MPMD-403:
For completeness - with {{:pmd}} being reporting plugin, and with no goal (that
I could find) to do non-reporting analysis to produce {{pmd.xml}} only, with
reporting context (and checking for {{{}skin{}}}) being prepared early, I'm
able to work around my original problem, by configuring {{doxia}} to use other
than {{html}} format (and not fail for project with not updated
{{{}site.xml{}}}).
> Standalone :pmd goal cannot be executed for 'skin cannot be null'
> -
>
> Key: MPMD-403
> URL: https://issues.apache.org/jira/browse/MPMD-403
> Project: Maven PMD Plugin
> Issue Type: Wish
> Components: PMD
>Affects Versions: 3.25.0
> Environment: Apache Maven 3.9.9
> (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Java version: 21.0.4
>Reporter: Piotr Zygielo
>Priority: Minor
>
> For example with project that has no {{m-pmd-p}} configured:
> {code:java}
> $ git init maven-jar-plugin
> $ cd maven-jar-plugin
> $ git remote add origin https://github.com/apache/maven-jar-plugin
> $ git fetch origin --depth=1 be27b5f35a8ca911a459d992c9c8f106084bf525
> $ git checkout be27b5f35a8ca911a459d992c9c8f106084bf525
> {code}
> previously (3.24.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.24.0:pmd
> ...
> [INFO] --- pmd:3.24.0:pmd (default-cli) @ maven-jar-plugin ---
> [WARNING] Unable to locate Source XRef to link to - DISABLED
> [INFO] PMD version: 7.3.0
> [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 7.372 s
> [INFO] Finished at: 2024-09-07T15:04:57+02:00
> [INFO]
>
> {code}
> while now (3.25.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 7.802 s
> [INFO] Finished at: 2024-09-07T15:08:59+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd (default-cli) on project
> maven-jar-plugin: Execution default-cli of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd failed: skin cannot be
> null -> [Help 1]
> {code}
>
> {code:java}
> # first bad commit: [c31b29af9835652db9ab0b9e919c8e14bc4efabf] [MPMD-389]
> Upgrade to Doxia 2.0.0 Milestone Stack
> {code}
>
> After checking {{site.xml}} there ({{m-jar-p}}), and adding {{}} it's
> fine to use 3.25.0.
> Thus changing the type and priority.
> Feel free to close as invalid. I'm sorry for the noise.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-403) Standalone :pmd goal cannot be executed for 'skin cannot be null'
[
https://issues.apache.org/jira/browse/MPMD-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880045#comment-17880045
]
Piotr Zygielo commented on MPMD-403:
(Repeated for visibiliy:) Feel free to close as invalid.
> Standalone :pmd goal cannot be executed for 'skin cannot be null'
> -
>
> Key: MPMD-403
> URL: https://issues.apache.org/jira/browse/MPMD-403
> Project: Maven PMD Plugin
> Issue Type: Wish
> Components: PMD
>Affects Versions: 3.25.0
> Environment: Apache Maven 3.9.9
> (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Java version: 21.0.4
>Reporter: Piotr Zygielo
>Priority: Minor
>
> For example with project that has no {{m-pmd-p}} configured:
> {code:java}
> $ git init maven-jar-plugin
> $ cd maven-jar-plugin
> $ git remote add origin https://github.com/apache/maven-jar-plugin
> $ git fetch origin --depth=1 be27b5f35a8ca911a459d992c9c8f106084bf525
> $ git checkout be27b5f35a8ca911a459d992c9c8f106084bf525
> {code}
> previously (3.24.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.24.0:pmd
> ...
> [INFO] --- pmd:3.24.0:pmd (default-cli) @ maven-jar-plugin ---
> [WARNING] Unable to locate Source XRef to link to - DISABLED
> [INFO] PMD version: 7.3.0
> [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 7.372 s
> [INFO] Finished at: 2024-09-07T15:04:57+02:00
> [INFO]
>
> {code}
> while now (3.25.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 7.802 s
> [INFO] Finished at: 2024-09-07T15:08:59+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd (default-cli) on project
> maven-jar-plugin: Execution default-cli of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd failed: skin cannot be
> null -> [Help 1]
> {code}
>
> {code:java}
> # first bad commit: [c31b29af9835652db9ab0b9e919c8e14bc4efabf] [MPMD-389]
> Upgrade to Doxia 2.0.0 Milestone Stack
> {code}
>
> After checking {{site.xml}} there ({{m-jar-p}}), and adding {{}} it's
> fine to use 3.25.0.
> Thus changing the type and priority.
> Feel free to close as invalid. I'm sorry for the noise.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MPMD-403) Standalone :pmd goal cannot be executed for 'skin cannot be null'
[
https://issues.apache.org/jira/browse/MPMD-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Zygielo updated MPMD-403:
---
Description:
For example with project that has no {{m-pmd-p}} configured:
{code:java}
$ git init maven-jar-plugin
$ cd maven-jar-plugin
$ git remote add origin https://github.com/apache/maven-jar-plugin
$ git fetch origin --depth=1 be27b5f35a8ca911a459d992c9c8f106084bf525
$ git checkout be27b5f35a8ca911a459d992c9c8f106084bf525
{code}
previously (3.24.0):
{code:java}
$ mvn org.apache.maven.plugins:maven-pmd-plugin:3.24.0:pmd
...
[INFO] --- pmd:3.24.0:pmd (default-cli) @ maven-jar-plugin ---
[WARNING] Unable to locate Source XRef to link to - DISABLED
[INFO] PMD version: 7.3.0
[INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3
skin.
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 7.372 s
[INFO] Finished at: 2024-09-07T15:04:57+02:00
[INFO]
{code}
while now (3.25.0):
{code:java}
$ mvn org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 7.802 s
[INFO] Finished at: 2024-09-07T15:08:59+02:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd (default-cli) on project
maven-jar-plugin: Execution default-cli of goal
org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd failed: skin cannot be
null -> [Help 1]
{code}
{code:java}
# first bad commit: [c31b29af9835652db9ab0b9e919c8e14bc4efabf] [MPMD-389]
Upgrade to Doxia 2.0.0 Milestone Stack
{code}
After checking {{site.xml}} there ({{m-jar-p}}), and adding {{}} it's
fine to use 3.25.0.
Thus changing the type and priority.
Feel free to close as invalid. I'm sorry for the noise.
was:
For example with project that has no {{m-pmd-p}} configured:
{code:java}
$ git init maven-jar-plugin
$ cd maven-jar-plugin
$ git remote add origin https://github.com/apache/maven-jar-plugin
$ git fetch origin --depth=1 be27b5f35a8ca911a459d992c9c8f106084bf525
$ git checkout be27b5f35a8ca911a459d992c9c8f106084bf525
{code}
previously (3.24.0):
{code:java}
$ mvn org.apache.maven.plugins:maven-pmd-plugin:3.24.0:pmd
...
[INFO] --- pmd:3.24.0:pmd (default-cli) @ maven-jar-plugin ---
[WARNING] Unable to locate Source XRef to link to - DISABLED
[INFO] PMD version: 7.3.0
[INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3
skin.
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 7.372 s
[INFO] Finished at: 2024-09-07T15:04:57+02:00
[INFO]
{code}
while now (3.25.0):
{code:java}
$ mvn org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 7.802 s
[INFO] Finished at: 2024-09-07T15:08:59+02:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd (default-cli) on project
maven-jar-plugin: Execution default-cli of goal
org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd failed: skin cannot be
null -> [Help 1]
{code}
{code:java}
# first bad commit: [c31b29af9835652db9ab0b9e919c8e14bc4efabf] [MPMD-389]
Upgrade to Doxia 2.0.0 Milestone Stack
{code}
After checking {{site.xml}} there ({{m-jar-p}}), and adding {{}} it's
fine to use 3.25.0.
Thus changing the type and priority.
Feel free to close as invalid.
> Standalone :pmd goal cannot be executed for 'skin cannot be null'
> -
>
> Key: MPMD-403
> URL: https://issues.apache.org/jira/browse/MPMD-403
> Project: Maven PMD Plugin
> Issue Type: Wish
> Components: PMD
>Affects Versions: 3.25.0
> Environment: Apache Maven 3.9.9
> (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Java version: 21.0.4
>Reporter: Piotr Zygielo
>Priority: Minor
>
> For example with project that has no {{m-pmd-p}} configured:
> {code:java}
> $ git init maven-jar-plugin
> $ cd maven-jar-plugin
> $ git remote add origin https://github.com/apache/maven-jar-plugin
> $ git fetch origin --depth=1 be27
[jira] [Updated] (MPMD-403) Standalone :pmd goal cannot be executed for 'skin cannot be null'
[
https://issues.apache.org/jira/browse/MPMD-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Zygielo updated MPMD-403:
---
Priority: Minor (was: Major)
> Standalone :pmd goal cannot be executed for 'skin cannot be null'
> -
>
> Key: MPMD-403
> URL: https://issues.apache.org/jira/browse/MPMD-403
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.25.0
> Environment: Apache Maven 3.9.9
> (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Java version: 21.0.4
>Reporter: Piotr Zygielo
>Priority: Minor
>
> For example with project that has no {{m-pmd-p}} configured:
> {code:java}
> $ git init maven-jar-plugin
> $ cd maven-jar-plugin
> $ git remote add origin https://github.com/apache/maven-jar-plugin
> $ git fetch origin --depth=1 be27b5f35a8ca911a459d992c9c8f106084bf525
> $ git checkout be27b5f35a8ca911a459d992c9c8f106084bf525
> {code}
> previously (3.24.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.24.0:pmd
> ...
> [INFO] --- pmd:3.24.0:pmd (default-cli) @ maven-jar-plugin ---
> [WARNING] Unable to locate Source XRef to link to - DISABLED
> [INFO] PMD version: 7.3.0
> [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 7.372 s
> [INFO] Finished at: 2024-09-07T15:04:57+02:00
> [INFO]
>
> {code}
> while now (3.25.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 7.802 s
> [INFO] Finished at: 2024-09-07T15:08:59+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd (default-cli) on project
> maven-jar-plugin: Execution default-cli of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd failed: skin cannot be
> null -> [Help 1]
> {code}
>
> {code:java}
> # first bad commit: [c31b29af9835652db9ab0b9e919c8e14bc4efabf] [MPMD-389]
> Upgrade to Doxia 2.0.0 Milestone Stack
> {code}
>
> After checking {{site.xml}} there ({{m-jar-p}}), and adding {{}} it's
> fine to use 3.25.0.
> Thus changing the type and priority.
> Feel free to close as invalid.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MPMD-403) Standalone :pmd goal cannot be executed for 'skin cannot be null'
[
https://issues.apache.org/jira/browse/MPMD-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Zygielo updated MPMD-403:
---
Description:
For example with project that has no {{m-pmd-p}} configured:
{code:java}
$ git init maven-jar-plugin
$ cd maven-jar-plugin
$ git remote add origin https://github.com/apache/maven-jar-plugin
$ git fetch origin --depth=1 be27b5f35a8ca911a459d992c9c8f106084bf525
$ git checkout be27b5f35a8ca911a459d992c9c8f106084bf525
{code}
previously (3.24.0):
{code:java}
$ mvn org.apache.maven.plugins:maven-pmd-plugin:3.24.0:pmd
...
[INFO] --- pmd:3.24.0:pmd (default-cli) @ maven-jar-plugin ---
[WARNING] Unable to locate Source XRef to link to - DISABLED
[INFO] PMD version: 7.3.0
[INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3
skin.
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 7.372 s
[INFO] Finished at: 2024-09-07T15:04:57+02:00
[INFO]
{code}
while now (3.25.0):
{code:java}
$ mvn org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 7.802 s
[INFO] Finished at: 2024-09-07T15:08:59+02:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd (default-cli) on project
maven-jar-plugin: Execution default-cli of goal
org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd failed: skin cannot be
null -> [Help 1]
{code}
{code:java}
# first bad commit: [c31b29af9835652db9ab0b9e919c8e14bc4efabf] [MPMD-389]
Upgrade to Doxia 2.0.0 Milestone Stack
{code}
After checking {{site.xml}} there ({{m-jar-p}}), and adding {{}} it's
fine to use 3.25.0.
Thus changing the type and priority.
Feel free to close as invalid.
was:
For example with project that has no {{m-pmd-p}} configured:
{code:java}
$ git init maven-jar-plugin
$ cd maven-jar-plugin
$ git remote add origin https://github.com/apache/maven-jar-plugin
$ git fetch origin --depth=1 be27b5f35a8ca911a459d992c9c8f106084bf525
$ git checkout be27b5f35a8ca911a459d992c9c8f106084bf525
{code}
previously (3.24.0):
{code:java}
$ mvn org.apache.maven.plugins:maven-pmd-plugin:3.24.0:pmd
...
[INFO] --- pmd:3.24.0:pmd (default-cli) @ maven-jar-plugin ---
[WARNING] Unable to locate Source XRef to link to - DISABLED
[INFO] PMD version: 7.3.0
[INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3
skin.
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 7.372 s
[INFO] Finished at: 2024-09-07T15:04:57+02:00
[INFO]
{code}
while now (3.25.0):
{code:java}
$ mvn org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 7.802 s
[INFO] Finished at: 2024-09-07T15:08:59+02:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd (default-cli) on project
maven-jar-plugin: Execution default-cli of goal
org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd failed: skin cannot be
null -> [Help 1]
{code}
{code:java}
# first bad commit: [c31b29af9835652db9ab0b9e919c8e14bc4efabf] [MPMD-389]
Upgrade to Doxia 2.0.0 Milestone Stack
{code}
> Standalone :pmd goal cannot be executed for 'skin cannot be null'
> -
>
> Key: MPMD-403
> URL: https://issues.apache.org/jira/browse/MPMD-403
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.25.0
> Environment: Apache Maven 3.9.9
> (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Java version: 21.0.4
>Reporter: Piotr Zygielo
>Priority: Major
>
> For example with project that has no {{m-pmd-p}} configured:
> {code:java}
> $ git init maven-jar-plugin
> $ cd maven-jar-plugin
> $ git remote add origin https://github.com/apache/maven-jar-plugin
> $ git fetch origin --depth=1 be27b5f35a8ca911a459d992c9c8f106084bf525
> $ git checkout be27b5f35a8ca911a459d992c9c8f106084bf525
> {code}
> previously (3.24.0):
> {code:java}
> $ mvn org.apache.maven.plugins:maven-pmd-plugin:3.2
[jira] [Created] (MPMD-403) Standalone :pmd goal cannot be executed for 'skin cannot be null'
Piotr Zygielo created MPMD-403:
--
Summary: Standalone :pmd goal cannot be executed for 'skin cannot
be null'
Key: MPMD-403
URL: https://issues.apache.org/jira/browse/MPMD-403
Project: Maven PMD Plugin
Issue Type: Bug
Components: PMD
Affects Versions: 3.25.0
Environment: Apache Maven 3.9.9
(8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
Java version: 21.0.4
Reporter: Piotr Zygielo
For example with project that has no {{m-pmd-p}} configured:
{code:java}
$ git init maven-jar-plugin
$ cd maven-jar-plugin
$ git remote add origin https://github.com/apache/maven-jar-plugin
$ git fetch origin --depth=1 be27b5f35a8ca911a459d992c9c8f106084bf525
$ git checkout be27b5f35a8ca911a459d992c9c8f106084bf525
{code}
previously (3.24.0):
{code:java}
$ mvn org.apache.maven.plugins:maven-pmd-plugin:3.24.0:pmd
...
[INFO] --- pmd:3.24.0:pmd (default-cli) @ maven-jar-plugin ---
[WARNING] Unable to locate Source XRef to link to - DISABLED
[INFO] PMD version: 7.3.0
[INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3
skin.
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 7.372 s
[INFO] Finished at: 2024-09-07T15:04:57+02:00
[INFO]
{code}
while now (2.35.0):
{code:java}
$ mvn org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 7.802 s
[INFO] Finished at: 2024-09-07T15:08:59+02:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd (default-cli) on project
maven-jar-plugin: Execution default-cli of goal
org.apache.maven.plugins:maven-pmd-plugin:3.25.0:pmd failed: skin cannot be
null -> [Help 1]
{code}
{code}
# first bad commit: [c31b29af9835652db9ab0b9e919c8e14bc4efabf] [MPMD-389]
Upgrade to Doxia 2.0.0 Milestone Stack
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPIR-468) Warning is issued but no way to fix it is provided
[
https://issues.apache.org/jira/browse/MPIR-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880038#comment-17880038
]
Piotr Zygielo commented on MPIR-468:
I bet it was [https://github.com/pmd/pmd/issues/5091] from {{pmd:cpd}} report,
as I've stopped seeing this after bumping {{pmd-*}} to 7.4.0.
> Warning is issued but no way to fix it is provided
> --
>
> Key: MPIR-468
> URL: https://issues.apache.org/jira/browse/MPIR-468
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Philipp Ottlinger
>Priority: Major
>
> Running the site build on my
> [example|https://github.com/ottlinger/fotorenamer/blob/master/pom.xml]
> project yields the following warning, which I would like to fix, but the
> mentioned configuration option is not defined somewhere in my pom.xml.
> {quote}
> $ ./mvnw site
>
> [INFO] Configuring report plugin maven-project-info-reports-plugin:3.7.0
> [INFO] Detected 15 reports for maven-project-info-reports-plugin:3.7.0:
> ci-management, dependencies, dependency-info, dependency-management,
> distribution-management, index, issue-management, licenses, mailing-lists,
> modules, plugin-management, plugins, scm, summary, team
> [WARNING] The option skipLexicalErrors is deprecated. Use failOnError instead.
>
> {quote}
> Where is skipLexicalErrors used and should be replaced by failOnError?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SUREFIRE-2261) NullPointerException when generating a test report
[
https://issues.apache.org/jira/browse/SUREFIRE-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17878412#comment-17878412
]
Piotr Zygielo commented on SUREFIRE-2261:
-
Sounds like duplicate of SUREFIRE-2257.
> NullPointerException when generating a test report
> --
>
> Key: SUREFIRE-2261
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2261
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Report Plugin
>Affects Versions: 3.5.0
>Reporter: Andrei Solntsev
>Priority: Major
>
> I am getting NullPointerException when trying to generate test report.
> The problem is NOT reproducible with version 3.4.0.
>
> Step to reproduce:
> # `git clone g...@github.com:selenide-examples/cucumber.git`
> # `mvn surefire-report:report -Dselenide.headless=true -e`
> Result:
> {{[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-report-plugin:3.5.0:report-only
> (default-cli) on project selenide-cucumber: Execution default-cli of goal
> org.apache.maven.plugins:maven-surefire-report-plugin:3.5.0:report-only
> failed: Cannot invoke "Object.toString()" because "value" is null -> [Help
> 1]}}
> {{org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-surefire-report-plugin:3.5.0:report-only
> (default-cli) on project selenide-cucumber: Execution default-cli of goal
> org.apache.maven.plugins:maven-surefire-report-plugin:3.5.0:report-only
> failed: Cannot invoke "Object.toString()" because "value" is null}}
> {{ at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:333)}}
> {{ at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)}}
> {{ at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)}}
> {{ at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)}}
> {{ at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)}}
> {{ at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)}}
> {{ at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)}}
> {{ at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)}}
> {{ 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:906)}}
> {{ 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:77)}}
> {{ at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)}}
> {{ at java.lang.reflect.Method.invoke (Method.java:569)}}
> {{ at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:255)}}
> {{ at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:201)}}
> {{ at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:361)}}
> {{ at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:314)}}
> {{Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-cli of goal
> org.apache.maven.plugins:maven-surefire-report-plugin:3.5.0:report-only
> failed: Cannot invoke "Object.toString()" because "value" is null}}
> {{ at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:133)}}
> {{ at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)}}
> {{ at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)}}
> {{ at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)}}
> {{ at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)}}
> {{
[jira] [Commented] (SUREFIRE-2257) [REGRESSION] NPEx: Cannot invoke "Object.toString()" because "value" is null
[
https://issues.apache.org/jira/browse/SUREFIRE-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877343#comment-17877343
]
Piotr Zygielo commented on SUREFIRE-2257:
-
bq. PR created, please test
Used 69c1b46d and all is fine now (no NPEx on report generation)
!surefire-3.5.0-2-g69c1b46d8.png!
Thanks!
> [REGRESSION] NPEx: Cannot invoke "Object.toString()" because "value" is null
>
>
> Key: SUREFIRE-2257
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2257
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Report Plugin
>Affects Versions: 3.5.0
>Reporter: Piotr Zygielo
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.5.1
>
> Attachments: 3.4.0-surefire-report.png, screenshot-1.png,
> screenshot-2.png, surefire-3.5.0-2-g69c1b46d8.png
>
>
> On upgrading from 3.4.0 to 3.5.0 (so it works fine in 3.4.0), build breaks
> with following:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on
> project X: Failed to render site: Error generating
> maven-surefire-report-plugin:3.5.0:report-only report: Cannot invoke
> "Object.toString()" because "value" is null -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on
> project X: Failed to render site
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> 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:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:103)
> at java.lang.reflect.Method.invoke (Method.java:580)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:255)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:201)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:361)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:314)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to render
> site
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:119)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.build
[jira] [Updated] (SUREFIRE-2257) [REGRESSION] NPEx: Cannot invoke "Object.toString()" because "value" is null
[
https://issues.apache.org/jira/browse/SUREFIRE-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Zygielo updated SUREFIRE-2257:
Attachment: surefire-3.5.0-2-g69c1b46d8.png
> [REGRESSION] NPEx: Cannot invoke "Object.toString()" because "value" is null
>
>
> Key: SUREFIRE-2257
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2257
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Report Plugin
>Affects Versions: 3.5.0
>Reporter: Piotr Zygielo
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.5.1
>
> Attachments: 3.4.0-surefire-report.png, screenshot-1.png,
> screenshot-2.png, surefire-3.5.0-2-g69c1b46d8.png
>
>
> On upgrading from 3.4.0 to 3.5.0 (so it works fine in 3.4.0), build breaks
> with following:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on
> project X: Failed to render site: Error generating
> maven-surefire-report-plugin:3.5.0:report-only report: Cannot invoke
> "Object.toString()" because "value" is null -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on
> project X: Failed to render site
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> 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:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:103)
> at java.lang.reflect.Method.invoke (Method.java:580)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:255)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:201)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:361)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:314)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to render
> site
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:119)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleB
[jira] [Commented] (SUREFIRE-2257) NPEx: Cannot invoke "Object.toString()" because "value" is null
[
https://issues.apache.org/jira/browse/SUREFIRE-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877192#comment-17877192
]
Piotr Zygielo commented on SUREFIRE-2257:
-
xref: https://github.com/cucumber/cucumber-jvm/issues/2918
> NPEx: Cannot invoke "Object.toString()" because "value" is null
> ---
>
> Key: SUREFIRE-2257
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2257
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Report Plugin
>Affects Versions: 3.5.0
>Reporter: Piotr Zygielo
>Priority: Major
> Attachments: 3.4.0-surefire-report.png
>
>
> On upgrading from 3.4.0 to 3.5.0 (so it works fine in 3.4.0), build breaks
> with following:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on
> project X: Failed to render site: Error generating
> maven-surefire-report-plugin:3.5.0:report-only report: Cannot invoke
> "Object.toString()" because "value" is null -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on
> project X: Failed to render site
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> 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:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:103)
> at java.lang.reflect.Method.invoke (Method.java:580)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:255)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:201)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:361)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:314)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to render
> site
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:119)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> 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.SingleThrea
[jira] [Commented] (SUREFIRE-2257) NPEx: Cannot invoke "Object.toString()" because "value" is null
[
https://issues.apache.org/jira/browse/SUREFIRE-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877180#comment-17877180
]
Piotr Zygielo commented on SUREFIRE-2257:
-
Probably it's for the {{classname}} of {{testcase}} element:
{code:xml}
{code}
Framework-generated {{classname}} attribute, dotless and with spaces, causes
package to be empty (then {{null}}) in {{renderSectionPackages:193}}.
This is fine for 3.4.0:
!3.4.0-surefire-report.png!
> NPEx: Cannot invoke "Object.toString()" because "value" is null
> ---
>
> Key: SUREFIRE-2257
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2257
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Report Plugin
>Affects Versions: 3.5.0
>Reporter: Piotr Zygielo
>Priority: Major
> Attachments: 3.4.0-surefire-report.png
>
>
> On upgrading from 3.4.0 to 3.5.0 (so it works fine in 3.4.0), build breaks
> with following:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on
> project X: Failed to render site: Error generating
> maven-surefire-report-plugin:3.5.0:report-only report: Cannot invoke
> "Object.toString()" because "value" is null -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on
> project X: Failed to render site
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> 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:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:103)
> at java.lang.reflect.Method.invoke (Method.java:580)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:255)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:201)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:361)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:314)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to render
> site
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:119)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (Lifecycl
[jira] [Updated] (SUREFIRE-2257) NPEx: Cannot invoke "Object.toString()" because "value" is null
[
https://issues.apache.org/jira/browse/SUREFIRE-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Zygielo updated SUREFIRE-2257:
Attachment: 3.4.0-surefire-report.png
> NPEx: Cannot invoke "Object.toString()" because "value" is null
> ---
>
> Key: SUREFIRE-2257
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2257
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Report Plugin
>Affects Versions: 3.5.0
>Reporter: Piotr Zygielo
>Priority: Major
> Attachments: 3.4.0-surefire-report.png
>
>
> On upgrading from 3.4.0 to 3.5.0 (so it works fine in 3.4.0), build breaks
> with following:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on
> project X: Failed to render site: Error generating
> maven-surefire-report-plugin:3.5.0:report-only report: Cannot invoke
> "Object.toString()" because "value" is null -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on
> project X: Failed to render site
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> 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:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:103)
> at java.lang.reflect.Method.invoke (Method.java:580)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:255)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:201)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:361)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:314)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to render
> site
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:119)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> 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.mav
[jira] [Comment Edited] (SUREFIRE-2257) NPEx: Cannot invoke "Object.toString()" because "value" is null
[
https://issues.apache.org/jira/browse/SUREFIRE-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877145#comment-17877145
]
Piotr Zygielo edited comment on SUREFIRE-2257 at 8/27/24 8:15 PM:
--
This may be caused by the report, {-}which wasn't created directly by
surefire{-}, but which is successfully validated against
[https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report.xsd].
The {{value}} is {{null}} for {{key = "id"}} in {{SinkUtils:188}} but I haven't
located the element yet.
(Edit: at this moment I'm not sure who creates the report, as
{{m-surefire-p:test}} clearly participates in the process).
was (Author: pzygielo):
This may be caused by the report, which wasn't created directly by surefire,
but which is successfully validated against
https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report.xsd.
The {{value}} is {{null}} for {{key = "id"}} in {{SinkUtils:188}} but I haven't
located the element yet.
> NPEx: Cannot invoke "Object.toString()" because "value" is null
> ---
>
> Key: SUREFIRE-2257
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2257
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Report Plugin
>Affects Versions: 3.5.0
>Reporter: Piotr Zygielo
>Priority: Major
>
> On upgrading from 3.4.0 to 3.5.0 (so it works fine in 3.4.0), build breaks
> with following:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on
> project X: Failed to render site: Error generating
> maven-surefire-report-plugin:3.5.0:report-only report: Cannot invoke
> "Object.toString()" because "value" is null -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on
> project X: Failed to render site
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> 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:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:103)
> at java.lang.reflect.Method.invoke (Method.java:580)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:255)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:201)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:361)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:314)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to render
> site
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:119)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor
[jira] [Commented] (SUREFIRE-2257) NPEx: Cannot invoke "Object.toString()" because "value" is null
[
https://issues.apache.org/jira/browse/SUREFIRE-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877155#comment-17877155
]
Piotr Zygielo commented on SUREFIRE-2257:
-
{code:bash}
...
[DEBUG] Unknown source: Modified invalid anchor name '' to 'null'
{code}
and this {{null}} is then referenced in {{:188}}.
> NPEx: Cannot invoke "Object.toString()" because "value" is null
> ---
>
> Key: SUREFIRE-2257
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2257
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Report Plugin
>Affects Versions: 3.5.0
>Reporter: Piotr Zygielo
>Priority: Major
>
> On upgrading from 3.4.0 to 3.5.0 (so it works fine in 3.4.0), build breaks
> with following:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on
> project X: Failed to render site: Error generating
> maven-surefire-report-plugin:3.5.0:report-only report: Cannot invoke
> "Object.toString()" because "value" is null -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on
> project X: Failed to render site
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> 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:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:103)
> at java.lang.reflect.Method.invoke (Method.java:580)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:255)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:201)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:361)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:314)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to render
> site
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:119)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> 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.build
[jira] [Commented] (SUREFIRE-2257) NPEx: Cannot invoke "Object.toString()" because "value" is null
[
https://issues.apache.org/jira/browse/SUREFIRE-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877145#comment-17877145
]
Piotr Zygielo commented on SUREFIRE-2257:
-
This may be caused by the report, which wasn't created directly by surefire,
but which is successfully validated against
https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report.xsd.
The {{value}} is {{null}} for {{key = "id"}} in {{SinkUtils:188}} but I haven't
located the element yet.
> NPEx: Cannot invoke "Object.toString()" because "value" is null
> ---
>
> Key: SUREFIRE-2257
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2257
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Report Plugin
>Affects Versions: 3.5.0
>Reporter: Piotr Zygielo
>Priority: Major
>
> On upgrading from 3.4.0 to 3.5.0 (so it works fine in 3.4.0), build breaks
> with following:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on
> project X: Failed to render site: Error generating
> maven-surefire-report-plugin:3.5.0:report-only report: Cannot invoke
> "Object.toString()" because "value" is null -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on
> project X: Failed to render site
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> 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:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:103)
> at java.lang.reflect.Method.invoke (Method.java:580)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:255)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:201)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:361)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:314)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to render
> site
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:119)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:10
[jira] [Updated] (SUREFIRE-2257) NPEx: Cannot invoke "Object.toString()" because "value" is null
[
https://issues.apache.org/jira/browse/SUREFIRE-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Zygielo updated SUREFIRE-2257:
Description:
On upgrading from 3.4.0 to 3.5.0 (so it works fine in 3.4.0), build breaks with
following:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on
project X: Failed to render site: Error generating
maven-surefire-report-plugin:3.5.0:report-only report: Cannot invoke
"Object.toString()" because "value" is null -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on
project X: Failed to render site
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:333)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:316)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:174)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
(MojoExecutor.java:75)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:162)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:159)
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:906)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
(DirectMethodHandleAccessor.java:103)
at java.lang.reflect.Method.invoke (Method.java:580)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:255)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:201)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:361)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:314)
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to render site
at org.apache.maven.plugins.site.render.SiteMojo.execute (SiteMojo.java:119)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:126)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:328)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:316)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:174)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
(MojoExecutor.java:75)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:162)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:159)
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:906)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
(DirectMethodHandleAccessor.java:103)
at java.lang.reflect.Method.invoke (Method.java:580)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launch
[jira] [Created] (SUREFIRE-2257) NPEx: Cannot invoke "Object.toString()" because "value" is null
Piotr Zygielo created SUREFIRE-2257:
---
Summary: NPEx: Cannot invoke "Object.toString()" because "value"
is null
Key: SUREFIRE-2257
URL: https://issues.apache.org/jira/browse/SUREFIRE-2257
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Report Plugin
Affects Versions: 3.5.0
Reporter: Piotr Zygielo
On upgrading from 3.4.0 to 3.5.0 (so it works fine in 3.4.0), build breaks with
following:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on
project X: Failed to render site: Error generating
maven-surefire-report-plugin:3.5.0:report-only report: Cannot invoke
"Object.toString()" because "value" is null -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on
project X: Failed to render site
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:333)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:316)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:174)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
(MojoExecutor.java:75)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:162)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:159)
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:906)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
(DirectMethodHandleAccessor.java:103)
at java.lang.reflect.Method.invoke (Method.java:580)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:255)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:201)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:361)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:314)
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to render site
at org.apache.maven.plugins.site.render.SiteMojo.execute (SiteMojo.java:119)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:126)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:328)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:316)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:174)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
(MojoExecutor.java:75)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:162)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:159)
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:906)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
at
[jira] [Closed] (SCM-1025) Broken links to mojos at Maven SCM Plugin:Goals Overview
[
https://issues.apache.org/jira/browse/SCM-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Zygielo closed SCM-1025.
--
Thank you all.
> Broken links to mojos at Maven SCM Plugin:Goals Overview
>
>
> Key: SCM-1025
> URL: https://issues.apache.org/jira/browse/SCM-1025
> Project: Maven SCM
> Issue Type: Bug
>Reporter: Piotr Zygielo
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: 2.2.0
>
>
> [https://maven.apache.org/scm/maven-scm-plugin/]
> Click {{scm:edit}} to go to
> [https://maven.apache.org/scm/maven-scm-plugin/edit-mojo.html] which is "Page
> Not Found".
> (or {{{}:checkin{}}}, {{{}:status{}}}... for the same)
>
>
> apache/maven-scm:90f9abc4397e269b929b039dda567f538b28375d
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SCM-1016) Build fails with JDK21
[
https://issues.apache.org/jira/browse/SCM-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871036#comment-17871036
]
Piotr Zygielo commented on SCM-1016:
With this change I'm getting no mojo pages (with maven 3.9.8/jdk 21).
For me it seems to be the cause of MNGSITE-540.
> Build fails with JDK21
> --
>
> Key: SCM-1016
> URL: https://issues.apache.org/jira/browse/SCM-1016
> Project: Maven SCM
> Issue Type: Bug
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: 2.1.0
>
>
> The following error is emitted
> {code}
> [ERROR] Step 'palantir-java-format' found problem in
> 'src/main/java/org/apache/maven/scm/AbstractScmVersion.java':
> 'com.sun.tools.javac.tree.JCTree
> com.sun.tools.javac.tree.JCTree$JCImport.getQualifiedIdentifier()'
> java.lang.NoSuchMethodError: 'com.sun.tools.javac.tree.JCTree
> com.sun.tools.javac.tree.JCTree$JCImport.getQualifiedIdentifier()'
> at com.palantir.javaformat.java.RemoveUnusedImports.getSimpleName
> (RemoveUnusedImports.java:245)
> at com.palantir.javaformat.java.RemoveUnusedImports.buildReplacements
> (RemoveUnusedImports.java:225)
> at com.palantir.javaformat.java.RemoveUnusedImports.removeUnusedImports
> (RemoveUnusedImports.java:209)
> at com.diffplug.spotless.glue.pjf.PalantirJavaFormatFormatterFunc.apply
> (PalantirJavaFormatFormatterFunc.java:39)
> at com.diffplug.spotless.FormatterFunc.apply (FormatterFunc.java:32)
> at com.diffplug.spotless.FormatterStepImpl$Standard.format
> (FormatterStepImpl.java:82)
> at com.diffplug.spotless.FormatterStep$Strict.format
> (FormatterStep.java:88)
> at com.diffplug.spotless.Formatter.compute (Formatter.java:230)
> at com.diffplug.spotless.PaddedCell.calculateDirtyState
> (PaddedCell.java:203)
> at com.diffplug.spotless.PaddedCell.calculateDirtyState
> (PaddedCell.java:190)
> at com.diffplug.spotless.maven.SpotlessCheckMojo.process
> (SpotlessCheckMojo.java:51)
> at com.diffplug.spotless.maven.AbstractSpotlessMojo.execute
> (AbstractSpotlessMojo.java:198)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> 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:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:103)
> at java.lang.reflect.Method.invoke (Method.java:580)
> 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}
> This is due to using an outdated palantir formatter in spotless-maven-plugin
> not yet compatible with Java 21
> (https://github.com/palantir/palantir-java-format/issues/885).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNGSITE-540) Broken links to mojos at Maven SCM Plugin:Goals Overview
[
https://issues.apache.org/jira/browse/MNGSITE-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Zygielo updated MNGSITE-540:
--
Description:
[https://maven.apache.org/scm/maven-scm-plugin/]
Click {{scm:edit}} to go to
[https://maven.apache.org/scm/maven-scm-plugin/edit-mojo.html] which is "Page
Not Found".
(or {{{}:checkin{}}}, {{{}:status{}}}... for the same)
apache/maven-scm:90f9abc4397e269b929b039dda567f538b28375d
was:
[https://maven.apache.org/scm/maven-scm-plugin/]
Click {{scm:edit}} to go to
[https://maven.apache.org/scm/maven-scm-plugin/edit-mojo.html] which is "Page
Not Found".
(or {{:checkin}}, {{:status}}... for the same)
> Broken links to mojos at Maven SCM Plugin:Goals Overview
>
>
> Key: MNGSITE-540
> URL: https://issues.apache.org/jira/browse/MNGSITE-540
> Project: Maven Project Web Site
> Issue Type: Bug
>Reporter: Piotr Zygielo
>Priority: Major
>
> [https://maven.apache.org/scm/maven-scm-plugin/]
> Click {{scm:edit}} to go to
> [https://maven.apache.org/scm/maven-scm-plugin/edit-mojo.html] which is "Page
> Not Found".
> (or {{{}:checkin{}}}, {{{}:status{}}}... for the same)
>
>
> apache/maven-scm:90f9abc4397e269b929b039dda567f538b28375d
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MNGSITE-540) Broken links to mojos at Maven SCM Plugin:Goals Overview
Piotr Zygielo created MNGSITE-540:
-
Summary: Broken links to mojos at Maven SCM Plugin:Goals Overview
Key: MNGSITE-540
URL: https://issues.apache.org/jira/browse/MNGSITE-540
Project: Maven Project Web Site
Issue Type: Bug
Reporter: Piotr Zygielo
[https://maven.apache.org/scm/maven-scm-plugin/]
Click {{scm:edit}} to go to
[https://maven.apache.org/scm/maven-scm-plugin/edit-mojo.html] which is "Page
Not Found".
(or {{:checkin}}, {{:status}}... for the same)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MEAR-322) Module repackaged as invalid archive
[
https://issues.apache.org/jira/browse/MEAR-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17868744#comment-17868744
]
Piotr Zygielo commented on MEAR-322:
Please close this issue.
> Module repackaged as invalid archive
>
>
> Key: MEAR-322
> URL: https://issues.apache.org/jira/browse/MEAR-322
> Project: Maven EAR Plugin
> Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Piotr Zygielo
>Priority: Major
> Fix For: more-investigation
>
>
> After m-ear-p upgrade from 3.2.0 to 3.3.0, ear produced by plugin contains
> invalid entry. That causes jar tool to error with
> {quote}java.util.zip.ZipException: only DEFLATED entries can have EXT
> descriptor
> at java.base/java.util.zip.ZipInputStream.readLOC(ZipInputStream.java:313)
> at
> java.base/java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:125)
> at jdk.jartool/sun.tools.jar.Main.extract(Main.java:1360)
> at jdk.jartool/sun.tools.jar.Main.run(Main.java:409)
> at jdk.jartool/sun.tools.jar.Main.main(Main.java:1680)
> {quote}
> Seems to be connected to setting {{archive/compress=false}} in the original
> jar project (original project - valid at its origin, becomes invalid part of
> ear).
> 07a84983809b4ec416b1330412bbd83844a88a44 is the first bad commit
>
>
> Reproducer: [https://github.com/pzrep/MEAR-322]
> and its failure: [https://github.com/pzrep/MEAR-322/actions/runs/3306348660]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MNG-8186) Introduce flag for warning when an aggregator mojo is locking other mojo executions
Piotr Zygielo created MNG-8186: -- Summary: Introduce flag for warning when an aggregator mojo is locking other mojo executions Key: MNG-8186 URL: https://issues.apache.org/jira/browse/MNG-8186 Project: Maven Issue Type: New Feature Affects Versions: 3.9.8 Reporter: Piotr Zygielo https://issues.apache.org/jira/browse/MNG-7476?focusedCommentId=17867695&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17867695 bq. This should not affect the build. And there's currently no way to avoid it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7476) Display a warning when an aggregator mojo is locking other mojo executions
[ https://issues.apache.org/jira/browse/MNG-7476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867692#comment-17867692 ] Piotr Zygielo commented on MNG-7476: bq. We could introduce a flag if needed. I'd appreciate that if the current warning is unavoidable and not actionable. > Display a warning when an aggregator mojo is locking other mojo executions > -- > > Key: MNG-7476 > URL: https://issues.apache.org/jira/browse/MNG-7476 > Project: Maven > Issue Type: Improvement >Affects Versions: 3.8.5 >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 3.8.6, 3.9.0, 4.0.0-alpha-2, 4.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7868) "Could not acquire lock(s)" error in concurrent maven builds
[
https://issues.apache.org/jira/browse/MNG-7868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867517#comment-17867517
]
Piotr Zygielo commented on MNG-7868:
Attached {{MNG-7868-pz_ai_37_lock.txt}} with the current failure with mvn 3.9.8
on Java 21.
> "Could not acquire lock(s)" error in concurrent maven builds
>
>
> Key: MNG-7868
> URL: https://issues.apache.org/jira/browse/MNG-7868
> Project: Maven
> Issue Type: Bug
> Environment: windows, maven 3.9.4
>Reporter: Jörg Hohwiller
>Priority: Major
> Attachments: MNG-7868-pz_ai_37_lock.txt,
> image-2024-04-10-15-44-37-013.png, screenshot-1.png
>
>
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install)
> on project foo.bar: Execution default-install of goal
> org.apache.maven.plugins:maven-install-plugin:3.1.1:install failed: Could not
> acquire lock(s) -> [Help 1]
> {code}
> I am using maven 3.9.4 on windows:
> {code}
> $ mvn -v
> Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
> Maven home: D:\projects\test\software\mvn
> Java version: 17.0.5, vendor: Eclipse Adoptium, runtime:
> D:\projects\test\software\java
> Default locale: en_US, platform encoding: UTF-8
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> {code}
> I searched for this bug and found issues like MRESOLVER-332 that first look
> identical or similar but do not really seem to be related so I decided to
> create this issue.
> For this bug I made the following observations:
> * it only happens with concurrent builds: {{mvn -T ...}}
> * is seems to be windows related (at least mainly happens on windows)
> * it is in-deterministic and is not so easy to create an isolated and simple
> project and a reproducible scenario that always results in this error.
> However, I get this very often in my current project with many modules (500+).
> * it is not specific to the maven-install-plugin and also happens from other
> spots in maven:
> I also got this stacktrace:
> {code}
> Suppressed: java.lang.IllegalStateException: Attempt 1: Could not acquire
> write lock for
> 'C:\Users\hohwille\.m2\repository\.locks\artifact~com.caucho~com.springsource.com.caucho~3.2.1.lock'
> in 30 SECONDS
> at
> org.eclipse.aether.internal.impl.synccontext.named.NamedLockFactoryAdapter$AdaptedLockSyncContext.acquire
> (NamedLockFactoryAdapter.java:202)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:271)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
> (DefaultArtifactResolver.java:259)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies
> (DefaultRepositorySystem.java:352)
> {code}
> See also this related discussion:
> https://github.com/apache/maven-mvnd/issues/836#issuecomment-1702488377
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MNG-7868) "Could not acquire lock(s)" error in concurrent maven builds
[
https://issues.apache.org/jira/browse/MNG-7868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867517#comment-17867517
]
Piotr Zygielo edited comment on MNG-7868 at 7/20/24 11:18 AM:
--
Attached {{MNG\-7868-pz_ai_37_lock.txt}} with the current failure with mvn
3.9.8 on Java 21.
was (Author: pzygielo):
Attached {{MNG-7868-pz_ai_37_lock.txt}} with the current failure with mvn 3.9.8
on Java 21.
> "Could not acquire lock(s)" error in concurrent maven builds
>
>
> Key: MNG-7868
> URL: https://issues.apache.org/jira/browse/MNG-7868
> Project: Maven
> Issue Type: Bug
> Environment: windows, maven 3.9.4
>Reporter: Jörg Hohwiller
>Priority: Major
> Attachments: MNG-7868-pz_ai_37_lock.txt,
> image-2024-04-10-15-44-37-013.png, screenshot-1.png
>
>
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install)
> on project foo.bar: Execution default-install of goal
> org.apache.maven.plugins:maven-install-plugin:3.1.1:install failed: Could not
> acquire lock(s) -> [Help 1]
> {code}
> I am using maven 3.9.4 on windows:
> {code}
> $ mvn -v
> Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
> Maven home: D:\projects\test\software\mvn
> Java version: 17.0.5, vendor: Eclipse Adoptium, runtime:
> D:\projects\test\software\java
> Default locale: en_US, platform encoding: UTF-8
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> {code}
> I searched for this bug and found issues like MRESOLVER-332 that first look
> identical or similar but do not really seem to be related so I decided to
> create this issue.
> For this bug I made the following observations:
> * it only happens with concurrent builds: {{mvn -T ...}}
> * is seems to be windows related (at least mainly happens on windows)
> * it is in-deterministic and is not so easy to create an isolated and simple
> project and a reproducible scenario that always results in this error.
> However, I get this very often in my current project with many modules (500+).
> * it is not specific to the maven-install-plugin and also happens from other
> spots in maven:
> I also got this stacktrace:
> {code}
> Suppressed: java.lang.IllegalStateException: Attempt 1: Could not acquire
> write lock for
> 'C:\Users\hohwille\.m2\repository\.locks\artifact~com.caucho~com.springsource.com.caucho~3.2.1.lock'
> in 30 SECONDS
> at
> org.eclipse.aether.internal.impl.synccontext.named.NamedLockFactoryAdapter$AdaptedLockSyncContext.acquire
> (NamedLockFactoryAdapter.java:202)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:271)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
> (DefaultArtifactResolver.java:259)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies
> (DefaultRepositorySystem.java:352)
> {code}
> See also this related discussion:
> https://github.com/apache/maven-mvnd/issues/836#issuecomment-1702488377
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-7868) "Could not acquire lock(s)" error in concurrent maven builds
[
https://issues.apache.org/jira/browse/MNG-7868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Zygielo updated MNG-7868:
---
Attachment: MNG-7868-pz_ai_37_lock.txt
> "Could not acquire lock(s)" error in concurrent maven builds
>
>
> Key: MNG-7868
> URL: https://issues.apache.org/jira/browse/MNG-7868
> Project: Maven
> Issue Type: Bug
> Environment: windows, maven 3.9.4
>Reporter: Jörg Hohwiller
>Priority: Major
> Attachments: MNG-7868-pz_ai_37_lock.txt,
> image-2024-04-10-15-44-37-013.png, screenshot-1.png
>
>
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install)
> on project foo.bar: Execution default-install of goal
> org.apache.maven.plugins:maven-install-plugin:3.1.1:install failed: Could not
> acquire lock(s) -> [Help 1]
> {code}
> I am using maven 3.9.4 on windows:
> {code}
> $ mvn -v
> Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
> Maven home: D:\projects\test\software\mvn
> Java version: 17.0.5, vendor: Eclipse Adoptium, runtime:
> D:\projects\test\software\java
> Default locale: en_US, platform encoding: UTF-8
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> {code}
> I searched for this bug and found issues like MRESOLVER-332 that first look
> identical or similar but do not really seem to be related so I decided to
> create this issue.
> For this bug I made the following observations:
> * it only happens with concurrent builds: {{mvn -T ...}}
> * is seems to be windows related (at least mainly happens on windows)
> * it is in-deterministic and is not so easy to create an isolated and simple
> project and a reproducible scenario that always results in this error.
> However, I get this very often in my current project with many modules (500+).
> * it is not specific to the maven-install-plugin and also happens from other
> spots in maven:
> I also got this stacktrace:
> {code}
> Suppressed: java.lang.IllegalStateException: Attempt 1: Could not acquire
> write lock for
> 'C:\Users\hohwille\.m2\repository\.locks\artifact~com.caucho~com.springsource.com.caucho~3.2.1.lock'
> in 30 SECONDS
> at
> org.eclipse.aether.internal.impl.synccontext.named.NamedLockFactoryAdapter$AdaptedLockSyncContext.acquire
> (NamedLockFactoryAdapter.java:202)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:271)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
> (DefaultArtifactResolver.java:259)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies
> (DefaultRepositorySystem.java:352)
> {code}
> See also this related discussion:
> https://github.com/apache/maven-mvnd/issues/836#issuecomment-1702488377
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] (MJAVADOC-804) Temporary files are left after test execution
[ https://issues.apache.org/jira/browse/MJAVADOC-804 ] Piotr Zygielo deleted comment on MJAVADOC-804: was (Author: pzygielo): [~michael-o] thanks for checking and taking care for this. Now I think this should not be of bug type as it is not about functionality of the plugin. Not sure what type 'Test' is used for, but perhaps it would fit better? > Temporary files are left after test execution > - > > Key: MJAVADOC-804 > URL: https://issues.apache.org/jira/browse/MJAVADOC-804 > Project: Maven Javadoc Plugin > Issue Type: Bug >Affects Versions: 3.7.0 >Reporter: Piotr Zygielo >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.7.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MJAVADOC-804) Temporary files are left after test execution
[ https://issues.apache.org/jira/browse/MJAVADOC-804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865808#comment-17865808 ] Piotr Zygielo commented on MJAVADOC-804: [~michael-o] thanks for checking and taking care for this. Now I think this should not be of bug type as it is not about functionality of the plugin. Not sure what type 'Test' is used for, but perhaps it would fit better? > Temporary files are left after test execution > - > > Key: MJAVADOC-804 > URL: https://issues.apache.org/jira/browse/MJAVADOC-804 > Project: Maven Javadoc Plugin > Issue Type: Bug >Affects Versions: 3.7.0 >Reporter: Piotr Zygielo >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.7.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MJAVADOC-804) Temporary files are left after test execution
[ https://issues.apache.org/jira/browse/MJAVADOC-804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865807#comment-17865807 ] Piotr Zygielo commented on MJAVADOC-804: [~michael-o] thanks for checking and taking care for this. Now I think this should not be of bug type as it is not about functionality of the plugin. Not sure what type 'Test' is used for, but perhaps it would fit better? > Temporary files are left after test execution > - > > Key: MJAVADOC-804 > URL: https://issues.apache.org/jira/browse/MJAVADOC-804 > Project: Maven Javadoc Plugin > Issue Type: Bug >Affects Versions: 3.7.0 >Reporter: Piotr Zygielo >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.7.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MJAVADOC-804) Temporary files are left after test execution
Piotr Zygielo created MJAVADOC-804: -- Summary: Temporary files are left after test execution Key: MJAVADOC-804 URL: https://issues.apache.org/jira/browse/MJAVADOC-804 Project: Maven Javadoc Plugin Issue Type: Bug Affects Versions: 3.7.0 Reporter: Piotr Zygielo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (MJAVADOC-710) Usage of removed or replaced property does not cause the build to fail
[ https://issues.apache.org/jira/browse/MJAVADOC-710 ]
Piotr Zygielo deleted comment on MJAVADOC-710:
was (Author: pzygielo):
{quote}I would like to close with - won't fix - here in plugin.
{quote}
I have no privilege to perform that action myself.
> Usage of removed or replaced property does not cause the build to fail
> --
>
> Key: MJAVADOC-710
> URL: https://issues.apache.org/jira/browse/MJAVADOC-710
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.3.2
>Reporter: Piotr Zygielo
>Priority: Major
>
> Per
> https://issues.apache.org/jira/browse/MJAVADOC-509?focusedCommentId=16581261
> {quote}Yes, additionalParam was replaced by additionalOptions in
> MJAVADOC-475(https://issues.apache.org/jira/browse/MJAVADOC-475) and the
> build will fail with 3.0.0 if this property is used.
> {quote}
> However current implementation does not do that. And as far as I've checked -
> the original implementation didn't do in 3.0.0 neither.
> This is due to {{mojo.getConfiguration()}} in
> {{AbstractJavadocMojo.verifyRemovedParameter}} having only parameters plugin
> committed for, and not all from {{}} element. Not at the
> moment of goal execution, at least.
> This causes problems when upgrading from pre-3 plugin as {{additionalparam}}
> is silently ignored.
> I see similar case is dealt in following way:
> -
> [https://github.com/apache/maven-jar-plugin/blob/0ad60f4f2862bf896b6c0dc57ea5a6999c49b0d4/src/main/java/org/apache/maven/plugins/jar/AbstractJarMojo.java#L107-L115]
> -
> [https://github.com/apache/maven-deploy-plugin/blob/36a2030c8851e21cd1e0bec01c3cea4dc6055a48/src/main/java/org/apache/maven/plugins/deploy/DeployFileMojo.java#L180-L188]
> - and few others
> which is to have {{@Deprecated}} parameter, and its presence is used for
> breaking the build.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MJAVADOC-710) Usage of removed or replaced property does not cause the build to fail
[
https://issues.apache.org/jira/browse/MJAVADOC-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865772#comment-17865772
]
Piotr Zygielo commented on MJAVADOC-710:
{quote}I would like to close with - won't fix - here in plugin.
{quote}
I have no privilege to perform that action myself.
> Usage of removed or replaced property does not cause the build to fail
> --
>
> Key: MJAVADOC-710
> URL: https://issues.apache.org/jira/browse/MJAVADOC-710
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.3.2
>Reporter: Piotr Zygielo
>Priority: Major
>
> Per
> https://issues.apache.org/jira/browse/MJAVADOC-509?focusedCommentId=16581261
> {quote}Yes, additionalParam was replaced by additionalOptions in
> MJAVADOC-475(https://issues.apache.org/jira/browse/MJAVADOC-475) and the
> build will fail with 3.0.0 if this property is used.
> {quote}
> However current implementation does not do that. And as far as I've checked -
> the original implementation didn't do in 3.0.0 neither.
> This is due to {{mojo.getConfiguration()}} in
> {{AbstractJavadocMojo.verifyRemovedParameter}} having only parameters plugin
> committed for, and not all from {{}} element. Not at the
> moment of goal execution, at least.
> This causes problems when upgrading from pre-3 plugin as {{additionalparam}}
> is silently ignored.
> I see similar case is dealt in following way:
> -
> [https://github.com/apache/maven-jar-plugin/blob/0ad60f4f2862bf896b6c0dc57ea5a6999c49b0d4/src/main/java/org/apache/maven/plugins/jar/AbstractJarMojo.java#L107-L115]
> -
> [https://github.com/apache/maven-deploy-plugin/blob/36a2030c8851e21cd1e0bec01c3cea4dc6055a48/src/main/java/org/apache/maven/plugins/deploy/DeployFileMojo.java#L180-L188]
> - and few others
> which is to have {{@Deprecated}} parameter, and its presence is used for
> breaking the build.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MJAVADOC-710) Usage of removed or replaced property does not cause the build to fail
[
https://issues.apache.org/jira/browse/MJAVADOC-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865773#comment-17865773
]
Piotr Zygielo commented on MJAVADOC-710:
{quote}I would like to close with - won't fix - here in plugin.
{quote}
I have no privilege to perform that action myself.
> Usage of removed or replaced property does not cause the build to fail
> --
>
> Key: MJAVADOC-710
> URL: https://issues.apache.org/jira/browse/MJAVADOC-710
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.3.2
>Reporter: Piotr Zygielo
>Priority: Major
>
> Per
> https://issues.apache.org/jira/browse/MJAVADOC-509?focusedCommentId=16581261
> {quote}Yes, additionalParam was replaced by additionalOptions in
> MJAVADOC-475(https://issues.apache.org/jira/browse/MJAVADOC-475) and the
> build will fail with 3.0.0 if this property is used.
> {quote}
> However current implementation does not do that. And as far as I've checked -
> the original implementation didn't do in 3.0.0 neither.
> This is due to {{mojo.getConfiguration()}} in
> {{AbstractJavadocMojo.verifyRemovedParameter}} having only parameters plugin
> committed for, and not all from {{}} element. Not at the
> moment of goal execution, at least.
> This causes problems when upgrading from pre-3 plugin as {{additionalparam}}
> is silently ignored.
> I see similar case is dealt in following way:
> -
> [https://github.com/apache/maven-jar-plugin/blob/0ad60f4f2862bf896b6c0dc57ea5a6999c49b0d4/src/main/java/org/apache/maven/plugins/jar/AbstractJarMojo.java#L107-L115]
> -
> [https://github.com/apache/maven-deploy-plugin/blob/36a2030c8851e21cd1e0bec01c3cea4dc6055a48/src/main/java/org/apache/maven/plugins/deploy/DeployFileMojo.java#L180-L188]
> - and few others
> which is to have {{@Deprecated}} parameter, and its presence is used for
> breaking the build.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MJAVADOC-710) Usage of removed or replaced property does not cause the build to fail
[
https://issues.apache.org/jira/browse/MJAVADOC-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865759#comment-17865759
]
Piotr Zygielo edited comment on MJAVADOC-710 at 7/14/24 9:25 AM:
-
I can't remember the thing. But PR-126 was closed as included in 127, and 127
was closed without being merged.
I rebased PR-126 on current master (d3afd39f) and m-javadoc-p is still fine
with replaced/removed parameters (which I found as bad back then). There are
warnings like: {{Parameter 'proxyHost' is unknown for plugin
'maven-javadoc-plugin:3.7.1-SNAPSHOT:javadoc-no-fork (default-cli)}} at least
now, but
[https://github.com/apache/maven-javadoc-plugin/blob/3eb47c5081bf6f4158333bd378641bc9b7c9a25f/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java#L1841-L1859]
seem to be useless.
As more than few weeks passed since PR-127 was closed, some conflicting changes
happened (in formatting/having spotless or so) thus I can't just rebase that on
master. But if someone agrees with what was reported here in first place, I
can pick changes again in new PR. Or maybe other solution could be implemented
by other party.
I'm open for discussion or for closing it should I be the only one to be
bothered with it.
was (Author: pzygielo):
I can't remember the thing. But PR-126 was closed as included in 127, and 127
was closed without being merged.
I rebased PR-126 on current master (d3afd39f) and m-javadoc-p is still fine
with replaced/removed parameters (which I found as bad back then). There are
warnings like: {{Parameter 'proxyHost' is unknown for plugin
'maven-javadoc-plugin:3.7.1-SNAPSHOT:javadoc-no-fork (default-cli)}} at least
now, but
[https://github.com/apache/maven-javadoc-plugin/blob/3eb47c5081bf6f4158333bd378641bc9b7c9a25f/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java#L1841-L1859]
seem to be useless.
As more than few weeks passed since PR-127 was closed, some conflicting changes
happened (in formatting/having spotless or so) thus I can't just rebase that on
master. But if someone agrees with with what was reported here in first place,
I can pick changes again in new PR. Or maybe other solution could be
implemented by other party.
I'm open for discussion or for closing it should I be the only one to be
bothered with it.
> Usage of removed or replaced property does not cause the build to fail
> --
>
> Key: MJAVADOC-710
> URL: https://issues.apache.org/jira/browse/MJAVADOC-710
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.3.2
>Reporter: Piotr Zygielo
>Priority: Major
>
> Per
> https://issues.apache.org/jira/browse/MJAVADOC-509?focusedCommentId=16581261
> {quote}Yes, additionalParam was replaced by additionalOptions in
> MJAVADOC-475(https://issues.apache.org/jira/browse/MJAVADOC-475) and the
> build will fail with 3.0.0 if this property is used.
> {quote}
> However current implementation does not do that. And as far as I've checked -
> the original implementation didn't do in 3.0.0 neither.
> This is due to {{mojo.getConfiguration()}} in
> {{AbstractJavadocMojo.verifyRemovedParameter}} having only parameters plugin
> committed for, and not all from {{}} element. Not at the
> moment of goal execution, at least.
> This causes problems when upgrading from pre-3 plugin as {{additionalparam}}
> is silently ignored.
> I see similar case is dealt in following way:
> -
> [https://github.com/apache/maven-jar-plugin/blob/0ad60f4f2862bf896b6c0dc57ea5a6999c49b0d4/src/main/java/org/apache/maven/plugins/jar/AbstractJarMojo.java#L107-L115]
> -
> [https://github.com/apache/maven-deploy-plugin/blob/36a2030c8851e21cd1e0bec01c3cea4dc6055a48/src/main/java/org/apache/maven/plugins/deploy/DeployFileMojo.java#L180-L188]
> - and few others
> which is to have {{@Deprecated}} parameter, and its presence is used for
> breaking the build.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MJAVADOC-710) Usage of removed or replaced property does not cause the build to fail
[
https://issues.apache.org/jira/browse/MJAVADOC-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865759#comment-17865759
]
Piotr Zygielo edited comment on MJAVADOC-710 at 7/14/24 9:24 AM:
-
I can't remember the thing. But PR-126 was closed as included in 127, and 127
was closed without being merged.
I rebased PR-126 on current master (d3afd39f) and m-javadoc-p is still fine
with replaced/removed parameters (which I found as bad back then). There are
warnings like: {{Parameter 'proxyHost' is unknown for plugin
'maven-javadoc-plugin:3.7.1-SNAPSHOT:javadoc-no-fork (default-cli)}} at least
now, but
[https://github.com/apache/maven-javadoc-plugin/blob/3eb47c5081bf6f4158333bd378641bc9b7c9a25f/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java#L1841-L1859]
seem to be useless.
As more than few weeks passed since PR-127 was closed, some conflicting changes
happened (in formatting/having spotless or so) thus I can't just rebase that on
master. But if someone agrees with with what was reported here in first place,
I can pick changes again in new PR. Or maybe other solution could be
implemented by other party.
I'm open for discussion or for closing it should I be the only one to be
bothered with it.
was (Author: pzygielo):
I can't remember the thing. But PR-126 was closed as included in 127, and 127
was closed without being merged.
I rebased PR-126 on current master (d3afd39f) and m-javadoc-p is still fine
with replaced/removed parameters (which I found as bad back then). There are
warnings like:{{ Parameter 'proxyHost' is unknown for plugin
'maven-javadoc-plugin:3.7.1-SNAPSHOT:javadoc-no-fork (default-cli)}} at least
now, but
[https://github.com/apache/maven-javadoc-plugin/blob/3eb47c5081bf6f4158333bd378641bc9b7c9a25f/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java#L1841-L1859]
seem to be useless.
As more than few weeks passed since PR-127 was closed, some conflicting changes
happened (in formatting/having spotless or so) thus I can't just rebase that on
master. But if someone agrees with with what was reported here in first place,
I can pick changes again in new PR. Or maybe other solution could be
implemented by other party.
I'm open for discussion or for closing it should I be the only one to be
bothered with it.
> Usage of removed or replaced property does not cause the build to fail
> --
>
> Key: MJAVADOC-710
> URL: https://issues.apache.org/jira/browse/MJAVADOC-710
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.3.2
>Reporter: Piotr Zygielo
>Priority: Major
>
> Per
> https://issues.apache.org/jira/browse/MJAVADOC-509?focusedCommentId=16581261
> {quote}Yes, additionalParam was replaced by additionalOptions in
> MJAVADOC-475(https://issues.apache.org/jira/browse/MJAVADOC-475) and the
> build will fail with 3.0.0 if this property is used.
> {quote}
> However current implementation does not do that. And as far as I've checked -
> the original implementation didn't do in 3.0.0 neither.
> This is due to {{mojo.getConfiguration()}} in
> {{AbstractJavadocMojo.verifyRemovedParameter}} having only parameters plugin
> committed for, and not all from {{}} element. Not at the
> moment of goal execution, at least.
> This causes problems when upgrading from pre-3 plugin as {{additionalparam}}
> is silently ignored.
> I see similar case is dealt in following way:
> -
> [https://github.com/apache/maven-jar-plugin/blob/0ad60f4f2862bf896b6c0dc57ea5a6999c49b0d4/src/main/java/org/apache/maven/plugins/jar/AbstractJarMojo.java#L107-L115]
> -
> [https://github.com/apache/maven-deploy-plugin/blob/36a2030c8851e21cd1e0bec01c3cea4dc6055a48/src/main/java/org/apache/maven/plugins/deploy/DeployFileMojo.java#L180-L188]
> - and few others
> which is to have {{@Deprecated}} parameter, and its presence is used for
> breaking the build.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MJAVADOC-710) Usage of removed or replaced property does not cause the build to fail
[
https://issues.apache.org/jira/browse/MJAVADOC-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865759#comment-17865759
]
Piotr Zygielo commented on MJAVADOC-710:
I can't remember the thing. But PR-126 was closed as included in 127, and 127
was closed without being merged.
I rebased PR-126 on current master (d3afd39f) and m-javadoc-p is still fine
with replaced/removed parameters (which I found as bad back then). There are
warnings like:{{ Parameter 'proxyHost' is unknown for plugin
'maven-javadoc-plugin:3.7.1-SNAPSHOT:javadoc-no-fork (default-cli)}} at least
now, but
[https://github.com/apache/maven-javadoc-plugin/blob/3eb47c5081bf6f4158333bd378641bc9b7c9a25f/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java#L1841-L1859]
seem to be useless.
As more than few weeks passed since PR-127 was closed, some conflicting changes
happened (in formatting/having spotless or so) thus I can't just rebase that on
master. But if someone agrees with with what was reported here in first place,
I can pick changes again in new PR. Or maybe other solution could be
implemented by other party.
I'm open for discussion or for closing it should I be the only one to be
bothered with it.
> Usage of removed or replaced property does not cause the build to fail
> --
>
> Key: MJAVADOC-710
> URL: https://issues.apache.org/jira/browse/MJAVADOC-710
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.3.2
>Reporter: Piotr Zygielo
>Priority: Major
>
> Per
> https://issues.apache.org/jira/browse/MJAVADOC-509?focusedCommentId=16581261
> {quote}Yes, additionalParam was replaced by additionalOptions in
> MJAVADOC-475(https://issues.apache.org/jira/browse/MJAVADOC-475) and the
> build will fail with 3.0.0 if this property is used.
> {quote}
> However current implementation does not do that. And as far as I've checked -
> the original implementation didn't do in 3.0.0 neither.
> This is due to {{mojo.getConfiguration()}} in
> {{AbstractJavadocMojo.verifyRemovedParameter}} having only parameters plugin
> committed for, and not all from {{}} element. Not at the
> moment of goal execution, at least.
> This causes problems when upgrading from pre-3 plugin as {{additionalparam}}
> is silently ignored.
> I see similar case is dealt in following way:
> -
> [https://github.com/apache/maven-jar-plugin/blob/0ad60f4f2862bf896b6c0dc57ea5a6999c49b0d4/src/main/java/org/apache/maven/plugins/jar/AbstractJarMojo.java#L107-L115]
> -
> [https://github.com/apache/maven-deploy-plugin/blob/36a2030c8851e21cd1e0bec01c3cea4dc6055a48/src/main/java/org/apache/maven/plugins/deploy/DeployFileMojo.java#L180-L188]
> - and few others
> which is to have {{@Deprecated}} parameter, and its presence is used for
> breaking the build.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7476) Display a warning when an aggregator mojo is locking other mojo executions
[
https://issues.apache.org/jira/browse/MNG-7476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863476#comment-17863476
]
Piotr Zygielo commented on MNG-7476:
{quote}This should not affect the build. And there's currently no way to avoid
it.
{quote}
Perhaps the log level could be reconsidered then to demote it to INFO? (Would
it be possible to select the level with the flag? It could be then explicitly
decided by the build(er) - kind of accepting the state and have no warning for
that?)
> Display a warning when an aggregator mojo is locking other mojo executions
> --
>
> Key: MNG-7476
> URL: https://issues.apache.org/jira/browse/MNG-7476
> Project: Maven
> Issue Type: Improvement
>Affects Versions: 3.8.5
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 3.8.6, 3.9.0, 4.0.0-alpha-2, 4.0.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7476) Display a warning when an aggregator mojo is locking other mojo executions
[ https://issues.apache.org/jira/browse/MNG-7476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863453#comment-17863453 ] Piotr Zygielo commented on MNG-7476: Can you share advice how to avoid/prevent this warning? If I see this in my parallel multi-module complex build - shall I expect bad result? > Display a warning when an aggregator mojo is locking other mojo executions > -- > > Key: MNG-7476 > URL: https://issues.apache.org/jira/browse/MNG-7476 > Project: Maven > Issue Type: Improvement >Affects Versions: 3.8.5 >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 3.8.6, 3.9.0, 4.0.0-alpha-2, 4.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPIR-462) [REGRESSION] NFEx: For input string: "1.8" in project w/ MR dependency
[
https://issues.apache.org/jira/browse/MPIR-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860245#comment-17860245
]
Piotr Zygielo commented on MPIR-462:
Thank you all - for the fix and releases leading to 3.6.1.
> [REGRESSION] NFEx: For input string: "1.8" in project w/ MR dependency
> --
>
> Key: MPIR-462
> URL: https://issues.apache.org/jira/browse/MPIR-462
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 3.6.0
> Environment: jdk:21
> mvn:3.9.7
> maven-site-plugin:3.12.1
>Reporter: Piotr Zygielo
>Assignee: Michael Osipov
>Priority: Critical
> Fix For: 3.6.1
>
> Attachments: MPIR-462.zip
>
>
> In project with {{io.projectreactor:reactor-core:3.6.6}} dependency:
> {code:java}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.12.1:site (default-site) on
> project X: Error generating
> maven-project-info-reports-plugin:3.6.0:dependencies report: For input
> string: "1.8" -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.12.1:site (default-site) on
> project X: Error generating
> maven-project-info-reports-plugin:3.6.0:dependencies report
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:193)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:180)
> at java.util.concurrent.FutureTask.run (FutureTask.java:317)
> at java.util.concurrent.Executors$RunnableAdapter.call
> (Executors.java:572)
> at java.util.concurrent.FutureTask.run (FutureTask.java:317)
> at java.util.concurrent.ThreadPoolExecutor.runWorker
> (ThreadPoolExecutor.java:1144)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:642)
> at java.lang.Thread.run (Thread.java:1583)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error generating
> maven-project-info-reports-plugin:3.6.0:dependencies report
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:153)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:193)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:180)
> at java.util.concurrent.FutureTask.run (FutureTask.java:317)
> at java.util.concurrent.Executors$RunnableAdapter.call
> (Executors.java:572)
> at java.util.concurrent.FutureTask.run (FutureTask.java:317)
> at java.util.concurrent.ThreadPoolExecutor.runWorker
> (ThreadPoolExecutor.java:1144)
> at java.util.concurrent.ThreadPoolExecuto
[jira] [Commented] (MPIR-462) [REGRESSION] NFEx: For input string: "1.8" in project w/ MR dependency
[
https://issues.apache.org/jira/browse/MPIR-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17855835#comment-17855835
]
Piotr Zygielo commented on MPIR-462:
{quote}The problem is in the maven-shared-jar dependency used by the plugin.
I'll be working on a solution very soon.
{quote}
Great.
But then, this will need:
# fix in maven-shared-jar (separate jira issue?)
# release of above
# dependency update here
to have it also work in MPIR, right?
> [REGRESSION] NFEx: For input string: "1.8" in project w/ MR dependency
> --
>
> Key: MPIR-462
> URL: https://issues.apache.org/jira/browse/MPIR-462
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 3.6.0
> Environment: jdk:21
> mvn:3.9.7
> maven-site-plugin:3.12.1
>Reporter: Piotr Zygielo
>Assignee: Michael Osipov
>Priority: Major
>
> In project with {{io.projectreactor:reactor-core:3.6.6}} dependency:
> {code:java}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.12.1:site (default-site) on
> project X: Error generating
> maven-project-info-reports-plugin:3.6.0:dependencies report: For input
> string: "1.8" -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.12.1:site (default-site) on
> project X: Error generating
> maven-project-info-reports-plugin:3.6.0:dependencies report
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:193)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:180)
> at java.util.concurrent.FutureTask.run (FutureTask.java:317)
> at java.util.concurrent.Executors$RunnableAdapter.call
> (Executors.java:572)
> at java.util.concurrent.FutureTask.run (FutureTask.java:317)
> at java.util.concurrent.ThreadPoolExecutor.runWorker
> (ThreadPoolExecutor.java:1144)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:642)
> at java.lang.Thread.run (Thread.java:1583)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error generating
> maven-project-info-reports-plugin:3.6.0:dependencies report
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:153)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:193)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:180)
> at java.util.concurrent.FutureTask.run (FutureTask.java:317)
> at java.util.concurrent.Executors$RunnableAdapter.call
> (Executors.java:572)
> at java.util.concurrent.FutureTask.run
[jira] [Updated] (MPIR-462) NFEx: For input string: "1.8" in project w/ io.projectreactor:reactor-core:3.6.6 dependency
[
https://issues.apache.org/jira/browse/MPIR-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Zygielo updated MPIR-462:
---
Description:
In project with {{io.projectreactor:reactor-core:3.6.6}} dependency:
{code:java}
Error: Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.12.1:site (default-site) on
project X: Error generating
maven-project-info-reports-plugin:3.6.0:dependencies report: For input string:
"1.8" -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.12.1:site (default-site) on
project X: Error generating
maven-project-info-reports-plugin:3.6.0:dependencies report
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:333)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:316)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:174)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
(MojoExecutor.java:75)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:162)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:159)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:105)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:193)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:180)
at java.util.concurrent.FutureTask.run (FutureTask.java:317)
at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:572)
at java.util.concurrent.FutureTask.run (FutureTask.java:317)
at java.util.concurrent.ThreadPoolExecutor.runWorker
(ThreadPoolExecutor.java:1144)
at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:642)
at java.lang.Thread.run (Thread.java:1583)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error generating
maven-project-info-reports-plugin:3.6.0:dependencies report
at org.apache.maven.plugins.site.render.SiteMojo.execute (SiteMojo.java:153)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:126)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:328)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:316)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:174)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
(MojoExecutor.java:75)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:162)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:159)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:105)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:193)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:180)
at java.util.concurrent.FutureTask.run (FutureTask.java:317)
at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:572)
at java.util.concurrent.FutureTask.run (FutureTask.java:317)
at java.util.concurrent.ThreadPoolExecutor.runWorker
(ThreadPoolExecutor.java:1144)
at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:642)
at java.lang.Thread.run (Thread.java:1583)
Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error
generating maven-project-info-reports-plugin:3.6.0:dependencies report
at
org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
(ReportDocumentRenderer.java:247)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
(DefaultSiteRenderer.java:348)
at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
(SiteMojo.java:194)
at org.apache.maven.plugins.site.render.SiteMojo.execute (SiteMojo.java:143)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:126)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:328)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:316)
[jira] [Updated] (MPIR-462) NFEx: For input string: "1.8" in project w/ MR dependency
[
https://issues.apache.org/jira/browse/MPIR-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Zygielo updated MPIR-462:
---
Summary: NFEx: For input string: "1.8" in project w/ MR dependency (was:
NFEx: For input string: "1.8" in project w/
io.projectreactor:reactor-core:3.6.6 dependency)
> NFEx: For input string: "1.8" in project w/ MR dependency
> -
>
> Key: MPIR-462
> URL: https://issues.apache.org/jira/browse/MPIR-462
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 3.6.0
> Environment: jdk:21
> mvn:3.9.7
> maven-site-plugin:3.12.1
>Reporter: Piotr Zygielo
>Priority: Major
>
> In project with {{io.projectreactor:reactor-core:3.6.6}} dependency:
> {code:java}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.12.1:site (default-site) on
> project X: Error generating
> maven-project-info-reports-plugin:3.6.0:dependencies report: For input
> string: "1.8" -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.12.1:site (default-site) on
> project X: Error generating
> maven-project-info-reports-plugin:3.6.0:dependencies report
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:193)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:180)
> at java.util.concurrent.FutureTask.run (FutureTask.java:317)
> at java.util.concurrent.Executors$RunnableAdapter.call
> (Executors.java:572)
> at java.util.concurrent.FutureTask.run (FutureTask.java:317)
> at java.util.concurrent.ThreadPoolExecutor.runWorker
> (ThreadPoolExecutor.java:1144)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:642)
> at java.lang.Thread.run (Thread.java:1583)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error generating
> maven-project-info-reports-plugin:3.6.0:dependencies report
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:153)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:193)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:180)
> at java.util.concurrent.FutureTask.run (FutureTask.java:317)
> at java.util.concurrent.Executors$RunnableAdapter.call
> (Executors.java:572)
> at java.util.concurrent.FutureTask.run (FutureTask.java:317)
> at java.util.concurrent.ThreadPoolExecutor.runWorker
> (ThreadPoolExecutor.java:1144)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:642)
> at java.lang.Thread.run (Thr
[jira] [Updated] (MPIR-462) NFEx: For input string: "1.8" in project w/ io.projectreactor:reactor-core:3.6.6 dependency
[
https://issues.apache.org/jira/browse/MPIR-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Zygielo updated MPIR-462:
---
Description:
{code:java}
Error: Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.12.1:site (default-site) on
project X: Error generating
maven-project-info-reports-plugin:3.6.0:dependencies report: For input string:
"1.8" -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.12.1:site (default-site) on
project X: Error generating
maven-project-info-reports-plugin:3.6.0:dependencies report
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:333)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:316)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:174)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
(MojoExecutor.java:75)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:162)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:159)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:105)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:193)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:180)
at java.util.concurrent.FutureTask.run (FutureTask.java:317)
at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:572)
at java.util.concurrent.FutureTask.run (FutureTask.java:317)
at java.util.concurrent.ThreadPoolExecutor.runWorker
(ThreadPoolExecutor.java:1144)
at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:642)
at java.lang.Thread.run (Thread.java:1583)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error generating
maven-project-info-reports-plugin:3.6.0:dependencies report
at org.apache.maven.plugins.site.render.SiteMojo.execute (SiteMojo.java:153)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:126)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:328)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:316)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:174)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
(MojoExecutor.java:75)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:162)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:159)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:105)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:193)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:180)
at java.util.concurrent.FutureTask.run (FutureTask.java:317)
at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:572)
at java.util.concurrent.FutureTask.run (FutureTask.java:317)
at java.util.concurrent.ThreadPoolExecutor.runWorker
(ThreadPoolExecutor.java:1144)
at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:642)
at java.lang.Thread.run (Thread.java:1583)
Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error
generating maven-project-info-reports-plugin:3.6.0:dependencies report
at
org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
(ReportDocumentRenderer.java:247)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
(DefaultSiteRenderer.java:348)
at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
(SiteMojo.java:194)
at org.apache.maven.plugins.site.render.SiteMojo.execute (SiteMojo.java:143)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:126)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:328)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:316)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExe
[jira] [Created] (MPIR-462) NFEx: For input string: "1.8" in project w/ io.projectreactor:reactor-core:3.6.6 dependency
Piotr Zygielo created MPIR-462:
--
Summary: NFEx: For input string: "1.8" in project w/
io.projectreactor:reactor-core:3.6.6 dependency
Key: MPIR-462
URL: https://issues.apache.org/jira/browse/MPIR-462
Project: Maven Project Info Reports Plugin
Issue Type: Bug
Components: dependencies
Affects Versions: 3.6.0
Environment: jdk:21
mvn:3.9.7
maven-site-plugin:3.12.1
Reporter: Piotr Zygielo
{code:java}
Error: Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.12.1:site (default-site) on
project X: Error generating
maven-project-info-reports-plugin:3.6.0:dependencies report: For input string:
"1.8" -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.12.1:site (default-site) on
project russel: Error generating
maven-project-info-reports-plugin:3.6.0:dependencies report
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:333)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:316)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:174)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
(MojoExecutor.java:75)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:162)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:159)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:105)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:193)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:180)
at java.util.concurrent.FutureTask.run (FutureTask.java:317)
at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:572)
at java.util.concurrent.FutureTask.run (FutureTask.java:317)
at java.util.concurrent.ThreadPoolExecutor.runWorker
(ThreadPoolExecutor.java:1144)
at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:642)
at java.lang.Thread.run (Thread.java:1583)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error generating
maven-project-info-reports-plugin:3.6.0:dependencies report
at org.apache.maven.plugins.site.render.SiteMojo.execute (SiteMojo.java:153)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:126)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:328)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:316)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:174)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
(MojoExecutor.java:75)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:162)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:159)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:105)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:193)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:180)
at java.util.concurrent.FutureTask.run (FutureTask.java:317)
at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:572)
at java.util.concurrent.FutureTask.run (FutureTask.java:317)
at java.util.concurrent.ThreadPoolExecutor.runWorker
(ThreadPoolExecutor.java:1144)
at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:642)
at java.lang.Thread.run (Thread.java:1583)
Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error
generating maven-project-info-reports-plugin:3.6.0:dependencies report
at
org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
(ReportDocumentRenderer.java:247)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
(DefaultSiteRenderer.java:348)
at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
(SiteMojo.java:194)
at org.apache.maven.plugins.site.render.SiteMojo.execute (SiteMojo.java:143)
at org.apache.maven.plugin.Defaul
[jira] [Comment Edited] (MNG-7194) PluginParameterExpressionEvaluator incorrectly interpolates unknown subexpression
[
https://issues.apache.org/jira/browse/MNG-7194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17853537#comment-17853537
]
Piotr Zygielo edited comment on MNG-7194 at 6/9/24 8:55 PM:
Just wonder if this could be related to my unmet expectation I have with
surefire and {{{}surefire.forkNumber{}}}.
Given
[https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#forkCount]
{quote}The system properties and the argLine of the forked processes may
contain the place holder string ${surefire.forkNumber}, which is replaced with
a fixed number for each of the parallel forks
{quote}
When I configure {{m-surefire-p}} with
{code:xml}
${surefire.forkNumber}
{code}
Then {{p1}} system property (available in test) is set to empty string (it's
not set during interpolation of parameters for plugin and
{{SurefireHelper.replaceThreadNumberPlaceholders}} finds nothing to work with).
(While {color:#de350b}I expect(ed){color} the value {{N}} there.)
But when I use
{code:xml}
_${surefire.forkNumber}_
{code}
(where {{_}} can be anything just to not leave {{{}${}}}-property reference
alone)
Then {{p1}} system property is set to {{\_N\_}} as expected, as it's passed to
SF as unchanged {{\_${surefire.forkNumber}\_}} and
{{SurefireHelper.replaceThreadNumberPlaceholders}} is happy with that.
If those cases are linked - then perhaps if
{quote}It should be just pre?
{quote}
is implemented, (would it cause {{__}} to be passed for my {{p1}} to SF?) it
would probably need some changes in SF in such case.
(Or could be handled in SF in first place separately.)
I think.
(Using underscore in my example was the worst idea, as online JIRA editor helps
and unescapes on my every edit...)
was (Author: pzygielo):
Just wonder if this could be related to my unmet expectation I have with
surefire and {{{}surefire.forkNumber{}}}.
Given
[https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#forkCount]
{quote}The system properties and the argLine of the forked processes may
contain the place holder string ${surefire.forkNumber}, which is replaced with
a fixed number for each of the parallel forks
{quote}
When I configure {{m-surefire-p}} with
{code:xml}
${surefire.forkNumber}
{code}
Then {{p1}} system property (available in test) is set to empty string (it's
not set during interpolation of parameters for plugin and
{{SurefireHelper.replaceThreadNumberPlaceholders}} finds nothing to work with).
(While {color:#de350b}I expect(ed){color} the value {{N}} there.)
But when I use
{code:xml}
_${surefire.forkNumber}_
{code}
(where {{_}} can be anything just to not leave {{{}${}}}-property reference
alone)
Then {{p1}} system property is set to {{\_N\_}} as expected, as it's passed to
SF as unchanged {{_${surefire.forkNumber}_}} and
{{SurefireHelper.replaceThreadNumberPlaceholders}} is happy with that.
If those cases are linked - then perhaps if
{quote}It should be just pre?
{quote}
is implemented, (would it cause {{__}} to be passed for my {{p1}} to SF?) it
would probably need some changes in SF in such case.
(Or could be handled in SF in first place separately.)
I think.
(Using underscore in my example was the worst idea, as online JIRA editor helps
and unescapes on my every edit...)
> PluginParameterExpressionEvaluator incorrectly interpolates unknown
> subexpression
> -
>
> Key: MNG-7194
> URL: https://issues.apache.org/jira/browse/MNG-7194
> Project: Maven
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Reporter: Robert Scholte
>Priority: Minor
>
> The PluginParameterExpressionEvaluator evaluate(String,Class)-method ends
> like this:
> {code:java}
> if ( value instanceof String )
> {
> // TODO: without #, this could just be an evaluate call...
> String val = (String) value;
> int exprStartDelimiter = val.indexOf( "${" );
> if ( exprStartDelimiter >= 0 )
> {
> if ( exprStartDelimiter > 0 )
> {
> value = val.substring( 0, exprStartDelimiter ) +
> evaluate( val.substring( exprStartDelimiter ) );
> }
> else
> {
> value = evaluate( val.substring( exprStartDelimiter ) );
> }
> }
> }
> {code}
> Assume that pre${unknown} needs to be evaluated and {{unknown}} does not
> exist, the result well be "{{prenull}}"
> Just ${unknown} evaluates to null, but because there's no String concat it
> will be a real null.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MNG-7194) PluginParameterExpressionEvaluator incorrectly interpolates unknown subexpression
[
https://issues.apache.org/jira/browse/MNG-7194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17853537#comment-17853537
]
Piotr Zygielo edited comment on MNG-7194 at 6/9/24 8:54 PM:
Just wonder if this could be related to my unmet expectation I have with
surefire and {{{}surefire.forkNumber{}}}.
Given
[https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#forkCount]
{quote}The system properties and the argLine of the forked processes may
contain the place holder string ${surefire.forkNumber}, which is replaced with
a fixed number for each of the parallel forks
{quote}
When I configure {{m-surefire-p}} with
{code:xml}
${surefire.forkNumber}
{code}
Then {{p1}} system property (available in test) is set to empty string (it's
not set during interpolation of parameters for plugin and
{{SurefireHelper.replaceThreadNumberPlaceholders}} finds nothing to work with).
(While {color:#de350b}I expect(ed){color} the value {{N}} there.)
But when I use
{code:xml}
_${surefire.forkNumber}_
{code}
(where {{_}} can be anything just to not leave {{{}${}}}-property reference
alone)
Then {{p1}} system property is set to {{\_N\_}} as expected, as it's passed to
SF as unchanged {{_${surefire.forkNumber}_}} and
{{SurefireHelper.replaceThreadNumberPlaceholders}} is happy with that.
If those cases are linked - then perhaps if
{quote}It should be just pre?
{quote}
is implemented, (would it cause {{__}} to be passed for my {{p1}} to SF?) it
would probably need some changes in SF in such case.
(Or could be handled in SF in first place separately.)
I think.
(Using underscore in my example was the worst idea, as online JIRA editor helps
and unescapes on my every edit...)
was (Author: pzygielo):
Just wonder if this could be related to my unmet expectation I have with
surefire and {{{}surefire.forkNumber{}}}.
Given
[https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#forkCount]
{quote}The system properties and the argLine of the forked processes may
contain the place holder string ${surefire.forkNumber}, which is replaced with
a fixed number for each of the parallel forks
{quote}
When I configure {{m-surefire-p}} with
{code:xml}
${surefire.forkNumber}
{code}
Then {{p1}} system property (available in test) is set to empty string (it's
not set during interpolation of parameters for plugin and
{{SurefireHelper.replaceThreadNumberPlaceholders}} finds nothing to work with).
(While {color:#de350b}I expect(ed){color} the value {{N}} there.)
But when I use
{code:xml}
_${surefire.forkNumber}_
{code}
(where {{_}} can be anything just to not leave {{{}${}}}-property reference
alone)
Then {{p1}} system property is set to {{_N_}} as expected, as it's passed to SF
as unchanged {{_${surefire.forkNumber}_}} and
{{SurefireHelper.replaceThreadNumberPlaceholders}} is happy with that.
If those cases are linked - then perhaps if
{quote}It should be just pre?
{quote}
is implemented, (would it cause {{__}} to be passed for my {{p1}} to SF?) it
would probably need some changes in SF in such case.
(Or could be handled in SF in first place separately.)
I think.
> PluginParameterExpressionEvaluator incorrectly interpolates unknown
> subexpression
> -
>
> Key: MNG-7194
> URL: https://issues.apache.org/jira/browse/MNG-7194
> Project: Maven
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Reporter: Robert Scholte
>Priority: Minor
>
> The PluginParameterExpressionEvaluator evaluate(String,Class)-method ends
> like this:
> {code:java}
> if ( value instanceof String )
> {
> // TODO: without #, this could just be an evaluate call...
> String val = (String) value;
> int exprStartDelimiter = val.indexOf( "${" );
> if ( exprStartDelimiter >= 0 )
> {
> if ( exprStartDelimiter > 0 )
> {
> value = val.substring( 0, exprStartDelimiter ) +
> evaluate( val.substring( exprStartDelimiter ) );
> }
> else
> {
> value = evaluate( val.substring( exprStartDelimiter ) );
> }
> }
> }
> {code}
> Assume that pre${unknown} needs to be evaluated and {{unknown}} does not
> exist, the result well be "{{prenull}}"
> Just ${unknown} evaluates to null, but because there's no String concat it
> will be a real null.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MNG-7194) PluginParameterExpressionEvaluator incorrectly interpolates unknown subexpression
[
https://issues.apache.org/jira/browse/MNG-7194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17853537#comment-17853537
]
Piotr Zygielo edited comment on MNG-7194 at 6/9/24 8:52 PM:
Just wonder if this could be related to my unmet expectation I have with
surefire and {{{}surefire.forkNumber{}}}.
Given
[https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#forkCount]
{quote}The system properties and the argLine of the forked processes may
contain the place holder string ${surefire.forkNumber}, which is replaced with
a fixed number for each of the parallel forks
{quote}
When I configure {{m-surefire-p}} with
{code:xml}
${surefire.forkNumber}
{code}
Then {{p1}} system property (available in test) is set to empty string (it's
not set during interpolation of parameters for plugin and
{{SurefireHelper.replaceThreadNumberPlaceholders}} finds nothing to work with).
(While {color:#de350b}I expect(ed){color} the value {{N}} there.)
But when I use
{code:xml}
_${surefire.forkNumber}_
{code}
(where {{_}} can be anything just to not leave {{{}${}}}-property reference
alone)
Then {{p1}} system property is set to {{_N_}} as expected, as it's passed to SF
as unchanged {{_${surefire.forkNumber}_}} and
{{SurefireHelper.replaceThreadNumberPlaceholders}} is happy with that.
If those cases are linked - then perhaps if
{quote}It should be just pre?
{quote}
is implemented, (would it cause {{__}} to be passed for my {{p1}} to SF?) it
would probably need some changes in SF in such case.
(Or could be handled in SF in first place separately.)
I think.
was (Author: pzygielo):
Just wonder if this could be related to my unmet expectation I have with
surefire and {{{}surefire.forkNumber{}}}.
Given
[https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#forkCount]
{quote}The system properties and the argLine of the forked processes may
contain the place holder string \{${surefire.forkNumber}}, which is replaced
with a fixed number for each of the parallel forks
{quote}
When I configure {{m-surefire-p}} with
{code:xml}
${surefire.forkNumber}
{code}
Then {{p1}} system property (available in test) is set to empty string (it's
not set during interpolation of parameters for plugin and
{{SurefireHelper.replaceThreadNumberPlaceholders}} finds nothing to work with).
(While {color:#de350b}I expect(ed){color} the value {{N}} there.)
But when I use
{code:xml}
_${surefire.forkNumber}_
{code}
(where {{_}} can be anything just to not leave {{{}${}}}-property reference
alone)
Then {{p1}} system property is set to {{\_N\_}} as expected, as it's passed to
SF as unchanged {{\_${surefire.forkNumber}\_}} and
{{SurefireHelper.replaceThreadNumberPlaceholders}} is happy with that.
If those cases are linked - then perhaps if
{quote}It should be just pre?
{quote}
is implemented, (would it cause {{__}} to be passed for my {{p1}} to SF?) it
would probably need some changes in SF in such case.
(Or could be handled in SF in first place separately.)
I think.
> PluginParameterExpressionEvaluator incorrectly interpolates unknown
> subexpression
> -
>
> Key: MNG-7194
> URL: https://issues.apache.org/jira/browse/MNG-7194
> Project: Maven
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Reporter: Robert Scholte
>Priority: Minor
>
> The PluginParameterExpressionEvaluator evaluate(String,Class)-method ends
> like this:
> {code:java}
> if ( value instanceof String )
> {
> // TODO: without #, this could just be an evaluate call...
> String val = (String) value;
> int exprStartDelimiter = val.indexOf( "${" );
> if ( exprStartDelimiter >= 0 )
> {
> if ( exprStartDelimiter > 0 )
> {
> value = val.substring( 0, exprStartDelimiter ) +
> evaluate( val.substring( exprStartDelimiter ) );
> }
> else
> {
> value = evaluate( val.substring( exprStartDelimiter ) );
> }
> }
> }
> {code}
> Assume that pre${unknown} needs to be evaluated and {{unknown}} does not
> exist, the result well be "{{prenull}}"
> Just ${unknown} evaluates to null, but because there's no String concat it
> will be a real null.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MNG-7194) PluginParameterExpressionEvaluator incorrectly interpolates unknown subexpression
[
https://issues.apache.org/jira/browse/MNG-7194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17853537#comment-17853537
]
Piotr Zygielo edited comment on MNG-7194 at 6/9/24 8:51 PM:
Just wonder if this could be related to my unmet expectation I have with
surefire and {{{}surefire.forkNumber{}}}.
Given
[https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#forkCount]
{quote}The system properties and the argLine of the forked processes may
contain the place holder string \{${surefire.forkNumber}}, which is replaced
with a fixed number for each of the parallel forks
{quote}
When I configure {{m-surefire-p}} with
{code:xml}
${surefire.forkNumber}
{code}
Then {{p1}} system property (available in test) is set to empty string (it's
not set during interpolation of parameters for plugin and
{{SurefireHelper.replaceThreadNumberPlaceholders}} finds nothing to work with).
(While {color:#de350b}I expect(ed){color} the value {{N}} there.)
But when I use
{code:xml}
_${surefire.forkNumber}_
{code}
(where {{_}} can be anything just to not leave {{{}${}}}-property reference
alone)
Then {{p1}} system property is set to {{\_N\_}} as expected, as it's passed to
SF as unchanged {{\_${surefire.forkNumber}\_}} and
{{SurefireHelper.replaceThreadNumberPlaceholders}} is happy with that.
If those cases are linked - then perhaps if
{quote}It should be just pre?
{quote}
is implemented, (would it cause {{__}} to be passed for my {{p1}} to SF?) it
would probably need some changes in SF in such case.
(Or could be handled in SF in first place separately.)
I think.
was (Author: pzygielo):
Just wonder if this could be related to my unmet expectation I have with
surefire and {{{}surefire.forkNumber{}}}.
Given
[https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#forkCount]
{quote}The system properties and the argLine of the forked processes may
contain the place holder string \{${surefire.forkNumber}}, which is replaced
with a fixed number for each of the parallel forks
{quote}
When I configure {{m-surefire-p}} with
{code:xml}
${surefire.forkNumber}
{code}
Then {{p1}} system property (available in test) is set to empty string (it's
not set during interpolation of parameters for plugin and
{{SurefireHelper.replaceThreadNumberPlaceholders}} finds nothing to work with).
(While {color:#de350b}I expect(ed){color} the value {{N}} there.)
But when I use
{code:xml}
_${surefire.forkNumber}_
{code}
(where {{_}} can be anything just to not leave {{{}${}}}-property reference
alone)
Then {{p1}} system property is set to {{\_N\_}} as expected, as it's passed to
SF as unchanged {{_${surefire.forkNumber}_}} and
{{SurefireHelper.replaceThreadNumberPlaceholders}} is happy with that.
If those cases are linked - then perhaps if
{quote}It should be just pre?
{quote}
is implemented, (would it cause {{__}} to be passed for my {{p1}} to SF?) it
would probably need some changes in SF in such case.
(Or could be handled in SF in first place separately.)
I think.
> PluginParameterExpressionEvaluator incorrectly interpolates unknown
> subexpression
> -
>
> Key: MNG-7194
> URL: https://issues.apache.org/jira/browse/MNG-7194
> Project: Maven
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Reporter: Robert Scholte
>Priority: Minor
>
> The PluginParameterExpressionEvaluator evaluate(String,Class)-method ends
> like this:
> {code:java}
> if ( value instanceof String )
> {
> // TODO: without #, this could just be an evaluate call...
> String val = (String) value;
> int exprStartDelimiter = val.indexOf( "${" );
> if ( exprStartDelimiter >= 0 )
> {
> if ( exprStartDelimiter > 0 )
> {
> value = val.substring( 0, exprStartDelimiter ) +
> evaluate( val.substring( exprStartDelimiter ) );
> }
> else
> {
> value = evaluate( val.substring( exprStartDelimiter ) );
> }
> }
> }
> {code}
> Assume that pre${unknown} needs to be evaluated and {{unknown}} does not
> exist, the result well be "{{prenull}}"
> Just ${unknown} evaluates to null, but because there's no String concat it
> will be a real null.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MNG-7194) PluginParameterExpressionEvaluator incorrectly interpolates unknown subexpression
[
https://issues.apache.org/jira/browse/MNG-7194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17853537#comment-17853537
]
Piotr Zygielo edited comment on MNG-7194 at 6/9/24 8:49 PM:
Just wonder if this could be related to my unmet expectation I have with
surefire and {{{}surefire.forkNumber{}}}.
Given
[https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#forkCount]
{quote}The system properties and the argLine of the forked processes may
contain the place holder string \{${surefire.forkNumber}}, which is replaced
with a fixed number for each of the parallel forks
{quote}
When I configure {{m-surefire-p}} with
{code:xml}
${surefire.forkNumber}
{code}
Then {{p1}} system property (available in test) is set to empty string (it's
not set during interpolation of parameters for plugin and
{{SurefireHelper.replaceThreadNumberPlaceholders}} finds nothing to work with).
(While {color:#de350b}I expect(ed){color} the value {{N}} there.)
But when I use
{code:xml}
_${surefire.forkNumber}_
{code}
(where {{_}} can be anything just to not leave {{{}${}}}-property reference
alone)
Then {{p1}} system property is set to {{\_N\_}} as expected, as it's passed to
SF as unchanged {{_${surefire.forkNumber}_}} and
{{SurefireHelper.replaceThreadNumberPlaceholders}} is happy with that.
If those cases are linked - then perhaps if
{quote}It should be just pre?
{quote}
is implemented, (would it cause {{__}} to be passed for my {{p1}} to SF?) it
would probably need some changes in SF in such case.
(Or could be handled in SF in first place separately.)
I think.
was (Author: pzygielo):
Just wonder if this could be related to my unmet expectation I have with
surefire and {{{}surefire.forkNumber{}}}.
Given
[https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#forkCount]
{quote}The system properties and the argLine of the forked processes may
contain the place holder string \{${surefire.forkNumber}}, which is replaced
with a fixed number for each of the parallel forks
{quote}
When I configure {{m-surefire-p}} with
{code:xml}
${surefire.forkNumber}
{code}
Then {{p1}} system property (available in test) is set to empty string (it's
not set during interpolation of parameters for plugin and
{{SurefireHelper.replaceThreadNumberPlaceholders}} finds nothing to work with).
(While {color:#de350b}I expect(ed){color} the value {{N}} there.)
But when I use
{code:xml}
_${surefire.forkNumber}_
{code}
(where {{_}} can be anything just to not leave {{{}${}}}-property reference
alone)
Then {{p1}} system property is set to {{_N_}} as expected, as it's passed to SF
as unchanged {{_${surefire.forkNumber}_}} and
{{SurefireHelper.replaceThreadNumberPlaceholders}} is happy with that.
If those cases are linked - then perhaps if
{quote}It should be just pre?
{quote}
is implemented, (would it cause {{__}} to be passed for my {{p1}} to SF?) it
would probably need some changes in SF in such case.
(Or could be handled in SF in first place separately.)
I think.
> PluginParameterExpressionEvaluator incorrectly interpolates unknown
> subexpression
> -
>
> Key: MNG-7194
> URL: https://issues.apache.org/jira/browse/MNG-7194
> Project: Maven
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Reporter: Robert Scholte
>Priority: Minor
>
> The PluginParameterExpressionEvaluator evaluate(String,Class)-method ends
> like this:
> {code:java}
> if ( value instanceof String )
> {
> // TODO: without #, this could just be an evaluate call...
> String val = (String) value;
> int exprStartDelimiter = val.indexOf( "${" );
> if ( exprStartDelimiter >= 0 )
> {
> if ( exprStartDelimiter > 0 )
> {
> value = val.substring( 0, exprStartDelimiter ) +
> evaluate( val.substring( exprStartDelimiter ) );
> }
> else
> {
> value = evaluate( val.substring( exprStartDelimiter ) );
> }
> }
> }
> {code}
> Assume that pre${unknown} needs to be evaluated and {{unknown}} does not
> exist, the result well be "{{prenull}}"
> Just ${unknown} evaluates to null, but because there's no String concat it
> will be a real null.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7194) PluginParameterExpressionEvaluator incorrectly interpolates unknown subexpression
[
https://issues.apache.org/jira/browse/MNG-7194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17853537#comment-17853537
]
Piotr Zygielo commented on MNG-7194:
Just wonder if this could be related to my unmet expectation I have with
surefire and {{{}surefire.forkNumber{}}}.
Given
[https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#forkCount]
{quote}The system properties and the argLine of the forked processes may
contain the place holder string \{${surefire.forkNumber}}, which is replaced
with a fixed number for each of the parallel forks
{quote}
When I configure {{m-surefire-p}} with
{code:xml}
${surefire.forkNumber}
{code}
Then {{p1}} system property (available in test) is set to empty string (it's
not set during interpolation of parameters for plugin and
{{SurefireHelper.replaceThreadNumberPlaceholders}} finds nothing to work with).
(While {color:#de350b}I expect(ed){color} the value {{N}} there.)
But when I use
{code:xml}
_${surefire.forkNumber}_
{code}
(where {{_}} can be anything just to not leave {{{}${}}}-property reference
alone)
Then {{p1}} system property is set to {{_N_}} as expected, as it's passed to SF
as unchanged {{_${surefire.forkNumber}_}} and
{{SurefireHelper.replaceThreadNumberPlaceholders}} is happy with that.
If those cases are linked - then perhaps if
{quote}It should be just pre?
{quote}
is implemented, (would it cause {{__}} to be passed for my {{p1}} to SF?) it
would probably need some changes in SF in such case.
(Or could be handled in SF in first place separately.)
I think.
> PluginParameterExpressionEvaluator incorrectly interpolates unknown
> subexpression
> -
>
> Key: MNG-7194
> URL: https://issues.apache.org/jira/browse/MNG-7194
> Project: Maven
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Reporter: Robert Scholte
>Priority: Minor
>
> The PluginParameterExpressionEvaluator evaluate(String,Class)-method ends
> like this:
> {code:java}
> if ( value instanceof String )
> {
> // TODO: without #, this could just be an evaluate call...
> String val = (String) value;
> int exprStartDelimiter = val.indexOf( "${" );
> if ( exprStartDelimiter >= 0 )
> {
> if ( exprStartDelimiter > 0 )
> {
> value = val.substring( 0, exprStartDelimiter ) +
> evaluate( val.substring( exprStartDelimiter ) );
> }
> else
> {
> value = evaluate( val.substring( exprStartDelimiter ) );
> }
> }
> }
> {code}
> Assume that pre${unknown} needs to be evaluated and {{unknown}} does not
> exist, the result well be "{{prenull}}"
> Just ${unknown} evaluates to null, but because there's no String concat it
> will be a real null.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7868) "Could not acquire lock(s)" error in concurrent maven builds
[
https://issues.apache.org/jira/browse/MNG-7868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17851069#comment-17851069
]
Piotr Zygielo commented on MNG-7868:
{quote}Interesting, and failure happened only in the scope of mentioned plugin?
{quote}
This happened in GitHub workflow, in multi-module project, in run #1 (next
re-run for the same sources was completed successfully), with two other modules
(one Spring Boot) finished with success, and then two next XXX, YYY failing in
{{pgpverify-maven-plugin:check}} only.
The project YYY uses {{m-shade-p}} (its upgrade to 3.6.0 caused CI to run) but
{{pgpverify}} fired first and {{shade}} didn't participate in the build at this
stage I believe.
> "Could not acquire lock(s)" error in concurrent maven builds
>
>
> Key: MNG-7868
> URL: https://issues.apache.org/jira/browse/MNG-7868
> Project: Maven
> Issue Type: Bug
> Environment: windows, maven 3.9.4
>Reporter: Jörg Hohwiller
>Priority: Major
> Attachments: image-2024-04-10-15-44-37-013.png, screenshot-1.png
>
>
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install)
> on project foo.bar: Execution default-install of goal
> org.apache.maven.plugins:maven-install-plugin:3.1.1:install failed: Could not
> acquire lock(s) -> [Help 1]
> {code}
> I am using maven 3.9.4 on windows:
> {code}
> $ mvn -v
> Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
> Maven home: D:\projects\test\software\mvn
> Java version: 17.0.5, vendor: Eclipse Adoptium, runtime:
> D:\projects\test\software\java
> Default locale: en_US, platform encoding: UTF-8
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> {code}
> I searched for this bug and found issues like MRESOLVER-332 that first look
> identical or similar but do not really seem to be related so I decided to
> create this issue.
> For this bug I made the following observations:
> * it only happens with concurrent builds: {{mvn -T ...}}
> * is seems to be windows related (at least mainly happens on windows)
> * it is in-deterministic and is not so easy to create an isolated and simple
> project and a reproducible scenario that always results in this error.
> However, I get this very often in my current project with many modules (500+).
> * it is not specific to the maven-install-plugin and also happens from other
> spots in maven:
> I also got this stacktrace:
> {code}
> Suppressed: java.lang.IllegalStateException: Attempt 1: Could not acquire
> write lock for
> 'C:\Users\hohwille\.m2\repository\.locks\artifact~com.caucho~com.springsource.com.caucho~3.2.1.lock'
> in 30 SECONDS
> at
> org.eclipse.aether.internal.impl.synccontext.named.NamedLockFactoryAdapter$AdaptedLockSyncContext.acquire
> (NamedLockFactoryAdapter.java:202)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:271)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
> (DefaultArtifactResolver.java:259)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies
> (DefaultRepositorySystem.java:352)
> {code}
> See also this related discussion:
> https://github.com/apache/maven-mvnd/issues/836#issuecomment-1702488377
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7868) "Could not acquire lock(s)" error in concurrent maven builds
[
https://issues.apache.org/jira/browse/MNG-7868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17851036#comment-17851036
]
Piotr Zygielo commented on MNG-7868:
{quote} All affected users: please upgrade to 3.9.7 and report back.
{quote}
I observed (once, no {{-e}} available, cannot reproduce so far) with maven
3.9.7, java 21 (corretto), ubuntu, starting with empty repository used
exclusively by the one maven execution (but with {{-T2C}}), following:
{code:java}
Error: Failed to execute goal
org.simplify4u.plugins:pgpverify-maven-plugin:1.18.1:check (default) on project
XXX: Execution default of goal
org.simplify4u.plugins:pgpverify-maven-plugin:1.18.1:check failed: Could not
acquire lock(s) -> [Help 1]
Error: Failed to execute goal
org.simplify4u.plugins:pgpverify-maven-plugin:1.18.1:check (default) on project
YYY: Execution default of goal
org.simplify4u.plugins:pgpverify-maven-plugin:1.18.1:check failed: Could not
acquire lock(s) -> [Help 1]
{code}
> "Could not acquire lock(s)" error in concurrent maven builds
>
>
> Key: MNG-7868
> URL: https://issues.apache.org/jira/browse/MNG-7868
> Project: Maven
> Issue Type: Bug
> Environment: windows, maven 3.9.4
>Reporter: Jörg Hohwiller
>Priority: Major
> Attachments: image-2024-04-10-15-44-37-013.png, screenshot-1.png
>
>
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install)
> on project foo.bar: Execution default-install of goal
> org.apache.maven.plugins:maven-install-plugin:3.1.1:install failed: Could not
> acquire lock(s) -> [Help 1]
> {code}
> I am using maven 3.9.4 on windows:
> {code}
> $ mvn -v
> Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
> Maven home: D:\projects\test\software\mvn
> Java version: 17.0.5, vendor: Eclipse Adoptium, runtime:
> D:\projects\test\software\java
> Default locale: en_US, platform encoding: UTF-8
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> {code}
> I searched for this bug and found issues like MRESOLVER-332 that first look
> identical or similar but do not really seem to be related so I decided to
> create this issue.
> For this bug I made the following observations:
> * it only happens with concurrent builds: {{mvn -T ...}}
> * is seems to be windows related (at least mainly happens on windows)
> * it is in-deterministic and is not so easy to create an isolated and simple
> project and a reproducible scenario that always results in this error.
> However, I get this very often in my current project with many modules (500+).
> * it is not specific to the maven-install-plugin and also happens from other
> spots in maven:
> I also got this stacktrace:
> {code}
> Suppressed: java.lang.IllegalStateException: Attempt 1: Could not acquire
> write lock for
> 'C:\Users\hohwille\.m2\repository\.locks\artifact~com.caucho~com.springsource.com.caucho~3.2.1.lock'
> in 30 SECONDS
> at
> org.eclipse.aether.internal.impl.synccontext.named.NamedLockFactoryAdapter$AdaptedLockSyncContext.acquire
> (NamedLockFactoryAdapter.java:202)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:271)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
> (DefaultArtifactResolver.java:259)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies
> (DefaultRepositorySystem.java:352)
> {code}
> See also this related discussion:
> https://github.com/apache/maven-mvnd/issues/836#issuecomment-1702488377
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MENFORCER-466) RequireUpperBoundDeps fails on provided dependencies since 3.2.1
[
https://issues.apache.org/jira/browse/MENFORCER-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17684216#comment-17684216
]
Piotr Zygielo commented on MENFORCER-466:
-
MENFORCER-402
> RequireUpperBoundDeps fails on provided dependencies since 3.2.1
>
>
> Key: MENFORCER-466
> URL: https://issues.apache.org/jira/browse/MENFORCER-466
> Project: Maven Enforcer Plugin
> Issue Type: Bug
>Affects Versions: 3.2.1
> Environment: Apache Maven 3.8.4
> (9b656c72d54e5bacbed989b64718c159fe39b537)
> Java version: 1.8.0_352, vendor: Temurin
>Reporter: Stefan Cordes
>Priority: Major
> Attachments: console-3.1.0.txt, console-3.2.1.txt, pom.xml
>
>
> The attached pom.xml works fine for
> {code:java}
> mvn enforcer:enforce -Dversion.maven-enforcer-plugin=3.1.0 {code}
> but
> {code:java}
> mvn enforcer:enforce -Dversion.maven-enforcer-plugin=3.2.1 {code}
> fails with
> {code:java}
> Rule 0: org.apache.maven.enforcer.rules.dependency.RequireUpperBoundDeps
> failed with message:
> Failed while enforcing RequireUpperBoundDeps. The error(s) are [
> Require upper bound dependencies error for org.apache.maven:maven-model:3.8.5
> [provided] paths to dependency are:
> +-com.canda.maven:mvnbase-maven-plugin:1.0.0-local-SNAPSHOT
> +-org.apache.maven:maven-plugin-api:3.8.5 [provided]
> +-org.apache.maven:maven-model:3.8.5 [provided]
> and
> +-com.canda.maven:mvnbase-maven-plugin:1.0.0-local-SNAPSHOT
> +-org.apache.maven:maven-core:3.8.7 [provided]
> +-org.apache.maven:maven-model:3.8.7 [provided]
> and
> +-com.canda.maven:mvnbase-maven-plugin:1.0.0-local-SNAPSHOT
> +-org.apache.maven:maven-core:3.8.7 [provided]
> +-org.apache.maven:maven-model-builder:3.8.7 [provided]
> +-org.apache.maven:maven-model:3.8.7 [provided]
> and
> +-com.canda.maven:mvnbase-maven-plugin:1.0.0-local-SNAPSHOT
> +-org.apache.maven:maven-core:3.8.7 [provided]
> +-org.apache.maven:maven-resolver-provider:3.8.7 [provided]
> +-org.apache.maven:maven-model:3.8.7 [provided] {code}
> Similar to dependencyConvergence (
> https://issues.apache.org/jira/browse/MENFORCER-407?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel&focusedCommentId=17683326#comment-17683326
> ) the updated plugin
> seems to check "provided" dependencies for upperBounds.
> All provided dependencies (at least the transitive ones?) needs to be ignored
> by RequireUpperBoundDeps.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MDEP-843) :list-classes does not use GAV parameters
[ https://issues.apache.org/jira/browse/MDEP-843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Zygielo updated MDEP-843: --- Description: I propose two ways to solve this: * PR 281 - Remove unused GAV fields - to stop publishing documentation for them * PR 282 - Use GAV fields if provided > :list-classes does not use GAV parameters > - > > Key: MDEP-843 > URL: https://issues.apache.org/jira/browse/MDEP-843 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: list-classes >Reporter: Piotr Zygielo >Priority: Minor > > I propose two ways to solve this: > * PR 281 - Remove unused GAV fields - to stop publishing documentation for > them > * PR 282 - Use GAV fields if provided -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDEP-843) :list-classes does not use GAV parameters
[ https://issues.apache.org/jira/browse/MDEP-843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Zygielo updated MDEP-843: --- Summary: :list-classes does not use GAV parameters (was: artifact) > :list-classes does not use GAV parameters > - > > Key: MDEP-843 > URL: https://issues.apache.org/jira/browse/MDEP-843 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: list-classes >Reporter: Piotr Zygielo >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDEP-843) artifact
[ https://issues.apache.org/jira/browse/MDEP-843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Zygielo updated MDEP-843: --- Component/s: list-classes > artifact > > > Key: MDEP-843 > URL: https://issues.apache.org/jira/browse/MDEP-843 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: list-classes >Reporter: Piotr Zygielo >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MDEP-843) artifact
Piotr Zygielo created MDEP-843: -- Summary: artifact Key: MDEP-843 URL: https://issues.apache.org/jira/browse/MDEP-843 Project: Maven Dependency Plugin Issue Type: Bug Reporter: Piotr Zygielo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDEP-842) :list-classes does not skip if skip is set
[ https://issues.apache.org/jira/browse/MDEP-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Zygielo updated MDEP-842: --- Description: I propose two ways to solve this * PR 280 - Remove unused skip field - based on [https://github.com/apache/maven-dependency-plugin/pull/57#discussion_r430505871] This would remove unused property from documentation of the goal. * PR 279 - Use skip field in :list-classes - based on [https://github.com/apache/maven-dependency-plugin/pull/57#discussion_r430520501] This would skip the execution as documentation suggests. was: I propose two ways to solve this * PR 280 - Remove unused skip field - based on [https://github.com/apache/maven-dependency-plugin/pull/57#discussion_r430505871] This would remove unused property from documentation of the goal. * PR 279 - Use skip field in :list-classes - based on [https://github.com/apache/maven-dependency-plugin/pull/57#discussion_r430520501] This would skip the execution as described by documentation suggests. > :list-classes does not skip if skip is set > -- > > Key: MDEP-842 > URL: https://issues.apache.org/jira/browse/MDEP-842 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: list-classes >Reporter: Piotr Zygielo >Priority: Minor > > I propose two ways to solve this > * PR 280 - Remove unused skip field - based on > [https://github.com/apache/maven-dependency-plugin/pull/57#discussion_r430505871] > This would remove unused property from documentation of the goal. > * PR 279 - Use skip field in :list-classes - based on > [https://github.com/apache/maven-dependency-plugin/pull/57#discussion_r430520501] > This would skip the execution as documentation suggests. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDEP-842) :list-classes does not skip if skip is set
[ https://issues.apache.org/jira/browse/MDEP-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Zygielo updated MDEP-842: --- Description: I propose two ways to solve this * PR 280 - Remove unused skip field - based on [https://github.com/apache/maven-dependency-plugin/pull/57#discussion_r430505871] This would remove unused property from documentation of the goal. * PR 279 - Use skip field in :list-classes - based on [https://github.com/apache/maven-dependency-plugin/pull/57#discussion_r430520501] This would skip the execution as described by documentation suggests. > :list-classes does not skip if skip is set > -- > > Key: MDEP-842 > URL: https://issues.apache.org/jira/browse/MDEP-842 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: list-classes >Reporter: Piotr Zygielo >Priority: Minor > > I propose two ways to solve this > * PR 280 - Remove unused skip field - based on > [https://github.com/apache/maven-dependency-plugin/pull/57#discussion_r430505871] > This would remove unused property from documentation of the goal. > * PR 279 - Use skip field in :list-classes - based on > [https://github.com/apache/maven-dependency-plugin/pull/57#discussion_r430520501] > This would skip the execution as described by documentation suggests. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDEP-842) :list-classes does not skip if skip is set
[ https://issues.apache.org/jira/browse/MDEP-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Zygielo updated MDEP-842: --- Summary: :list-classes does not skip if skip is set (was: skip) > :list-classes does not skip if skip is set > -- > > Key: MDEP-842 > URL: https://issues.apache.org/jira/browse/MDEP-842 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: list-classes >Reporter: Piotr Zygielo >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDEP-842) skip
[ https://issues.apache.org/jira/browse/MDEP-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Zygielo updated MDEP-842: --- Component/s: list-classes > skip > > > Key: MDEP-842 > URL: https://issues.apache.org/jira/browse/MDEP-842 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: list-classes >Reporter: Piotr Zygielo >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MDEP-842) skip
Piotr Zygielo created MDEP-842: -- Summary: skip Key: MDEP-842 URL: https://issues.apache.org/jira/browse/MDEP-842 Project: Maven Dependency Plugin Issue Type: Bug Reporter: Piotr Zygielo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MCOMPILER-511) proc:only doesn't work as expected
[
https://issues.apache.org/jira/browse/MCOMPILER-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17651733#comment-17651733
]
Piotr Zygielo commented on MCOMPILER-511:
-
When with given reproducer
{{mvn clean generate-sources}}
is used - no .class is generated (no compilation happens), as then execution
{{id=process}} takes place.
I believe it's the info log that uses "Compiling". But what other verb would be
more appropriate? javacing?
With {{clean compile}} - the second :compile (the first is bound to
generare-sources) DOES compile. As expected.
IMO - all is fine with the plugin, and this issue is either invalid or should
be changed to improvement to change the log message, if that is possible at all.
> proc:only doesn't work as expected
> --
>
> Key: MCOMPILER-511
> URL: https://issues.apache.org/jira/browse/MCOMPILER-511
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.10.1
> Environment: Windows, Tested with JDK 1.8, 11, 17
>Reporter: Stefan Röck
>Priority: Major
>
> According to the docs
> [https://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#proc,]
> *proc:only* should only process annotation processors but *not* trigger
> compilation. However, files are always compiled with the following config:
> {code}
>
> org.apache.maven.plugins
> maven-compiler-plugin
> 3.10.1
>
>
> process
> generate-sources
>
> compile
>
>
>
>
> org.immutables.processor.ProxyProcessor
>
> only
>
>
>
>
> {code}
> See small reproducer repo at https://github.com/stefanroeck/annotationtest
> In the logs I can see that the prop is passed through, but still 2 classes
> are compiled:
> {code}
> 21:12:25,407 [DEBUG] -d C:\dev\IdeaProjects\annotationtest\target\classes
> -classpath
> C:\dev\IdeaProjects\annotationtest\target\classes;C:\Dev\.m2\repository\org\immutables\value\2.8.8\value-2.8.8.jar;
> -sourcepath
> C:\dev\IdeaProjects\annotationtest\src\main\java;C:\dev\IdeaProjects\annotationtest\target\generated-sources\annotations;
> -s C:\dev\IdeaProjects\annotationtest\target\generated-sources\annotations
> -proc:only -processor org.immutables.processor.ProxyProcessor -g -nowarn
> -target 17 -source 17 -encoding UTF-8
> 21:12:25,412 [DEBUG] incrementalBuildHelper#beforeRebuildExecution
> 21:12:25,412 [INFO] Compiling 2 source files to
> C:\dev\IdeaProjects\annotationtest\target\classes
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MCOMPILER-513) Error cross-compiling (JDK 18+ to release 17-) source with lint warnings
[
https://issues.apache.org/jira/browse/MCOMPILER-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17650988#comment-17650988
]
Piotr Zygielo commented on MCOMPILER-513:
-
May I ask to have it assigned to release (probably
[https://issues.apache.org/jira/projects/MCOMPILER/versions/12351444)] and
closed, please?
> Error cross-compiling (JDK 18+ to release 17-) source with lint warnings
>
>
> Key: MCOMPILER-513
> URL: https://issues.apache.org/jira/browse/MCOMPILER-513
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.10.1
>Reporter: Piotr Zygielo
>Priority: Major
>
> {code:java}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2.865 s
> [INFO] Finished at: 2022-11-30T16:32:53Z
> [INFO]
>
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.10.1:compile
> (default-compile) on project mcp-OOS-bad-class: Fatal error compiling: bad
> class file: /BCDEFGH/java.base/java/io/ObjectOutputStream.sig
> Error: unable to access file: java.nio.file.ClosedFileSystemException
> {code}
> This sounds a bit like MCOMPILER-450 (for the
> {{{}ClosedFileSystemException{}}}), but there is no reproducer there so it's
> hard to tell. The comment suggests to me that it's not related, b/c the bug
> described here needs no modules.
> Reproducer for the case: [https://github.com/pzrep/mcp-OOS-bad-class]
> The key change, that _fixes_ this is
> [https://github.com/codehaus-plexus/plexus-compiler/pull/204].
> PC in MCOMPILER was updated in
> - [https://github.com/apache/maven-compiler-plugin/pull/122]
> - [https://github.com/apache/maven-compiler-plugin/pull/139]
> but with no JIRA reference. PR 122 can be selected as _fixed in_ then.
> Yes, it's fixed already, but I'm reporting this for inclusion in RN.
> Workaround until new MCOMPILER release: override plexus-compiler dependencies
> to at least 2.12.0.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MNG-7645) Implement some toStrings
Piotr Zygielo created MNG-7645:
--
Summary: Implement some toStrings
Key: MNG-7645
URL: https://issues.apache.org/jira/browse/MNG-7645
Project: Maven
Issue Type: Improvement
Affects Versions: 3.8.6
Reporter: Piotr Zygielo
If something decides to dump some build/session details, like
`maven-bundle-plugin` with `--debug` does, currently it produces:
{noformat}
[DEBUG] BND Instructions:
project.build.mailingLists=[org.apache.maven.model.MailingList@16e91d6f,
org.apache.maven.model.MailingList@57104caa]
project.licenses=[org.apache.maven.model.License@416855dc,
org.apache.maven.model.License@1f342afb]
project.build.scm=org.apache.maven.model.Scm@5d4369c5{noformat}
I propose to change that to something more friendly by overriding toString.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MCOMPILER-513) Error cross-compiling (JDK 18+ to release 17-) source with lint warnings
Piotr Zygielo created MCOMPILER-513:
---
Summary: Error cross-compiling (JDK 18+ to release 17-) source
with lint warnings
Key: MCOMPILER-513
URL: https://issues.apache.org/jira/browse/MCOMPILER-513
Project: Maven Compiler Plugin
Issue Type: Bug
Affects Versions: 3.10.1
Reporter: Piotr Zygielo
{code:java}
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2.865 s
[INFO] Finished at: 2022-11-30T16:32:53Z
[INFO]
Error: Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.10.1:compile (default-compile)
on project mcp-OOS-bad-class: Fatal error compiling: bad class file:
/BCDEFGH/java.base/java/io/ObjectOutputStream.sig
Error: unable to access file: java.nio.file.ClosedFileSystemException
{code}
This sounds a bit like MCOMPILER-450 (for the
{{{}ClosedFileSystemException{}}}), but there is no reproducer there so it's
hard to tell. The comment suggests to me that it's not related, b/c the bug
described here needs no modules.
Reproducer for the case: [https://github.com/pzrep/mcp-OOS-bad-class]
The key change, that _fixes_ this is
[https://github.com/codehaus-plexus/plexus-compiler/pull/204].
PC in MCOMPILER was updated in
- [https://github.com/apache/maven-compiler-plugin/pull/122]
- [https://github.com/apache/maven-compiler-plugin/pull/139]
but with no JIRA reference. PR 122 can be selected as _fixed in_ then.
Yes, it's fixed already, but I'm reporting this for inclusion in RN.
Workaround until new MCOMPILER release: override plexus-compiler dependencies
to at least 2.12.0.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MINSTALL-186) install-file fails when the file belongs to the local repository and using a localRepositoryPath
[
https://issues.apache.org/jira/browse/MINSTALL-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638740#comment-17638740
]
Piotr Zygielo commented on MINSTALL-186:
> I have updated the steps to reproduce, hoping it is more understandable.
Thanks - I'm getting the same error now.
> install-file fails when the file belongs to the local repository and using a
> localRepositoryPath
>
>
> Key: MINSTALL-186
> URL: https://issues.apache.org/jira/browse/MINSTALL-186
> Project: Maven Install Plugin
> Issue Type: Bug
> Components: install:install-file
>Affects Versions: 3.0.1, 3.1.0
>Reporter: Romain Bioteau
>Priority: Trivial
>
> To reproduce:
> Assuming maven-deploy-plugin 3.0.0 EXISTS in your local repository:
> {code:bash}
> ❯ mvn org.apache.maven.plugins:maven-install-plugin:3.1.0:install-file
> -Dfile=$HOME/.m2/repository/org/apache/maven/plugins/maven-deploy-plugin/3.0.0/maven-deploy-plugin-3.0.0.jar
> -DlocalRepositoryPath=/tmp/repo -Dversion=3.0.0
> -DartifactId=maven-deploy-plugin -DgroupId=org.apache.maven.plugins -Dtype=jar
> [INFO] Scanning for projects...
> [INFO]
> [INFO] --< org.apache.maven:standalone-pom
> >---
> [INFO] Building Maven Stub Project (No POM) 1
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- maven-install-plugin:3.1.0:install-file (default-cli) @
> standalone-pom ---
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.164 s
> [INFO] Finished at: 2022-11-25T19:12:32+01:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:3.1.0:install-file
> (default-cli) on project standalone-pom: Cannot install artifact. Artifact is
> already in the local repository.
> [ERROR]
> [ERROR] File in question is:
> /home/romain/.m2/repository/org/apache/maven/plugins/maven-deploy-plugin/3.0.0/maven-deploy-plugin-3.0.0.jar
> [ERROR]
> [ERROR] -> [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
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MINSTALL-186) install-file fails when the file belongs to the local repository and using a localRepositoryPath
[
https://issues.apache.org/jira/browse/MINSTALL-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638693#comment-17638693
]
Piotr Zygielo commented on MINSTALL-186:
If not specified, plugin complains that they are missing. You shared no pom to
start with, so I used no-pom.
Update reproduction steps.
> install-file fails when the file belongs to the local repository and using a
> localRepositoryPath
>
>
> Key: MINSTALL-186
> URL: https://issues.apache.org/jira/browse/MINSTALL-186
> Project: Maven Install Plugin
> Issue Type: Bug
> Components: install:install-file
>Affects Versions: 3.0.1, 3.1.0
>Reporter: Romain Bioteau
>Priority: Trivial
>
> To reproduce:
> {code:bash}
> mvn install:install-file
> -Dfile=/org/apache/test/1.0.0/test/test-1.0.0.jar
> -DlocalRepositoryPath=target/repo/path
> {code}
> Fails with with an error message like:
> {noformat}
> org.apache.maven.plugin.MojoFailureException: Cannot install artifact.
> Artifact is already in the local repository.
> File in question is:
> /home/romain/git/maven-install-plugin/target/test-classes/unit/install-file-from-local-repository-test/target/org/apache/maven/test/maven-install-test/1.0-SNAPSHOT/maven-install-test-1.0-SNAPSHOT.jar
> at
> org.apache.maven.plugins.install.InstallFileMojo.execute(InstallFileMojo.java:250)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MINSTALL-186) install-file fails when the file belongs to the local repository and using a localRepositoryPath
[
https://issues.apache.org/jira/browse/MINSTALL-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638689#comment-17638689
]
Piotr Zygielo commented on MINSTALL-186:
Using maven 3.8.6, I can't reproduce this
{code:java}
$ mvn org.apache.maven.plugins:maven-install-plugin:3.1.0:install-file
-Dfile=$HOME/.m2/repository/org/apache/maven/plugins/maven-deploy-plugin/3.0.0/maven-deploy-plugin-3.0.0.jar
-DlocalRepositoryPath=/tmp/repo -DgroupId=org.apache -DartifactId=test
-Dpackaging=jar -Dversion=1.0{code}
always completes with success:
{code:java}
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.apache.maven:standalone-pom >---
[INFO] Building Maven Stub Project (No POM) 1
[INFO] [ pom ]-
[INFO]
[INFO] --- maven-install-plugin:3.1.0:install-file (default-cli) @
standalone-pom ---
[INFO] Installing
.../.m2/repository/org/apache/maven/plugins/maven-deploy-plugin/3.0.0/maven-deploy-plugin-3.0.0.jar
to /tmp/repo/org/apache/test/1.0/test-1.0.jar
[INFO] Installing /tmp/maven-deploy-plugin-3.0.010112682731321406765.pom to
/tmp/repo/org/apache/test/1.0/test-1.0.pom
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 0.524 s
[INFO] Finished at: 2022-11-25T17:04:19+01:00
[INFO]
{code}
> install-file fails when the file belongs to the local repository and using a
> localRepositoryPath
>
>
> Key: MINSTALL-186
> URL: https://issues.apache.org/jira/browse/MINSTALL-186
> Project: Maven Install Plugin
> Issue Type: Bug
> Components: install:install-file
>Affects Versions: 3.0.1, 3.1.0
>Reporter: Romain Bioteau
>Priority: Trivial
>
> To reproduce:
> {code:bash}
> mvn install:install-file
> -Dfile=/org/apache/test/1.0.0/test/test-1.0.0.jar
> -DlocalRepositoryPath=target/repo/path
> {code}
> Fails with with an error message like:
> {noformat}
> org.apache.maven.plugin.MojoFailureException: Cannot install artifact.
> Artifact is already in the local repository.
> File in question is:
> /home/romain/git/maven-install-plugin/target/test-classes/unit/install-file-from-local-repository-test/target/org/apache/maven/test/maven-install-test/1.0-SNAPSHOT/maven-install-test-1.0-SNAPSHOT.jar
> at
> org.apache.maven.plugins.install.InstallFileMojo.execute(InstallFileMojo.java:250)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MDEP-674) maven-dependency-plugin goals should define m2e metadata
[ https://issues.apache.org/jira/browse/MDEP-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637170#comment-17637170 ] Piotr Zygielo commented on MDEP-674: Could the title be updated, please? > maven-dependency-plugin goals should define m2e metadata > > > Key: MDEP-674 > URL: https://issues.apache.org/jira/browse/MDEP-674 > Project: Maven Dependency Plugin > Issue Type: Improvement > Components: copy >Reporter: Mickael Istria >Assignee: Konrad Windszus >Priority: Minor > Fix For: 3.4.0 > > > I often use the maven-dependency-plugon:copy goal for packaging purpose. > However, Eclipse m2e complains that "plugin execution isn't covered...". > This could be improved by adding just m2e lifecycle mapping metadata and > leveraging the BuildContext API: > https://www.eclipse.org/m2e/documentation/m2e-making-maven-plugins-compat.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7593) Lack of old versions of org.jruby:jruby-core package in the maven index.
[ https://issues.apache.org/jira/browse/MNG-7593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17629893#comment-17629893 ] Piotr Zygielo commented on MNG-7593: This is wrong place to report this, use this [https://issues.sonatype.org/] instead. > Lack of old versions of org.jruby:jruby-core package in the maven index. > > > Key: MNG-7593 > URL: https://issues.apache.org/jira/browse/MNG-7593 > Project: Maven > Issue Type: Bug >Reporter: Kate Donk >Priority: Minor > Attachments: 3BDDA2CA-335A-4CD9-ADFF-0F51EEFDF181.jpeg > > > Hello, I didn't find where else can I get an answer about this issue. > While working with the [Maven index|[https://repo1.maven.org/] ] to get the > list of all available versions of the Maven package: "org.jruby:jruby-core", > for some reason there are a lot of old version numbers that are missing > [here|[https://repo1.maven.org/maven2/org/jruby/jruby-core/maven-metadata.xml]] > > There are much more versions that were before 1.6.0.RC3, is this data is > missing on purpose? Or maybe I'm getting something wrong. > I noticed that something isn't right because in OSV vulnerability DB this > package had much smaller version as the fixed version for some CVE. I > attached a screenshot. > Thanks in advance, Kate. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPH-191) help:evaluate fails on Java 18 - java.util.Hashtable.table not accessible
[
https://issues.apache.org/jira/browse/MPH-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626015#comment-17626015
]
Piotr Zygielo commented on MPH-191:
---
help:evaluate works for me with JDK18:
{noformat}
$ mvn -V org.apache.maven.plugins:maven-help-plugin:3.3.0:evaluate
-Dexpression=project.properties -N
Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Maven home: /usr/local/maven
Java version: 18.0.1.1, vendor: Oracle Corporation, runtime:
/usr/local/jdk-18.0.1.1
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "5.19.16-100.fc35.x86_64", arch: "amd64", family:
"unix"
[INFO] Scanning for projects...
[INFO]
[INFO] -< org.apache.maven.plugins:maven-help-plugin >-
[INFO] Building Apache Maven Help Plugin 3.3.1-SNAPSHOT
[INFO] [ maven-plugin ]
[INFO]
[INFO] --- maven-help-plugin:3.3.0:evaluate (default-cli) @ maven-help-plugin
---
[INFO] No artifact parameter specified, using
'org.apache.maven.plugins:maven-help-plugin:maven-plugin:3.3.1-SNAPSHOT' as
project.
[INFO]
posix
RedundantThrows,NewlineAtEndOfFile,ParameterNumber,MethodLength,FileLength
Apache Development Snapshot
Repository
https://repository.apache.org/content/repositories/snapshots
1.11.1
true
8
false
1.8
1.8
true
3.6.4
.../maven-sites
plugins-archives/maven-help-plugin-LATEST
3.6.4
3.2.5
1.8
3.2.5
https://www.apache.org/images/asf_logo_wide_2016.png
2022-08-14T12:24:27Z
UTF-8
UTF-8
0.3.5
https://builds.apache.org/analysis/
source-release
plain
3.0.0-M7
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 2.272 s
[INFO] Finished at: 2022-10-29T09:03:08+02:00
[INFO]
{noformat}
> help:evaluate fails on Java 18 - java.util.Hashtable.table not accessible
> -
>
> Key: MPH-191
> URL: https://issues.apache.org/jira/browse/MPH-191
> Project: Maven Help Plugin
> Issue Type: Bug
> Components: evaluate
>Affects Versions: 3.3.0
>Reporter: Ondrej Zizka
>Priority: Minor
>
> When running help:evaluate:
> {noformat}
> com.thoughtworks.xstream.converters.reflection.ReflectionConverter[ERROR]
> message[2] : Unable to make field private transient
> java.util.Hashtable$Entry[] java.util.Hashtable.table accessible: module
> java.base does not "opens java.util" to unnamed module @4fc3529
> {noformat}
> {noformat}
> $ $MVN $MVN_OPTS help:system help:effective-settings help:effective-pom
> dependency:tree help:evaluate -Dexpression=project.properties -q
> -DforceStdout[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-help-plugin:3.3.0:evaluate (default-cli) on
> project tracker-service-app: Execution default-cli of goal
> org.apache.maven.plugins:maven-help-plugin:3.3.0:evaluate failed: No
> converter available[ERROR] Debugging information [ERROR] message
> : No converter available[ERROR] type:
> org.apache.maven.plugins.help.AbstractEffectiveMojo$SortedProperties[ERROR]
> converter :
> com.thoughtworks.xstream.converters.reflection.SerializableConverter[ERROR]
> message[1] : Unable to make private void
> java.util.Hashtable.readObject(java.io.ObjectInputStream) throws
> java.io.IOException,java.lang.ClassNotFoundException accessible: module
> java.base does not "opens java.util" to unnamed module @4fc3529[ERROR]
> converter[1]:
> com.thoughtworks.xstream.converters.reflection.ReflectionConverter[ERROR]
> message[2] : Unable to make field private transient
> java.util.Hashtable$Entry[] java.util.Hashtable.table accessible: module
> java.base does not "opens java.util" to unnamed module @4fc3529{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MEAR-322) Module repackaged as invalid archive
[
https://issues.apache.org/jira/browse/MEAR-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Zygielo updated MEAR-322:
---
Description:
After m-ear-p upgrade from 3.2.0 to 3.3.0, ear produced by plugin contains
invalid entry. That causes jar tool to error with
{quote}java.util.zip.ZipException: only DEFLATED entries can have EXT descriptor
at java.base/java.util.zip.ZipInputStream.readLOC(ZipInputStream.java:313)
at
java.base/java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:125)
at jdk.jartool/sun.tools.jar.Main.extract(Main.java:1360)
at jdk.jartool/sun.tools.jar.Main.run(Main.java:409)
at jdk.jartool/sun.tools.jar.Main.main(Main.java:1680)
{quote}
Seems to be connected to setting {{archive/compress=false}} in the original jar
project (original project - valid at its origin, becomes invalid part of ear).
07a84983809b4ec416b1330412bbd83844a88a44 is the first bad commit
Reproducer: [https://github.com/pzrep/MEAR-322]
and its failure: [https://github.com/pzrep/MEAR-322/actions/runs/3306348660]
was:
After m-ear-p upgrade from 3.2.0 to 3.3.0, ear produced by plugin contains
invalid entry. That causes jar tool to error with
{quote}java.util.zip.ZipException: only DEFLATED entries can have EXT descriptor
at java.base/java.util.zip.ZipInputStream.readLOC(ZipInputStream.java:313)
at
java.base/java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:125)
at jdk.jartool/sun.tools.jar.Main.extract(Main.java:1360)
at jdk.jartool/sun.tools.jar.Main.run(Main.java:409)
at jdk.jartool/sun.tools.jar.Main.main(Main.java:1680)
{quote}
Seems to be connected to setting {{archive/compress=false}} in the original jar
project (original project - valid at its origin, becomes invalid part of ear).
This happens for original project with {{packaging=clojure}} in my case.
07a84983809b4ec416b1330412bbd83844a88a44 is the first bad commit
Reproducer: [https://github.com/pzrep/MEAR-322]
and its failure: [https://github.com/pzrep/MEAR-322/actions/runs/3306348660]
> Module repackaged as invalid archive
>
>
> Key: MEAR-322
> URL: https://issues.apache.org/jira/browse/MEAR-322
> Project: Maven EAR Plugin
> Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Piotr Zygielo
>Priority: Major
> Fix For: more-investigation
>
>
> After m-ear-p upgrade from 3.2.0 to 3.3.0, ear produced by plugin contains
> invalid entry. That causes jar tool to error with
> {quote}java.util.zip.ZipException: only DEFLATED entries can have EXT
> descriptor
> at java.base/java.util.zip.ZipInputStream.readLOC(ZipInputStream.java:313)
> at
> java.base/java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:125)
> at jdk.jartool/sun.tools.jar.Main.extract(Main.java:1360)
> at jdk.jartool/sun.tools.jar.Main.run(Main.java:409)
> at jdk.jartool/sun.tools.jar.Main.main(Main.java:1680)
> {quote}
> Seems to be connected to setting {{archive/compress=false}} in the original
> jar project (original project - valid at its origin, becomes invalid part of
> ear).
> 07a84983809b4ec416b1330412bbd83844a88a44 is the first bad commit
>
>
> Reproducer: [https://github.com/pzrep/MEAR-322]
> and its failure: [https://github.com/pzrep/MEAR-322/actions/runs/3306348660]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MEAR-322) Module repackaged as invalid archive
[
https://issues.apache.org/jira/browse/MEAR-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17622785#comment-17622785
]
Piotr Zygielo commented on MEAR-322:
Thanks for checking more JDKs and providing links.
I confirm that compressing original module solves the problem, and using JDK 8
or 19 also helps.
Please close this issue, as I have no power to do so and I accept proposed
workarounds.
> Module repackaged as invalid archive
>
>
> Key: MEAR-322
> URL: https://issues.apache.org/jira/browse/MEAR-322
> Project: Maven EAR Plugin
> Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Piotr Zygielo
>Priority: Major
> Fix For: more-investigation
>
>
> After m-ear-p upgrade from 3.2.0 to 3.3.0, ear produced by plugin contains
> invalid entry. That causes jar tool to error with
> {quote}java.util.zip.ZipException: only DEFLATED entries can have EXT
> descriptor
> at java.base/java.util.zip.ZipInputStream.readLOC(ZipInputStream.java:313)
> at
> java.base/java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:125)
> at jdk.jartool/sun.tools.jar.Main.extract(Main.java:1360)
> at jdk.jartool/sun.tools.jar.Main.run(Main.java:409)
> at jdk.jartool/sun.tools.jar.Main.main(Main.java:1680)
> {quote}
> Seems to be connected to setting {{archive/compress=false}} in the original
> jar project (original project - valid at its origin, becomes invalid part of
> ear).
> This happens for original project with {{packaging=clojure}} in my case.
> 07a84983809b4ec416b1330412bbd83844a88a44 is the first bad commit
>
>
> Reproducer: [https://github.com/pzrep/MEAR-322]
> and its failure: [https://github.com/pzrep/MEAR-322/actions/runs/3306348660]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MEAR-322) Module repackaged as invalid archive
[
https://issues.apache.org/jira/browse/MEAR-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Zygielo updated MEAR-322:
---
Description:
After m-ear-p upgrade from 3.2.0 to 3.3.0, ear produced by plugin contains
invalid entry. That causes jar tool to error with
{quote}java.util.zip.ZipException: only DEFLATED entries can have EXT descriptor
at java.base/java.util.zip.ZipInputStream.readLOC(ZipInputStream.java:313)
at
java.base/java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:125)
at jdk.jartool/sun.tools.jar.Main.extract(Main.java:1360)
at jdk.jartool/sun.tools.jar.Main.run(Main.java:409)
at jdk.jartool/sun.tools.jar.Main.main(Main.java:1680)
{quote}
Seems to be connected to setting {{archive/compress=false}} in the original jar
project (original project - valid at its origin, becomes invalid part of ear).
This happens for original project with {{packaging=clojure}} in my case.
07a84983809b4ec416b1330412bbd83844a88a44 is the first bad commit
Reproducer: [https://github.com/pzrep/MEAR-322]
and its failure: [https://github.com/pzrep/MEAR-322/actions/runs/3306348660]
was:
After m-ear-p upgrade from 3.2.0 to 3.3.0, ear produced by plugin contains
invalid entry. That causes jar tool to error with
{quote}java.util.zip.ZipException: only DEFLATED entries can have EXT descriptor
at java.base/java.util.zip.ZipInputStream.readLOC(ZipInputStream.java:313)
at
java.base/java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:125)
at jdk.jartool/sun.tools.jar.Main.extract(Main.java:1360)
at jdk.jartool/sun.tools.jar.Main.run(Main.java:409)
at jdk.jartool/sun.tools.jar.Main.main(Main.java:1680){quote}
Seems to be connected to setting {{archive/compress=false}} in the original jar
project (original project - valid at its origin, becomes invalid part of ear).
This happens for original project with {{packaging=clojure}} in my case.
07a84983809b4ec416b1330412bbd83844a88a44 is the first bad commit
> Module repackaged as invalid archive
>
>
> Key: MEAR-322
> URL: https://issues.apache.org/jira/browse/MEAR-322
> Project: Maven EAR Plugin
> Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Piotr Zygielo
>Priority: Major
>
> After m-ear-p upgrade from 3.2.0 to 3.3.0, ear produced by plugin contains
> invalid entry. That causes jar tool to error with
> {quote}java.util.zip.ZipException: only DEFLATED entries can have EXT
> descriptor
> at java.base/java.util.zip.ZipInputStream.readLOC(ZipInputStream.java:313)
> at
> java.base/java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:125)
> at jdk.jartool/sun.tools.jar.Main.extract(Main.java:1360)
> at jdk.jartool/sun.tools.jar.Main.run(Main.java:409)
> at jdk.jartool/sun.tools.jar.Main.main(Main.java:1680)
> {quote}
> Seems to be connected to setting {{archive/compress=false}} in the original
> jar project (original project - valid at its origin, becomes invalid part of
> ear).
> This happens for original project with {{packaging=clojure}} in my case.
> 07a84983809b4ec416b1330412bbd83844a88a44 is the first bad commit
>
>
> Reproducer: [https://github.com/pzrep/MEAR-322]
> and its failure: [https://github.com/pzrep/MEAR-322/actions/runs/3306348660]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MEAR-322) Module repackaged as invalid archive
[
https://issues.apache.org/jira/browse/MEAR-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Zygielo updated MEAR-322:
---
Description:
After m-ear-p upgrade from 3.2.0 to 3.3.0, ear produced by plugin contains
invalid entry. That causes jar tool to error with
{quote}java.util.zip.ZipException: only DEFLATED entries can have EXT descriptor
at java.base/java.util.zip.ZipInputStream.readLOC(ZipInputStream.java:313)
at
java.base/java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:125)
at jdk.jartool/sun.tools.jar.Main.extract(Main.java:1360)
at jdk.jartool/sun.tools.jar.Main.run(Main.java:409)
at jdk.jartool/sun.tools.jar.Main.main(Main.java:1680){quote}
Seems to be connected to setting {{archive/compress=false}} in the original jar
project (original project - valid at its origin, becomes invalid part of ear).
This happens for original project with {{packaging=clojure}} in my case.
07a84983809b4ec416b1330412bbd83844a88a44 is the first bad commit
was:
After m-ear-p upgrade from 3.2.0 to 3.3.0, this
{quote}Exception while deploying the app: java.util.zip.ZipException: only
DEFLATED entries can have EXT descriptor
{quote}
is reported when deployed to Payara 5.2022.3.
At this moment I'm not sure if this is fault of plugin, payara or the project.
But the plugin upgrade is the only change done.
Seems to be connected to setting {{archive/compress=false}} in the ear (or
module) project.
07a84983809b4ec416b1330412bbd83844a88a44 is the first bad commit
> Module repackaged as invalid archive
>
>
> Key: MEAR-322
> URL: https://issues.apache.org/jira/browse/MEAR-322
> Project: Maven EAR Plugin
> Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Piotr Zygielo
>Priority: Major
>
> After m-ear-p upgrade from 3.2.0 to 3.3.0, ear produced by plugin contains
> invalid entry. That causes jar tool to error with
> {quote}java.util.zip.ZipException: only DEFLATED entries can have EXT
> descriptor
> at java.base/java.util.zip.ZipInputStream.readLOC(ZipInputStream.java:313)
> at
> java.base/java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:125)
> at jdk.jartool/sun.tools.jar.Main.extract(Main.java:1360)
> at jdk.jartool/sun.tools.jar.Main.run(Main.java:409)
> at jdk.jartool/sun.tools.jar.Main.main(Main.java:1680){quote}
> Seems to be connected to setting {{archive/compress=false}} in the original
> jar project (original project - valid at its origin, becomes invalid part of
> ear).
> This happens for original project with {{packaging=clojure}} in my case.
> 07a84983809b4ec416b1330412bbd83844a88a44 is the first bad commit
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MEAR-322) Module repackaged as invalid archive
[
https://issues.apache.org/jira/browse/MEAR-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Zygielo updated MEAR-322:
---
Summary: Module repackaged as invalid archive (was: Exception while
deploying the app: java.util.zip.ZipException: only DEFLATED entries can have
EXT descriptor)
> Module repackaged as invalid archive
>
>
> Key: MEAR-322
> URL: https://issues.apache.org/jira/browse/MEAR-322
> Project: Maven EAR Plugin
> Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Piotr Zygielo
>Priority: Major
>
> After m-ear-p upgrade from 3.2.0 to 3.3.0, this
> {quote}Exception while deploying the app: java.util.zip.ZipException: only
> DEFLATED entries can have EXT descriptor
> {quote}
> is reported when deployed to Payara 5.2022.3.
> At this moment I'm not sure if this is fault of plugin, payara or the
> project. But the plugin upgrade is the only change done.
> Seems to be connected to setting {{archive/compress=false}} in the ear (or
> module) project.
>
> 07a84983809b4ec416b1330412bbd83844a88a44 is the first bad commit
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MEAR-322) Exception while deploying the app: java.util.zip.ZipException: only DEFLATED entries can have EXT descriptor
[
https://issues.apache.org/jira/browse/MEAR-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Zygielo updated MEAR-322:
---
Description:
After m-ear-p upgrade from 3.2.0 to 3.3.0, this
{quote}Exception while deploying the app: java.util.zip.ZipException: only
DEFLATED entries can have EXT descriptor
{quote}
is reported when deployed to Payara 5.2022.3.
At this moment I'm not sure if this is fault of plugin, payara or the project.
But the plugin upgrade is the only change done.
Seems to be connected to setting {{archive/compress=false}} in the ear (or
module) project.
07a84983809b4ec416b1330412bbd83844a88a44 is the first bad commit
was:
After m-ear-p upgrade from 3.2.0 to 3.3.0, this
{quote}Exception while deploying the app: java.util.zip.ZipException: only
DEFLATED entries can have EXT descriptor
{quote}
is reported when deployed to Payara 5.2022.3.
At this moment I'm not sure if this is fault of plugin, payara or the project.
But the plugin upgrade is the only change done.
Seems to be connected to setting {{archive/compress=false}} in the ear (or
module) project.
> Exception while deploying the app: java.util.zip.ZipException: only DEFLATED
> entries can have EXT descriptor
>
>
> Key: MEAR-322
> URL: https://issues.apache.org/jira/browse/MEAR-322
> Project: Maven EAR Plugin
> Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Piotr Zygielo
>Priority: Major
>
> After m-ear-p upgrade from 3.2.0 to 3.3.0, this
> {quote}Exception while deploying the app: java.util.zip.ZipException: only
> DEFLATED entries can have EXT descriptor
> {quote}
> is reported when deployed to Payara 5.2022.3.
> At this moment I'm not sure if this is fault of plugin, payara or the
> project. But the plugin upgrade is the only change done.
> Seems to be connected to setting {{archive/compress=false}} in the ear (or
> module) project.
>
> 07a84983809b4ec416b1330412bbd83844a88a44 is the first bad commit
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MEAR-322) Exception while deploying the app: java.util.zip.ZipException: only DEFLATED entries can have EXT descriptor
[
https://issues.apache.org/jira/browse/MEAR-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Zygielo updated MEAR-322:
---
Description:
After m-ear-p upgrade from 3.2.0 to 3.3.0, this
{quote}Exception while deploying the app: java.util.zip.ZipException: only
DEFLATED entries can have EXT descriptor
{quote}
is reported when deployed to Payara 5.2022.3.
At this moment I'm not sure if this is fault of plugin, payara or the project.
But the plugin upgrade is the only change done.
Seems to be connected to setting {{archive/compress=false}} in the ear (or
module) project.
was:
After m-ear-p upgrade from 3.2.0 to 3.3.0, this
bq. Exception while deploying the app: java.util.zip.ZipException: only
DEFLATED entries can have EXT descriptor
is reported when deployed to Payara 5.2022.3.
At this moment I'm not sure if this is fault of plugin, payara or the project.
But the plugin upgrade is the only change done.
> Exception while deploying the app: java.util.zip.ZipException: only DEFLATED
> entries can have EXT descriptor
>
>
> Key: MEAR-322
> URL: https://issues.apache.org/jira/browse/MEAR-322
> Project: Maven EAR Plugin
> Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Piotr Zygielo
>Priority: Major
>
> After m-ear-p upgrade from 3.2.0 to 3.3.0, this
> {quote}Exception while deploying the app: java.util.zip.ZipException: only
> DEFLATED entries can have EXT descriptor
> {quote}
> is reported when deployed to Payara 5.2022.3.
> At this moment I'm not sure if this is fault of plugin, payara or the
> project. But the plugin upgrade is the only change done.
> Seems to be connected to setting {{archive/compress=false}} in the ear (or
> module) project.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MEAR-322) Exception while deploying the app: java.util.zip.ZipException: only DEFLATED entries can have EXT descriptor
Piotr Zygielo created MEAR-322: -- Summary: Exception while deploying the app: java.util.zip.ZipException: only DEFLATED entries can have EXT descriptor Key: MEAR-322 URL: https://issues.apache.org/jira/browse/MEAR-322 Project: Maven EAR Plugin Issue Type: Bug Affects Versions: 3.3.0 Reporter: Piotr Zygielo After m-ear-p upgrade from 3.2.0 to 3.3.0, this bq. Exception while deploying the app: java.util.zip.ZipException: only DEFLATED entries can have EXT descriptor is reported when deployed to Payara 5.2022.3. At this moment I'm not sure if this is fault of plugin, payara or the project. But the plugin upgrade is the only change done. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-7568) [WARNING] The requested profile "ABCDEF" could not be activated because it does not exist.
[
https://issues.apache.org/jira/browse/MNG-7568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Zygielo updated MNG-7568:
---
Affects Version/s: 3.8.6
> [WARNING] The requested profile "ABCDEF" could not be activated because it
> does not exist.
> --
>
> Key: MNG-7568
> URL: https://issues.apache.org/jira/browse/MNG-7568
> Project: Maven
> Issue Type: Bug
> Components: Core, Profiles
>Affects Versions: 3.8.1, 3.8.6
>Reporter: Piotr Zygielo
>Assignee: Robert Scholte
>Priority: Major
>
> WARNING comes at end of build log if profile is defined in settings.xml (it
> definitely does exist) and even more, I am deactivating it, not activating...
> {code:bash}
> mvn -P!ABCDEF clean test
> {code}
> in fact, profile is deactivated during build so everything goes as expected,
> except misleading message
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MNG-7568) [WARNING] The requested profile "ABCDEF" could not be activated because it does not exist.
Piotr Zygielo created MNG-7568:
--
Summary: [WARNING] The requested profile "ABCDEF" could not be
activated because it does not exist.
Key: MNG-7568
URL: https://issues.apache.org/jira/browse/MNG-7568
Project: Maven
Issue Type: Bug
Components: Core, Profiles
Affects Versions: 3.8.1
Reporter: Piotr Zygielo
Assignee: Robert Scholte
WARNING comes at end of build log if profile is defined in settings.xml (it
definitely does exist) and even more, I am deactivating it, not activating...
{code:bash}
mvn -P!ABCDEF clean test
{code}
in fact, profile is deactivated during build so everything goes as expected,
except misleading message
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MASSEMBLY-941) file permissions removed during assembly:single since 3.2.0
[ https://issues.apache.org/jira/browse/MASSEMBLY-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509731#comment-17509731 ] Piotr Zygielo edited comment on MASSEMBLY-941 at 10/4/22 8:32 AM: -- This seems to be documented/caused here: https://github.com/codehaus-plexus/plexus-archiver/blob/a4a6b0771148b90221f9e02c0fff9299d45e8520/src/main/java/org/codehaus/plexus/archiver/AbstractArchiver.java#L1326 https://github.com/codehaus-plexus/plexus-archiver/commit/98940db17e3e55ee69646a8b46510f6d1ecad800 https://github.com/codehaus-plexus/plexus-archiver/pull/121 https://github.com/codehaus-plexus/plexus-archiver/pull/121#discussion_r331805108: > This can be quite inconvenient if the archive contains executable scripts > (not uncommon for Java applications). https://github.com/codehaus-plexus/plexus-archiver/pull/121#discussion_r334241220: > yes, executable bit is the most wanted one. was (Author: pzygielo): This seems to be documented/caused here: https://github.com/codehaus-plexus/plexus-archiver/blob/a4a6b0771148b90221f9e02c0fff9299d45e8520/src/main/java/org/codehaus/plexus/archiver/AbstractArchiver.java#L1326 https://github.com/codehaus-plexus/plexus-archiver/commit/98940db17e3e55ee69646a8b46510f6d1ecad800 https://github.com/codehaus-plexus/plexus-archiver/pull/121 > file permissions removed during assembly:single since 3.2.0 > --- > > Key: MASSEMBLY-941 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-941 > Project: Maven Assembly Plugin > Issue Type: Bug > Components: permissions >Affects Versions: 3.2.0, 3.3.0 >Reporter: Christopher Tubbs >Priority: Critical > > Since 3.2.0, existing file permissions seem to be ignored when creating a > tarball assembly, and files stored in the assembly do not have their original > file permissions preserved. > Using version 3.1.1 of this plugin and earlier, when creating a tar.gz, > existing file permissions are normally preserved. This is now broken in > 3.2.0, unless the component descriptor explicitly sets the fileModes. > This was discovered trying to prepare a release candidate for Apache Accumulo > using the apache-23.pom parent POM's predefined `source-release-tar` > descriptor using the `single` goal. We noticed that the resulting > source-release tarball had stripped all the executable permissions from our > scripts, instead of preserving them. This makes the resulting source release > more difficult to build from source. > A source-release assembly, and any other assembly that does not specify the > file permissions explicitly, should preserve the existing file permissions, > just as it used to with 3.1.1 and earlier. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7211) [WARNING] The requested profile "ABCDEF" could not be activated because it does not exist.
[
https://issues.apache.org/jira/browse/MNG-7211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612232#comment-17612232
]
Piotr Zygielo commented on MNG-7211:
https://github.com/apache/maven/pull/809
> [WARNING] The requested profile "ABCDEF" could not be activated because it
> does not exist.
> --
>
> Key: MNG-7211
> URL: https://issues.apache.org/jira/browse/MNG-7211
> Project: Maven
> Issue Type: Bug
> Components: Core, Profiles
>Affects Versions: 3.8.1
>Reporter: Miroslav Zaťko
>Assignee: Robert Scholte
>Priority: Major
>
> WARNING comes at end of build log if profile is defined in settings.xml (it
> definitely does exist) and even more, I am deactivating it, not activating...
> {code:bash}
> mvn -P!ABCDEF clean test
> {code}
> in fact, profile is deactivated during build so everything goes as expected,
> except misleading message
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MJAR-286) NullPointerException when includes are empty
[ https://issues.apache.org/jira/browse/MJAR-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17607654#comment-17607654 ] Piotr Zygielo commented on MJAR-286: NPEx is no longer reported with 3.3.0 (since c02be208f3f4422ed0e9990e56602e3ee7d246a0). > NullPointerException when includes are empty > > > Key: MJAR-286 > URL: https://issues.apache.org/jira/browse/MJAR-286 > Project: Maven JAR Plugin > Issue Type: Bug >Affects Versions: 3.1.2, 3.2.2 > Environment: Maven 3.8.4, Windows 10 >Reporter: Markus Dangl >Priority: Major > Attachments: mvn-clean-package.log > > > When includes are empty, but a `src/main/resources` directory exists, maven > fails with a NullPointerException. If this is a misconfigured pom, it should > at least give a proper error message. > > I produced a minimized case here: > [https://github.com/xicesky/bug-in-maven-jar-plugin] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (MASSEMBLY-941) file permissions removed during assembly:single since 3.2.0
[ https://issues.apache.org/jira/browse/MASSEMBLY-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509731#comment-17509731 ] Piotr Zygielo edited comment on MASSEMBLY-941 at 9/16/22 7:08 AM: -- This seems to be documented/caused here: https://github.com/codehaus-plexus/plexus-archiver/blob/a4a6b0771148b90221f9e02c0fff9299d45e8520/src/main/java/org/codehaus/plexus/archiver/AbstractArchiver.java#L1326 was (Author: pzygielo): This seems to be documented/caused here: https://github.com/codehaus-plexus/plexus-archiver/blob/master/src/main/java/org/codehaus/plexus/archiver/AbstractArchiver.java#L1326 > file permissions removed during assembly:single since 3.2.0 > --- > > Key: MASSEMBLY-941 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-941 > Project: Maven Assembly Plugin > Issue Type: Bug > Components: permissions >Affects Versions: 3.2.0, 3.3.0 >Reporter: Christopher Tubbs >Priority: Critical > > Since 3.2.0, existing file permissions seem to be ignored when creating a > tarball assembly, and files stored in the assembly do not have their original > file permissions preserved. > Using version 3.1.1 of this plugin and earlier, when creating a tar.gz, > existing file permissions are normally preserved. This is now broken in > 3.2.0, unless the component descriptor explicitly sets the fileModes. > This was discovered trying to prepare a release candidate for Apache Accumulo > using the apache-23.pom parent POM's predefined `source-release-tar` > descriptor using the `single` goal. We noticed that the resulting > source-release tarball had stripped all the executable permissions from our > scripts, instead of preserving them. This makes the resulting source release > more difficult to build from source. > A source-release assembly, and any other assembly that does not specify the > file permissions explicitly, should preserve the existing file permissions, > just as it used to with 3.1.1 and earlier. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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&focusedCommentId=17584342#comment-17584342
]
Piotr Zygielo commented on MPMD-353:
> Adding jansi 2.4.0 to plugin dependencies has no effect
I observe the same - adding org.fusesource.jansi:jansi:2.4.0 to plugin's
dependencies does not help when building with maven 3.6.3 in my project.
> 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] =
> 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/d
[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&focusedCommentId=17584056#comment-17584056
]
Piotr Zygielo commented on MPMD-353:
Outdated wrapped maven on my side (3.6.3). Works fine with current 3.8.6.
Please close this issue.
> 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] =
> 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/doxi
[jira] [Created] (MPMD-353) An API incompatibility was encountered while executing org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd
Piotr Zygielo created MPMD-353:
--
Summary: 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
{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
