Hi,
A little late as the vote has already closed... Tested on several public
and internal projects, on Windows and macOS. No blocking issues
discovered. +1 from me.
We might want to check how the Maven Daemon is built/packaged/shipped. I
recall they had the same issues as Karl Heinz mentions
+1
it's still rc but I have a couple of issues with Jetty build
(https://github.com/jetty/jetty.project).
I am not sure why this is a warning.
[WARNING] BOM imports from within reactor should be avoided @ line 15, column 7
it's very convenient for very large projects that publish boms and
example
+1
Tony Chemit 于2024年11月27日 周三17:20写道：
> +1 (nb)
>
> tested on an internal project with 50 modules and some plugins inside
> of it
>
> Could not verify the hole project because of
> org.codehaus.mojo.extraenforcer.dependencies.BanDuplicateClasses on
> some maven artifacts
>
> But I did not change
+1 (nb)
tested on an internal project with 50 modules and some plugins inside
of it
Could not verify the hole project because of
org.codehaus.mojo.extraenforcer.dependencies.BanDuplicateClasses on
some maven artifacts
But I did not change anything inside the project to be maven 4 aware,
s
+1 (NB)
Successfully tested on a 61 module internal app suite. Notables:
* AnsiConsole removal caused a docker-maven-plugin CNFE and thankfully it
has a recent release fixing that.
* Exposed a Spring GraphQL schema classpath file search configuration
issue, worked around by overriding the default
+1
tested on an internal project
I am still not fan of all warnings related to imports but I don't see a
better solution to make developers aware of conflicts and their risks
On Tue, Nov 26, 2024 at 1:51 PM Mateusz Gajewski <
mateusz.gajew...@starburstdata.com> wrote:
> +1 nb, tested on Trino
>
+1 nb, tested on Trino
On Tue, Nov 26, 2024 at 1:26 PM Guillaume Nodet wrote:
> +1
>
> Le lun. 25 nov. 2024 à 12:50, Tamás Cservenák a
> écrit :
>
> > Howdy,
> >
> > We solved 46 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12355164
> >
> >
+1
Le lun. 25 nov. 2024 à 12:50, Tamás Cservenák a
écrit :
> Howdy,
>
> We solved 46 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12355164
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%
Le mar. 26 nov. 2024 à 07:30, Delany a écrit :
> Hi. Two issues came up:
>
> I use this archived plugin to ensure consistent filenames (if there's an
> alternative please let me know!)
>
>
> com.github.ngeor
> yak4j-filename-conventions-maven-plugin
>
>
+1
On Mon, 25 Nov 2024 at 12:49, Tamás Cservenák wrote:
>
> Howdy,
>
> We solved 46 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12355164
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%
Hi. Two issues came up:
I use this archived plugin to ensure consistent filenames (if there's an
alternative please let me know!)
com.github.ngeor
yak4j-filename-conventions-maven-plugin
org.codehaus.plexus
plexus-utils
Hi,
+1 from me.
We need to add an information how to solve the following on MacOS:
$> mvn --version
Nov 25, 2024 5:59:44 PM org.jline.nativ.JLineNativeLoader log
WARNING: Failed to load native library:libjlinenative.jnilib. osinfo:
Mac/arm64 (caused by: java.lang.UnsatisfiedLinkError:
/Users/kh
12 matches
Mail list logo
