Re: maven 3.9.x warnings

Le sam. 20 mai 2023 à 10:22, Slawomir Jaranowski a écrit : > Hi, > > We have two kinds of causes which can emit warnings: > 1. wrong using of plugin by user like use deprecated or unexisting > parameters, using deprecated goals > 2. wrong implementation in plugin, eg scope, EOL components > > Fir

Re: maven 3.9.x warnings

Hi, We have two kinds of causes which can emit warnings: 1. wrong using of plugin by user like use deprecated or unexisting parameters, using deprecated goals 2. wrong implementation in plugin, eg scope, EOL components First group should be displayed - because the end user can fix their own build

Re: maven 3.9.x warnings

Can't we store the text warnings in a file target/mvn-warning.txt (whatever the name is) Then per default a single warning line telling the user there will be potential issues with this build in maven 4.x (more details look at target/mvn-warning.txt) and telling him the flags to have more details

Re: maven 3.9.x warnings

Thank you for speaking up. I would encourage others that feel the same way to speak up as well. I do not believe that the "we ram this through and hope that at some point all plugins are updated so the warnings die down" is a viable approach. This is what I wrote on the PR ("you/your" is @tamas he

Re: maven 3.9.x warnings

+1 to make NONE the default, know it defeats the purpose but this feature makes end user builds nasty whereas it should help them. I would also be +1 to make it a help:check-state goal rather than having it in maven core where it is quite pointless IMHO as explained in earlier threads. Le ven. 19

Re: maven 3.9.x warnings

I put https://github.com/apache/maven/pull/1116 together which does exactly that. It is literally three lines of code. -h On Fri, May 19, 2023 at 12:17 PM Henning Schmiedehausen < henn...@schmiedehausen.org> wrote: > Hi Gary, > > Seems we both work in similar places. :-) Looking at > https://gi

Re: maven 3.9.x warnings

Hi Gary, Seems we both work in similar places. :-) Looking at https://github.com/apache/maven/commit/11d97e64e7e3fbed23d8e98abdd8c015a957ee82, it seems that 3.9.3 (whenever that comes) will improve things; the default logging is still not great but at least I can add `NONE` to all my projects get

Re: maven 3.9.x warnings

>From this user's POV, I feel these warning force me to spin my wheels: If I have old plugins I can update their versions, and then I still get the warnings, none of which I can do anything about. I can do something about compiler warnings, I can do nothing about these. I am left to explain up and

Re: maven 3.9.x warnings

Am 2023-05-19 um 20:15 schrieb Henning Schmiedehausen: Hi Tamas, You need to write documentation that helps your users. All the error messages and warnings and "this is wrong, fix it" messages to users do not help. This passive-aggressive attempt to surface problems in an obscure way to the end

Re: maven 3.9.x warnings

Hi Tamas, Thanks for the quick response. On Fri, May 19, 2023 at 2:35 AM Tamás Cservenák wrote: > Howdy, > > So, have a small local change, probably to go with 3.9.3. > [...] > [WARNING] * org.basepom.maven:inline-maven-plugin:1.0.1 > [WARNING] Declared at location(s): > [WARNING]* or

Re: maven 3.9.x warnings

s Cservenák > Sent: Friday, May 19, 2023 5:44 AM > To: Maven Developers List > Subject: Re: maven 3.9.x warnings > > FTR, issue (and PR linked to it) > https://issues.apache.org/jira/browse/MNG-7786 > > On Fri, May 19, 2023 at 11:35 AM Tamás Cservenák > wrote: > &g

Re: maven 3.9.x warnings

s successful build... > Now a bunch of warnings > > I think for clarity that just needs to be flipped to. > > ...bunch of warnings... > Status of the build > > -Original Message- > From: Tamás Cservenák > Sent: Friday, May 19, 2023 5:35 AM > To: Maven

RE: maven 3.9.x warnings

MO is kind of expected noise for the most part. There are definitely some improvements to be had in general though. -Original Message- From: Tamás Cservenák Sent: Friday, May 19, 2023 5:44 AM To: Maven Developers List Subject: Re: maven 3.9.x warnings FTR, issue (and PR linked to it)

RE: maven 3.9.x warnings

Now a bunch of warnings I think for clarity that just needs to be flipped to. ...bunch of warnings... Status of the build -Original Message- From: Tamás Cservenák Sent: Friday, May 19, 2023 5:35 AM To: Maven Developers List Subject: Re: maven 3.9.x warnings Howdy, So, have a small

Re: maven 3.9.x warnings

FTR, issue (and PR linked to it) https://issues.apache.org/jira/browse/MNG-7786 On Fri, May 19, 2023 at 11:35 AM Tamás Cservenák wrote: > Howdy, > > So, have a small local change, probably to go with 3.9.3. > > changes: > - message modified, it is now clear that it is "plugin descriptor" that >

Re: maven 3.9.x warnings

Howdy, So, have a small local change, probably to go with 3.9.3. changes: - message modified, it is now clear that it is "plugin descriptor" that contains unwanted artifacts - added new check that "checks reality", the plugin resolved dependencies So, now messages on JDBI project look like this

Re: maven 3.9.x warnings

Henning, your do have open option to go: in inline-maven-project upgrade (buggy) maven-plugin-plugin 3.6.2 (suffers from https://issues.apache.org/jira/browse/MPLUGIN-382) to a more recent one. OTOH, this issue revealed a validation issue: - it relies on pluginDescriptor/dependencies to perform v

maven 3.9.x warnings

>From maven 3.9.2: [WARNING] * org.basepom.maven:inline-maven-plugin:1.0.1 [WARNING] Declared at location(s): [WARNING]* org.jdbi:jdbi3-core:3.38.3-SNAPSHOT (core/pom.xml) @ line 145 [WARNING] Used in module(s): [WARNING]* org.jdbi:jdbi3-core:3.38.3-SNAPSHOT (core/pom.xml) [WARNING]