+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
They seem to have migrated the issues from JIRA to GitHub. That would be
#1 option, but I'm not sure if we need to go into that direction.
Le ven. 22 nov. 2024 à 17:28, Arnaud Héritier a
écrit :
> I know spring teams did such move in the past
> ref:
>
> https://spring.io/blog/2019/01/15/spring-
Le ven. 22 nov. 2024 à 12:17, Michael Osipov a écrit :
> I'd like to complete the cleanup, as dicussed earlier, end of this year.
> This will give us a leaner migration base.
>
>
That's only relevant for #1., isn't it ?
I don't think the JIRA instance is going to go away anytime soon, so I
don't
Le lun. 25 nov. 2024 à 14:41, Martin Desruisseaux <
martin.desruisse...@geomatys.com> a écrit :
> Le 2024-11-25 à 13 h 23, Guillaume Nodet a écrit :
>
> > Yes, the model can now evolve much more easily than with Maven 3,
> > that's one of the main benefits of Maven 4. You should create a PR for
>
Le 2024-11-25 à 13 h 23, Guillaume Nodet a écrit :
Yes, the model can now evolve much more easily than with Maven 3,
that's one of the main benefits of Maven 4. You should create a PR for
these changes, eventually in draft mode if it's not ready yet.
Thanks, done in draft mode: https://githu
Le lun. 25 nov. 2024 à 13:16, Martin Desruisseaux <
martin.desruisse...@geomatys.com> a écrit :
> Hello all
>
> Just for planning, there is one significant change that I was hopping to
> bring to Maven model: the introduction of a Source element, as discussed
> previously. A draft is a [1]. If Mav
Hello all
Just for planning, there is one significant change that I was hopping to
bring to Maven model: the introduction of a Source element, as discussed
previously. A draft is a [1]. If Maven 4.0.0 is released soon, would a
change of model still be possible in, for example, Maven 4.1?
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%20MNG%20AND%20resolution%20%3D%20Unresolved
Staging repo:
https://repos
10 matches
Mail list logo