[jira] [Commented] (MDEP-883) Upgrade maven-plugin parent to 40
[ https://issues.apache.org/jira/browse/MDEP-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753331#comment-17753331 ] ASF GitHub Bot commented on MDEP-883: - khmarbaise opened a new pull request, #332: URL: https://github.com/apache/maven-dependency-plugin/pull/332 Following this checklist to help us incorporate your contribution quickly and easily: - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MDEP) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] Format the pull request title like `[MDEP-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MDEP-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [ ] You have run the integration tests successfully (`mvn -Prun-its clean verify`). If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [ ] I hereby declare this contribution to be licensed under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). > Upgrade maven-plugin parent to 40 > - > > Key: MDEP-883 > URL: https://issues.apache.org/jira/browse/MDEP-883 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.6.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-dependency-plugin] khmarbaise opened a new pull request, #332: [MDEP-883] - Upgrade maven-plugin parent to 40
khmarbaise opened a new pull request, #332: URL: https://github.com/apache/maven-dependency-plugin/pull/332 Following this checklist to help us incorporate your contribution quickly and easily: - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MDEP) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] Format the pull request title like `[MDEP-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MDEP-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [ ] You have run the integration tests successfully (`mvn -Prun-its clean verify`). If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [ ] I hereby declare this contribution to be licensed under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (MDEP-883) Upgrade maven-plugin parent to 40
[ https://issues.apache.org/jira/browse/MDEP-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MDEP-883: Assignee: Karl Heinz Marbaise > Upgrade maven-plugin parent to 40 > - > > Key: MDEP-883 > URL: https://issues.apache.org/jira/browse/MDEP-883 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.6.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MDEP-883) Upgrade maven-plugin parent to 40
Karl Heinz Marbaise created MDEP-883: Summary: Upgrade maven-plugin parent to 40 Key: MDEP-883 URL: https://issues.apache.org/jira/browse/MDEP-883 Project: Maven Dependency Plugin Issue Type: Dependency upgrade Affects Versions: 3.6.0 Reporter: Karl Heinz Marbaise Fix For: next-release -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-1273) getFiles/getFileNames do not throw IOException
[ https://issues.apache.org/jira/browse/MSHARED-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753330#comment-17753330 ] ASF GitHub Bot commented on MSHARED-1273: - elharo merged PR #160: URL: https://github.com/apache/maven-shared-utils/pull/160 > getFiles/getFileNames do not throw IOException > -- > > Key: MSHARED-1273 > URL: https://issues.apache.org/jira/browse/MSHARED-1273 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-shared-utils >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-shared-utils] elharo merged pull request #160: [MSHARED-1273] restore IOException
elharo merged PR #160: URL: https://github.com/apache/maven-shared-utils/pull/160 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MSHARED-1289) Deprecate maven-shared-utils
[ https://issues.apache.org/jira/browse/MSHARED-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753329#comment-17753329 ] ASF GitHub Bot commented on MSHARED-1289: - elharo commented on PR #165: URL: https://github.com/apache/maven-shared-utils/pull/165#issuecomment-1675272349 Still a hard no on this one. This needs to be dealt with one piece at a time, not as a single PR that deprecates things that are in use and that we don't have replacements for. Even more importantly, we need to eliminate plexus-utils, not reintroduce it. The foggy ownership and licensing story make it infeasible for Apache projects. > Deprecate maven-shared-utils > > > Key: MSHARED-1289 > URL: https://issues.apache.org/jira/browse/MSHARED-1289 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-shared-utils >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > > As discussed in > https://lists.apache.org/thread/9wkmo1cfq7hx6qwo2xp070rkdz1w5myp this library > never became successor of plexus-utils and therefore is less maintained. > Instead of maintaining two libraries we should deprecated Maven Shared Utils > and recommend using plain JDK API where possible or fall back to either > plexus-utils or other well known third party libraries. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-shared-utils] elharo commented on pull request #165: [MSHARED-1289] Deprecate library
elharo commented on PR #165: URL: https://github.com/apache/maven-shared-utils/pull/165#issuecomment-1675272349 Still a hard no on this one. This needs to be dealt with one piece at a time, not as a single PR that deprecates things that are in use and that we don't have replacements for. Even more importantly, we need to eliminate plexus-utils, not reintroduce it. The foggy ownership and licensing story make it infeasible for Apache projects. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MSHARED-1274) Deprecate the xml bits from maven-shared-utils
[ https://issues.apache.org/jira/browse/MSHARED-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753328#comment-17753328 ] ASF GitHub Bot commented on MSHARED-1274: - elharo merged PR #162: URL: https://github.com/apache/maven-shared-utils/pull/162 > Deprecate the xml bits from maven-shared-utils > -- > > Key: MSHARED-1274 > URL: https://issues.apache.org/jira/browse/MSHARED-1274 > Project: Maven Shared Components > Issue Type: Task > Components: maven-shared-utils >Reporter: Guillaume Nodet >Priority: Major > > The xml bits from plexus-utils are a de-facto part of the maven 3.x api and > we should not have two conflicting versions of it. Now that it has been > extract in a separate project in plexus-xml, I think it is time to deprecate > those classes in maven-shared-utils. Fwiw, the core implementation classes > are mainly implemented with Maven 4.x maven-xml-impl module, and the Xpp3Dom > class from plexus-xml is mainly a wrapper around the new XmlNode/XmlNodeImpl > class from maven, however the parser is still present in plexus-xml. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-shared-utils] elharo merged pull request #162: [MSHARED-1274] Deprecate Xpp3Dom and related classes
elharo merged PR #162: URL: https://github.com/apache/maven-shared-utils/pull/162 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-shared-utils] elharo merged pull request #161: remove vestigial comments
elharo merged PR #161: URL: https://github.com/apache/maven-shared-utils/pull/161 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MSHARED-1273) getFiles/getFileNames do not throw IOException
[ https://issues.apache.org/jira/browse/MSHARED-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753327#comment-17753327 ] ASF GitHub Bot commented on MSHARED-1273: - elharo commented on PR #160: URL: https://github.com/apache/maven-shared-utils/pull/160#issuecomment-1675267806 Because I accidentally deleted this in a previous PR without noticing that it broke the public API. > getFiles/getFileNames do not throw IOException > -- > > Key: MSHARED-1273 > URL: https://issues.apache.org/jira/browse/MSHARED-1273 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-shared-utils >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-shared-utils] elharo commented on pull request #160: [MSHARED-1273] restore IOException
elharo commented on PR #160: URL: https://github.com/apache/maven-shared-utils/pull/160#issuecomment-1675267806 Because I accidentally deleted this in a previous PR without noticing that it broke the public API. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MDEP-832) Remove commons-collections-4
[
https://issues.apache.org/jira/browse/MDEP-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MDEP-832:
-
Fix Version/s: next-release
> Remove commons-collections-4
>
>
> Key: MDEP-832
> URL: https://issues.apache.org/jira/browse/MDEP-832
> Project: Maven Dependency Plugin
> Issue Type: Improvement
>Affects Versions: 3.3.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: next-release
>
>
> Remove the dependency:
> {code:xml}
>
> org.apache.commons
> commons-collections4
> 4.2
>
> {code}
> which is used only for a single method.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MDEP-882) Upgrade plexus-archiver due to CVE-2023-37460
[ https://issues.apache.org/jira/browse/MDEP-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MDEP-882. > Upgrade plexus-archiver due to CVE-2023-37460 > - > > Key: MDEP-882 > URL: https://issues.apache.org/jira/browse/MDEP-882 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.6.0 >Reporter: Bruno Volpato >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: next-release > > > The dependency plexus-archiver 4.7.1 is within the range for > [https://nvd.nist.gov/vuln/detail/CVE-2023-37460], and is critical as it may > be a surface for remote code execution. > > Dependabot opened the pull request for the bump: > [https://github.com/apache/maven-dependency-plugin/pull/330]. > > I'm filing this to bring up that this is critical to merge + trying to > encourage a possible release whenever possible. > > Thank you! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRESOLVER-289) Remove "Aether wiki" link from site
[ https://issues.apache.org/jira/browse/MRESOLVER-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753320#comment-17753320 ] Tamas Cservenak commented on MRESOLVER-289: --- https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan > Remove "Aether wiki" link from site > --- > > Key: MRESOLVER-289 > URL: https://issues.apache.org/jira/browse/MRESOLVER-289 > Project: Maven Resolver > Issue Type: Task > Components: Resolver >Reporter: Tamas Cservenak >Priority: Major > > It points to Eclipe wiki that is defunct. Possibly migrate something from > there, if needed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-dependency-plugin] khmarbaise opened a new pull request, #331: Code Improvements
khmarbaise opened a new pull request, #331: URL: https://github.com/apache/maven-dependency-plugin/pull/331 * using Files.newBufferedWriter(), Files.lines() * using reader.lines().forEach() * Removed inverse logic. * Using StandardCharsets.UTF_8 instead of literal texts. Following this checklist to help us incorporate your contribution quickly and easily: - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MDEP) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] Format the pull request title like `[MDEP-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MDEP-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [ ] You have run the integration tests successfully (`mvn -Prun-its clean verify`). If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [ ] I hereby declare this contribution to be licensed under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MDEP-877) goal unpack: ignores path in includes/excludes
[
https://issues.apache.org/jira/browse/MDEP-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753303#comment-17753303
]
Karl Heinz Marbaise commented on MDEP-877:
--
It would be helpful to have a full working example...
> goal unpack: ignores path in includes/excludes
> --
>
> Key: MDEP-877
> URL: https://issues.apache.org/jira/browse/MDEP-877
> Project: Maven Dependency Plugin
> Issue Type: New Feature
> Components: unpack
>Affects Versions: 3.6.0
>Reporter: Ernst Reissner
>Priority: Major
>
> in my jar i have files
> - .latexmkrc and
> - raw/.latexmkrc
> I want to extract only .latexmkrc
> So I configure:
> ```
>
> eu.simuline.m2latex
> latex-maven-plugin
> ${versionLatexPlugin}
> jar
>
> true
>
> ${latexDir}
> .latexmkrc,
> .chktexrc
>
>
>
>
>
> ```
> But what is extracted is still raw/.latexmkrc.
> Even if i add `raw/.latexmkrc` this does not help.
> I have the impression, the config just ignores all but the file name.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MDEP-878) Unexpected failure in mappers: no empty replacement or extension possible
[
https://issues.apache.org/jira/browse/MDEP-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753302#comment-17753302
]
Karl Heinz Marbaise commented on MDEP-878:
--
It would be helpful if you could provide a full working example...
> Unexpected failure in mappers: no empty replacement or extension possible
> --
>
> Key: MDEP-878
> URL: https://issues.apache.org/jira/browse/MDEP-878
> Project: Maven Dependency Plugin
> Issue Type: New Feature
>Reporter: Ernst Reissner
>Priority: Major
>
> I have the following configuration:
> {code:xml}
>
> eu.simuline.m2latex
> latex-maven-plugin
> ${versionLatexPlugin}
> jar
> true
> src/main/resources
> .latexmkrc.raw
>
>
> c.raw$
> c
>
>
>
> {code}
> As you can see, I tricked.
> i wanted just to replace `.raw` by the empty string.
> This was not possible and I think, an empty replacement is fully valid.
> Also I would have used the `FileExtensionMapper`, but also this does not
> accept an empty extension.
> Analogously I think, this should be allowed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MDEP-878) Unexpected failure in mappers: no empty replacement or extension possible
[
https://issues.apache.org/jira/browse/MDEP-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MDEP-878:
-
Description:
I have the following configuration:
{code:xml}
eu.simuline.m2latex
latex-maven-plugin
${versionLatexPlugin}
jar
true
src/main/resources
.latexmkrc.raw
c.raw$
c
{code}
As you can see, I tricked.
i wanted just to replace `.raw` by the empty string.
This was not possible and I think, an empty replacement is fully valid.
Also I would have used the `FileExtensionMapper`, but also this does not accept
an empty extension.
Analogously I think, this should be allowed.
was:
I have the following configuration:
```
eu.simuline.m2latex
latex-maven-plugin
${versionLatexPlugin}
jar
true
src/main/resources
.latexmkrc.raw
c.raw$
c
```
As you can see, I tricked.
i wanted just to replace `.raw` by the empty string.
This was not possible and I think, an empty replacement is fully valid.
Also I would have used the `FileExtensionMapper`, but also this does not accept
an empty extension.
Analogously I think, this should be allowed.
> Unexpected failure in mappers: no empty replacement or extension possible
> --
>
> Key: MDEP-878
> URL: https://issues.apache.org/jira/browse/MDEP-878
> Project: Maven Dependency Plugin
> Issue Type: New Feature
>Reporter: Ernst Reissner
>Priority: Major
>
> I have the following configuration:
> {code:xml}
>
> eu.simuline.m2latex
> latex-maven-plugin
> ${versionLatexPlugin}
> jar
> true
> src/main/resources
> .latexmkrc.raw
>
>
> c.raw$
> c
>
>
>
> {code}
> As you can see, I tricked.
> i wanted just to replace `.raw` by the empty string.
> This was not possible and I think, an empty replacement is fully valid.
> Also I would have used the `FileExtensionMapper`, but also this does not
> accept an empty extension.
> Analogously I think, this should be allowed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MDEP-882) Upgrade plexus-archiver due to CVE-2023-37460
[ https://issues.apache.org/jira/browse/MDEP-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MDEP-882: - Affects Version/s: 3.6.0 > Upgrade plexus-archiver due to CVE-2023-37460 > - > > Key: MDEP-882 > URL: https://issues.apache.org/jira/browse/MDEP-882 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.6.0 >Reporter: Bruno Volpato >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: next-release > > > The dependency plexus-archiver 4.7.1 is within the range for > [https://nvd.nist.gov/vuln/detail/CVE-2023-37460], and is critical as it may > be a surface for remote code execution. > > Dependabot opened the pull request for the bump: > [https://github.com/apache/maven-dependency-plugin/pull/330]. > > I'm filing this to bring up that this is critical to merge + trying to > encourage a possible release whenever possible. > > Thank you! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDEP-882) Upgrade plexus-archiver due to CVE-2023-37460
[ https://issues.apache.org/jira/browse/MDEP-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MDEP-882: - Fix Version/s: next-release > Upgrade plexus-archiver due to CVE-2023-37460 > - > > Key: MDEP-882 > URL: https://issues.apache.org/jira/browse/MDEP-882 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Bruno Volpato >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: next-release > > > The dependency plexus-archiver 4.7.1 is within the range for > [https://nvd.nist.gov/vuln/detail/CVE-2023-37460], and is critical as it may > be a surface for remote code execution. > > Dependabot opened the pull request for the bump: > [https://github.com/apache/maven-dependency-plugin/pull/330]. > > I'm filing this to bring up that this is critical to merge + trying to > encourage a possible release whenever possible. > > Thank you! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (MDEP-882) Upgrade plexus-archiver due to CVE-2023-37460
[ https://issues.apache.org/jira/browse/MDEP-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise resolved MDEP-882. -- Resolution: Fixed https://github.com/apache/maven-dependency-plugin/commit/0243c410d504303e25465f7c5d39790d1c272684 > Upgrade plexus-archiver due to CVE-2023-37460 > - > > Key: MDEP-882 > URL: https://issues.apache.org/jira/browse/MDEP-882 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Bruno Volpato >Assignee: Karl Heinz Marbaise >Priority: Major > > The dependency plexus-archiver 4.7.1 is within the range for > [https://nvd.nist.gov/vuln/detail/CVE-2023-37460], and is critical as it may > be a surface for remote code execution. > > Dependabot opened the pull request for the bump: > [https://github.com/apache/maven-dependency-plugin/pull/330]. > > I'm filing this to bring up that this is critical to merge + trying to > encourage a possible release whenever possible. > > Thank you! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MDEP-882) Upgrade plexus-archiver due to CVE-2023-37460
[ https://issues.apache.org/jira/browse/MDEP-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MDEP-882: Assignee: Karl Heinz Marbaise > Upgrade plexus-archiver due to CVE-2023-37460 > - > > Key: MDEP-882 > URL: https://issues.apache.org/jira/browse/MDEP-882 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Bruno Volpato >Assignee: Karl Heinz Marbaise >Priority: Major > > The dependency plexus-archiver 4.7.1 is within the range for > [https://nvd.nist.gov/vuln/detail/CVE-2023-37460], and is critical as it may > be a surface for remote code execution. > > Dependabot opened the pull request for the bump: > [https://github.com/apache/maven-dependency-plugin/pull/330]. > > I'm filing this to bring up that this is critical to merge + trying to > encourage a possible release whenever possible. > > Thank you! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHADE-454) Shade Plugin does not work with JDK 20
[
https://issues.apache.org/jira/browse/MSHADE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753296#comment-17753296
]
Michael Osipov commented on MSHADE-454:
---
[~patrickjamesbarry], try the new release with a dependency override.
> Shade Plugin does not work with JDK 20
> --
>
> Key: MSHADE-454
> URL: https://issues.apache.org/jira/browse/MSHADE-454
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Patrick Barry
>Priority: Major
>
> We are trying to use JDK 20 and this was the only plugin we had to
> work-around because it would not work. Are there plans to update this plugin
> to support JDK 20+? Is there a work-around until changes are made?
>
> Our current work-around is using assembly plugin, but we use shade plugin in
> many of the apps we are migrating and our preference is to continue to use
> Shade-plugin.
> Currently- if you try to use shade plugin with JDK 20, you get : Unsupported
> class file major version 64
>
> {noformat}
> Error creating shaded jar: Unsupported class file major version 64
> 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:104)
> at java.lang.reflect.Method.invoke (Method.java:578)
> 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)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: Unsupported class file major version 64
> at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute
> (ShadeMojo.java:624)
> 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
[jira] [Commented] (MSHADE-454) Shade Plugin does not work with JDK 20
[
https://issues.apache.org/jira/browse/MSHADE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753292#comment-17753292
]
Torsten Curdt commented on MSHADE-454:
--
Interesting. I did know that makes a difference. Apparently it does. Thanks for
the help.
I just released 2.9.0. Should be available once the maven repo has synced.
> Shade Plugin does not work with JDK 20
> --
>
> Key: MSHADE-454
> URL: https://issues.apache.org/jira/browse/MSHADE-454
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Patrick Barry
>Priority: Major
>
> We are trying to use JDK 20 and this was the only plugin we had to
> work-around because it would not work. Are there plans to update this plugin
> to support JDK 20+? Is there a work-around until changes are made?
>
> Our current work-around is using assembly plugin, but we use shade plugin in
> many of the apps we are migrating and our preference is to continue to use
> Shade-plugin.
> Currently- if you try to use shade plugin with JDK 20, you get : Unsupported
> class file major version 64
>
> {noformat}
> Error creating shaded jar: Unsupported class file major version 64
> 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:104)
> at java.lang.reflect.Method.invoke (Method.java:578)
> 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)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: Unsupported class file major version 64
> at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute
> (ShadeMojo.java:624)
> 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
>
[GitHub] [maven-pmd-plugin] dependabot[bot] commented on pull request #134: Bump release-drafter/release-drafter from 5.23.0 to 5.24.0
dependabot[bot] commented on PR #134: URL: https://github.com/apache/maven-pmd-plugin/pull/134#issuecomment-1675136860 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-pmd-plugin] slachiewicz closed pull request #134: Bump release-drafter/release-drafter from 5.23.0 to 5.24.0
slachiewicz closed pull request #134: Bump release-drafter/release-drafter from 5.23.0 to 5.24.0 URL: https://github.com/apache/maven-pmd-plugin/pull/134 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-doxia-converter] dependabot[bot] closed pull request #42: Bump plexus-utils from 3.5.0 to 3.5.1
dependabot[bot] closed pull request #42: Bump plexus-utils from 3.5.0 to 3.5.1 URL: https://github.com/apache/maven-doxia-converter/pull/42 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-doxia-converter] dependabot[bot] commented on pull request #42: Bump plexus-utils from 3.5.0 to 3.5.1
dependabot[bot] commented on PR #42: URL: https://github.com/apache/maven-doxia-converter/pull/42#issuecomment-1675119848 Looks like org.codehaus.plexus:plexus-utils is no longer updatable, so this is no longer needed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-resources-plugin] dependabot[bot] commented on pull request #61: Bump slf4j-simple from 1.7.36 to 2.0.7
dependabot[bot] commented on PR #61: URL: https://github.com/apache/maven-resources-plugin/pull/61#issuecomment-1675118004 OK, I won't notify you about version 2.x.x again, unless you re-open this PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-resources-plugin] dependabot[bot] closed pull request #61: Bump slf4j-simple from 1.7.36 to 2.0.7
dependabot[bot] closed pull request #61: Bump slf4j-simple from 1.7.36 to 2.0.7 URL: https://github.com/apache/maven-resources-plugin/pull/61 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MSHARED-1273) getFiles/getFileNames do not throw IOException
[ https://issues.apache.org/jira/browse/MSHARED-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753287#comment-17753287 ] ASF GitHub Bot commented on MSHARED-1273: - slachiewicz commented on PR #160: URL: https://github.com/apache/maven-shared-utils/pull/160#issuecomment-1675114501 why restore? > getFiles/getFileNames do not throw IOException > -- > > Key: MSHARED-1273 > URL: https://issues.apache.org/jira/browse/MSHARED-1273 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-shared-utils >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-file-management] slachiewicz merged pull request #27: Bump org.junit:junit-bom from 5.9.3 to 5.10.0
slachiewicz merged PR #27: URL: https://github.com/apache/maven-file-management/pull/27 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-shared-jar] slachiewicz merged pull request #22: Bump junitVersion from 5.9.2 to 5.10.0
slachiewicz merged PR #22: URL: https://github.com/apache/maven-shared-jar/pull/22 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-scm] slachiewicz merged pull request #182: Bump apache/maven-gh-actions-shared from 2 to 3
slachiewicz merged PR #182: URL: https://github.com/apache/maven-scm/pull/182 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-wrapper] slachiewicz merged pull request #103: Bump org.junit:junit-bom from 5.9.2 to 5.10.0
slachiewicz merged PR #103: URL: https://github.com/apache/maven-wrapper/pull/103 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-doxia] dependabot[bot] closed pull request #163: Bump junitVersion from 5.9.2 to 5.9.3
dependabot[bot] closed pull request #163: Bump junitVersion from 5.9.2 to 5.9.3 URL: https://github.com/apache/maven-doxia/pull/163 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-doxia] dependabot[bot] opened a new pull request, #173: Bump junitVersion from 5.9.2 to 5.10.0
dependabot[bot] opened a new pull request, #173: URL: https://github.com/apache/maven-doxia/pull/173 Bumps `junitVersion` from 5.9.2 to 5.10.0. Updates `org.junit.jupiter:junit-jupiter-api` from 5.9.2 to 5.10.0 Release notes Sourced from https://github.com/junit-team/junit5/releases;>org.junit.jupiter:junit-jupiter-api's releases. JUnit 5.10.0 = Platform 1.10.0 + Jupiter 5.10.0 + Vintage 5.10.0 See http://junit.org/junit5/docs/5.10.0/release-notes/;>Release Notes. Full Changelog: https://github.com/junit-team/junit5/compare/r5.10.0-RC2...r5.10.0;>https://github.com/junit-team/junit5/compare/r5.10.0-RC2...r5.10.0 JUnit 5.10.0-RC2 = Platform 1.10.0-RC2+ Jupiter 5.10.0-RC2 + Vintage 5.10.0-RC2 See http://junit.org/junit5/docs/5.10.0-RC2/release-notes/;>Release Notes. JUnit 5.10.0-RC1 = Platform 1.10.0-RC1 + Jupiter 5.10.0-RC1 + Vintage 5.10.0-RC1 See http://junit.org/junit5/docs/5.10.0-RC1/release-notes/;>Release Notes. JUnit 5.10.0-M1 = Platform 1.10.0-M1 + Jupiter 5.10.0-M1 + Vintage 5.10.0-M1 See http://junit.org/junit5/docs/5.10.0-M1/release-notes/;>Release Notes. JUnit 5.9.3 = Platform 1.9.3 + Jupiter 5.9.3 + Vintage 5.9.3 See http://junit.org/junit5/docs/5.9.3/release-notes/;>Release Notes. Commits https://github.com/junit-team/junit5/commit/7f619ca7ac9ecd1b20cc01c44a4df98f5fb67804;>7f619ca Release 5.10 https://github.com/junit-team/junit5/commit/9899de4a92520fb1b76cd1d4f2c9cd9150ebcfd1;>9899de4 Update Gradle Enterprise plugin to 3.14 https://github.com/junit-team/junit5/commit/45b970fad4ea35ae46f40c8794611d47f8f28087;>45b970f Replace soon-to-be-deprecated usages of project.buildDir https://github.com/junit-team/junit5/commit/463ae360d86837b955731df7d7fe56e9f7c155dd;>463ae36 Prune Release Notes for 5.10 GA https://github.com/junit-team/junit5/commit/893c64b47575df1d6499fb2064c81160c02e5c14;>893c64b Back to snapshots for further development https://github.com/junit-team/junit5/commit/e6ff0c53ba851e48eaf26acc39988c5c4b469580;>e6ff0c5 Release 5.10.0-RC2 https://github.com/junit-team/junit5/commit/b08a76b59f468df1dffeaae84a9bac4aa9163043;>b08a76b Add 5.10.0-RC2 release notes https://github.com/junit-team/junit5/commit/2c278c7536c0c66eb2fc04e3c8665561bae0f0a7;>2c278c7 Revert Prune Release Notes for 5.10 GA https://github.com/junit-team/junit5/commit/acb6e65442b39c4372d8187f240f8f4f32da56d3;>acb6e65 Provide access to source element annotations for TempDirFactory https://github.com/junit-team/junit5/commit/73818a193b7020a5c7bb3b11b1f178d8fe206462;>73818a1 Bump org.gradle.toolchains:foojay-resolver from 0.5.0 to 0.6.0 Additional commits viewable in https://github.com/junit-team/junit5/compare/r5.9.2...r5.10.0;>compare view Updates `org.junit.jupiter:junit-jupiter-engine` from 5.9.2 to 5.10.0 Release notes Sourced from https://github.com/junit-team/junit5/releases;>org.junit.jupiter:junit-jupiter-engine's releases. JUnit 5.10.0 = Platform 1.10.0 + Jupiter 5.10.0 + Vintage 5.10.0 See http://junit.org/junit5/docs/5.10.0/release-notes/;>Release Notes. Full Changelog: https://github.com/junit-team/junit5/compare/r5.10.0-RC2...r5.10.0;>https://github.com/junit-team/junit5/compare/r5.10.0-RC2...r5.10.0 JUnit 5.10.0-RC2 = Platform 1.10.0-RC2+ Jupiter 5.10.0-RC2 + Vintage 5.10.0-RC2 See http://junit.org/junit5/docs/5.10.0-RC2/release-notes/;>Release Notes. JUnit 5.10.0-RC1 = Platform 1.10.0-RC1 + Jupiter 5.10.0-RC1 + Vintage 5.10.0-RC1 See http://junit.org/junit5/docs/5.10.0-RC1/release-notes/;>Release Notes. JUnit 5.10.0-M1 = Platform 1.10.0-M1 + Jupiter 5.10.0-M1 + Vintage 5.10.0-M1 See http://junit.org/junit5/docs/5.10.0-M1/release-notes/;>Release Notes. JUnit 5.9.3 = Platform 1.9.3 + Jupiter 5.9.3 + Vintage 5.9.3 See http://junit.org/junit5/docs/5.9.3/release-notes/;>Release Notes. Commits https://github.com/junit-team/junit5/commit/7f619ca7ac9ecd1b20cc01c44a4df98f5fb67804;>7f619ca Release 5.10 https://github.com/junit-team/junit5/commit/9899de4a92520fb1b76cd1d4f2c9cd9150ebcfd1;>9899de4 Update Gradle Enterprise plugin to 3.14 https://github.com/junit-team/junit5/commit/45b970fad4ea35ae46f40c8794611d47f8f28087;>45b970f Replace soon-to-be-deprecated usages of project.buildDir https://github.com/junit-team/junit5/commit/463ae360d86837b955731df7d7fe56e9f7c155dd;>463ae36 Prune Release Notes for 5.10 GA https://github.com/junit-team/junit5/commit/893c64b47575df1d6499fb2064c81160c02e5c14;>893c64b Back to snapshots for further development https://github.com/junit-team/junit5/commit/e6ff0c53ba851e48eaf26acc39988c5c4b469580;>e6ff0c5 Release 5.10.0-RC2 https://github.com/junit-team/junit5/commit/b08a76b59f468df1dffeaae84a9bac4aa9163043;>b08a76b Add 5.10.0-RC2 release notes https://github.com/junit-team/junit5/commit/2c278c7536c0c66eb2fc04e3c8665561bae0f0a7;>2c278c7 Revert
[jira] [Commented] (MSHADE-454) Shade Plugin does not work with JDK 20
[
https://issues.apache.org/jira/browse/MSHADE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753279#comment-17753279
]
Michael Osipov commented on MSHADE-454:
---
Yes, that is your problem. You are invoking two intersecting phases. deploy
implies package. Drop it, it should work.
> Shade Plugin does not work with JDK 20
> --
>
> Key: MSHADE-454
> URL: https://issues.apache.org/jira/browse/MSHADE-454
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Patrick Barry
>Priority: Major
>
> We are trying to use JDK 20 and this was the only plugin we had to
> work-around because it would not work. Are there plans to update this plugin
> to support JDK 20+? Is there a work-around until changes are made?
>
> Our current work-around is using assembly plugin, but we use shade plugin in
> many of the apps we are migrating and our preference is to continue to use
> Shade-plugin.
> Currently- if you try to use shade plugin with JDK 20, you get : Unsupported
> class file major version 64
>
> {noformat}
> Error creating shaded jar: Unsupported class file major version 64
> 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:104)
> at java.lang.reflect.Method.invoke (Method.java:578)
> 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)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: Unsupported class file major version 64
> at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute
> (ShadeMojo.java:624)
> 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
[jira] [Commented] (MSITE-976) Bump plexus-archiver from 4.7.1 to 4.8.0
[ https://issues.apache.org/jira/browse/MSITE-976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753277#comment-17753277 ] ASF GitHub Bot commented on MSITE-976: -- slachiewicz merged PR #157: URL: https://github.com/apache/maven-site-plugin/pull/157 > Bump plexus-archiver from 4.7.1 to 4.8.0 > > > Key: MSITE-976 > URL: https://issues.apache.org/jira/browse/MSITE-976 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: 4.0.0-M10 > > > Fix for CVE-2023-37460 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSITE-976) Bump plexus-archiver from 4.7.1 to 4.8.0
[ https://issues.apache.org/jira/browse/MSITE-976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MSITE-976. -- Resolution: Fixed > Bump plexus-archiver from 4.7.1 to 4.8.0 > > > Key: MSITE-976 > URL: https://issues.apache.org/jira/browse/MSITE-976 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: 4.0.0-M10 > > > Fix for CVE-2023-37460 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSITE-976) Bump plexus-archiver from 4.7.1 to 4.8.0
[ https://issues.apache.org/jira/browse/MSITE-976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MSITE-976: --- Description: Fix for CVE-2023-37460 > Bump plexus-archiver from 4.7.1 to 4.8.0 > > > Key: MSITE-976 > URL: https://issues.apache.org/jira/browse/MSITE-976 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: 4.0.0-M10 > > > Fix for CVE-2023-37460 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSITE-976) Bump plexus-archiver from 4.7.1 to 4.8.0
Sylwester Lachiewicz created MSITE-976: -- Summary: Bump plexus-archiver from 4.7.1 to 4.8.0 Key: MSITE-976 URL: https://issues.apache.org/jira/browse/MSITE-976 Project: Maven Site Plugin Issue Type: Dependency upgrade Reporter: Sylwester Lachiewicz Fix For: 4.0.0-M10 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSITE-803) checkstyle version 8.4 not accessible.
[
https://issues.apache.org/jira/browse/MSITE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz closed MSITE-803.
--
Resolution: Won't Fix
> checkstyle version 8.4 not accessible.
> ---
>
> Key: MSITE-803
> URL: https://issues.apache.org/jira/browse/MSITE-803
> Project: Maven Site Plugin
> Issue Type: Wish
>Reporter: Ernst Reissner
>Priority: Major
>
> One may use checkstyle plugin for various versions of checkstyle e.g.
> 8.4 specifying
> {code:xml}
> com.puppycrawl.tools
> checkstyle
> 8.4
> {code}
> e.g. in the pluginManagement.
> In contrast, it is not possible to specify this in the reporting section.
> As a workaround, i would prefer adding a checkstyleVersion property in
> the configuration.
> Not that by default the plugin used checkstyle 6.11.2 whereas the current
> is 8.4.
> An even less expensive workaround would be to deliver the plugin invoking a
> more recent version of checkstyle.
> I would prefer at least 7.2.
> It is bad that so various features are not accessible, as e.g.
> designforextension is not reported if @Override found.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MBUILDCACHE-60) Remove Guava dependency
[ https://issues.apache.org/jira/browse/MBUILDCACHE-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MBUILDCACHE-60. --- Resolution: Fixed > Remove Guava dependency > --- > > Key: MBUILDCACHE-60 > URL: https://issues.apache.org/jira/browse/MBUILDCACHE-60 > Project: Maven Build Cache Extension > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Minor > Labels: pull-request-available > Fix For: 1.1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MBUILDCACHE-60) Remove Guava dependency
[ https://issues.apache.org/jira/browse/MBUILDCACHE-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753276#comment-17753276 ] ASF GitHub Bot commented on MBUILDCACHE-60: --- slachiewicz merged PR #86: URL: https://github.com/apache/maven-build-cache-extension/pull/86 > Remove Guava dependency > --- > > Key: MBUILDCACHE-60 > URL: https://issues.apache.org/jira/browse/MBUILDCACHE-60 > Project: Maven Build Cache Extension > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Minor > Labels: pull-request-available > Fix For: 1.1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-build-cache-extension] slachiewicz merged pull request #86: [MBUILDCACHE-60] Remove undeclared Guava dependency with Arrays.asList
slachiewicz merged PR #86: URL: https://github.com/apache/maven-build-cache-extension/pull/86 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MBUILDCACHE-60) Remove Guava dependency
[ https://issues.apache.org/jira/browse/MBUILDCACHE-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MBUILDCACHE-60: Fix Version/s: 1.1.0 > Remove Guava dependency > --- > > Key: MBUILDCACHE-60 > URL: https://issues.apache.org/jira/browse/MBUILDCACHE-60 > Project: Maven Build Cache Extension > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Minor > Labels: pull-request-available > Fix For: 1.1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHADE-454) Shade Plugin does not work with JDK 20
[
https://issues.apache.org/jira/browse/MSHADE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753272#comment-17753272
]
Torsten Curdt commented on MSHADE-454:
--
Maybe the "package" and "deploy" in one is causing this?
> Shade Plugin does not work with JDK 20
> --
>
> Key: MSHADE-454
> URL: https://issues.apache.org/jira/browse/MSHADE-454
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Patrick Barry
>Priority: Major
>
> We are trying to use JDK 20 and this was the only plugin we had to
> work-around because it would not work. Are there plans to update this plugin
> to support JDK 20+? Is there a work-around until changes are made?
>
> Our current work-around is using assembly plugin, but we use shade plugin in
> many of the apps we are migrating and our preference is to continue to use
> Shade-plugin.
> Currently- if you try to use shade plugin with JDK 20, you get : Unsupported
> class file major version 64
>
> {noformat}
> Error creating shaded jar: Unsupported class file major version 64
> 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:104)
> at java.lang.reflect.Method.invoke (Method.java:578)
> 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)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: Unsupported class file major version 64
> at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute
> (ShadeMojo.java:624)
> 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
>
[jira] [Commented] (MSHADE-454) Shade Plugin does not work with JDK 20
[
https://issues.apache.org/jira/browse/MSHADE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753269#comment-17753269
]
Torsten Curdt commented on MSHADE-454:
--
Can you try a `mvn -B -Prelease --file pom.xml package deploy` because that's
what the CI server tries to do.
> Shade Plugin does not work with JDK 20
> --
>
> Key: MSHADE-454
> URL: https://issues.apache.org/jira/browse/MSHADE-454
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Patrick Barry
>Priority: Major
>
> We are trying to use JDK 20 and this was the only plugin we had to
> work-around because it would not work. Are there plans to update this plugin
> to support JDK 20+? Is there a work-around until changes are made?
>
> Our current work-around is using assembly plugin, but we use shade plugin in
> many of the apps we are migrating and our preference is to continue to use
> Shade-plugin.
> Currently- if you try to use shade plugin with JDK 20, you get : Unsupported
> class file major version 64
>
> {noformat}
> Error creating shaded jar: Unsupported class file major version 64
> 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:104)
> at java.lang.reflect.Method.invoke (Method.java:578)
> 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)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: Unsupported class file major version 64
> at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute
> (ShadeMojo.java:624)
> 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
[jira] [Commented] (MSHADE-454) Shade Plugin does not work with JDK 20
[
https://issues.apache.org/jira/browse/MSHADE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753266#comment-17753266
]
Michael Osipov commented on MSHADE-454:
---
I can build from master with
{noformat}
osipovmi@deblndw011x:/tmp/jdependency (master *%=)
$ mvn clean package -Prelease -V
Apache Maven 3.8.8 (4c87b05d9aedce574290d1acc98575ed5eb6cd39)
Maven home: /usr/local/share/java/maven
Java version: 1.8.0_372, vendor: OpenJDK BSD Porting Team, runtime:
/usr/local/openjdk8/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "freebsd", version: "12.4-stable", arch: "amd64", family: "unix"
[INFO] Scanning for projects...
[INFO]
[INFO] ---< org.vafer:jdependency >
[INFO] Building jdependency 2.9.0
[INFO] from pom.xml
{noformat}
> Shade Plugin does not work with JDK 20
> --
>
> Key: MSHADE-454
> URL: https://issues.apache.org/jira/browse/MSHADE-454
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Patrick Barry
>Priority: Major
>
> We are trying to use JDK 20 and this was the only plugin we had to
> work-around because it would not work. Are there plans to update this plugin
> to support JDK 20+? Is there a work-around until changes are made?
>
> Our current work-around is using assembly plugin, but we use shade plugin in
> many of the apps we are migrating and our preference is to continue to use
> Shade-plugin.
> Currently- if you try to use shade plugin with JDK 20, you get : Unsupported
> class file major version 64
>
> {noformat}
> Error creating shaded jar: Unsupported class file major version 64
> 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:104)
> at java.lang.reflect.Method.invoke (Method.java:578)
> 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)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: Unsupported class file major version 64
> at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute
> (ShadeMojo.java:624)
> 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
>
[jira] [Commented] (MNG-7848) Add s390x pipeline to Jenkins CI
[ https://issues.apache.org/jira/browse/MNG-7848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753219#comment-17753219 ] ASF GitHub Bot commented on MNG-7848: - kun-lu20 commented on PR #1216: URL: https://github.com/apache/maven/pull/1216#issuecomment-1674756441 @olamy Thanks again! > Add s390x pipeline to Jenkins CI > > > Key: MNG-7848 > URL: https://issues.apache.org/jira/browse/MNG-7848 > Project: Maven > Issue Type: New Feature > Components: Bootstrap Build, Integration Tests >Reporter: Kun Lu >Priority: Major > Labels: pull-request-available > > Apache INFRA team has installed necessary JDK flavours on all s390x nodes > (Please check issue > [https://issues.apache.org/jira/projects/INFRA/issues/INFRA-24781]). We’d > like to add the s390x pipeline to Jenkins CI by raising a PR to add ` > Jenkinsfile.s390x` to the Maven code base. > Can anyone from Maven team help us review the PR and create the s390x > pipeline on Jenkins? Thanks! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven] kun-lu20 commented on pull request #1216: [MNG-7848] Remove `Configure deploy` stage from s390x pipeline
kun-lu20 commented on PR #1216: URL: https://github.com/apache/maven/pull/1216#issuecomment-1674756441 @olamy Thanks again! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
