Re: [VOTE] Require Java 17 for Maven 4

+1 On Wed, Feb 28, 2024, at 08:30, Benjamin Marwell wrote: > Hi Maven Devs/Users/Committers and PMC members! > > After several discussions on the mailing lists, I would like to > start a vote in favour of setting the minimal Java bytecode target > of Maven-Core 4 to 17 and hence require Java 17

Re: Maven Dependency Plugin - Log4j vulnerabilities

That was just to demonstrate how i got the dependency chain, that file was there, but if you're going to be this hostile, i'm not interested anymore, muting thread On Thu, 3 Mar 2022 at 08:48, Piotr Żygieło wrote: > > On Thu, 3 Mar 2022 at 08:37, Thomas Matthijs wrote: > > >

Re: Maven Dependency Plugin - Log4j vulnerabilities

Hello, Can confirm this project downloads log4j 1.12.12 for me rm -rf ~/.m2/repository/log4j/log4j sudo chown root:root ~/.m2/repository/log4j/log4j [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:3.2.0:copy (copy-artifact) on project demo: Execution

Re: Any feedback for MNG-6261?

Have you double checked file permissions? if it can't read the parent pom (maybe not all dirs are +x etc) then it wil have the behavior you see On Thu, Jul 27, 2017 at 10:07 PM, Dawid Weiss wrote: > I added a comment on that issue. The problem is not deterministic for >

Re: Publish Maven releases on SDKMAN!

Looks like yet another package manager, and just as most upstream projects don't provide the packages/build for every linux distro and package manager system under the sun, this project looks no different. The sdkman community should help provide the maven releases on it, and not the maven