[GitHub] [maven-build-cache-extension] dependabot[bot] opened a new pull request, #96: Bump ch.qos.logback:logback-classic from 1.3.7 to 1.3.11
dependabot[bot] opened a new pull request, #96: URL: https://github.com/apache/maven-build-cache-extension/pull/96 Bumps [ch.qos.logback:logback-classic](https://github.com/qos-ch/logback) from 1.3.7 to 1.3.11. Commits https://github.com/qos-ch/logback/commit/d085896954a6302b58f6a0a724694aac57f6ba45";>d085896 prepare release 1.3.11 https://github.com/qos-ch/logback/commit/fdc736135302a81f64ec0eeac185a54cab48aa9d";>fdc7361 revert Configurator interface to match that in version 1.4.8 https://github.com/qos-ch/logback/commit/f023eb53df4b85e8b8682f4a34e97644ce488e14";>f023eb5 start work on 1.3.11-SNAPSHOT https://github.com/qos-ch/logback/commit/ab267a1cf676e705b115b65d3f2eb2ae2097a649";>ab267a1 prepare release 1.3.10 https://github.com/qos-ch/logback/commit/2640679207c7a91c1781b139a28c60f90bd0eadc";>2640679 slight editing of logback-classic/src/main/java/module-info.java https://github.com/qos-ch/logback/commit/7d942c8974965481900c0b754c7d67cf60545745";>7d942c8 remove Rank and RankValue from Configurator. These types have been replaced b... https://github.com/qos-ch/logback/commit/02fe1a98c5b65a63cda678a79c090421fad85f5d";>02fe1a9 revert Configurator interface from logback-core to logback-classic https://github.com/qos-ch/logback/commit/7a440b80440f2c1aefa672c3ec31690ec4a1b51a";>7a440b8 remove commented out code https://github.com/qos-ch/logback/commit/7a8c54372e0e17f8dd7577ea1395c47fb020c4ce";>7a8c543 start work on 1.3.10-SNAPSHOT https://github.com/qos-ch/logback/commit/73f99846f27b4093bb285bedb1e578fd45771ff2";>73f9984 prepare release 1.3.9 Additional commits viewable in https://github.com/qos-ch/logback/compare/v_1.3.7...v_1.3.11";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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-build-cache-extension] dependabot[bot] commented on pull request #95: Bump ch.qos.logback:logback-classic from 1.3.7 to 1.3.9
dependabot[bot] commented on PR #95: URL: https://github.com/apache/maven-build-cache-extension/pull/95#issuecomment-1672748863 Superseded by #96. -- 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-build-cache-extension] dependabot[bot] closed pull request #95: Bump ch.qos.logback:logback-classic from 1.3.7 to 1.3.9
dependabot[bot] closed pull request #95: Bump ch.qos.logback:logback-classic from 1.3.7 to 1.3.9 URL: https://github.com/apache/maven-build-cache-extension/pull/95 -- 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] (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&focusedCommentId=17752685#comment-17752685
]
Michael Osipov commented on MSHADE-454:
---
Look at the stacktrace, JDependency has a shaded version of ASM which does not
support Java 20 while the upstream version does:
https://github.com/tcurdt/jdependency/blob/02caec79effecc88e9a427011d49879b0731b6ef/pom.xml#L12
Try jdep from master and update this plugin and it should work. So we need to
wait for a new jdependency version.
[~tcurdt], can you make a new version of JDependency?
> 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
> (Lifecycl
[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&focusedCommentId=17752687#comment-17752687
]
Torsten Curdt commented on MSHADE-454:
--
Sorry for being a little behind. I sure can.
> 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&focusedCommentId=17752694#comment-17752694
]
Torsten Curdt commented on MSHADE-454:
--
Meh. The CI pipeline failed to release.
{noformat}
Error: We have duplicated artifacts attached.
1165[INFO]
1166[INFO] BUILD FAILURE
1167[INFO]
1168[INFO] Total time: 21.139 s
1169[INFO] Finished at: 2023-08-10T08:24:40Z
1170[INFO]
1171Error: Failed to execute goal
org.apache.maven.plugins:maven-source-plugin:3.3.0:jar-no-fork (attach-sources)
on project jdependency: Presumably you have configured maven-source-plugn to
execute twice times in your build. You have to configure a classifier for at
least on of them. -> [Help 1]{noformat}
Not sure why the source plugin is complaining. If someone has some insights?
https://github.com/tcurdt/jdependency/actions/runs/5818725372/job/15775712616
> 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.MojoExec
[GitHub] [maven-mvnd] eliasbalasis commented on issue #836: `Could not acquire write lock for…` errors
eliasbalasis commented on issue #836:
URL: https://github.com/apache/maven-mvnd/issues/836#issuecomment-1673539783
I am getting the same using Named Locks on Hazelcast, on a Docker container
though.
-Daether.syncContext.named.factory=semaphore-hazelcast
-Daether.syncContext.named.nameMapper=gav
I have all the required JARs in "lib/ext" and the Hazelcast configuration in
${maven.conf}/hazelcast.xml
--
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] [Created] (MWRAPPER-114) Maven wrapper relative distributionUrl does not work on Windows
Edward Woolhouse created MWRAPPER-114:
-
Summary: Maven wrapper relative distributionUrl does not work on
Windows
Key: MWRAPPER-114
URL: https://issues.apache.org/jira/browse/MWRAPPER-114
Project: Maven Wrapper
Issue Type: Bug
Components: Maven Wrapper Jar
Affects Versions: 3.2.0
Environment: Windows
Reporter: Edward Woolhouse
If Maven Wrapper is used with a relative distributionUrl on Windows then an
error message indicating invalid path characters is shown.
{code:java}
# Directory structure
./mvnw
./mvnw.cmd
./.mvn/wrapper/maven-wrapper.jar
./.mvn/wrapper/maven-wrapper.properties
...{code}
{code:java}
# maven-wrapper.properties
distributionUrl=apache-maven-3.8.8-bin.zip
wrapperUrl=maven-wrapper.jar{code}
When run
{code:java}
./mvnw
...
java.nio.file.InvalidPathException: Illegal char <:> at index 2:
/C:/some-path/apache-maven-3.8.8.zip {code}
This is caused by PathAssembler.java:getBaseName unnecessarilly stringifying
the distibution URL. The fix is as follows
{code:java}
private String getBaseName(URI distUrl) {
- return Paths.get(distUrl.getPath()).getFileName().toString();
+ return Paths.get(distUrl).getFileName().toString();
}{code}
--
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&focusedCommentId=17752908#comment-17752908
]
Torsten Curdt commented on MSHADE-454:
--
Seems like the maven-source-plugin introduced some changes in 3.3.0 that broke
the release pipeline. And it seems like I am not the only one struggling with
that change.
While I think understand the reasoning behind the introduced check, it seems
like false error in the jdependency case.
But I happy to have someone convince me otherwise.
I would love to fix the release build properly. Not quite sure how that
classifier thing is supposed work/help here.
But if it's urgent I guess I could downgrade the plugin for the release.
Let me know if you have some input [~patrickjamesbarry] [~michael-o]
> 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
> (DefaultMojosExecutio
[GitHub] [maven-mvnd] eliasbalasis commented on issue #836: `Could not acquire write lock for…` errors
eliasbalasis commented on issue #836: URL: https://github.com/apache/maven-mvnd/issues/836#issuecomment-1673849424 FYI. I have discovered that there is probably some problem with the Maven resolver implementation. I initially used apache-maven-3.8.8-resolver-1.9.7 but neither [Redisson](https://maven.apache.org/resolver/maven-resolver-named-locks-redisson/index.html) nor [Hazelcast](https://maven.apache.org/resolver/maven-resolver-named-locks-hazelcast/index.html) worked. Now I am using apache-maven-3.8.8-resolver-1.8.2 and [Redisson](https://maven.apache.org/resolver/maven-resolver-named-locks-redisson/index.html) works but [Hazelcast](https://maven.apache.org/resolver/maven-resolver-named-locks-hazelcast/index.html) still doesn't work. I am guessing this will be all eventually fixed in Maven 3.9 as soon as it matures first. -- 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] (MWRAPPER-114) Maven wrapper relative distributionUrl does not work on Windows
[
https://issues.apache.org/jira/browse/MWRAPPER-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17752917#comment-17752917
]
Edward Woolhouse commented on MWRAPPER-114:
---
Well, it's not as simple a fix as that, as this fix would break the ability to
use non-local paths. Needs a little more thought. Maybe special handling for
the file:/// scheme?
> Maven wrapper relative distributionUrl does not work on Windows
> ---
>
> Key: MWRAPPER-114
> URL: https://issues.apache.org/jira/browse/MWRAPPER-114
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Jar
>Affects Versions: 3.2.0
> Environment: Windows
>Reporter: Edward Woolhouse
>Priority: Normal
>
> If Maven Wrapper is used with a relative distributionUrl on Windows then an
> error message indicating invalid path characters is shown.
>
> {code:java}
> # Directory structure
> ./mvnw
> ./mvnw.cmd
> ./.mvn/wrapper/maven-wrapper.jar
> ./.mvn/wrapper/maven-wrapper.properties
> ...{code}
> {code:java}
> # maven-wrapper.properties
> distributionUrl=apache-maven-3.8.8-bin.zip
> wrapperUrl=maven-wrapper.jar{code}
> When run
> {code:java}
> ./mvnw
> ...
> java.nio.file.InvalidPathException: Illegal char <:> at index 2:
> /C:/some-path/apache-maven-3.8.8.zip {code}
> This is caused by PathAssembler.java:getBaseName unnecessarilly stringifying
> the distibution URL. The fix is as follows
> {code:java}
> private String getBaseName(URI distUrl) {
> - return Paths.get(distUrl.getPath()).getFileName().toString();
> + return Paths.get(distUrl).getFileName().toString();
> }{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-source-plugin] bvolpato commented on pull request #12: Bump org.codehaus.plexus:plexus-archiver from 4.7.1 to 4.8.0
bvolpato commented on PR #12: URL: https://github.com/apache/maven-source-plugin/pull/12#issuecomment-1673901688 +1, this is really important because of [CVE-2023-37460](https://nvd.nist.gov/vuln/detail/CVE-2023-37460) -- 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] 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-1673963275 Hi @olamy , Could you please merge this PR and set up a s390x pipeline? Thank you so much! -- 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] (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&focusedCommentId=17752924#comment-17752924 ] ASF GitHub Bot commented on MNG-7848: - kun-lu20 commented on PR #1216: URL: https://github.com/apache/maven/pull/1216#issuecomment-1673963275 Hi @olamy , Could you please merge this PR and set up a s390x pipeline? Thank you so much! > 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)
[jira] [Created] (MSOURCES-142) Upgrade org.codehaus.plexus:plexus-archiver to 4.8.0
Sylwester Lachiewicz created MSOURCES-142: - Summary: Upgrade org.codehaus.plexus:plexus-archiver to 4.8.0 Key: MSOURCES-142 URL: https://issues.apache.org/jira/browse/MSOURCES-142 Project: Maven Source Plugin Issue Type: Dependency upgrade Reporter: Sylwester Lachiewicz Assignee: Sylwester Lachiewicz Fix For: 3.3.1 Update due to [CVE-2023-37460|https://nvd.nist.gov/vuln/detail/CVE-2023-37460] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSOURCES-142) Upgrade plexus-archiver to 4.8.0
[ https://issues.apache.org/jira/browse/MSOURCES-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MSOURCES-142: -- Summary: Upgrade plexus-archiver to 4.8.0 (was: Upgrade org.codehaus.plexus:plexus-archiver to 4.8.0) > Upgrade plexus-archiver to 4.8.0 > > > Key: MSOURCES-142 > URL: https://issues.apache.org/jira/browse/MSOURCES-142 > Project: Maven Source Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.3.1 > > > Update due to > [CVE-2023-37460|https://nvd.nist.gov/vuln/detail/CVE-2023-37460] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSOURCES-142) Upgrade plexus-archiver to 4.8.0
[ https://issues.apache.org/jira/browse/MSOURCES-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MSOURCES-142. - Resolution: Fixed > Upgrade plexus-archiver to 4.8.0 > > > Key: MSOURCES-142 > URL: https://issues.apache.org/jira/browse/MSOURCES-142 > Project: Maven Source Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.3.1 > > > Update due to > [CVE-2023-37460|https://nvd.nist.gov/vuln/detail/CVE-2023-37460] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSOURCES-142) Upgrade plexus-archiver to 4.8.0
[ https://issues.apache.org/jira/browse/MSOURCES-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17752927#comment-17752927 ] ASF GitHub Bot commented on MSOURCES-142: - slachiewicz merged PR #12: URL: https://github.com/apache/maven-source-plugin/pull/12 > Upgrade plexus-archiver to 4.8.0 > > > Key: MSOURCES-142 > URL: https://issues.apache.org/jira/browse/MSOURCES-142 > Project: Maven Source Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.3.1 > > > Update due to > [CVE-2023-37460|https://nvd.nist.gov/vuln/detail/CVE-2023-37460] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven] olamy merged pull request #1216: [MNG-7848] Remove `Configure deploy` stage from s390x pipeline
olamy merged PR #1216: URL: https://github.com/apache/maven/pull/1216 -- 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] (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&focusedCommentId=17752994#comment-17752994 ] ASF GitHub Bot commented on MNG-7848: - olamy merged PR #1216: URL: https://github.com/apache/maven/pull/1216 > 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] olamy commented on pull request #1216: [MNG-7848] Remove `Configure deploy` stage from s390x pipeline
olamy commented on PR #1216: URL: https://github.com/apache/maven/pull/1216#issuecomment-1674081140 done but there is something to fix https://ci-maven.apache.org/job/Maven/job/Maven%20Core%20s390x/job/master/1/console -- 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] (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&focusedCommentId=17752997#comment-17752997 ] ASF GitHub Bot commented on MNG-7848: - olamy commented on PR #1216: URL: https://github.com/apache/maven/pull/1216#issuecomment-1674081140 done but there is something to fix https://ci-maven.apache.org/job/Maven/job/Maven%20Core%20s390x/job/master/1/console > 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)
[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&focusedCommentId=17753002#comment-17753002 ] ASF GitHub Bot commented on MNG-7848: - olamy commented on PR #1216: URL: https://github.com/apache/maven/pull/1216#issuecomment-1674100297 oops it's fixed > 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)
