Yes I tend to agree the user experience is really confusing currently.
Just use mvn archetype:generate with the default project and warnings
are generated.
[WARNING] Plugin validation issues were detected in 2 plugin(s)
[WARNING] * org.apache.maven.plugins:maven-site-plugin:3.12.1
[WARNING] * o
ing executes there and
> the vast ecosystem requires that I get feedback from downstream users.
> Even noisy or not, its expected short lived (hopefully).
>
> -Original Message-
> From: Romain Manni-Bucau
> Sent: Saturday, May 13, 2023 3:54 PM
> To: Maven Developers Li
rything executes there and the vast ecosystem requires that I get
feedback from downstream users. Even noisy or not, its expected short lived
(hopefully).
-Original Message-
From: Romain Manni-Bucau
Sent: Saturday, May 13, 2023 3:54 PM
To: Maven Developers List
Subject: Re: Some thoughts about
+1 very close to what I expressed on slack.
Think end user should also be able to see these warning to select a plugi
or evaluate a migration but at request -> new help plugin goal IMHO.
Le sam. 13 mai 2023 à 21:22, Henning Schmiedehausen <
henn...@schmiedehausen.org> a écrit :
> Hi,
>
> [I want
Hi,
[I wanted to write about this for a while]
Maven has recently (3.9.x) started to log warning messages like this:
*[WARNING] Parameter 'localRepository' is deprecated core expression; Avoid
use of ArtifactRepository type. If you need access to local repository,
switch to '${repositorySystemSe
