+1
Le ven. 19 mai 2023 à 15:49, Michael Osipov a écrit :
> Hi,
>
> we solved 4 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317223&version=12353164
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project+%3D+MC
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
Hi,
The page on https://maven.apache.org/resolver/maven-3.8.x.html states
that *"Since
version 1.7.0, Maven Resolver requires Java 8 to run and a brand new
default sync context factory has been implemented."*.
Assuming for a moment that Java 8+ is a no-brainer, what does the second
part of that s
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
Am 2023-05-19 um 23:27 schrieb Finkelman, Jacob:
During a maven publish if the server closes the TCP connection after the upload
of an asset sometimes the publish will fail with a failed to respond while
attempting to upload the checksum.
Speaking of checksum, here is your concrete problem:
During a maven publish if the server closes the TCP connection after the upload
of an asset sometimes the publish will fail with a failed to respond while
attempting to upload the checksum. The correct behavior to wanting to send more
HTTP requests on a closed TCP connection, is to open a new TC
+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
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
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
>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
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
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
+1
pt., 19 maj 2023, 19:11 użytkownik Tamás Cservenák
napisał:
> +1
>
> On Fri, May 19, 2023 at 3:49 PM Michael Osipov
> wrote:
>
> > Hi,
> >
> > we solved 4 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317223&version=12353164
> >
> > There are still a co
+1
On Fri, May 19, 2023 at 3:49 PM Michael Osipov wrote:
> Hi,
>
> we solved 4 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317223&version=12353164
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project+%3D+MC
+1
pt., 19 maj 2023 o 15:49 Michael Osipov napisał(a):
> Hi,
>
> we solved 4 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317223&version=12353164
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project+%3D+MCHE
+1
Le ven. 19 mai 2023 à 16:08, Michael Osipov a écrit :
> Hi,
>
> we solved 17 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317227&version=12352921
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MDEP/issues
>
> St
+1
On Fri, May 19, 2023, 16:08 Michael Osipov wrote:
> Hi,
>
> we solved 17 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317227&version=12352921
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MDEP/issues
>
> Stagin
+1
pt., 19 maj 2023, 18:28 użytkownik Slawomir Jaranowski <
s.jaranow...@gmail.com> napisał:
> +1
>
> pt., 19 maj 2023 o 16:08 Michael Osipov napisał(a):
>
> > Hi,
> >
> > we solved 17 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317227&version=12352921
>
+1
pt., 19 maj 2023 o 16:08 Michael Osipov napisał(a):
> Hi,
>
> we solved 17 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317227&version=12352921
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MDEP/issues
>
> Stag
Hi,
we solved 17 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317227&version=12352921
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/projects/MDEP/issues
Staging repo:
https://repository.apache.org/content/repositories/maven-1947/
h
3rd PR:
https://github.com/apache/maven/pull/1114
On Fri, May 19, 2023 at 3:03 PM Jeremy Landis
wrote:
> I think the warnings in general have thus far been a good thing. The
> level of plugins reacting now and people reporting issues is very clear.
> I'd suspect this to die down in next month o
Hi,
we solved 4 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317223&version=12353164
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project+%3D+MCHECKSTYLE+AND+resolution+%3D+Unresolved
Staging repo:
https://repository.a
Howdy,
so far I have PRs:
Fix for Henning case (make the message clear that it is descriptor)
https://github.com/apache/maven/pull/1112
Adding new modes https://github.com/apache/maven/pull/1113
Will see for that one as well.
T
On Fri, May 19, 2023 at 2:58 PM Jeremy Landis
wrote:
> While you
I think the warnings in general have thus far been a good thing. The level of
plugins reacting now and people reporting issues is very clear. I'd suspect
this to die down in next month or two as these flush themselves out and really
maven 3.9.x is all about journey to maven 4 so this IMO is ki
While you are at it, could you change the warnings to show just before the
final status of the build? Some projects at least in VERBOSE have so many
warnings that it makes it much harder to know the project built successfully.
ATM it's something like this.
...Status successful build...
Now a b
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
>
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
+1
On Thu, 18 May 2023 at 07:41, Slawomir Jaranowski
wrote:
>
> Hi,
>
> We solved 7 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317924&version=12346658
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%
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
29 matches
Mail list logo
