You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Tamás Cservenák <ta...@cservenak.net> on 2023/05/26 07:45:46 UTC
[HEADS UP] Upcoming Resolver and Maven releases
Howdy,
Resolver 1.9.11 is shaping:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.11
one resolver issue under scrutiny:
https://issues.apache.org/jira/browse/MRESOLVER-362
Maven 3.9.3 as well:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.3
As usual, I plan these for next week, so if anyone has anything to say,
speak up!
Thanks
T
Re: [HEADS UP] Upcoming Resolver and Maven releases
Posted by Delany <de...@gmail.com>.
Hi Tamas,
I'm still getting locking issues with maven-surefire-plugin:3.1.0
I assumed these were resolved in
https://issues.apache.org/jira/browse/MRESOLVER-346 which i believe made it
into Maven 3.9.2, so switched back to Maven 3.9.0
What was the previous default value of aether.syncContext.named.time?
30s is not long enough for my build.
Thanks,
On Fri, 26 May 2023 at 09:46, Tamás Cservenák <ta...@cservenak.net> wrote:
> Howdy,
>
> Resolver 1.9.11 is shaping:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.11
>
> one resolver issue under scrutiny:
> https://issues.apache.org/jira/browse/MRESOLVER-362
>
> Maven 3.9.3 as well:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.3
>
> As usual, I plan these for next week, so if anyone has anything to say,
> speak up!
>
> Thanks
> T
>
Re: [HEADS UP] Upcoming Resolver and Maven releases
Posted by Henning Schmiedehausen <he...@schmiedehausen.org>.
I don't care about the threads. They are fine with me. I care about the
amount of ceremony that you create that eats into developer time. If you
want to do it for yourself: feel free to do so. It is your time after all.
But you and others then turn around and say "everyone now needs to do what
I am doing and you can no longer work the way that Apache always worked".
And I object to that.
There is value in ceremony for large, gnarly, critical changes that need
discussion. And those should be approached very carefully and slowly. But
having ceremony for a non-controversial, one line change that can be backed
out easily if needed, is ceremony for ceremonies' sake.
-h
On Wed, May 31, 2023 at 4:23 AM Tamás Cservenák <ta...@cservenak.net> wrote:
> Henning,
>
> This intent of all threads (the "[HEADS UP]") that I have been creating
> since the 3.9.0 release was actually meant as a communication effort to
> users not on ML (btw, see related comm related discussions). What I usually
> do is copy the ponymail URL of the thread and post it on twitter or
> mastodon etc.
> People not on ML are still eager to be "in the loop", to get the news about
> 3.9.x just like you might be.
>
> While I understand your frustration about these threads (probably noise to
> you), please understand the intent behind these threads it as well.
>
> Thanks
> T
>
>
>
> On Sun, May 28, 2023 at 10:58 PM Henning Schmiedehausen <
> henning@schmiedehausen.org> wrote:
>
> > You spend so much time on ceremony and bureaucracy by filing tickets that
> > no one is going to pick up or read and then creating pull requests that
> at
> > best will be glanced at and then "LGTM"ed.
> >
> > This is a trivial, non-controversial change that any committer can just
> > commit. Worst case scenario, someone else is going to comment on it and
> > then it can be iterated. That is how Apache has always worked and why CTR
> > is more efficient with a small team. Every committer is explicitly
> trusted
> > to work on the code base without constant "there needs to be a ticket.
> > there needs to be a PR. there needs to be a week of discussion whether
> that
> > change is good. there needs to be "approval" or "majority agreement" by
> > some star chamber that can decide what is good for the project.
> >
> > Reserve the ceremony and discussion for the large, gnarly, controversial
> > changes that warrant discussion and where there is value in doing more
> > upfront planning. But for god's sake, stop doing ceremony for ceremony's
> > sake.
> >
> > It is a literal one-liner. - https://github.com/apache/maven/pull/1132
> >
> > -h
> >
> >
> > On Fri, May 26, 2023 at 1:24 PM Tamás Cservenák <ta...@cservenak.net>
> > wrote:
> >
> > > Howdy,
> > >
> > > good call, created https://issues.apache.org/jira/browse/MNG-7797
> > >
> > > Thanks
> > > T
> > >
> > > On Fri, May 26, 2023 at 10:09 PM Henning Schmiedehausen <
> > > henning@schmiedehausen.org> wrote:
> > >
> > > > maven 3.9.2:
> > > >
> > > > mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean
> > > > install
> > > > [...]
> > > >
> > > > current 3.9.3-SNAPSHOT:
> > > >
> > > > mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean
> > > > install
> > > > [...]
> > > >
> > > > *[WARNING] Invalid value specified for property
> > maven.plugin.validation:
> > > > 'BRIEF'. Supported values are (case insensitive): [NONE, INLINE,
> > SUMMARY,
> > > > VERBOSE]*
> > > >
> > > > You shipped "BRIEF" in 3.9.2, removing it now breaks scripts that
> added
> > > > this to the command line or the pom.
> > > >
> > > > I suggest mapping "BRIEF" to "SUMMARY".
> > > >
> > > > -h
> > > >
> > > >
> > > > On Fri, May 26, 2023 at 12:46 AM Tamás Cservenák <
> tamas@cservenak.net>
> > > > wrote:
> > > >
> > > > > Howdy,
> > > > >
> > > > > Resolver 1.9.11 is shaping:
> > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.11
> > > > >
> > > > > one resolver issue under scrutiny:
> > > > > https://issues.apache.org/jira/browse/MRESOLVER-362
> > > > >
> > > > > Maven 3.9.3 as well:
> > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.3
> > > > >
> > > > > As usual, I plan these for next week, so if anyone has anything to
> > say,
> > > > > speak up!
> > > > >
> > > > > Thanks
> > > > > T
> > > > >
> > > >
> > >
> >
>
Re: [HEADS UP] Upcoming Resolver and Maven releases
Posted by Tamás Cservenák <ta...@cservenak.net>.
Henning,
This intent of all threads (the "[HEADS UP]") that I have been creating
since the 3.9.0 release was actually meant as a communication effort to
users not on ML (btw, see related comm related discussions). What I usually
do is copy the ponymail URL of the thread and post it on twitter or
mastodon etc.
People not on ML are still eager to be "in the loop", to get the news about
3.9.x just like you might be.
While I understand your frustration about these threads (probably noise to
you), please understand the intent behind these threads it as well.
Thanks
T
On Sun, May 28, 2023 at 10:58 PM Henning Schmiedehausen <
henning@schmiedehausen.org> wrote:
> You spend so much time on ceremony and bureaucracy by filing tickets that
> no one is going to pick up or read and then creating pull requests that at
> best will be glanced at and then "LGTM"ed.
>
> This is a trivial, non-controversial change that any committer can just
> commit. Worst case scenario, someone else is going to comment on it and
> then it can be iterated. That is how Apache has always worked and why CTR
> is more efficient with a small team. Every committer is explicitly trusted
> to work on the code base without constant "there needs to be a ticket.
> there needs to be a PR. there needs to be a week of discussion whether that
> change is good. there needs to be "approval" or "majority agreement" by
> some star chamber that can decide what is good for the project.
>
> Reserve the ceremony and discussion for the large, gnarly, controversial
> changes that warrant discussion and where there is value in doing more
> upfront planning. But for god's sake, stop doing ceremony for ceremony's
> sake.
>
> It is a literal one-liner. - https://github.com/apache/maven/pull/1132
>
> -h
>
>
> On Fri, May 26, 2023 at 1:24 PM Tamás Cservenák <ta...@cservenak.net>
> wrote:
>
> > Howdy,
> >
> > good call, created https://issues.apache.org/jira/browse/MNG-7797
> >
> > Thanks
> > T
> >
> > On Fri, May 26, 2023 at 10:09 PM Henning Schmiedehausen <
> > henning@schmiedehausen.org> wrote:
> >
> > > maven 3.9.2:
> > >
> > > mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean
> > > install
> > > [...]
> > >
> > > current 3.9.3-SNAPSHOT:
> > >
> > > mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean
> > > install
> > > [...]
> > >
> > > *[WARNING] Invalid value specified for property
> maven.plugin.validation:
> > > 'BRIEF'. Supported values are (case insensitive): [NONE, INLINE,
> SUMMARY,
> > > VERBOSE]*
> > >
> > > You shipped "BRIEF" in 3.9.2, removing it now breaks scripts that added
> > > this to the command line or the pom.
> > >
> > > I suggest mapping "BRIEF" to "SUMMARY".
> > >
> > > -h
> > >
> > >
> > > On Fri, May 26, 2023 at 12:46 AM Tamás Cservenák <ta...@cservenak.net>
> > > wrote:
> > >
> > > > Howdy,
> > > >
> > > > Resolver 1.9.11 is shaping:
> > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.11
> > > >
> > > > one resolver issue under scrutiny:
> > > > https://issues.apache.org/jira/browse/MRESOLVER-362
> > > >
> > > > Maven 3.9.3 as well:
> > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.3
> > > >
> > > > As usual, I plan these for next week, so if anyone has anything to
> say,
> > > > speak up!
> > > >
> > > > Thanks
> > > > T
> > > >
> > >
> >
>
Re: [HEADS UP] Upcoming Resolver and Maven releases
Posted by Christoph Läubrich <ma...@laeubi-soft.de>.
Well the problem is that most users won't notice any "votes" or are able
to take action on it (e.g. because they can't run a custom build maven
on their CI easily).
I already have recommended that there should be a SNAPSHOT build on the
download-page with clear indication to the user to help testing these
snapshots, but for some strange ASF policy it is not allowed to promote
snapshots on the download page.
e.g. on Tycho we have quite some success with the strategy we have a
simple instructions here:
https://github.com/eclipse-tycho/tycho/wiki#getting-tycho-snapshots
and a lot of projects using at least an extra nightly-build to get
warned early if things change/break for them so most of the time we get
reports of regressions withing a few days and can often verify fixes
right after the snapshot is deployed as people simply restart their
builds and can report back if it is fixed.
Am 29.05.23 um 09:36 schrieb Romain Manni-Bucau:
> Le lun. 29 mai 2023 à 09:03, Delany <de...@gmail.com> a écrit :
>
>> Since most issues (like this one) are discovered after release, what about
>> introducing a backward compatibility policy of "second-to-last"?
>> For example, a feature is introduced (with config value BRIEF) in 3.9.2
>> Then its decided in 3.9.3 to change it to something else (SUMMARY).
>> This should be allowed since 3.9.3 is within the "cool off period".
>> If that wasn't done then from 3.9.4 the usual process of deprecation can be
>> followed to remove it (with attendant bureaucracy).
>> For the kind of developers who always update to the latest, like myself,
>> this isn't a problem.
>> I have chosen to get the latest features with the tradeoff of having to
>> deal with new issues.
>> This way the window for change is widened to include real world scenarios
>> and one settles these sorts of issues sooner.
>> Delany
>>
>
> Hi, this is what the vote is done for, if we do then you'll probably want
> to tackle people upgrading later too (so a range) or to majors too so,
> IMHO, it is just moving the issue that people don't test their build with
> the snapshots. For the cli we can surely write a command to help but will
> not solve the actual build so, still IMHO, we should just encourage people
> to test during the vote period and if they don't we can't help much except
> trying to fix unexpected regressions ASAP.
>
>
>>
>> On Sun, 28 May 2023 at 22:58, Henning Schmiedehausen <
>> henning@schmiedehausen.org> wrote:
>>
>>> You spend so much time on ceremony and bureaucracy by filing tickets that
>>> no one is going to pick up or read and then creating pull requests that
>> at
>>> best will be glanced at and then "LGTM"ed.
>>>
>>> This is a trivial, non-controversial change that any committer can just
>>> commit. Worst case scenario, someone else is going to comment on it and
>>> then it can be iterated. That is how Apache has always worked and why CTR
>>> is more efficient with a small team. Every committer is explicitly
>> trusted
>>> to work on the code base without constant "there needs to be a ticket.
>>> there needs to be a PR. there needs to be a week of discussion whether
>> that
>>> change is good. there needs to be "approval" or "majority agreement" by
>>> some star chamber that can decide what is good for the project.
>>>
>>> Reserve the ceremony and discussion for the large, gnarly, controversial
>>> changes that warrant discussion and where there is value in doing more
>>> upfront planning. But for god's sake, stop doing ceremony for ceremony's
>>> sake.
>>>
>>> It is a literal one-liner. - https://github.com/apache/maven/pull/1132
>>>
>>> -h
>>>
>>>
>>> On Fri, May 26, 2023 at 1:24 PM Tamás Cservenák <ta...@cservenak.net>
>>> wrote:
>>>
>>>> Howdy,
>>>>
>>>> good call, created https://issues.apache.org/jira/browse/MNG-7797
>>>>
>>>> Thanks
>>>> T
>>>>
>>>> On Fri, May 26, 2023 at 10:09 PM Henning Schmiedehausen <
>>>> henning@schmiedehausen.org> wrote:
>>>>
>>>>> maven 3.9.2:
>>>>>
>>>>> mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean
>>>>> install
>>>>> [...]
>>>>>
>>>>> current 3.9.3-SNAPSHOT:
>>>>>
>>>>> mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean
>>>>> install
>>>>> [...]
>>>>>
>>>>> *[WARNING] Invalid value specified for property
>>> maven.plugin.validation:
>>>>> 'BRIEF'. Supported values are (case insensitive): [NONE, INLINE,
>>> SUMMARY,
>>>>> VERBOSE]*
>>>>>
>>>>> You shipped "BRIEF" in 3.9.2, removing it now breaks scripts that
>> added
>>>>> this to the command line or the pom.
>>>>>
>>>>> I suggest mapping "BRIEF" to "SUMMARY".
>>>>>
>>>>> -h
>>>>>
>>>>>
>>>>> On Fri, May 26, 2023 at 12:46 AM Tamás Cservenák <
>> tamas@cservenak.net>
>>>>> wrote:
>>>>>
>>>>>> Howdy,
>>>>>>
>>>>>> Resolver 1.9.11 is shaping:
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.11
>>>>>>
>>>>>> one resolver issue under scrutiny:
>>>>>> https://issues.apache.org/jira/browse/MRESOLVER-362
>>>>>>
>>>>>> Maven 3.9.3 as well:
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.3
>>>>>>
>>>>>> As usual, I plan these for next week, so if anyone has anything to
>>> say,
>>>>>> speak up!
>>>>>>
>>>>>> Thanks
>>>>>> T
>>>>>>
>>>>>
>>>>
>>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [HEADS UP] Upcoming Resolver and Maven releases
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Le lun. 29 mai 2023 à 09:03, Delany <de...@gmail.com> a écrit :
> Since most issues (like this one) are discovered after release, what about
> introducing a backward compatibility policy of "second-to-last"?
> For example, a feature is introduced (with config value BRIEF) in 3.9.2
> Then its decided in 3.9.3 to change it to something else (SUMMARY).
> This should be allowed since 3.9.3 is within the "cool off period".
> If that wasn't done then from 3.9.4 the usual process of deprecation can be
> followed to remove it (with attendant bureaucracy).
> For the kind of developers who always update to the latest, like myself,
> this isn't a problem.
> I have chosen to get the latest features with the tradeoff of having to
> deal with new issues.
> This way the window for change is widened to include real world scenarios
> and one settles these sorts of issues sooner.
> Delany
>
Hi, this is what the vote is done for, if we do then you'll probably want
to tackle people upgrading later too (so a range) or to majors too so,
IMHO, it is just moving the issue that people don't test their build with
the snapshots. For the cli we can surely write a command to help but will
not solve the actual build so, still IMHO, we should just encourage people
to test during the vote period and if they don't we can't help much except
trying to fix unexpected regressions ASAP.
>
> On Sun, 28 May 2023 at 22:58, Henning Schmiedehausen <
> henning@schmiedehausen.org> wrote:
>
> > You spend so much time on ceremony and bureaucracy by filing tickets that
> > no one is going to pick up or read and then creating pull requests that
> at
> > best will be glanced at and then "LGTM"ed.
> >
> > This is a trivial, non-controversial change that any committer can just
> > commit. Worst case scenario, someone else is going to comment on it and
> > then it can be iterated. That is how Apache has always worked and why CTR
> > is more efficient with a small team. Every committer is explicitly
> trusted
> > to work on the code base without constant "there needs to be a ticket.
> > there needs to be a PR. there needs to be a week of discussion whether
> that
> > change is good. there needs to be "approval" or "majority agreement" by
> > some star chamber that can decide what is good for the project.
> >
> > Reserve the ceremony and discussion for the large, gnarly, controversial
> > changes that warrant discussion and where there is value in doing more
> > upfront planning. But for god's sake, stop doing ceremony for ceremony's
> > sake.
> >
> > It is a literal one-liner. - https://github.com/apache/maven/pull/1132
> >
> > -h
> >
> >
> > On Fri, May 26, 2023 at 1:24 PM Tamás Cservenák <ta...@cservenak.net>
> > wrote:
> >
> > > Howdy,
> > >
> > > good call, created https://issues.apache.org/jira/browse/MNG-7797
> > >
> > > Thanks
> > > T
> > >
> > > On Fri, May 26, 2023 at 10:09 PM Henning Schmiedehausen <
> > > henning@schmiedehausen.org> wrote:
> > >
> > > > maven 3.9.2:
> > > >
> > > > mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean
> > > > install
> > > > [...]
> > > >
> > > > current 3.9.3-SNAPSHOT:
> > > >
> > > > mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean
> > > > install
> > > > [...]
> > > >
> > > > *[WARNING] Invalid value specified for property
> > maven.plugin.validation:
> > > > 'BRIEF'. Supported values are (case insensitive): [NONE, INLINE,
> > SUMMARY,
> > > > VERBOSE]*
> > > >
> > > > You shipped "BRIEF" in 3.9.2, removing it now breaks scripts that
> added
> > > > this to the command line or the pom.
> > > >
> > > > I suggest mapping "BRIEF" to "SUMMARY".
> > > >
> > > > -h
> > > >
> > > >
> > > > On Fri, May 26, 2023 at 12:46 AM Tamás Cservenák <
> tamas@cservenak.net>
> > > > wrote:
> > > >
> > > > > Howdy,
> > > > >
> > > > > Resolver 1.9.11 is shaping:
> > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.11
> > > > >
> > > > > one resolver issue under scrutiny:
> > > > > https://issues.apache.org/jira/browse/MRESOLVER-362
> > > > >
> > > > > Maven 3.9.3 as well:
> > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.3
> > > > >
> > > > > As usual, I plan these for next week, so if anyone has anything to
> > say,
> > > > > speak up!
> > > > >
> > > > > Thanks
> > > > > T
> > > > >
> > > >
> > >
> >
>
Re: [HEADS UP] Upcoming Resolver and Maven releases
Posted by Delany <de...@gmail.com>.
Since most issues (like this one) are discovered after release, what about
introducing a backward compatibility policy of "second-to-last"?
For example, a feature is introduced (with config value BRIEF) in 3.9.2
Then its decided in 3.9.3 to change it to something else (SUMMARY).
This should be allowed since 3.9.3 is within the "cool off period".
If that wasn't done then from 3.9.4 the usual process of deprecation can be
followed to remove it (with attendant bureaucracy).
For the kind of developers who always update to the latest, like myself,
this isn't a problem.
I have chosen to get the latest features with the tradeoff of having to
deal with new issues.
This way the window for change is widened to include real world scenarios
and one settles these sorts of issues sooner.
Delany
On Sun, 28 May 2023 at 22:58, Henning Schmiedehausen <
henning@schmiedehausen.org> wrote:
> You spend so much time on ceremony and bureaucracy by filing tickets that
> no one is going to pick up or read and then creating pull requests that at
> best will be glanced at and then "LGTM"ed.
>
> This is a trivial, non-controversial change that any committer can just
> commit. Worst case scenario, someone else is going to comment on it and
> then it can be iterated. That is how Apache has always worked and why CTR
> is more efficient with a small team. Every committer is explicitly trusted
> to work on the code base without constant "there needs to be a ticket.
> there needs to be a PR. there needs to be a week of discussion whether that
> change is good. there needs to be "approval" or "majority agreement" by
> some star chamber that can decide what is good for the project.
>
> Reserve the ceremony and discussion for the large, gnarly, controversial
> changes that warrant discussion and where there is value in doing more
> upfront planning. But for god's sake, stop doing ceremony for ceremony's
> sake.
>
> It is a literal one-liner. - https://github.com/apache/maven/pull/1132
>
> -h
>
>
> On Fri, May 26, 2023 at 1:24 PM Tamás Cservenák <ta...@cservenak.net>
> wrote:
>
> > Howdy,
> >
> > good call, created https://issues.apache.org/jira/browse/MNG-7797
> >
> > Thanks
> > T
> >
> > On Fri, May 26, 2023 at 10:09 PM Henning Schmiedehausen <
> > henning@schmiedehausen.org> wrote:
> >
> > > maven 3.9.2:
> > >
> > > mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean
> > > install
> > > [...]
> > >
> > > current 3.9.3-SNAPSHOT:
> > >
> > > mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean
> > > install
> > > [...]
> > >
> > > *[WARNING] Invalid value specified for property
> maven.plugin.validation:
> > > 'BRIEF'. Supported values are (case insensitive): [NONE, INLINE,
> SUMMARY,
> > > VERBOSE]*
> > >
> > > You shipped "BRIEF" in 3.9.2, removing it now breaks scripts that added
> > > this to the command line or the pom.
> > >
> > > I suggest mapping "BRIEF" to "SUMMARY".
> > >
> > > -h
> > >
> > >
> > > On Fri, May 26, 2023 at 12:46 AM Tamás Cservenák <ta...@cservenak.net>
> > > wrote:
> > >
> > > > Howdy,
> > > >
> > > > Resolver 1.9.11 is shaping:
> > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.11
> > > >
> > > > one resolver issue under scrutiny:
> > > > https://issues.apache.org/jira/browse/MRESOLVER-362
> > > >
> > > > Maven 3.9.3 as well:
> > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.3
> > > >
> > > > As usual, I plan these for next week, so if anyone has anything to
> say,
> > > > speak up!
> > > >
> > > > Thanks
> > > > T
> > > >
> > >
> >
>
Re: [HEADS UP] Upcoming Resolver and Maven releases
Posted by Henning Schmiedehausen <he...@schmiedehausen.org>.
You spend so much time on ceremony and bureaucracy by filing tickets that
no one is going to pick up or read and then creating pull requests that at
best will be glanced at and then "LGTM"ed.
This is a trivial, non-controversial change that any committer can just
commit. Worst case scenario, someone else is going to comment on it and
then it can be iterated. That is how Apache has always worked and why CTR
is more efficient with a small team. Every committer is explicitly trusted
to work on the code base without constant "there needs to be a ticket.
there needs to be a PR. there needs to be a week of discussion whether that
change is good. there needs to be "approval" or "majority agreement" by
some star chamber that can decide what is good for the project.
Reserve the ceremony and discussion for the large, gnarly, controversial
changes that warrant discussion and where there is value in doing more
upfront planning. But for god's sake, stop doing ceremony for ceremony's
sake.
It is a literal one-liner. - https://github.com/apache/maven/pull/1132
-h
On Fri, May 26, 2023 at 1:24 PM Tamás Cservenák <ta...@cservenak.net> wrote:
> Howdy,
>
> good call, created https://issues.apache.org/jira/browse/MNG-7797
>
> Thanks
> T
>
> On Fri, May 26, 2023 at 10:09 PM Henning Schmiedehausen <
> henning@schmiedehausen.org> wrote:
>
> > maven 3.9.2:
> >
> > mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean
> > install
> > [...]
> >
> > current 3.9.3-SNAPSHOT:
> >
> > mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean
> > install
> > [...]
> >
> > *[WARNING] Invalid value specified for property maven.plugin.validation:
> > 'BRIEF'. Supported values are (case insensitive): [NONE, INLINE, SUMMARY,
> > VERBOSE]*
> >
> > You shipped "BRIEF" in 3.9.2, removing it now breaks scripts that added
> > this to the command line or the pom.
> >
> > I suggest mapping "BRIEF" to "SUMMARY".
> >
> > -h
> >
> >
> > On Fri, May 26, 2023 at 12:46 AM Tamás Cservenák <ta...@cservenak.net>
> > wrote:
> >
> > > Howdy,
> > >
> > > Resolver 1.9.11 is shaping:
> > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.11
> > >
> > > one resolver issue under scrutiny:
> > > https://issues.apache.org/jira/browse/MRESOLVER-362
> > >
> > > Maven 3.9.3 as well:
> > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.3
> > >
> > > As usual, I plan these for next week, so if anyone has anything to say,
> > > speak up!
> > >
> > > Thanks
> > > T
> > >
> >
>
Re: [HEADS UP] Upcoming Resolver and Maven releases
Posted by Slawomir Jaranowski <s....@gmail.com>.
Hi,
With validation=summary when only EXTERNAL issue are presents we have:
[WARNING]
[WARNING] Plugin [INTERNAL] validation issues were detected in following
plugin(s)
[WARNING]
[WARNING]
[WARNING] For more or less details, use 'maven.plugin.validation' property
with one of the values (case insensitive): [NONE, INLINE, SUMMARY, VERBOSE]
What do you think about the SUMMARY display also EXTERNAL and missing BRIEF
only INTERNAL?
pt., 26 maj 2023 o 23:03 Tamás Cservenák <ta...@cservenak.net> napisał(a):
> Draft:
> https://github.com/apache/maven-site/pull/424
>
> T
>
> On Fri, May 26, 2023, 22:23 Tamás Cservenák <ta...@cservenak.net> wrote:
>
> > Howdy,
> >
> > good call, created https://issues.apache.org/jira/browse/MNG-7797
> >
> > Thanks
> > T
> >
> > On Fri, May 26, 2023 at 10:09 PM Henning Schmiedehausen <
> > henning@schmiedehausen.org> wrote:
> >
> >> maven 3.9.2:
> >>
> >> mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean
> >> install
> >> [...]
> >>
> >> current 3.9.3-SNAPSHOT:
> >>
> >> mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean
> >> install
> >> [...]
> >>
> >> *[WARNING] Invalid value specified for property maven.plugin.validation:
> >> 'BRIEF'. Supported values are (case insensitive): [NONE, INLINE,
> SUMMARY,
> >> VERBOSE]*
> >>
> >> You shipped "BRIEF" in 3.9.2, removing it now breaks scripts that added
> >> this to the command line or the pom.
> >>
> >> I suggest mapping "BRIEF" to "SUMMARY".
> >>
> >> -h
> >>
> >>
> >> On Fri, May 26, 2023 at 12:46 AM Tamás Cservenák <ta...@cservenak.net>
> >> wrote:
> >>
> >> > Howdy,
> >> >
> >> > Resolver 1.9.11 is shaping:
> >> >
> >> >
> >>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.11
> >> >
> >> > one resolver issue under scrutiny:
> >> > https://issues.apache.org/jira/browse/MRESOLVER-362
> >> >
> >> > Maven 3.9.3 as well:
> >> >
> >> >
> >>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.3
> >> >
> >> > As usual, I plan these for next week, so if anyone has anything to
> say,
> >> > speak up!
> >> >
> >> > Thanks
> >> > T
> >> >
> >>
> >
>
--
Sławomir Jaranowski
Re: [HEADS UP] Upcoming Resolver and Maven releases
Posted by Tamás Cservenák <ta...@cservenak.net>.
Draft:
https://github.com/apache/maven-site/pull/424
T
On Fri, May 26, 2023, 22:23 Tamás Cservenák <ta...@cservenak.net> wrote:
> Howdy,
>
> good call, created https://issues.apache.org/jira/browse/MNG-7797
>
> Thanks
> T
>
> On Fri, May 26, 2023 at 10:09 PM Henning Schmiedehausen <
> henning@schmiedehausen.org> wrote:
>
>> maven 3.9.2:
>>
>> mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean
>> install
>> [...]
>>
>> current 3.9.3-SNAPSHOT:
>>
>> mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean
>> install
>> [...]
>>
>> *[WARNING] Invalid value specified for property maven.plugin.validation:
>> 'BRIEF'. Supported values are (case insensitive): [NONE, INLINE, SUMMARY,
>> VERBOSE]*
>>
>> You shipped "BRIEF" in 3.9.2, removing it now breaks scripts that added
>> this to the command line or the pom.
>>
>> I suggest mapping "BRIEF" to "SUMMARY".
>>
>> -h
>>
>>
>> On Fri, May 26, 2023 at 12:46 AM Tamás Cservenák <ta...@cservenak.net>
>> wrote:
>>
>> > Howdy,
>> >
>> > Resolver 1.9.11 is shaping:
>> >
>> >
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.11
>> >
>> > one resolver issue under scrutiny:
>> > https://issues.apache.org/jira/browse/MRESOLVER-362
>> >
>> > Maven 3.9.3 as well:
>> >
>> >
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.3
>> >
>> > As usual, I plan these for next week, so if anyone has anything to say,
>> > speak up!
>> >
>> > Thanks
>> > T
>> >
>>
>
Re: [HEADS UP] Upcoming Resolver and Maven releases
Posted by Tamás Cservenák <ta...@cservenak.net>.
Howdy,
good call, created https://issues.apache.org/jira/browse/MNG-7797
Thanks
T
On Fri, May 26, 2023 at 10:09 PM Henning Schmiedehausen <
henning@schmiedehausen.org> wrote:
> maven 3.9.2:
>
> mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean
> install
> [...]
>
> current 3.9.3-SNAPSHOT:
>
> mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean
> install
> [...]
>
> *[WARNING] Invalid value specified for property maven.plugin.validation:
> 'BRIEF'. Supported values are (case insensitive): [NONE, INLINE, SUMMARY,
> VERBOSE]*
>
> You shipped "BRIEF" in 3.9.2, removing it now breaks scripts that added
> this to the command line or the pom.
>
> I suggest mapping "BRIEF" to "SUMMARY".
>
> -h
>
>
> On Fri, May 26, 2023 at 12:46 AM Tamás Cservenák <ta...@cservenak.net>
> wrote:
>
> > Howdy,
> >
> > Resolver 1.9.11 is shaping:
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.11
> >
> > one resolver issue under scrutiny:
> > https://issues.apache.org/jira/browse/MRESOLVER-362
> >
> > Maven 3.9.3 as well:
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.3
> >
> > As usual, I plan these for next week, so if anyone has anything to say,
> > speak up!
> >
> > Thanks
> > T
> >
>
Re: [HEADS UP] Upcoming Resolver and Maven releases
Posted by Henning Schmiedehausen <he...@schmiedehausen.org>.
maven 3.9.2:
mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean
install
[...]
current 3.9.3-SNAPSHOT:
mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean
install
[...]
*[WARNING] Invalid value specified for property maven.plugin.validation:
'BRIEF'. Supported values are (case insensitive): [NONE, INLINE, SUMMARY,
VERBOSE]*
You shipped "BRIEF" in 3.9.2, removing it now breaks scripts that added
this to the command line or the pom.
I suggest mapping "BRIEF" to "SUMMARY".
-h
On Fri, May 26, 2023 at 12:46 AM Tamás Cservenák <ta...@cservenak.net>
wrote:
> Howdy,
>
> Resolver 1.9.11 is shaping:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.11
>
> one resolver issue under scrutiny:
> https://issues.apache.org/jira/browse/MRESOLVER-362
>
> Maven 3.9.3 as well:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.3
>
> As usual, I plan these for next week, so if anyone has anything to say,
> speak up!
>
> Thanks
> T
>