Re: [DISCUSS] Removal of ineffective switch for Maven 4

[Guillaume Nodet]

Le mar. 28 mai 2024 à 20:23, Maarten Mulders  a
écrit :

> Yep, that commit was over 3 years ago... Yet Maven 3.8 and 3.9 have been
> released since that date, and both version series report having those
> options - although "ineffective".
>
>
Yes, that's because the 3.x branch has been created a long time ago.


>
> The good thing is that Maven 4 does not report them. So I'll leave it at
> that.
>
>
> Maarten
>
> On 25/05/2024 14:00, Guillaume Nodet wrote:
> > I think those have been removed  3 years ago...
> >   https://issues.apache.org/jira/browse/MNG-6888
> >
> > Le ven. 24 mai 2024 à 13:10, Maarten Mulders  a
> > écrit :
> >
> >> On 24/05/2024 09:43, Michael Osipov wrote:
> >>> On 2024/05/24 07:06:45 Maarten Mulders wrote:
> >>>> Hi all,
> >>>>
> >>>> Today, I noticed Maven has an `-up` switch, for `--update-plugins`.
> The
> >>>> help text says it's ineffective, only kept for backward compatibility.
> >>>>
> >>>> With the advent of Maven 4, would this be a good moment to remove this
> >>>> switch?
> >>>
> >>> There much more of them to be killed, but before we do that we need to
> >> make sure that any of our plugins which invoke Maven never pass them,
> then
> >> we can discuss their removal.
> >>
> >> Just checked, and indeed, there are a few more listed explicitly as
> >> "ineffective":
> >>
> >> -cpu, --check-plugin-updates
> >> -npr, --no-plugin-registry
> >> -npu, --no-plugin-updates
> >> -up, --update-plugins
> >>
> >> My idea would then be to see if any of these four are used in our own
> >> code base (core as well as plugins). If there are usages, let's remove
> >> them. That should not be hard, as they don't trigger any behaviour
> >> anymore. After that, we can continue to drop them from the Maven CLI.
> >>
> >> Would that make sense?
> >>
> >>
> >> Maarten
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: dev-h...@maven.apache.org
> >>
> >>
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 

Guillaume Nodet

Re: [DISCUSS] Removal of ineffective switch for Maven 4

[Guillaume Nodet]

I think those have been removed  3 years ago...
 https://issues.apache.org/jira/browse/MNG-6888

Le ven. 24 mai 2024 à 13:10, Maarten Mulders  a
écrit :

> On 24/05/2024 09:43, Michael Osipov wrote:
> > On 2024/05/24 07:06:45 Maarten Mulders wrote:
> >> Hi all,
> >>
> >> Today, I noticed Maven has an `-up` switch, for `--update-plugins`. The
> >> help text says it's ineffective, only kept for backward compatibility.
> >>
> >> With the advent of Maven 4, would this be a good moment to remove this
> >> switch?
> >
> > There much more of them to be killed, but before we do that we need to
> make sure that any of our plugins which invoke Maven never pass them, then
> we can discuss their removal.
>
> Just checked, and indeed, there are a few more listed explicitly as
> "ineffective":
>
> -cpu, --check-plugin-updates
> -npr, --no-plugin-registry
> -npu, --no-plugin-updates
> -up, --update-plugins
>
> My idea would then be to see if any of these four are used in our own
> code base (core as well as plugins). If there are usages, let's remove
> them. That should not be hard, as they don't trigger any behaviour
> anymore. After that, we can continue to drop them from the Maven CLI.
>
> Would that make sense?
>
>
> Maarten
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 

Guillaume Nodet

Maven contributor recognition (Re: [DISCUSS] Add Hendrik Ebbers as a committer)

[Guillaume Nodet]

Tamas, Benjamin, in both your votes, you want to invite someone who has not
been very public, because you interacted with him around Maven and trust
him. Are Hendrik and Mateusz willing to become committers and be more
involved than they are ? Did you see the invitation as a way to get them
more involved in maven itself, and switch from user to dev side ?
We need to be somewhat cautious, as we may have people that have submitted
a few PRs already and who did not engage in one-to-one conversations with
PMC members and who would also deserve such status...

Which leads me to the question : do we need a more formal recognition of
Maven contributors / "power users" ? I.e. something to tell them: if you
ever need committer access (i.e. you actually want to contribute code/doc),
submit a few PRs and we'll get there.

Just some thoughts...

Le sam. 25 mai 2024 à 10:57, Guillaume Nodet  a écrit :

>
> IMHO, The point is not what kind of contributions (code or non code) a
> possible individual has done.
> IMHO, voting a committer is a trust problem.  The individual needs to
> establish some trust with the PMC.  If someone is involved in private
> conversations with a few PMC members, the others won’t be able to establish
> any kind of confidence here.  So the contributions need to be visible, so
> that all PMC members can see those.
> And I agree the bar should be as low as possible.
> I also think non code contribution is fine, but it has to be doc, if not
> code.  There’s no real need to have committer karma if you don’t need to it
> to commit…
>
> 
> Guillaume Nodet
>
>
>
> Le sam. 25 mai 2024 à 03:48, Olivier Lamy  a écrit :
>
>> Hi,
>> I would agree here with Maarten.
>>
>> @Tamas the discussion was not about "no code contribution" but about
>> at least community contributions (mailing list or Jira issues)
>> That's why I asked for Jira id but I could find only on issue and
>> nothing on mailing list. (that's why I don't understand your "a
>> valuable source of latest Maven release verifications and bugfix
>> validations.")
>>
>> I'm not against low-level contribution (not code is fine such only in
>> documentation or recording issues in Jira), but there must be at least
>> a low level of such involvement.
>>
>>
>> On Fri, 24 May 2024 at 21:03, Maarten Mulders 
>> wrote:
>> >
>> > Hi everyone,
>> >
>> >
>> > As this is a discussion thread, I will refrain from issuing a vote and
>> > only share my thoughts.
>> >
>> >
>> >
>> > While I absolutely welcome having new committers, I am a bit in doubt in
>> > this case, just as much as I was in the case that Tamás refers to. It
>> > feels odd to not invite one person as a committer because they did not
>> > contribute code, and invite somebody else who has just as few code
>> > contributions. I think in similar situations, we should draw one line.
>> >
>> >
>> >
>> > As for people that mainly contribute other things than code, I am not
>> > sure we should make them a committer. This is not because I think code
>> > contributions are better than non-code contributions! My doubt is this:
>> > when we appoint somebody a committer, that person can make changes to
>> > plugins without submitting patches or pull requests by directly pushing
>> > to the 'master' branch. I feel that it's a bit "risky" to grant people
>> > that option when we haven't seen much code contributions from their
>> > side. How would we ensure the (code) quality of the plugins?
>> >
>> > As said before, I see a lot of value in contributions that are not code.
>> > Thinking out loud: can't we give people in this situation an Apache ID
>> > without the possibility to push code without review?
>> >
>> >
>> >
>> > Back to the original question. The message says that Hendrik works
>> > closely with a lot of people, including myself. Unfortunately I cannot
>> > attest for his contributions. I'm not saying he didn't contribute
>> > anything, it's just that I am not aware of it and cannot judge the
>> > quality of his contributions.
>> >
>> >
>> > Thanks,
>> >
>> >
>> > Maarten
>> >
>> >
>> > On 24/05/2024 12:08, Tamás Cservenák wrote:
>> > > +1
>> > >
>> > > Nota bene:
>> > > I started previously a similar vote, also for a dev w/o direct code
>> > > contributions, but that vote was canceled as he had "no code
&g

Re: [VOTE] Release Apache Maven 3.9.7

[Guillaume Nodet]

+1

Le mer. 22 mai 2024 à 12:10, Tamás Cservenák  a écrit :

> Howdy,
>
> We solved 21 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12353964
>
> 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://repository.apache.org/content/repositories/maven-2125/
>
> Dev dist directory (binary bundles updated):
> https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.7/
>
> Source release checksums:
> apache-maven-3.9.7-src.tar.gz.sha512
>
> a3c211ce683afbde9c4becf8b32397d14d3e7d8e8261094da037dcf27a697a93134440e055e7a9e7e26af2db543d4d9c4e7b0296560f5193df7ba90b9a68d1d1
>
> apache-maven-3.9.7-src.zip.sha512
>
> cdd8249807e251d07c613a65120058993e47a4cbf7f6dbda8599c7ca7ab4ed3fedc727e651f43cba0e9b0d604055c1106c1243be64a1d52c5ddf72dbec5e65dc
>
> Staged site:
> https://maven.apache.org/ref/3-LATEST/
>
> Draft for release notes:
> https://github.com/apache/maven-site/pull/521
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72h
>
> [ ] +1
> [ ] +0
> [ ] -1
>


-- 

Guillaume Nodet

Re: [VOTE] Release Apache Maven 4.0.0-beta-3

[Guillaume Nodet]

The main (only ?) reason is that I always forget to create a branch before
releasing.
So master contains beta-2. Or should I rewrite history and force push ? Or
we’d end up with two commits for beta-1 (but a single tag obviously).
If we agree on a mechanism, we should update the release process
accordingly, as I’m blindly following it (hence I forget to create a
branch).

Guillaume


Le mer. 22 mai 2024 à 20:32, Romain Manni-Bucau  a
écrit :

> Hi Guillaume,
>
> Why isnt it beta1 - I know but we shouldn't burn version even in
> alpha/beta, every time it makes noise we can't justify technically :(?
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>
>
> Le mer. 22 mai 2024 à 17:12, Guillaume Nodet  a écrit :
>
> > This is a vote to release Apache Maven 4.0.0-beta-3, as I've cut another
> > release to fix blocking issues found in beta-2.
> >
> >
> > We solved 25 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12354634
> >
> > There are still some issues in JIRA:
> > https://issues.apache.org/jira/projects/MNG/issues
> >
> > Release candidates:
> > https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-beta-3/
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/maven-2126/
> >
> > Source release SHA512:
> > - apache-maven-4.0.0-beta-3-src.zip
> >
> >
> 4125acba32218e341b34c1bbe7700f5aa71947fd1a6a5d418825822099800e3b798a5300eaf711e0709866b7e5fc6fee323515af18d8ab25d7eaac034d72b1c6
> > - apache-maven-4.0.0-beta-3-src.tar.gz
> >
> >
> 8ca063a72fdacbcbe4afc33fc46e6c8920327092d11f3d8a77723ce995c3e24d1e8413cce3d5bc59a47657316834bfb9d4706d8bdffa5da5e147bcb404381808
> >
> > Staging site:
> > https://maven.apache.org/ref/4-LATEST/
> >
> > Guide to testing staged releases:
> > https://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > The vote is open for at least 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > --
> > Guillaume Nodet
> >
>

[CANCEL] [VOTE] Release Apache Maven 4.0.0-beta-2

[Guillaume Nodet]

Cancelling this vote.

Le lun. 13 mai 2024 à 19:40, Guillaume Nodet  a écrit :

> I've cut another release after having fixed a bug in the consumer pom
> creation.
>
> This is a vote to release Apache Maven 4.0.0-beta-1.
>
> We solved 21 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=
> 12354392
> <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12354392>
>
> There are still some issues in JIRA:
> https://issues.apache.org/jira/projects/MNG/issues
>
> Release candidates:
> https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-beta-2/
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2117/
>
> Source release SHA512:
> - apache-maven-4.0.0-beta-1-src.zip
>
>
> 0dff19216028ed7ab15914795c62a2a3247b9f45daedfd0db88266edecf97f16c888c7aac501b6b2d9373e03c828e9ba30f9837cfaafd9a4f32b04fa0776e0d3
> - apache-maven-4.0.0-beta-1-src.tar.gz
>
>
> 04df9d340081fa5cc4c840fee4bbed0d65d2d622e9cdbc0a713438a104933485f22d31bf4b35ce695913b790cf10f11f8f31ce73e0a796debfe7fc99268d9701
>
> Staging site:
> https://maven.apache.org/ref/4-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> The vote is open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> --
> 
> Guillaume Nodet
>
>

-- 

Guillaume Nodet

[VOTE] Release Apache Maven 4.0.0-beta-3

[Guillaume Nodet]

This is a vote to release Apache Maven 4.0.0-beta-3, as I've cut another
release to fix blocking issues found in beta-2.


We solved 25 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12354634

There are still some issues in JIRA:
https://issues.apache.org/jira/projects/MNG/issues

Release candidates:
https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-beta-3/

Staging repository:
https://repository.apache.org/content/repositories/maven-2126/

Source release SHA512:
- apache-maven-4.0.0-beta-3-src.zip
4125acba32218e341b34c1bbe7700f5aa71947fd1a6a5d418825822099800e3b798a5300eaf711e0709866b7e5fc6fee323515af18d8ab25d7eaac034d72b1c6
- apache-maven-4.0.0-beta-3-src.tar.gz
8ca063a72fdacbcbe4afc33fc46e6c8920327092d11f3d8a77723ce995c3e24d1e8413cce3d5bc59a47657316834bfb9d4706d8bdffa5da5e147bcb404381808

Staging site:
https://maven.apache.org/ref/4-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

The vote is open for at least 72 hours.

[ ] +1
[ ] +0
[ ] -1

--
Guillaume Nodet

Re: Trying to test the reworked compiler plugin

[Guillaume Nodet]

And
https://github.com/Geomatys/maven/commit/5165ca60a1b44cd2a376cd1bfe48f558a2cbd54f
looks interesting, as the interface was introduced in 4.x branch, so no
need to keep it as it's not used anymore.  Feel free to create a proper PR.

Le mar. 21 mai 2024 à 11:15, Guillaume Nodet  a écrit :

>
>
> Le lun. 20 mai 2024 à 11:37, Tamás Cservenák  a
> écrit :
>
>> Howdy,
>>
>> maven-plugin-tools: We agreed with Guillaume to split it: instead of
>> mvn4, master will be "maven 4" and we will introduce a maven-3.x branch for
>> Maven3 support. Currently the master was meant to support both (maven3 and
>> maven4 plugins), but it proved problematic, hence the split. A plugin
>> cannot be both anyway, it is this or that hence the user can choose which
>> version, 3.x or 4.x wants to use.
>> plugin-testing: AFAIK, same stands here, due huge difference how those
>> operate (maven-core vs new maven API).
>>
>> This is all yet to be done.
>>
>> @Guillaume Nodet  ping
>>
>
> I'm trying to fix the remaining issues to release beta.  Once that's done,
> we can upgrade the m-plugin-p and m-plugin-tools to beta.
> And yes, we should remove the `mvn4` branches from those 2 components.
>
>
>>
>> Thanks
>> T
>>
>> On Sat, May 18, 2024 at 1:44 PM Martin Desruisseaux <
>> martin.desruisse...@geomatys.com> wrote:
>>
>>> Hello all
>>>
>>> I'm trying to run the tests on the reworked compiler plugin for Maven 4,
>>> but execution is having an issue with Maven dependency injection. Before
>>> to give more details, I would like to check if I'm up to date.
>>>
>>> Three months ago, I was told to use the following branches:
>>>
>>>   * Maven core from https://github.com/apache/maven
>>>   * Plugin tools from
>>> https://github.com/apache/maven-plugin-tools/pull/242
>>>   * Plugin testing from
>>> https://github.com/apache/maven-plugin-testing/pull/39
>>>   * Compiler from
>>> https://github.com/apache/maven-compiler-plugin/pull/147
>>>
>>> I have kept my "Maven core" clone up-to-date. Other pull requests seem
>>> to have no new commits, but the master branches on which they are based
>>> have been updated. I wanted to search if more up-to-date Maven 4
>>> branches exist somewhere else, but the situation is a bit confusing:
>>>
>>>   * There is "mvn4" branches on many plugin repositories, but they are 2
>>> years old. Would it be possible to either update them or delete them?
>>>   * I found no code other than above pull requests that I could identify
>>> as designed for Maven 4. If the above pull requests are not ready to
>>> be merged, would it be possible to turn them as branches on Maven
>>> repositories, possibly replacing the previous "mvn4" branches? The
>>> goal is to make easy to find the most up-to-date code.
>>>
>>> If the above pull requests are the most up-to-date code for Maven 4,
>>> would it be possible to update them to "4.0.0-beta-2"? I tried to do
>>> that on my side, but got some difficulties. First, it seems that the
>>> following changes must be applied on Maven core for making possible to
>>> compile the plugins:
>>>
>>>   *
>>> https://github.com/Geomatys/maven/commit/5165ca60a1b44cd2a376cd1bfe48f558a2cbd54f
>>>
>>> I have not created a pull request for the above because I'm not sure if
>>> I understood the issue correctly. Next, after changing the dependencies
>>> to "4.0.0-beta-3-SNAPSHOT", the build of "maven-plugin-testing-harness"
>>> has the following test failure:
>>>
>>> java.lang.IllegalArgumentException: session is null
>>> at org.apache.maven.internal.impl.Utils.cast(Utils.java:44)
>>> at
>>> org.apache.maven.internal.impl.InternalSession.from(InternalSession.java:45)
>>> at
>>> org.apache.maven.project.DefaultProjectBuilder$BuildSession.(DefaultProjectBuilder.java:291)
>>> at
>>> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:135)
>>> at
>>> org.apache.maven.plugin.testing.MojoRule.readMavenProject(MojoRule.java:276)
>>> at
>>> org.apache.maven.plugin.testing.MojoRule.lookupConfiguredMojo(MojoRule.java:296)
>>> at
>>> org.apache.maven.plugin.testing.MojoRuleTest.testLookupInitializedMojo(MojoRuleTest.java:165)
>>>
>>> The code prod

Re: Trying to test the reworked compiler plugin

[Guillaume Nodet]

Le lun. 20 mai 2024 à 11:37, Tamás Cservenák  a écrit :

> Howdy,
>
> maven-plugin-tools: We agreed with Guillaume to split it: instead of mvn4,
> master will be "maven 4" and we will introduce a maven-3.x branch for
> Maven3 support. Currently the master was meant to support both (maven3 and
> maven4 plugins), but it proved problematic, hence the split. A plugin
> cannot be both anyway, it is this or that hence the user can choose which
> version, 3.x or 4.x wants to use.
> plugin-testing: AFAIK, same stands here, due huge difference how those
> operate (maven-core vs new maven API).
>
> This is all yet to be done.
>
> @Guillaume Nodet  ping
>

I'm trying to fix the remaining issues to release beta.  Once that's done,
we can upgrade the m-plugin-p and m-plugin-tools to beta.
And yes, we should remove the `mvn4` branches from those 2 components.


>
> Thanks
> T
>
> On Sat, May 18, 2024 at 1:44 PM Martin Desruisseaux <
> martin.desruisse...@geomatys.com> wrote:
>
>> Hello all
>>
>> I'm trying to run the tests on the reworked compiler plugin for Maven 4,
>> but execution is having an issue with Maven dependency injection. Before
>> to give more details, I would like to check if I'm up to date.
>>
>> Three months ago, I was told to use the following branches:
>>
>>   * Maven core from https://github.com/apache/maven
>>   * Plugin tools from
>> https://github.com/apache/maven-plugin-tools/pull/242
>>   * Plugin testing from
>> https://github.com/apache/maven-plugin-testing/pull/39
>>   * Compiler from
>> https://github.com/apache/maven-compiler-plugin/pull/147
>>
>> I have kept my "Maven core" clone up-to-date. Other pull requests seem
>> to have no new commits, but the master branches on which they are based
>> have been updated. I wanted to search if more up-to-date Maven 4
>> branches exist somewhere else, but the situation is a bit confusing:
>>
>>   * There is "mvn4" branches on many plugin repositories, but they are 2
>> years old. Would it be possible to either update them or delete them?
>>   * I found no code other than above pull requests that I could identify
>> as designed for Maven 4. If the above pull requests are not ready to
>> be merged, would it be possible to turn them as branches on Maven
>> repositories, possibly replacing the previous "mvn4" branches? The
>> goal is to make easy to find the most up-to-date code.
>>
>> If the above pull requests are the most up-to-date code for Maven 4,
>> would it be possible to update them to "4.0.0-beta-2"? I tried to do
>> that on my side, but got some difficulties. First, it seems that the
>> following changes must be applied on Maven core for making possible to
>> compile the plugins:
>>
>>   *
>> https://github.com/Geomatys/maven/commit/5165ca60a1b44cd2a376cd1bfe48f558a2cbd54f
>>
>> I have not created a pull request for the above because I'm not sure if
>> I understood the issue correctly. Next, after changing the dependencies
>> to "4.0.0-beta-3-SNAPSHOT", the build of "maven-plugin-testing-harness"
>> has the following test failure:
>>
>> java.lang.IllegalArgumentException: session is null
>> at org.apache.maven.internal.impl.Utils.cast(Utils.java:44)
>> at
>> org.apache.maven.internal.impl.InternalSession.from(InternalSession.java:45)
>> at
>> org.apache.maven.project.DefaultProjectBuilder$BuildSession.(DefaultProjectBuilder.java:291)
>> at
>> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:135)
>> at
>> org.apache.maven.plugin.testing.MojoRule.readMavenProject(MojoRule.java:276)
>> at
>> org.apache.maven.plugin.testing.MojoRule.lookupConfiguredMojo(MojoRule.java:296)
>> at
>> org.apache.maven.plugin.testing.MojoRuleTest.testLookupInitializedMojo(MojoRuleTest.java:165)
>>
>> The code producing the null value is:
>>
>> static InternalSession
>> from(org.eclipse.aether.RepositorySystemSession session) {
>>  return cast(InternalSession.class,
>> session.getData().get(InternalSession.class), "session");
>> }
>>
>> It seems related to the issue that I'm having with the compiler plugin,
>> where the following annotated field:
>>
>> /**
>>   * The current build session instance.
>>   */
>> @Inject
>> protected Session session;
>>
>> Stay null during the test execution. Is there any advise about how to
>> proceed? For me, the ideal would be to have the "mvn4" branches in at
>> least "maven-plugin-tools", "apache/maven-plugin-testing" and
>> "maven-compiler-plugin" replaced by up-to-date branches (I wlll take
>> care of rebasing my work on an up-to-date compiler branch).
>>
>>  Thanks,
>>
>>  Martin
>>
>>

-- 

Guillaume Nodet

[VOTE] Release Apache Maven 4.0.0-beta-2

[Guillaume Nodet]

I've cut another release after having fixed a bug in the consumer pom
creation.

This is a vote to release Apache Maven 4.0.0-beta-1.

We solved 21 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=
12354392
<https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12354392>

There are still some issues in JIRA:
https://issues.apache.org/jira/projects/MNG/issues

Release candidates:
https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-beta-2/

Staging repository:
https://repository.apache.org/content/repositories/maven-2117/

Source release SHA512:
- apache-maven-4.0.0-beta-1-src.zip

0dff19216028ed7ab15914795c62a2a3247b9f45daedfd0db88266edecf97f16c888c7aac501b6b2d9373e03c828e9ba30f9837cfaafd9a4f32b04fa0776e0d3
- apache-maven-4.0.0-beta-1-src.tar.gz

04df9d340081fa5cc4c840fee4bbed0d65d2d622e9cdbc0a713438a104933485f22d31bf4b35ce695913b790cf10f11f8f31ce73e0a796debfe7fc99268d9701

Staging site:
https://maven.apache.org/ref/4-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

The vote is open for at least 72 hours.

[ ] +1
[ ] +0
[ ] -1

-- 
----
Guillaume Nodet

[CANCEL] [VOTE] Release Apache Maven 4.0.0-beta-1

[Guillaume Nodet]

I need to cancel this release.
It's still affected by a problem when building consumer POM with the
interaction of the flatten-m-p (or any plugin rewriting the original POM).
I'll recut another release tomorrow.

Guillaume

Le lun. 13 mai 2024 à 17:04, Guillaume Nodet  a écrit :

>
> This is a vote to release Apache Maven 4.0.0-beta-1.
>
> We solved 21 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=
> 12354392
>
> There are still some issues in JIRA:
> https://issues.apache.org/jira/projects/MNG/issues
>
> Release candidates:
> https://dist.apache.org/repos/dist/dev/maven/maven-4/beta-1/
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2116/
>
> Source release SHA512:
> - apache-maven-4.0.0-beta-1-src.zip
>
>
> 2f88553334405b536a0278f25ff694ddb9cd80fca56ce71e63114f8dbd3361b96100056e236f97c5b1330fd7191aaace298b91c1b1ed85b04096f71d4b158500
> - apache-maven-4.0.0-beta-1-src.tar.gz
>
>
> 9c6a828e2aa9fcced8dc209f741502d831708ae12458c1a213d99b6981347405e44042ba028ad39b5916fd92edd633dd3e9bec4968b988f1da8fa2ac8f36
>
> Staging site:
> https://maven.apache.org/ref/4-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> The vote is open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> --
> 
> Guillaume Nodet
>
>

-- 

Guillaume Nodet

[VOTE] Release Apache Maven 4.0.0-beta-1

[Guillaume Nodet]

This is a vote to release Apache Maven 4.0.0-beta-1.

We solved 21 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=
12354392

There are still some issues in JIRA:
https://issues.apache.org/jira/projects/MNG/issues

Release candidates:
https://dist.apache.org/repos/dist/dev/maven/maven-4/beta-1/

Staging repository:
https://repository.apache.org/content/repositories/maven-2116/

Source release SHA512:
- apache-maven-4.0.0-beta-1-src.zip

2f88553334405b536a0278f25ff694ddb9cd80fca56ce71e63114f8dbd3361b96100056e236f97c5b1330fd7191aaace298b91c1b1ed85b04096f71d4b158500
- apache-maven-4.0.0-beta-1-src.tar.gz

9c6a828e2aa9fcced8dc209f741502d831708ae12458c1a213d99b6981347405e44042ba028ad39b5916fd92edd633dd3e9bec4968b988f1da8fa2ac8f36

Staging site:
https://maven.apache.org/ref/4-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

The vote is open for at least 72 hours.

[ ] +1
[ ] +0
[ ] -1

-- 

Guillaume Nodet

Re: [DISCUSS] Maven Plugin SPI

[Guillaume Nodet]

I wonder if we should use proper package versioning (using
Specification-Title and Specification-Version manifest attributes, or any
other better mechanism)  and consider the artifact version as a marketing
version which should not carry any real semantics.

Guillaume

Le lun. 6 mai 2024 à 15:04, Tamás Cservenák  a écrit :

> Sure,
>
> Again, I am fine with having SPI artifact next to plugin consumer artifact.
> All I wanted to prevent is having tens or more versions of SPI artifact
> released, while in fact they are "same thing".
>
> T
>
> On Mon, May 6, 2024 at 3:03 PM Guillaume Nodet  wrote:
>
> > Le lun. 6 mai 2024 à 14:38, Tamás Cservenák  a
> écrit
> > :
> >
> > > lapsus: as in maven-core and maven-model SHOULD NOT share the same
> > release
> > > lifecycle. They DO currently.
> > > Which implies that we have as many maven-model artifacts released so
> far
> > as
> > > many maven, but many of them are binary equivalent to each other.
> > >
> >
> > What's the drawback with that ? It's much easier to handle for both the
> > developper side
> > and for the consumer side (they only have to upgrade a single version
> > instead of two).
> >
> > I'm quite on the opposite side, and I'd much rather simplify our release
> > cycles rather
> > than going with one repo per jar...
> >
> >
> > > That's all I wanted to prevent. Am fine with having SPI next to the
> > plugin
> > > as well...
> > >
> > > T
> > >
> > > On Mon, May 6, 2024 at 2:36 PM Tamás Cservenák 
> > > wrote:
> > >
> > > > Pretty much the same story as Maven models vs Maven "core"
> (maven-core
> > in
> > > > 3.x or api-imple in 4) they don't share the same release
> lifecycle.
> > > >
> > > > SPI is not to be changed often, while we do patch releases of the
> > > plugins.
> > > > Am not saying we cannot keep SPI along with Plugins, I am just saying
> > > that
> > > > it's pointless: we will have many releases of the same thing.
> > > >
> > > > On Mon, May 6, 2024 at 2:31 PM Guillaume Nodet 
> > > wrote:
> > > >
> > > >> Le lun. 6 mai 2024 à 14:29, Tamás Cservenák  a
> > > >> écrit :
> > > >>
> > > >> > Howdy,
> > > >> >
> > > >> > IIUC you have a problem with designated G?
> > > >> > As if so, that is really irrelevant. Point is that SPI cannot
> reside
> > > >> with
> > > >> > Plugin, as they share totally different release cycles.
> > > >> >
> > > >>
> > > >> Why ?
> > > >>
> > > >>
> > > >> >
> > > >> > Second, you mention a plugin dep, that is hence available in the
> > same
> > > >> scope
> > > >> > as the plugin itself...  which is obviously not enough in some
> > cases.
> > > >> >
> > > >> > T
> > > >> >
> > > >> > On Mon, May 6, 2024 at 2:25 PM Romain Manni-Bucau <
> > > >> rmannibu...@gmail.com>
> > > >> > wrote:
> > > >> >
> > > >> > > Hi Tamas,
> > > >> > >
> > > >> > > I kind of fail to see why org.apache.maven.maven-plugin-spi
> makes
> > > >> sense
> > > >> > > instead of org.apache.maven.plugins.$pluginArtifact-spi ?
> > > >> > > My understanding is that we already have that since any plugin
> can
> > > >> > define a
> > > >> > > specific SPI in its code and get it injected from a plugin dep
> > using
> > > >> its
> > > >> > >  block - exactly like shade plugin references its
> > > >> > > transformers to be concrete.
> > > >> > > So for me nothing to create nor modify to get an old feature.
> > > >> > >
> > > >> > > Romain Manni-Bucau
> > > >> > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > >> > > <https://rmannibucau.metawerx.net/> | Old Blog
> > > >> > > <http://rmannibucau.wordpress.com> | Github <
> > > >> > > https://github.com/rmannibucau> |
> > > >> > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> > > >> > &g

Re: [DISCUSS] Maven Plugin SPI

[Guillaume Nodet]

Le lun. 6 mai 2024 à 14:38, Tamás Cservenák  a écrit :

> lapsus: as in maven-core and maven-model SHOULD NOT share the same release
> lifecycle. They DO currently.
> Which implies that we have as many maven-model artifacts released so far as
> many maven, but many of them are binary equivalent to each other.
>

What's the drawback with that ? It's much easier to handle for both the
developper side
and for the consumer side (they only have to upgrade a single version
instead of two).

I'm quite on the opposite side, and I'd much rather simplify our release
cycles rather
than going with one repo per jar...


> That's all I wanted to prevent. Am fine with having SPI next to the plugin
> as well...
>
> T
>
> On Mon, May 6, 2024 at 2:36 PM Tamás Cservenák 
> wrote:
>
> > Pretty much the same story as Maven models vs Maven "core" (maven-core in
> > 3.x or api-imple in 4) they don't share the same release lifecycle.
> >
> > SPI is not to be changed often, while we do patch releases of the
> plugins.
> > Am not saying we cannot keep SPI along with Plugins, I am just saying
> that
> > it's pointless: we will have many releases of the same thing.
> >
> > On Mon, May 6, 2024 at 2:31 PM Guillaume Nodet 
> wrote:
> >
> >> Le lun. 6 mai 2024 à 14:29, Tamás Cservenák  a
> >> écrit :
> >>
> >> > Howdy,
> >> >
> >> > IIUC you have a problem with designated G?
> >> > As if so, that is really irrelevant. Point is that SPI cannot reside
> >> with
> >> > Plugin, as they share totally different release cycles.
> >> >
> >>
> >> Why ?
> >>
> >>
> >> >
> >> > Second, you mention a plugin dep, that is hence available in the same
> >> scope
> >> > as the plugin itself...  which is obviously not enough in some cases.
> >> >
> >> > T
> >> >
> >> > On Mon, May 6, 2024 at 2:25 PM Romain Manni-Bucau <
> >> rmannibu...@gmail.com>
> >> > wrote:
> >> >
> >> > > Hi Tamas,
> >> > >
> >> > > I kind of fail to see why org.apache.maven.maven-plugin-spi makes
> >> sense
> >> > > instead of org.apache.maven.plugins.$pluginArtifact-spi ?
> >> > > My understanding is that we already have that since any plugin can
> >> > define a
> >> > > specific SPI in its code and get it injected from a plugin dep using
> >> its
> >> > >  block - exactly like shade plugin references its
> >> > > transformers to be concrete.
> >> > > So for me nothing to create nor modify to get an old feature.
> >> > >
> >> > > Romain Manni-Bucau
> >> > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> >> > > <https://rmannibucau.metawerx.net/> | Old Blog
> >> > > <http://rmannibucau.wordpress.com> | Github <
> >> > > https://github.com/rmannibucau> |
> >> > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> >> > > <
> >> > >
> >> >
> >>
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >> > > >
> >> > >
> >> > >
> >> > > Le lun. 6 mai 2024 à 14:08, Tamás Cservenák  a
> >> > écrit
> >> > > :
> >> > >
> >> > > > Howdy,
> >> > > >
> >> > > > I'd like to create a new ASF Maven git repo "maven-plugin-spi".
> >> > > >
> >> > > > This repository would hold SPIs as explained here
> >> > > >
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+Plugin+SPI
> >> > > >
> >> > > > Designated G: "org.apache.maven.maven-plugin-spi"
> >> > > >
> >> > > > For now, we have two candidates to apply SPI pattern:
> >> > > > * maven-deploy-plugin (yet to be added)
> >> > > > * maven-gpg-plugin (already have it, but in unusable form, as it
> >> does
> >> > not
> >> > > > follow pattern from wiki)
> >> > > >
> >> > > > Example GAs:
> >> > > > org.apache.maven.maven-plugin-spi:maven-deploy-spi
> >> > > > org.apache.maven.maven-plugin-spi:maven-gpg-spi
> >> > > >
> >> > > > Thanks
> >> > > > T
> >> > > >
> >> > >
> >> >
> >>
> >>
> >> --
> >> 
> >> Guillaume Nodet
> >>
> >
>


-- 

Guillaume Nodet

Re: [DISCUSS] Maven Plugin SPI

[Guillaume Nodet]

Le lun. 6 mai 2024 à 14:29, Tamás Cservenák  a écrit :

> Howdy,
>
> IIUC you have a problem with designated G?
> As if so, that is really irrelevant. Point is that SPI cannot reside with
> Plugin, as they share totally different release cycles.
>

Why ?


>
> Second, you mention a plugin dep, that is hence available in the same scope
> as the plugin itself...  which is obviously not enough in some cases.
>
> T
>
> On Mon, May 6, 2024 at 2:25 PM Romain Manni-Bucau 
> wrote:
>
> > Hi Tamas,
> >
> > I kind of fail to see why org.apache.maven.maven-plugin-spi makes sense
> > instead of org.apache.maven.plugins.$pluginArtifact-spi ?
> > My understanding is that we already have that since any plugin can
> define a
> > specific SPI in its code and get it injected from a plugin dep using its
> >  block - exactly like shade plugin references its
> > transformers to be concrete.
> > So for me nothing to create nor modify to get an old feature.
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://rmannibucau.metawerx.net/> | Old Blog
> > <http://rmannibucau.wordpress.com> | Github <
> > https://github.com/rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> > <
> >
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> > >
> >
> >
> > Le lun. 6 mai 2024 à 14:08, Tamás Cservenák  a
> écrit
> > :
> >
> > > Howdy,
> > >
> > > I'd like to create a new ASF Maven git repo "maven-plugin-spi".
> > >
> > > This repository would hold SPIs as explained here
> > > https://cwiki.apache.org/confluence/display/MAVEN/Maven+Plugin+SPI
> > >
> > > Designated G: "org.apache.maven.maven-plugin-spi"
> > >
> > > For now, we have two candidates to apply SPI pattern:
> > > * maven-deploy-plugin (yet to be added)
> > > * maven-gpg-plugin (already have it, but in unusable form, as it does
> not
> > > follow pattern from wiki)
> > >
> > > Example GAs:
> > > org.apache.maven.maven-plugin-spi:maven-deploy-spi
> > > org.apache.maven.maven-plugin-spi:maven-gpg-spi
> > >
> > > Thanks
> > > T
> > >
> >
>


-- 

Guillaume Nodet

Re: [DISCUSS] Maven Plugin SPI

[Guillaume Nodet]

I also don't really see the value of having all SPI in a single repo.
It seems easier to have each SPI inside the repository of each maven plugin
instead.

Le lun. 6 mai 2024 à 14:25, Romain Manni-Bucau  a
écrit :

> Hi Tamas,
>
> I kind of fail to see why org.apache.maven.maven-plugin-spi makes sense
> instead of org.apache.maven.plugins.$pluginArtifact-spi ?
> My understanding is that we already have that since any plugin can define a
> specific SPI in its code and get it injected from a plugin dep using its
>  block - exactly like shade plugin references its
> transformers to be concrete.
> So for me nothing to create nor modify to get an old feature.
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>
>
> Le lun. 6 mai 2024 à 14:08, Tamás Cservenák  a écrit
> :
>
> > Howdy,
> >
> > I'd like to create a new ASF Maven git repo "maven-plugin-spi".
> >
> > This repository would hold SPIs as explained here
> > https://cwiki.apache.org/confluence/display/MAVEN/Maven+Plugin+SPI
> >
> > Designated G: "org.apache.maven.maven-plugin-spi"
> >
> > For now, we have two candidates to apply SPI pattern:
> > * maven-deploy-plugin (yet to be added)
> > * maven-gpg-plugin (already have it, but in unusable form, as it does not
> > follow pattern from wiki)
> >
> > Example GAs:
> > org.apache.maven.maven-plugin-spi:maven-deploy-spi
> > org.apache.maven.maven-plugin-spi:maven-gpg-spi
> >
> > Thanks
> > T
> >
>


-- 

Guillaume Nodet

Re: Quo Vadis Maven?

[Guillaume Nodet]

I'd like to release beta-1 next week.
Maven Daemon is ready to be upgrade to it with
https://github.com/apache/maven-mvnd/pull/974

Tamás, what's your plan regarding the two remaining issues:
 * https://issues.apache.org/jira/browse/MNG-8041
 * https://issues.apache.org/jira/browse/MNG-8073

Cheers,
Guillaume

Le mar. 23 avr. 2024 à 23:12, Tamás Cservenák  a
écrit :

> Howdy,
>
> This is just a short newsflash about upcoming planned releases related to
> Maven.
>
> Recently we got a huge spike in plugin releases, with various fixes and
> improvements. I will not enumerate all of them here, just use `mvn
> versions:display-plugin-updates` to pick them up ;)
> (and more plugins to come).
>
> What I do want to share is about our upcoming Maven releases...
>
> Maven 3.9.7 is nearing (read: coming soon), and will have an important
> Resolver update and other important fixes. Most importantly, the file-locks
> are getting nice improvement (feedback VERY welcome).
>
> Maven 3.9.7 issues:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.7
>
> Resolver 1.9.19 issues (mostly bug fixes):
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.19
>
> At the same time, we plan to release Maven Daemon (m39) as well, to have it
> aligned with Maven 3,9,7: with many bug fixes and improvements/alignments
> to "how Maven 3 behave". Our goal is to make the two (mvn and mvnd)
> interchangeable on workstations.
>
> Next, Maven 4 is turning beta, so the next release will be beta1! And
> again, same thing for Maven Damon (m40), we will have a release that will
> include Maven 4 beta-1.
>
> Maven 4 beta-1
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%204.0.0-beta-1
>
> Resolver 2.0.0 (currently alpha-11, will become beta after Maven4 beta-1
> release):
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%202.0.0-alpha-11
>
> Keep your eyes on our upcoming releases,
> and have fun!
> - The Apache Maven team
>


-- 

Guillaume Nodet

Re: maven-compat removal?

[Guillaume Nodet]

Maven-compat has been deprecated years ago, so the goal would be to get rid
of it.
For months, efforts have been made to first make maven-compat completely
optional.
This is now the case in maven itself.
However, some plugins still rely on it and they should be migrated to use
Maven 3 apis.
This is a required step before being able to get rid of maven-compat.

I'm still hesitant about the time table, whether maven-compat should be
removed from
4.0 distribution or not.  It may be slightly premature, since a few plugins
still depend on it.

Le mar. 30 avr. 2024 à 02:02, Olivier Lamy  a écrit :
>
> Hi,
> I can see plenty of PRs with maven-compat removal.
> Maybe this could be explained and so more people could help for this task?
>
> cheers
> Olivier
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>


--

Guillaume Nodet

Re: [VOTE] Release Maven Install Plugin 3.1.2

[Guillaume Nodet]

+1


Le ven. 26 avr. 2024 à 12:41, Tamás Cservenák  a
écrit :

> Howdy,
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317524=12353548
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MINSTALL/issues
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2099/
>
> Source release checksum(s):
>
> f5847a66c2acc2b21b4afa5f4aa257ce3b41fcc63315720ccd68fa2cc497de8bef251ad500c6df051a2441846d521ce24de62858670f0c95101271166e9c6ce8
>
> Staging site:
> https://maven.apache.org/plugins-archives/maven-install-plugin-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>


-- 

Guillaume Nodet

Re: [VOTE] Release Maven Resolver 1.9.19

[Guillaume Nodet]

+1

Le mar. 16 avr. 2024 à 15:20, Tamás Cservenák  a
écrit :

> Howdy,
>
> Note: Maven Resolver 1.x lineage is in "bugfix only" maintenance mode.
>
> This Resolver 1.9.19 release is a bugfix release: A file locking related
> bug was fixed, that explains a lot about mysterious "could not acquire
> lock" problems. A cosmetic bugfix, where generated classpath string may
> contain trailing colon (":"). And finally, an improvement, that makes
> resolver able to work on FS implementations that do not allow mtime
> updates, like some cloud FS implementations are.
>
> We solved 10 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353946
>
> There are still some issues in JIRA:
> https://issues.apache.org/jira/projects/MRESOLVER/issues
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2090
>
> Source release SHA512:
>
> 1f8e0f457a0e27e61e9850f6c234d3fdca79764bf847a47cd40c09cb1bcdb8a2e1d6e21ff5789cb8bab416cb4b7c024afe84e68f19401f79f658ce7cc05cb8b4
>
> Staging site:
> https://maven.apache.org/resolver-archives/resolver-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>


-- 

Guillaume Nodet

[ANN] Apache Maven Resolver 2.0.0-alpha-10 released

[Guillaume Nodet]

Howdy,
The Apache Maven team is pleased to announce the release of the
Maven Resolver 2.0.0-alpha-10.
https://maven.apache.org/resolver-archives/resolver-2.0.0-alpha-10/
This is an eighth (alpha-4 and alpha-9 was scrubbed) preview release
of Resolver 2.0.0, that would allow any downstream consumers to try
it out and adapt. The supplier is aligned with Maven 4.0.0-alpha-13.
This resolver now implements "dynamic scopes" using newly introduced
ScopeManager (as opposed to Resolver 1.x "cemented/wired in scopes"),
making Resolver truly "scope agnostic" (as it is from now on just a
matter of scope manager configuration). Also, a bug fix is there
that restores backward binary compatibility.
Release Notes - Maven Resolver - Version 2.0.0-alpha-10
** Bug
* [MRESOLVER-515] - Restore compatibility broken by MRESOLVER-496
** New Feature
* [MRESOLVER-301] - Artifact Generators
* [MRESOLVER-512] - Scope Manager
** Task
* [MRESOLVER-516] - Align GPG signature generator
* [MRESOLVER-517] - Fix javadoc and align method name on scope manager
** Dependency upgrade
* [MRESOLVER-508] - Update to Junit 5.10.2
* [MRESOLVER-509] - Update to mockito 5.11.0
* [MRESOLVER-510] - Update to Redisson 3.27.2
* [MRESOLVER-511] - Update testcontainers to 1.19.7
* [MRESOLVER-513] - Update to Slf4j 2.0.12
* [MRESOLVER-514] - Update to Commons Codec 1.16.1
Have fun,
Maven Team

Re: [VOTE] Release Maven Resolver 2.0.0-alpha-10

[Guillaume Nodet]

+1

Le ven. 29 mars 2024 à 13:22, Tamás Cservenák  a écrit :
>
> Howdy,
>
> Note: This is an eighth (alpha-4 and alpha-9 was scrubbed) preview release
> of Resolver 2.0.0, that would allow any downstream consumers to try it out
> and adapt. The supplier is aligned with Maven 4.0.0-alpha-13. This resolver
> now implements "dynamic scopes" using newly introduced ScopeManager (as
> opposed to Resolver 1.x "cemented/wired in scopes"), making Resolver truly
> "scope agnostic" (as it is from now on just a matter of scope manager
> configuration). Also, a bug fix is there that restores backward binary
> compatibility.
>
> For configuration changes, see
> https://maven.apache.org/resolver-archives/resolver-LATEST/configuration.html
>
> IF the vote is successful, the staging site will NOT be moved to
> https://maven.apache.org/resolver/ but instead will be made reachable from
> https://maven.apache.org/resolver-archives/resolver-2.0.0-alpha-10/ only.
>
> The 1.9.18 is still the "latest stable" release of Maven Resolver.
>
> ===
>
> We solved 11 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12354447
>
> There are still some issues in JIRA:
> https://issues.apache.org/jira/projects/MRESOLVER/issues
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2080/
>
> Source release SHA512:
> ba52c431d11adcfbbd2aac088c4ba0bb9c4f864f084047d45ed64fa806ee0625fadd6447cce6f39f05abd493c6f54cc2b6d70740efa6bc994ce694936f6c9e0d
>
> Staging site:
> https://maven.apache.org/resolver-archives/resolver-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1



-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [PR] [MNG-8081] interpolate available properties during default profile selection (Maven 4.x) [maven]

[Guillaume Nodet]

I thought you were referring to having a small language in the
property activation...

Le mer. 20 mars 2024 à 22:06, Matt Benson  a écrit :
>
> I just opted to solve potentially several feature requests with a single
> code change rather than addressing each one separately with similar code
> repeated in e.g. every profile activator implementation.
>
> On Wed, Mar 20, 2024 at 3:57 PM gnodet (via GitHub)  wrote:
>
> >
> > gnodet commented on PR #1446:
> > URL: https://github.com/apache/maven/pull/1446#issuecomment-2010621686
> >
> >> That was what I originally considered, but I quickly came to the
> > opinion that as soon as we did it that way, someone would want to use some
> > such property to match a Java version, etc., and that this would be a
> > generally applicable way to solve a broad cross section of similar use
> > cases.
> >
> >How could that be considered a bad thing ?
> >
> >
> > --
> > This is an automated message from the Apache Git Service.
> > To respond to the message, please log on to GitHub and use the
> > URL above to go to the specific comment.
> >
> > To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
> >
> > For queries about this service, please contact Infrastructure at:
> > us...@infra.apache.org
> >
> >



-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [RESULT] [VOTE] Release maven-filtering-3.3.2 and maven-remote-resources-plugin-3.2.0

[Guillaume Nodet]

Ah, the vote was closed this morning by Tamas...  ;-)
Forget this thread then.


Le dim. 10 mars 2024 à 23:12, Guillaume Nodet  a écrit :
>
> Not sure what happens during the week, but the staging repository
> seems to have been published to central already.
> Has anyone published it ?
>
> Le dim. 10 mars 2024 à 22:51, Guillaume Nodet  a écrit :
> >
> > Closing this vote with 4 +1s and no other votes.
> > I'll publish the sites (thx Hervé !) and the binaries.
> >
> > Cheers,
> > Guillaume
> >
> > Le sam. 2 mars 2024 à 10:47, Guillaume Nodet  a écrit :
> > >
> > > I've staged release candidates for maven-filtering-3.3.2 and
> > > maven-remote-resources-plugin-3.2.0 at
> > > https://repository.apache.org/content/repositories/maven-2067
> > >
> > > JIRA release notes:
> > >   https://issues.apache.org/jira/projects/MSHARED/versions/12353084
> > >   https://issues.apache.org/jira/projects/MRRESOURCES/versions/12353591
> > >
> > > Note that m-remote-resources-p depends on the release of
> > > maven-filtering, hence the single vote.
> > >
> > > Please review and vote !
> > >
> > > --
> > > 
> > > Guillaume Nodet
>
>
>
> --
> 
> Guillaume Nodet



--

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [RESULT] [VOTE] Release maven-filtering-3.3.2 and maven-remote-resources-plugin-3.2.0

[Guillaume Nodet]

Not sure what happens during the week, but the staging repository
seems to have been published to central already.
Has anyone published it ?

Le dim. 10 mars 2024 à 22:51, Guillaume Nodet  a écrit :
>
> Closing this vote with 4 +1s and no other votes.
> I'll publish the sites (thx Hervé !) and the binaries.
>
> Cheers,
> Guillaume
>
> Le sam. 2 mars 2024 à 10:47, Guillaume Nodet  a écrit :
> >
> > I've staged release candidates for maven-filtering-3.3.2 and
> > maven-remote-resources-plugin-3.2.0 at
> > https://repository.apache.org/content/repositories/maven-2067
> >
> > JIRA release notes:
> >   https://issues.apache.org/jira/projects/MSHARED/versions/12353084
> >   https://issues.apache.org/jira/projects/MRRESOURCES/versions/12353591
> >
> > Note that m-remote-resources-p depends on the release of
> > maven-filtering, hence the single vote.
> >
> > Please review and vote !
> >
> > --
> > 
> > Guillaume Nodet



-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[RESULT] [VOTE] Release maven-filtering-3.3.2 and maven-remote-resources-plugin-3.2.0

[Guillaume Nodet]

Closing this vote with 4 +1s and no other votes.
I'll publish the sites (thx Hervé !) and the binaries.

Cheers,
Guillaume

Le sam. 2 mars 2024 à 10:47, Guillaume Nodet  a écrit :
>
> I've staged release candidates for maven-filtering-3.3.2 and
> maven-remote-resources-plugin-3.2.0 at
> https://repository.apache.org/content/repositories/maven-2067
>
> JIRA release notes:
>   https://issues.apache.org/jira/projects/MSHARED/versions/12353084
>   https://issues.apache.org/jira/projects/MRRESOURCES/versions/12353591
>
> Note that m-remote-resources-p depends on the release of
> maven-filtering, hence the single vote.
>
> Please review and vote !
>
> --
> 
> Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release maven-filtering-3.3.2 and maven-remote-resources-plugin-3.2.0

[Guillaume Nodet]

+1

Le sam. 2 mars 2024 à 10:47, Guillaume Nodet  a écrit :
>
> I've staged release candidates for maven-filtering-3.3.2 and
> maven-remote-resources-plugin-3.2.0 at
> https://repository.apache.org/content/repositories/maven-2067
>
> JIRA release notes:
>   https://issues.apache.org/jira/projects/MSHARED/versions/12353084
>   https://issues.apache.org/jira/projects/MRRESOURCES/versions/12353591
>
> Note that m-remote-resources-p depends on the release of
> maven-filtering, hence the single vote.
>
> Please review and vote !
>
> --
> 
> Guillaume Nodet



-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [DISCUSS] Maven Core Plugins versioning

[Guillaume Nodet]

Or maybe a 1 hundred bump: 3.12.1 -> 3.100.0 ?   It may be more clear,
as that's a number we don't usually reach...

Le ven. 8 mars 2024 à 17:20, Guillaume Nodet  a écrit :
>
> I'm slightly hesitant about that.
> It seems to me plugins have mostly been compatible, so we very rarely
> used a major version switch, but we do have plugins in 3.12.1 for
> example, which would be translated to 3.0.12.1.  Not even sure how the
> 4th digit is supported...
> I wonder if an alternative proposal would be to do a 10 unit big jump
> in the minor version to represent a breaking change, so from 3.12.1 to
> 3.23.0
>
> Guillaume
>
> Le ven. 8 mars 2024 à 11:19, Tamás Cservenák  a écrit :
> >
> > So, can we agree on following (maybe even vote if needed)?
> >
> > I. Core Plugin Versioning
> > Maven3 plugins carry 3.x as the major version number, and Maven4 plugins
> > will carry 4.x major versions?
> >
> > II. Consequence: How to interpret Core plugin versions
> > See above. In short: the first element is "maven API level", rest could be
> > "shifted left" and interpreted like that.
> >
> > III. Consequence: How to express Core plugin "breaking change"?
> > Ideally, we should NOT have them. But, in case we must:
> > - use minor bump and .0 patch to clearly show this is a "bigger" change
> > (hence, 3.1.0 -> 3.2.0 should be interpreted by users like "I need to sift
> > thru release notes before just blindly update")
> > - clearly document the breakage in release notes, announce and site
> >
> > T
> >
> > On Thu, Mar 7, 2024 at 9:23 AM Tamás Cservenák  wrote:
> >
> > > Michael,
> > >
> > > I am unsure why it would not work? As I explained in my initial email,
> > > Maven2 plugins were 2.x, Maven3 plugins were 3.x, so why could not Maven4
> > > be 4.x?
> > > I think that "maven plugin" is quite well defined (is not "just a jar").
> > > While I would expect your "bump the major version" for some library, in
> > > maven land we can lay down our own rules.
> > > This is not about history, but actually the opposite: how can the user
> > > decide should it (or can it) jump from version X to X+1 (given the java,
> > > maven he uses in build).
> > > After all, if breakage is documented, users can adopt the plugin required
> > > changes.
> > >
> > > I'd just like to keep it simple, and unchanged for now: it worked before
> > > just fine.
> > >
> > > T
> > >
> > > On Thu, Mar 7, 2024 at 8:40 AM Michael Osipov  wrote:
> > >
> > >> This is a general problem and cannot be solved. As soon as you need to
> > >> break the plugin compat you need to bump the major version. That
> > >> breakage does not need to be related to Maven at all.
> > >> Upshot: No matter what you do, you will do it wrong. I would rely on
> > >> MPLUGIN foo to manage he compat history.
> > >>
> > >> M
> > >>
> > >> -
> > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > >> For additional commands, e-mail: dev-h...@maven.apache.org
> > >>
> > >>
>
>
>
> --
> 
> Guillaume Nodet



-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [DISCUSS] Maven Core Plugins versioning

[Guillaume Nodet]

I'm slightly hesitant about that.
It seems to me plugins have mostly been compatible, so we very rarely
used a major version switch, but we do have plugins in 3.12.1 for
example, which would be translated to 3.0.12.1.  Not even sure how the
4th digit is supported...
I wonder if an alternative proposal would be to do a 10 unit big jump
in the minor version to represent a breaking change, so from 3.12.1 to
3.23.0

Guillaume

Le ven. 8 mars 2024 à 11:19, Tamás Cservenák  a écrit :
>
> So, can we agree on following (maybe even vote if needed)?
>
> I. Core Plugin Versioning
> Maven3 plugins carry 3.x as the major version number, and Maven4 plugins
> will carry 4.x major versions?
>
> II. Consequence: How to interpret Core plugin versions
> See above. In short: the first element is "maven API level", rest could be
> "shifted left" and interpreted like that.
>
> III. Consequence: How to express Core plugin "breaking change"?
> Ideally, we should NOT have them. But, in case we must:
> - use minor bump and .0 patch to clearly show this is a "bigger" change
> (hence, 3.1.0 -> 3.2.0 should be interpreted by users like "I need to sift
> thru release notes before just blindly update")
> - clearly document the breakage in release notes, announce and site
>
> T
>
> On Thu, Mar 7, 2024 at 9:23 AM Tamás Cservenák  wrote:
>
> > Michael,
> >
> > I am unsure why it would not work? As I explained in my initial email,
> > Maven2 plugins were 2.x, Maven3 plugins were 3.x, so why could not Maven4
> > be 4.x?
> > I think that "maven plugin" is quite well defined (is not "just a jar").
> > While I would expect your "bump the major version" for some library, in
> > maven land we can lay down our own rules.
> > This is not about history, but actually the opposite: how can the user
> > decide should it (or can it) jump from version X to X+1 (given the java,
> > maven he uses in build).
> > After all, if breakage is documented, users can adopt the plugin required
> > changes.
> >
> > I'd just like to keep it simple, and unchanged for now: it worked before
> > just fine.
> >
> > T
> >
> > On Thu, Mar 7, 2024 at 8:40 AM Michael Osipov  wrote:
> >
> >> This is a general problem and cannot be solved. As soon as you need to
> >> break the plugin compat you need to bump the major version. That
> >> breakage does not need to be related to Maven at all.
> >> Upshot: No matter what you do, you will do it wrong. I would rely on
> >> MPLUGIN foo to manage he compat history.
> >>
> >> M
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: dev-h...@maven.apache.org
> >>
> >>



-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven 4.0.0-alpha-13

[Guillaume Nodet]

+1


Guillaume Nodet



Le mer. 6 mars 2024 à 21:44, Tamás Cservenák  a écrit :

> Howdy,
>
> This is a vote to release Apache Maven 4.0.0-alpha-13.
>
> We solved 32 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12354062
>
> There are still some issues in JIRA:
> https://issues.apache.org/jira/projects/MNG/issues
>
> Release candidates:
> https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-13/
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2068/
>
> Source release SHA512:
> - apache-maven-4.0.0-alpha-13-src.zip
>
> 5e997e382ad7e5021009b74a6a80b9c9076282a3a71260636efc99c28ffad2c4d093d896364e705d853015f6c7d949523fc78c4ebb6aa55edeb43e383f084e3d
> - apache-maven-4.0.0-alpha-13-src.tar.gz
>
> 59cc1b312b240e93e9f51ab9549c69385e12ccf5453b8e6238470437fce8ca802bda0eddc66ca94c5d6d05c02e44c0f78d0d7d2038998559a61df6e5c599da10
>
> Staging site:
> https://maven.apache.org/ref/4-LATEST/
> Note: site publishing (execution time of `mvn scm-publish:publish-scm`) now
> takes 32 minutes! We need to do something about this...
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>

Re: [VOTE] Release Apache Maven 4.0.0-alpha-13

[Guillaume Nodet]

This does not seem to be related to MNG-8012 given the message. This is
more probably
https://issues.apache.org/jira/browse/MNG-7854



Guillaume Nodet



Le jeu. 7 mars 2024 à 09:06, Tamás Cservenák  a écrit :

> Karl,
>
> Initial reason is maybe this:
> https://issues.apache.org/jira/browse/MNG-8012
>
> Can you point me at the repo?
>
> Thanks
> T
>
>
> On Thu, Mar 7, 2024 at 12:07 AM Karl Heinz Marbaise 
> wrote:
>
> > Hi,
> >
> > I see the following with 4.0.0-alpha-13  with a test project (spring
> > boot based 3.3.0-M2):
> >
> > [INFO] Unable to find the root directory. Create a .mvn directory in the
> > root directory or add the root="true" attribute on the root project's
> > model to identify it.
> > [INFO] Scanning for projects...
> > [WARNING]
> > [WARNING] Some problems were encountered while building the effective
> > model for 'com.soebes.spring.example:employee:jar:0.0.1-SNAPSHOT'
> > [WARNING] Ignored POM import for:
> > org.apache.maven.plugin-tools:maven-plugin-annotations:jar:3.7.0@compile
> > as already imported
> >
> org.apache.maven.plugin-tools:maven-plugin-annotations:jar:3.10.2@compile.
> >   Add a the conflicting managed dependency directly to the
> > dependencyManagement section of the POM. @
> > org.springframework.boot:spring-boot-dependencies:3.3.0-M2,
> >
> >
> /Users/khm/.m2/repository/org/springframework/boot/spring-boot-dependencies/3.3.0-M2/spring-boot-dependencies-3.3.0-M2.pom
> > [WARNING]
> > [WARNING] It is highly recommended to fix these problems because they
> > threaten the stability of your build.
> > [WARNING]
> > [WARNING] For this reason, future Maven versions might no longer support
> > building such malformed projects.
> > [WARNING]
> >
> > The given bom file contains also a pluginManagement section with a
> > number of plugins defined in 
> >
> >
> > The interesting part is that 4.0.0-alpha-12 does not produce such
> > warning at all:
> >
> > [INFO] Unable to find the root directory. Create a .mvn directory in the
> > root directory or add the root="true" attribute on the root project's
> > model to identify it.
> > [INFO] Scanning for projects...
> > [INFO]
> > [INFO] --<
> > com.soebes.spring.example:employee
> >  >--
> > [INFO] Building Employee Demo Application 0.0.1-SNAPSHOT
> > [INFO]   from pom.xml
> > [INFO] -[ jar
> > ]--
> > [INFO]
> > [INFO] --- clean:3.3.2:clean (default-clean) @ employee ---
> > [INFO] Deleting
> > /Users/khm/ws-git-soebes/examples/spring-boot-plus-spring-data/target
> > [INFO]
> >
> > Any ideas what happens?
> >
> >
> > Kind regards
> > Karl Heinz Marbaise
> >
> > On 06.03.24 21:42, Tamás Cservenák wrote:
> > > Howdy,
> > >
> > > This is a vote to release Apache Maven 4.0.0-alpha-13.
> > >
> > > We solved 32 issues:
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12354062
> > >
> > > There are still some issues in JIRA:
> > > https://issues.apache.org/jira/projects/MNG/issues
> > >
> > > Release candidates:
> > > https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-13/
> > >
> > > Staging repository:
> > > https://repository.apache.org/content/repositories/maven-2068/
> > >
> > > Source release SHA512:
> > > - apache-maven-4.0.0-alpha-13-src.zip
> > >
> >
> 5e997e382ad7e5021009b74a6a80b9c9076282a3a71260636efc99c28ffad2c4d093d896364e705d853015f6c7d949523fc78c4ebb6aa55edeb43e383f084e3d
> > > - apache-maven-4.0.0-alpha-13-src.tar.gz
> > >
> >
> 59cc1b312b240e93e9f51ab9549c69385e12ccf5453b8e6238470437fce8ca802bda0eddc66ca94c5d6d05c02e44c0f78d0d7d2038998559a61df6e5c599da10
> > >
> > > Staging site:
> > > https://maven.apache.org/ref/4-LATEST/
> > > Note: site publishing (execution time of `mvn scm-publish:publish-scm`)
> > now
> > > takes 32 minutes! We need to do something about this...
> > >
> > > Guide to testing staged releases:
> > >
> https://maven.apache.org/guides/development/guide-testing-releases.html
> > >
> > > Vote open for 72 hours.
> > >
> > > [ ] +1
> > > [ ] +0
> > > [ ] -1
> > >
> >
> >
>

[VOTE] Release maven-filtering-3.3.2 and maven-remote-resources-plugin-3.2.0

[Guillaume Nodet]

I've staged release candidates for maven-filtering-3.3.2 and
maven-remote-resources-plugin-3.2.0 at
https://repository.apache.org/content/repositories/maven-2067

JIRA release notes:
  https://issues.apache.org/jira/projects/MSHARED/versions/12353084
  https://issues.apache.org/jira/projects/MRRESOURCES/versions/12353591

Note that m-remote-resources-p depends on the release of
maven-filtering, hence the single vote.

Please review and vote !

-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Require Java 17 for Maven 4

[Guillaume Nodet]

+1

Le mer. 28 févr. 2024 à 08:31, Benjamin Marwell  a écrit :
>
> Hi Maven Devs/Users/Committers and PMC members!
>
> After several discussions on the mailing lists, I would like to
> start a vote in favour of setting the minimal Java bytecode target
> of Maven-Core 4 to 17 and hence require Java 17 for Maven 4.
>
> This is a procedural majority vote [1*]:
> You can also vote with fractions and negative votes are not vetoes.
>
> Please also notice:
> * Maven 3 will stay at Java 8 no matter what.
> * We may raise Maven 4 to JDK 21 later if we feel like it (depending
> on the release date).
>   This is not part of this vote.
> * The linked PR is not part of this vote (this is not a code vote).
>   But you may take a look at it to understand the intended change.
>
> PR: https://github.com/apache/maven/pull/1430
>
> Maven-Parent will not be raised with this vote, the other PR is not
> part of this vote.
>
> Please refrain from starting discussions in this thread, but do
> include a reasoning on downvotes and feel free to start a new
> discussion on the mailing list, or comment on the existing ones.
>
> ---
>
> Vote open for 72 hours:
>
> [ ] +1 (set JDK17 min version for Maven 4.x)
> [ ] +0
> [ ] -1 (please include reasoning)
>
> ---
>
> - Ben
>
> [1*]: https://www.apache.org/foundation/voting.html



-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Hand ups - new releases in next week

[Guillaume Nodet]

I'm also planning to release
  * maven-filtering 2.3.2
   the following PRs would need review:
https://github.com/apache/maven-filtering/milestone/1
   remaining issues:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20component%20%3D%20maven-filtering%20AND%20status%20!%3D%20Closed

  * maven-remote-resources-plugin 3.2.0
 PRs to review:
https://github.com/apache/maven-remote-resources-plugin/pulls
 issues fixed:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRRESOURCES%20AND%20fixVersion%20%3D%20next-release
 remaining issues:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRRESOURCES%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC

Le sam. 24 févr. 2024 à 14:46, Slawomir Jaranowski
 a écrit :
>
> Hi,
>
> I'm going to release at the end of next week:
>
> 1. maven-assembly-plugin
>
> issues for next release:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317220%20AND%20fixVersion%20%3D%2012353243%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC
> open issues: https://issues.apache.org/jira/projects/MASSEMBLY
> open PRs: https://github.com/apache/maven-compiler-plugin/pulls
>
> 2. plexus-compiler
>
> fixes:
> https://github.com/codehaus-plexus/plexus-compiler/compare/plexus-compiler-2.14.2...refs/heads/master
> open issues: https://github.com/codehaus-plexus/plexus-compiler/issues
> open PRs in: https://github.com/codehaus-plexus/plexus-compiler/pulls
>
> 2. maven-compiler-plugin
>
> issues for next release:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317225%20AND%20fixVersion%20%3D%2012354079%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC
> open issues: https://issues.apache.org/jira/projects/MCOMPILER
> open PRs: https://github.com/apache/maven-compiler-plugin/pulls
>
> 3. maven-jar-plugin
>
> issues for next release:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317526%20AND%20fixVersion%20%3D%2012352303%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC
> open issues: https://issues.apache.org/jira/projects/MJAR
> open PRs: https://github.com/apache/maven-jar-plugin/pulls
>
> So any help will be appreciated with:
>
> - check or comments opened issues - maybe some more can be fixed
> - review opened PR - many times review from contributors and users are very
> valuable
> - check documentation - sometime we can fix a simple misspells, broken
> links, clarify a more bit and so on
>
> All contributors are welcome - old and new ones with helping on preparing
> the new release.
>
> --
> Sławomir Jaranowski



-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven Shade Plugin version 3.5.2

[Guillaume Nodet]

+1

And fwiw, I fully support what Hervé said.  A release is a best effort
from the one who decides to start it and if Hervé was not confident in
merging the other PRs, that's fine with me.

Guillaume

Le dim. 18 févr. 2024 à 17:12, Hervé Boutemy  a écrit :
>
> FYI I reviewed PRs and merged what I was confident with
> I can't say if this one can be merged: I don't know the feature sufficiently
>
> I understand the good intent of the feedback, even if I find -1 a little bit
> strong: I did what I could, believe in my good intent too doing that release
>
> Regards,
>
> Hervé
>
> Le dimanche 18 février 2024, 15:14:37 CET Elliotte Rusty Harold a écrit :
> > On Sun, Feb 18, 2024 at 8:43 AM Romain Manni-Bucau
> >
> >  wrote:
> > > Hi Eliotte,
> > >
> > > Is the -1 only motivated by the fact there is a PR opened?
> >
> > That there is an unaddressed PR that looks worthy of review and has
> > been open for months without a reply. 13 others are open. One of them
> > is not ready for review. I haven't looked at the other 12 since, IMHO,
> > one unreviewed PR is sufficient reason to delay a cut.
> >
> > > If so please consider two things:
> > > *  it is always the case for most releases (maven, asf, living projects
> > > ;))
> > > so not sure when it became a hard criteria but if so we should probably
> > > think to be more open if we want to release a day
> >
> > It isn't necessary to finish and merge all PRs before a release, but a
> > review is not much to ask when someone has volunteered effort to fix
> > something. Rarely, there's an emergency push for a critical bug. Short
> > of that, it doesn't take all that long to scan the Github queue and
> > see if there's anything useful that got missed. In practice though I
> > often find even simple dependabot PRs unmerged after a release is cut.
> > I would like to get in the habit of tidying up the queue prior to a
> > release cut.
> >
> > > * If you take time to review the PR you mention you will also see it just
> > > revert a fix and that the final code should be more complex if it lands in
> > > shade plugin a day - there are always workarounds there - so don't think
> > > we
> > > can make it in the week so can await another round and way more time to
> > > make it right (long story sort shade has an old bug where it mixes the
> > > same
> > > config for different kind of rewritten sources, while it often works and
> > > stays simple, it also makes it insanely hard to be right since you don't
> > > know what you rewrite - a variable, a package, a class name, ...)
> >
> > That's all fine, but please say this on the PR so the new contributor
> > can address these points. It's not good for PRs to sit in limbo for
> > years. Commenting on PRs also helps to avoid someone else who doesn't
> > have the context you do (e.g. me) from coming along and simply merging
> > the PR because I don't happen to notice the problems you do.
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>


-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Java version for Maven 4?

[Guillaume Nodet]

Before actually changing the runtime requirement, I’d like to make sure we
have good enough support for toolchains on the dev side and in CI (Jenkins,
GitHub actions…).
On the dev side, I once proposed to have an easy integration with sdkman, I
think I did raise a PR for that months ago…


Guillaume Nodet



Le sam. 3 févr. 2024 à 15:17, Martin Desruisseaux <
martin.desruisse...@geomatys.com> a écrit :

> Hello
>
>  From the replies in this thread, it seems to me that there is a
> consensus for moving Maven 4 to some Java version after 8. I see:
>
>   * 0 in favour of Java 11
>   * 1.5 in favour of Java 17 (the .5 is because I split a vote between
> Java 17 and 21)
>   * 2.5 in favour of Java 21
>   * 4 seem neutral (including myself)
>
> Do we take that as an agreement to require Java 21 for building Maven 4?
>
> On a related question, what should be the minimal Java version for
> *running* Maven 4? Keeping in mind that if Java 21 (for example) was
> required, users would still be able to compile for an older Java version
> using the --release option.
>
>  Martin
>
>

Re: [VOTE] Release Maven Resolver 2.0.0-alpha-7

[Guillaume Nodet]

+1

Le jeu. 25 janv. 2024 à 19:58, Tamás Cservenák  a écrit :
>
> Howdy,
>
> Note: This is a sixth (alpha-4 was scrubbed) preview release of Resolver
> 2.0.0, that would allow any downstream consumers to try it out and adapt.
> The supplier is aligned with Maven 4.0.0-alpha-12. Delivered features are
> mostly smaller improvements, bug fixes and dependency updates. One notable
> change is that this release makes "file locking" enabled by default. This
> alpha contains pretty much every major feature we planned for 2.0.0. Of
> course, we do NOT exclude more issues to be added (most likely bugs) down
> the road, but the final 2.0.0 release is getting near.
>
> For configuration changes, see
> https://maven.apache.org/resolver-archives/resolver-LATEST/configuration.html
>
> IF the vote is successful, the staging site will NOT be moved to
> https://maven.apache.org/resolver/ but instead will be made reachable from
> https://maven.apache.org/resolver-archives/resolver-2.0.0-alpha-7/ only.
>
> The 1.9.18 is still the "latest stable" release of Maven Resolver.
>
> ===
>
> We solved 20 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12354065
>
> There are still some issues in JIRA:
> https://issues.apache.org/jira/projects/MRESOLVER/issues
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2063
>
> Source release SHA512:
> af765437edad19adb5cca208841c431bafc983288f5fd6ea09f6446a8ad30bcb27e2c0b81e4652ab4a95ecc8ca95a03cbeb20e3283a3ff1ced40caf6c3dbcf1b
>
> Staging site:
> https://maven.apache.org/resolver-archives/resolver-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1



-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Java version for Maven 4?

[Guillaume Nodet]

Le lun. 22 janv. 2024 à 09:52, Hervé Boutemy  a écrit :
>
> Le dimanche 21 janvier 2024, 22:03:59 CET Guillaume Nodet a écrit :
> > At build time, I think it's fine to bump to whatever is needed to make
> > our life manageable. If 17 is required, so be it.
> +1
>
> my biggest concern with Maven 4 is not JDK runtime requirement, but plugins
> future when a plugin wants to be able to use the new Maven 4 API
>
> IIUC, Maven 4 has a compatibility layer to run Maven Plugin 3.x (= built with
> Maven 3 plugin API).
> On our core plugins, there is a Maven 4 branch that tests what the plugin
> would become when it migrates to new Maven 4 API (and check that Maven 4 API
> works as expected)
>
> But IIUC, once a plugin uses Maven 4 API, it de-facto cannot be run on Maven 3
>
> Questions:
> - is that true at plugin level or goal level?

It has to be at the plugin level.  The main reason is that all goals
share the same
classloader and the rules to build the classloader will very probably change
between the Maven 3 API and the Maven 4 API, as the Maven 4 API should
provide a much smaller class loader than the current one.
See https://issues.apache.org/jira/browse/MNG-7955

> - new Maven 4 API for now is not so much about providing new features, but
> improving/clarifying plugin  expectations from Maven core: are there known
> features in Maven 4 API not available in Maven 3 that would bring stronger
> interest in writing a goal for Maven 4?
>
> concern: does it mean that we either should not upgrade our master branches to
> Maven 4 API too early? Will we need to maintain a 3.x branch in parallel to 4/
> main branch?
> And the questions I have for plugins maintained at Maven project level will
> impact every third party plugin maintainer: we need to make things explicit,
> IMHO
> The JVM upgrade in parallel IMHO is less a concern, as it is a consequence of
> previous plugin prerequisite choice on Maven
>
> Hervé
>
> >
> > Guillaume
> >
> > Le sam. 20 janv. 2024 à 19:18, Martin Desruisseaux
> >
> >  a écrit :
> > > Hello
> > >
> > > I would like a little clarification about the Java version for Maven 4.
> > > I saw debate on this mailing list, but has a decision been reached? I
> > > got the impression that Maven 4 would require Java 11, but last time I
> > > checked, the pom.xml file was still declaring Java 8 as the target. If
> > > Java 11 is the target, updating the pom.xml would unlock some features
> > > and make some code a little bit simpler.
> > >
> > > Related question: even if Maven 4 targets Java 8 or 11, would it be
> > > acceptable to require Java 17 with `--release 8` or `--release 11`
> > > option only for Maven 4 compilation (not execution)? I ask because as
> > > far as I know, we cannot write code buildable with both Java 11 and Java
> > > 17 if the code uses HTML headings in Javadoc comments and the Javadoc
> > > checks are enabled. If the project builds on Java 11, then it fails on
> > > Java 17. Or if it builds on Java 17, then it fails on Java 11. For
> > > building on both versions, we must either avoid HTML headings, or
> > > disable Javadoc checks (more details at [1]). Using HTML headings is not
> > > very important, so they could be removed. But the `--release 11`
> > > approach would allow a more gradual transition to newest Java versions
> > > while preserving compatibility for users.
> > >
> > >  Martin
> > >
> > > [1]https://github.com/apache/maven/pull/1378#issuecomment-1902173221
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>


-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Java version for Maven 4?

[Guillaume Nodet]

At build time, I think it's fine to bump to whatever is needed to make
our life manageable. If 17 is required, so be it.

Guillaume

Le sam. 20 janv. 2024 à 19:18, Martin Desruisseaux
 a écrit :
>
> Hello
>
> I would like a little clarification about the Java version for Maven 4.
> I saw debate on this mailing list, but has a decision been reached? I
> got the impression that Maven 4 would require Java 11, but last time I
> checked, the pom.xml file was still declaring Java 8 as the target. If
> Java 11 is the target, updating the pom.xml would unlock some features
> and make some code a little bit simpler.
>
> Related question: even if Maven 4 targets Java 8 or 11, would it be
> acceptable to require Java 17 with `--release 8` or `--release 11`
> option only for Maven 4 compilation (not execution)? I ask because as
> far as I know, we cannot write code buildable with both Java 11 and Java
> 17 if the code uses HTML headings in Javadoc comments and the Javadoc
> checks are enabled. If the project builds on Java 11, then it fails on
> Java 17. Or if it builds on Java 17, then it fails on Java 11. For
> building on both versions, we must either avoid HTML headings, or
> disable Javadoc checks (more details at [1]). Using HTML headings is not
> very important, so they could be removed. But the `--release 11`
> approach would allow a more gradual transition to newest Java versions
> while preserving compatibility for users.
>
>  Martin
>
> [1]https://github.com/apache/maven/pull/1378#issuecomment-1902173221



-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[ANN] Apache Maven 4.0.0-alpha-12 released

[Guillaume Nodet]

The Apache Maven team is pleased to announce the release of
Apache Maven 4.0.0-alpha-12.

Apache Maven is a software project management and comprehension tool.
Based on the concept of a project object model (POM), Maven can manage
a project's build, reporting and documentation from a central piece of
information.

Maven 4.0.0-alpha-12 is available via https://maven.apache.org/download.cgi

This is an alpha release, not suitable for production. If you hit any problem,
please raise a JIRA issue or send an email to the mailing list.

The full list of changes can be found in our issue management system.
Notable changes include:
 * brings the latest Maven Resolver 2.0.0-alpha-6
 * leverages resolver's artifact collection filtering
 * leverages resolver's new transitive dependency manager
 * use JLine to provide better line editing
 * upgrades SLF4j to 2.x
 * do not resolve projects anymore outside the reactor to provide
better consistency during builds

The JLine library included in this release is missing the native
libraries, which will cause problems on Windows or non-traditional
Unix platforms where the JLine's exec provider does not work (see
MNG-8017).

For more information read
https://maven.apache.org/docs/4.0.0-alpha-12/release-notes.html

Enjoy !
On behalf of the Apache Maven PMC team
Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[RESULT] [VOTE] Release Apache Maven 4.0.0-alpha-12

[Guillaume Nodet]

Vote passes with 6 votes, PMC quorum being reached.
I'll publish the release asap.

Guillaume

Le ven. 12 janv. 2024 à 11:44, Guillaume Nodet  a écrit :

> I'm starting a new vote to release this new alpha.
> This release brings the latest Maven Resolver 2.0.0-alpha-6, leveraging
> artifact collection filtering and the new transitive dependency manager.
> JLine has been leveraged to provide better line editing, SLF4j has been
> upgraded to 2.x. Also, projects are not resolved anymore outside the
> reactor to provide better consistency during builds.
>
> Fwiw, a few plugins have already been ported to the new API (clean,
> install, deploy, resources, compiler) and do pass their integration
> tests, i'll update the PR
> https://github.com/apache/maven/pull/1048
> <https://github.com/apache/maven/pull/1048/files> asap.
>
> 13 issues solved:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12354059
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2062
>
> Dev dist directory:
> https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-12/
>
> Staged site:
> https://maven.apache.org/ref/4-LATEST/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72h
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> --
> 
> Guillaume Nodet
>
>

-- 

Guillaume Nodet

Re: [VOTE] Release Apache Maven 4.0.0-alpha-12

[Guillaume Nodet]

+1

Le ven. 12 janv. 2024 à 11:44, Guillaume Nodet  a écrit :

> I'm starting a new vote to release this new alpha.
> This release brings the latest Maven Resolver 2.0.0-alpha-6, leveraging
> artifact collection filtering and the new transitive dependency manager.
> JLine has been leveraged to provide better line editing, SLF4j has been
> upgraded to 2.x. Also, projects are not resolved anymore outside the
> reactor to provide better consistency during builds.
>
> Fwiw, a few plugins have already been ported to the new API (clean,
> install, deploy, resources, compiler) and do pass their integration
> tests, i'll update the PR
> https://github.com/apache/maven/pull/1048
> <https://github.com/apache/maven/pull/1048/files> asap.
>
> 13 issues solved:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12354059
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2062
>
> Dev dist directory:
> https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-12/
>
> Staged site:
> https://maven.apache.org/ref/4-LATEST/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72h
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> --
> 
> Guillaume Nodet
>
>

-- 

Guillaume Nodet

Re: [VOTE] Release Apache Maven 4.0.0-alpha-12

[Guillaume Nodet]

The explanation in this case, is that the BOM's parent has been changed
yesterday, and I just realized after releasing alpha-11 when looking at the
staging repo, that the groupId was wrong, so I did not call for a vote for
it, fixed the groupId and cut alpha-12.
The other would have been to force push a reset on master and recut
alpha-11.

Le ven. 12 janv. 2024 à 12:00, Guillaume Nodet  a écrit :

>
>
> Le ven. 12 janv. 2024 à 11:47, Romain Manni-Bucau 
> a écrit :
>
>> Hi Guillaume,
>>
>> Is it possible to not burn versions, it is always misleading for end users
>> so would be great to get the alpha 11 out maybe?
>>
>
>  It seems it is the rule in the Maven project, but I'd be happy to change
> it. I fully agree.
>
>
>>
>> Romain Manni-Bucau
>> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
>> <https://rmannibucau.metawerx.net/> | Old Blog
>> <http://rmannibucau.wordpress.com> | Github <
>> https://github.com/rmannibucau> |
>> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
>> <
>> https://www.packtpub.com/application-development/java-ee-8-high-performance
>> >
>>
>>
>> Le ven. 12 janv. 2024 à 11:44, Guillaume Nodet  a
>> écrit :
>>
>> > I'm starting a new vote to release this new alpha.
>> > This release brings the latest Maven Resolver 2.0.0-alpha-6, leveraging
>> > artifact collection filtering and the new transitive dependency manager.
>> > JLine has been leveraged to provide better line editing, SLF4j has been
>> > upgraded to 2.x. Also, projects are not resolved anymore outside the
>> > reactor to provide better consistency during builds.
>> >
>> > Fwiw, a few plugins have already been ported to the new API (clean,
>> > install, deploy, resources, compiler) and do pass their integration
>> > tests, i'll update the PR
>> > https://github.com/apache/maven/pull/1048
>> > <https://github.com/apache/maven/pull/1048/files> asap.
>> >
>> > 13 issues solved:
>> >
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12354059
>> >
>> > Staging repository:
>> > https://repository.apache.org/content/repositories/maven-2062
>> >
>> > Dev dist directory:
>> > https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-12/
>> >
>> > Staged site:
>> > https://maven.apache.org/ref/4-LATEST/
>> >
>> > Guide to testing staged releases:
>> > http://maven.apache.org/guides/development/guide-testing-releases.html
>> >
>> > Vote open for 72h
>> >
>> > [ ] +1
>> > [ ] +0
>> > [ ] -1
>> >
>> > --
>> > 
>> > Guillaume Nodet
>> >
>>
>
>
> --
> 
> Guillaume Nodet
>
>

-- 

Guillaume Nodet

Re: [VOTE] Release Apache Maven 4.0.0-alpha-12

[Guillaume Nodet]

Le ven. 12 janv. 2024 à 11:47, Romain Manni-Bucau  a
écrit :

> Hi Guillaume,
>
> Is it possible to not burn versions, it is always misleading for end users
> so would be great to get the alpha 11 out maybe?
>

 It seems it is the rule in the Maven project, but I'd be happy to change
it. I fully agree.


>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>
>
> Le ven. 12 janv. 2024 à 11:44, Guillaume Nodet  a
> écrit :
>
> > I'm starting a new vote to release this new alpha.
> > This release brings the latest Maven Resolver 2.0.0-alpha-6, leveraging
> > artifact collection filtering and the new transitive dependency manager.
> > JLine has been leveraged to provide better line editing, SLF4j has been
> > upgraded to 2.x. Also, projects are not resolved anymore outside the
> > reactor to provide better consistency during builds.
> >
> > Fwiw, a few plugins have already been ported to the new API (clean,
> > install, deploy, resources, compiler) and do pass their integration
> > tests, i'll update the PR
> > https://github.com/apache/maven/pull/1048
> > <https://github.com/apache/maven/pull/1048/files> asap.
> >
> > 13 issues solved:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12354059
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/maven-2062
> >
> > Dev dist directory:
> > https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-12/
> >
> > Staged site:
> > https://maven.apache.org/ref/4-LATEST/
> >
> > Guide to testing staged releases:
> > http://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for 72h
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > --
> > 
> > Guillaume Nodet
> >
>


-- 

Guillaume Nodet

[VOTE] Release Apache Maven 4.0.0-alpha-12

[Guillaume Nodet]

I'm starting a new vote to release this new alpha.
This release brings the latest Maven Resolver 2.0.0-alpha-6, leveraging
artifact collection filtering and the new transitive dependency manager.
JLine has been leveraged to provide better line editing, SLF4j has been
upgraded to 2.x. Also, projects are not resolved anymore outside the
reactor to provide better consistency during builds.

Fwiw, a few plugins have already been ported to the new API (clean,
install, deploy, resources, compiler) and do pass their integration
tests, i'll update the PR
https://github.com/apache/maven/pull/1048
<https://github.com/apache/maven/pull/1048/files> asap.

13 issues solved:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12354059

Staging repository:
https://repository.apache.org/content/repositories/maven-2062

Dev dist directory:
https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-12/

Staged site:
https://maven.apache.org/ref/4-LATEST/

Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for 72h

[ ] +1
[ ] +0
[ ] -1

-- 
----
Guillaume Nodet

Re: [VOTE] Release Maven Resolver 2.0.0-alpha-6

[Guillaume Nodet]

+1

Le lun. 8 janv. 2024 à 10:16, Tamás Cservenák  a
écrit :

> Howdy,
>
> Note: This is a fifth (alpha-4 was scrubbed) preview release of Resolver
> 2.0.0, that would allow any downstream consumers to try it out and adapt.
> Supplier is aligned with Maven 4.0.0-alpha-10. Major features are
> dependency management and filtering improvements. This alpha contains
> pretty much everything we planned for 2.0.0. Of course we do exclude more
> issues to be added (most likely bugs) down the road but final 2.0.0 is
> close.
>
> For configuration changes, see
>
> https://maven.apache.org/resolver-archives/resolver-LATEST/configuration.html
>
> IF the vote is successful, the staging site will NOT be moved to
> https://maven.apache.org/resolver/ but instead will be made reachable from
> https://maven.apache.org/resolver-archives/resolver-2.0.0-alpha-6/ only.
>
> The 1.9.18 is still the "latest stable" release of Maven Resolver.
>
> ===
>
> We solved 6 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12354046
>
> There are still some issues in JIRA:
> https://issues.apache.org/jira/projects/MRESOLVER/issues
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2059
>
> Source release SHA512:
>
> acee147df2eeb09f2b5bd34fdcb80d5d9d47c92a430b54c708ee71e6a48aab0b04bd9b2f84344545c9d51658a1a077c3f7f6fc374d7120330994f8ec73bbd2ea
>
> Staging site:
> https://maven.apache.org/resolver-archives/resolver-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>


-- 

Guillaume Nodet

[ANN] Apache Maven 4.0.0-alpha-10 released

[Guillaume Nodet]

The Apache Maven team is pleased to announce the release of
Apache Maven 4.0.0-alpha-10.

Apache Maven is a software project management and comprehension tool.
Based on the concept of a project object model (POM), Maven can manage
a project's build, reporting and documentation from a central piece of
information.

Maven 4.0.0-alpha-10 is available via https://maven.apache.org/download.cgi

This is an alpha release, not suitable for production. If you hit any
problem,
please raise a JIRA issue or send an email to the mailing list.

The full list of changes can be found in our issue management system [1].
Among those are:
 * user controlled relocations
 * fix broken javadoc:jar goal
 * fix resolver that may cause maven never to quit

For more information read
https://maven.apache.org/docs/4.0.0-alpha-10/release-notes.html

[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12354013

Enjoy !
Guillaume Nodet

Re: [VOTE] Release Apache Maven 4.0.0-alpha-10

[Guillaume Nodet]

Closing this vote with 7 +1s and no other votes.
I'll publish the release asap.

Le lun. 18 déc. 2023 à 19:16, Guillaume Nodet  a écrit :

> I'm starting a new vote to release this new alpha.  This mainly brings
> in latest resolver alpha release which fixes a nasty bug causing maven
> to never quit.
>
> Fwiw, a few plugins have already been ported to the new API (clean,
> install, deploy, resources, compiler) and do pass their integration
> tests, i'll update the PR
> https://github.com/apache/maven/pull/1048/files asap.
>
> 13 issues solved:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12354013
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2050
>
> Dev dist directory:
> https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-10/
>
> Staged site:
> https://maven.apache.org/ref/4-LATEST/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72h
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> --
> 
> Guillaume Nodet
>


-- 

Guillaume Nodet

Re: [VOTE] Release Apache Maven 4.0.0-alpha-10

[Guillaume Nodet]

+1

Le lun. 18 déc. 2023 à 19:16, Guillaume Nodet  a écrit :

> I'm starting a new vote to release this new alpha.  This mainly brings
> in latest resolver alpha release which fixes a nasty bug causing maven
> to never quit.
>
> Fwiw, a few plugins have already been ported to the new API (clean,
> install, deploy, resources, compiler) and do pass their integration
> tests, i'll update the PR
> https://github.com/apache/maven/pull/1048/files asap.
>
> 13 issues solved:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12354013
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2050
>
> Dev dist directory:
> https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-10/
>
> Staged site:
> https://maven.apache.org/ref/4-LATEST/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72h
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> --
> 
> Guillaume Nodet
>


-- 

Guillaume Nodet

Re: Guidance on Maven 4 API issue

[Guillaume Nodet]

Sure, but you asked for an API, there's none so far.

I'm not sure what kind of API we could offer, as this depends on what you
want to build.  If you build an OSGi plugin, you may want to restrict the
visibility to exported packages, kinda like with JPMS.  Takari lifecycle
does this sort of thing too.  So the API depends on the packaging / type of
artifact you're building imho.

Imho, but Tamas has thought about it more afaik, JPMS modules should have
their own packaging / lifecycle, not reusing plain JAR, as the rules are
different.  The compiler plugin maybe should be a different plugin too,
that would make things less complicated maybe.

Guillaume

Le mar. 19 déc. 2023 à 13:55, Martin Desruisseaux <
martin.desruisse...@geomatys.com> a écrit :

> Le 2023-12-19 à 13 h 32, Guillaume Nodet a écrit :
> >
> result.getPaths().stream().map(Path::toString).collect(Collectors.joining(":"))
>
> This is more complicated than that. From a set of dependencies, we need
> to dispatch them between class-path, module-path and --patch-module
> option (the latter may be seen as a class-path specific to each module).
> This is done by an analysis of dependencies properties. Which is why I
> think we need one more piece of API dedicated to this task.
>
>  Martin
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 

Guillaume Nodet

Re: Guidance on Maven 4 API issue

[Guillaume Nodet]

Yes,

result.getPaths().stream().map(Path::toString).collect(Collectors.joining(":"))

Usually, I would assume the plugin needs to also concat with the
target/classes and target/test-classes as done in the compiler plugin:
https://github.com/gnodet/maven-compiler-plugin/blob/m-api/src/main/java/org/apache/maven/plugin/compiler/CompilerMojo.java#L339-L362


Le mar. 19 déc. 2023 à 13:13, Tamás Cservenák  a
écrit :

> Howdy,
>
> I think this is it, no? Guillaume?
>
> https://github.com/apache/maven/blob/master/api/maven-api-core/src/main/java/org/apache/maven/api/services/DependencyResolverResult.java#L40
>
> Basically you need to concat paths (using OS path separator) to get
> classpath
>
> Maybe we want this on API as well, as even Resolver 1.x did publish this:
>
> https://github.com/apache/maven-resolver/blob/maven-resolver-1.9.18/maven-resolver-util/src/main/java/org/eclipse/aether/util/graph/visitor/AbstractDepthFirstNodeListGenerator.java#L130
>
>
> Thanks
> T
>
> On Tue, Dec 19, 2023 at 1:08 PM Martin Desruisseaux <
> martin.desruisse...@geomatys.com> wrote:
>
> > Le 2023-12-19 à 11 h 36, Guillaume Nodet a écrit :
> > >
> > > Ideally, you'd only focus on org.apache.maven.api.* and forget about
> > > everything else. That's the Maven 4 API and all other things are not
> > > part of that API (including MavenProject). The class path resolution
> > > should be done using the following code:
> > >
> > > (…snip…)
> > > for (Dependency dependency : result.getDependencies().keySet()) {
> > >DependencyProperties properties =
> > dependency.getDependencyProperties();
> > >...
> > > }
> >
> > Thanks, I will adapt the code proposal. But above example gets only the
> > list of dependencies. Is there is central place in Maven 4 API for doing
> > the next step, which is to build the class-path, etc. from this set, or
> > is it expected that each plugin would do this work themselves? In the
> > latter case, I would like to replace this assumption by an API doing
> > this work for plugins. Plugins would not be forced to use that API, but
> > encouraged.
> >
> >  Martin
> >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>


-- 

Guillaume Nodet

Re: Guidance on Maven 4 API issue

[Guillaume Nodet]

Ideally, you'd only focus on org.apache.maven.api.* and forget about
everything else. That's the Maven 4 API and all other things are not part
of that API (including MavenProject).

The class path resolution should be done using the following code:

   org.apache.maven.api.Session session;
   org.apache.maven.api.Project project;

   DependencyResolverResult result =
session.getService(DependencyResolver.class).resolve(session, project,
ResolutionScope.PROJECT_COMPILE);
   for (Dependency dependency : result.getDependencies().keySet()) {
  DependencyProperties properties =
dependency.getDependencyProperties();
  ...
   }


Le mar. 19 déc. 2023 à 10:50, Martin Desruisseaux <
martin.desruisse...@geomatys.com> a écrit :

> Hello
>
> Le 2023-12-19 à 10 h 10, Tamás Cservenák a écrit :
>
> > These are all good questions. Ideally I'd not touch maven-artifact,
> > rather all should be usable with the new Maven API. For example: in
> > new Api there is Project, and DependencyResolver service, it does not
> > help? (by revealing properties?)
> >
> Thanks for your reply. I just had a look to DependencyResolver. Can you
> confirm if my understanding is right, and point me to the right approach
> if not?
>
>   * org.apache.maven.project.MavenProject is the place where the
> classpath is built. This is the crucial part of this work, I'm
> looking for a central place which does the analysis of dependency
> properties and build class-path, module-path, doclet-path,
> agent-path, processor-path, etc. from them.
>   * org.apache.maven.api.services.DependencyResolver has "resolve"
> methods which provide dependency properties through the
> DependencyResolverResult → Node → Dependency → DependencyProperties
> path.
>
> However in MavenProject (if it is the right place where to build
> class-path, module-path, etc.), I see no DependencyResolver,
> DependencyResolverResult or Node. How do I make the link?
>
> Regarding the separation between "maven-artifact" and "maven-api-core"
> modules, I see that both of them define their own Artifact interface:
>
>   * org.apache.maven.artifact.Artifact
>   * org.apache.maven.api.Artifact
>
> Somewhere there is code that copy data from one structure to the other.
> Wouldn't it be simpler to have only one interface?
>
>  Martin
>
>

-- 

Guillaume Nodet

[VOTE] Release Apache Maven 4.0.0-alpha-10

[Guillaume Nodet]

I'm starting a new vote to release this new alpha.  This mainly brings
in latest resolver alpha release which fixes a nasty bug causing maven
to never quit.

Fwiw, a few plugins have already been ported to the new API (clean,
install, deploy, resources, compiler) and do pass their integration
tests, i'll update the PR
https://github.com/apache/maven/pull/1048/files asap.

13 issues solved:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12354013

Staging repository:
https://repository.apache.org/content/repositories/maven-2050

Dev dist directory:
https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-10/

Staged site:
https://maven.apache.org/ref/4-LATEST/

Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for 72h

[ ] +1
[ ] +0
[ ] -1

-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Maven Resolver 2.0.0-alpha-5

[Guillaume Nodet]

+1

Le jeu. 14 déc. 2023 à 19:00, Tamás Cservenák  a écrit :
>
> Howdy,
>
> Note: This is a fourth (alpha-4 was scrubbed) preview release of Resolver
> 2.0.0, that would allow any downstream consumers to try it out and adapt.
> It contains session and transport related bug fixes and various other new
> features and improvements. The new HTTP/2 transports are now proclaimed
> "official".
>
> For configuration changes, see
> https://maven.apache.org/resolver-archives/resolver-LATEST/configuration.html
>
> IF the vote is successful, the staging site will NOT be moved to
> https://maven.apache.org/resolver/ but instead will be made reachable from
> https://maven.apache.org/resolver-archives/resolver-2.0.0-alpha-5/ only.
>
> The 1.9.18 is still the "latest stable" release of Maven Resolver.
>
> ===
>
> We solved 14 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12354032
>
> There are still some issues in JIRA:
> https://issues.apache.org/jira/projects/MRESOLVER/issues
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2048
>
> Source release SHA512:
> d2c8e9e2f6f4d42e84dd5b301802aa1a98b4f36a1bbe850c2800d050495f3a0774fbc96f448d02007fe6b3062380f6eec62e326295b417ac68ff61c63c5535e5
>
> Staging site:
> https://maven.apache.org/resolver-archives/resolver-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1



-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Maven Resolver 2.0.0-alpha-4

[Guillaume Nodet]

+1

Le jeu. 14 déc. 2023 à 00:20, Tamás Cservenák  a écrit :
>
> Howdy,
>
> Note: This is a fourth preview release of Resolver 2.0.0 (for Mr M: this
> time will not say "last" alpha), that would allow any downstream consumers
> to try it out and adapt. It contains session and transport related bug
> fixes and various other new features and improvements. The new HTTP/2
> transports are now proclaimed "official".
>
> For configuration changes, see
> https://maven.apache.org/resolver-archives/resolver-LATEST/configuration.html
>
> IF the vote is successful, the staging site will NOT be moved to
> https://maven.apache.org/resolver/ but instead will be made reachable from
> https://maven.apache.org/resolver-archives/resolver-2.0.0-alpha-4/ only.
>
> The 1.9.18 is still the "latest stable" release of Maven Resolver.
>
> ===
>
> We solved 12 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12354028
>
> There are still some issues in JIRA:
> https://issues.apache.org/jira/projects/MRESOLVER/issues
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2046
>
> Source release SHA512:
> ab825c124e35da80f5244930b3f723ef8ea6d0e6b8b4bb3a72c7256dcc7054b9ed8c9a5c23f294766699021151d8bd961d8755c4d74ff363c41835cbaa1a7903
>
> Staging site:
> https://maven.apache.org/resolver-archives/resolver-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1



-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[ANN] Apache Maven 4.0.0-alpha-9 released

[Guillaume Nodet]

The Apache Maven team is pleased to announce the release of
Apache Maven 4.0.0-alpha-9.

Apache Maven is a software project management and comprehension tool.
Based on the concept of a project object model (POM), Maven can manage
a project's build, reporting and documentation from a central piece of
information.

Maven 4.0.0-alpha-9 is available via https://maven.apache.org/download.cgi

This is an alpha release, not suitable for production. If you hit any problem,
please raise a JIRA issue or send an email to the mailing list.

The full list of changes can be found in our issue management system [1].
Among those are:
 * switch to Maven Resolver 2.0.0-alpha-3
 * multi-threaded model builder
 * namespace support in xml configuration
 * ability to create proxies to inject SessionScoped beans into singletons
 * Maven 4 API improvements: plugin api, dependency collection /
resolution, version / version range resolution

For more information read
https://maven.apache.org/docs/4.0.0-alpha-9/release-notes.html

[1] 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12353746

Enjoy !
Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[RESULT] [VOTE] Release Apache Maven 4.0.0-alpha-9

[Guillaume Nodet]

Closing this vote with 6 +1s and no other votes.
I'll publish and announce the release asap.

Thx !

Le ven. 8 déc. 2023 à 20:12, Guillaume Nodet  a écrit :

> I'm starting a new vote to release this new alpha.
>
> This alpha release provides a bunch of new things:
>   * switch to maven-resolver 2.0.0-alpha-3
>   * multi-threaded model builder
>   * namespace support in xml configuration
>   * ability to create proxies to inject SessionScoped beans into singletons
>   * Maven 4 API improvements: plugin api, dependency collection /
> resolution, version / version range resolution
>
> Fwiw, a few plugins have already been ported to the new API (clean,
> install, deploy, resources, compiler) and do pass their integration tests,
> i'll update the PR https://github.com/apache/maven/pull/1048/files asap.
>
> 29 issues solved:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12353746
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2042
>
> Dev dist directory:
> https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-9/
>
> Staged site:
> https://maven.apache.org/ref/4-LATEST/
>
> Draft for release notes:
> https://github.com/apache/maven-site/pull/474
>
> https://github.com/apache/maven-site/blob/434a9bad8c13b6df76643d4d2ef0628b5ff4a8d4/content/markdown/docs/4.0.0-alpha-9/release-notes.md
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72h
>
> [ ] +1
> [ ] +0
> [ ] -1
>
>
> --
> 
> Guillaume Nodet
>
>

-- 

Guillaume Nodet

Re: [VOTE] Release Apache Maven 4.0.0-alpha-9

[Guillaume Nodet]

+1

Le ven. 8 déc. 2023 à 20:12, Guillaume Nodet  a écrit :

> I'm starting a new vote to release this new alpha.
>
> This alpha release provides a bunch of new things:
>   * switch to maven-resolver 2.0.0-alpha-3
>   * multi-threaded model builder
>   * namespace support in xml configuration
>   * ability to create proxies to inject SessionScoped beans into singletons
>   * Maven 4 API improvements: plugin api, dependency collection /
> resolution, version / version range resolution
>
> Fwiw, a few plugins have already been ported to the new API (clean,
> install, deploy, resources, compiler) and do pass their integration tests,
> i'll update the PR https://github.com/apache/maven/pull/1048/files asap.
>
> 29 issues solved:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12353746
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2042
>
> Dev dist directory:
> https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-9/
>
> Staged site:
> https://maven.apache.org/ref/4-LATEST/
>
> Draft for release notes:
> https://github.com/apache/maven-site/pull/474
>
> https://github.com/apache/maven-site/blob/434a9bad8c13b6df76643d4d2ef0628b5ff4a8d4/content/markdown/docs/4.0.0-alpha-9/release-notes.md
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72h
>
> [ ] +1
> [ ] +0
> [ ] -1
>
>
> --
> 
> Guillaume Nodet
>
>

-- 

Guillaume Nodet

[VOTE] Release Apache Maven 4.0.0-alpha-9

[Guillaume Nodet]

I'm starting a new vote to release this new alpha.

This alpha release provides a bunch of new things:
  * switch to maven-resolver 2.0.0-alpha-3
  * multi-threaded model builder
  * namespace support in xml configuration
  * ability to create proxies to inject SessionScoped beans into singletons
  * Maven 4 API improvements: plugin api, dependency collection /
resolution, version / version range resolution

Fwiw, a few plugins have already been ported to the new API (clean,
install, deploy, resources, compiler) and do pass their integration tests,
i'll update the PR https://github.com/apache/maven/pull/1048/files asap.

29 issues solved:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12353746

Staging repository:
https://repository.apache.org/content/repositories/maven-2042

Dev dist directory:
https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-9/

Staged site:
https://maven.apache.org/ref/4-LATEST/

Draft for release notes:
https://github.com/apache/maven-site/pull/474
https://github.com/apache/maven-site/blob/434a9bad8c13b6df76643d4d2ef0628b5ff4a8d4/content/markdown/docs/4.0.0-alpha-9/release-notes.md

Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for 72h

[ ] +1
[ ] +0
[ ] -1


-- 

Guillaume Nodet

Re: [VOTE] Release Maven Javadoc Plugin version 3.6.3

[Guillaume Nodet]

+1

Le jeu. 30 nov. 2023 à 22:41, Michael Osipov  a écrit :

> Hi,
>
> we solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529=12353857
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MJAVADOC/issues
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2041/
>
> https://repository.apache.org/content/repositories/maven-2041/org/apache/maven/plugins/maven-javadoc-plugin/3.6.3/maven-javadoc-plugin-3.6.3-source-release.zip
>
> Source release checksum(s):
> maven-javadoc-plugin-3.6.3-source-release.zip
> sha512:
>
> 724078534531971f9b2a616fe4493f103311686275a495fd7dcdfe019ec0eec5f0f9a85b3329584a68ffcddd244840245ee9265c4aa512b94201701076c70a68
>
> Staging site:
> https://maven.apache.org/plugins-archives/maven-javadoc-plugin-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Release Maven Resolver 2.0.0-alpha-3

[Guillaume Nodet]

+1

Le mar. 28 nov. 2023 à 16:00, Tamás Cservenák  a
écrit :

> Howdy,
>
> Note: This is a third (and hopefully last, unless something unexpected
> crops out) preview release of Resolver 2.0.0, that would allow any
> downstream consumers to try it out and adapt. It contains major cleanup and
> package and class renames (not affecting public APIs, but affecting
> configuration!). It also includes "windows fix" from the 1.9.18 version.
>
> For configuration changes, see
>
> https://maven.apache.org/resolver-archives/resolver-LATEST/configuration.html
>
> Note: this page above is from now on GENERATED out of sources. Before it
> was manually authored that was error prone and laborious, plus there was a
> source vs page discrepancy as well it omitted some properties (usually by
> mistake).
>
> IF the vote is successful, the staging site will NOT be moved to
> https://maven.apache.org/resolver/ but instead will be made reachable from
> https://maven.apache.org/resolver-archives/resolver-2.0.0-alpha-3/ only.
>
> The 1.9.18 is still the "latest stable" release of Maven Resolver.
>
> ===
>
> We solved 12 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353963
>
> There are still some issues in JIRA:
> https://issues.apache.org/jira/projects/MRESOLVER/issues
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2040
>
> Source release SHA512:
>
> 3eeb611f90da03a20479ef6086a3112ffd5c0289a72011e65c274e919ac2573d5d3fa124c1a3e506fdbecb15b22969c925ae1c1937b0e0778ceeb8fe8803dead
>
> Staging site:
> https://maven.apache.org/resolver-archives/resolver-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>


-- 

Guillaume Nodet

Re: [VOTE] Apache Maven Build Cache Extension 1.1.0

[Guillaume Nodet]

+1

Le lun. 27 nov. 2023 à 03:12, Olivier Lamy  a écrit :

> Hi,
> I'd like to release the Apache Maven Build Cache Extension 1.1.0.
> We've fixed 8 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352470=Text=12324820
>
> Staging repo
> https://repository.apache.org/content/repositories/maven-2038/
>
> source release
> https://repository.apache.org/content/repositories/maven-2038/org/apache/maven/extensions/maven-build-cache-extension/1.1.0/maven-build-cache-extension-1.1.0-source-release.zip
>
> sha512
> https://repository.apache.org/content/repositories/maven-2038/org/apache/maven/extensions/maven-build-cache-extension/1.1.0/maven-build-cache-extension-1.1.0-source-release.zip.sha512
>
> Staging site:
> https://maven.apache.org/extensions-archives/maven-build-cache-extension-LATEST/
>
> Vote open for 72h
>
> +1
> 0
> -1
>
> regards
> Olivier
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 

Guillaume Nodet

Re: [VOTE] Release Maven Site Plugin version 4.0.0-M12

[Guillaume Nodet]

+1

Le mar. 21 nov. 2023 à 22:22, Michael Osipov  a écrit :
>
> Hi,
>
> IMPORTANT: This require the following staging repositories:
>
> * Maven Reporting Impl 4.0.0-M12
> * Maven Reporting Exec 4.0.0-M12
>
> we solved 7 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12353780
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution%20%3D%20Unresolved
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2036/
> https://repository.apache.org/content/repositories/maven-2036/org/apache/maven/plugins/maven-site-plugin/4.0.0-M12/maven-site-plugin-4.0.0-M12-source-release.zip
>
> Source release checksum(s):
> maven-site-plugin-4.0.0-M12-source-release.zip
> sha512:
> 463da0c6ccb7d0fbbf8b5460ed61c361b6560b6f394857328e251df645e0c2ae08a9872dd74ee06878baaeea26821947dc3453bb380439fa8b6733ac6d93a18c
>
> Staging site:
> https://maven.apache.org/plugins-archives/maven-site-plugin-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>


-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven Reporting Impl version 4.0.0-M12

[Guillaume Nodet]

+1

Le mar. 21 nov. 2023 à 21:00, Michael Osipov  a écrit :
>
> Hi,
>
> we solved 5 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12353750
>
> There is one issue left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-reporting-impl
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2034/
> https://repository.apache.org/content/repositories/maven-2034/org/apache/maven/reporting/maven-reporting-impl/4.0.0-M12/maven-reporting-impl-4.0.0-M12-source-release.zip
>
> Source release checksum(s):
> maven-reporting-impl-4.0.0-M12-source-release.zip
> sha512:
> cb827514757e9dfb4a8a726723782124b3412602ff26c290c186acd20a2749a2aa37e49c8a6f5e4c04c55744a04baf914b28fba428a9db67f7a0f5c02ef0
>
> Staging site:
> https://maven.apache.org/shared-archives/maven-reporting-impl-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>


-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven Reporting Exec version 2.0.0-M12

[Guillaume Nodet]

+1

Le mar. 21 nov. 2023 à 21:12, Michael Osipov  a écrit :
>
> Hi,
>
> IMPORTANT: This require the following staging repositories:
>
> * Maven Reporting Impl 4.0.0-M12
>
> we solved 4 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12353779
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-reporting-exec
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2035/
> https://repository.apache.org/content/repositories/maven-2035/org/apache/maven/reporting/maven-reporting-exec/2.0.0-M12/maven-reporting-exec-2.0.0-M12-source-release.zip
>
> Source release checksum(s):
> maven-reporting-exec-2.0.0-M12-source-release.zip
> sha512:
> e37d85dd227f7ae8c254c054681b25558899ad0eb40b43c90640af4fa11ed05efa0439bda584e498bbc587b551427fe88ec94972d7c270f7a517b9f71b343c0c
>
> Staging site:
> https://maven.apache.org/shared-archives/maven-reporting-exec-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>


-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Maven Resolver 1.9.18

[Guillaume Nodet]

+1

Le mer. 22 nov. 2023 à 17:17, Tamás Cservenák  a écrit :
>
> Howdy,
>
> Note1: Maven Resolver 1.x lineage is in "bugfix only" maintenance mode.
> Note2: Resolver 1.9.17 release is declared "broken" by RM, release 1.9.18
> undos the unwanted code change that happened in FileUtils@1.9.17 and
> restores source compatibility between 2.x and 1.9.x.
>
> We solved 2 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353878
>
> There are still some issues in JIRA:
> https://issues.apache.org/jira/projects/MRESOLVER/issues
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2037
>
> Source release SHA512:
> b74842017a4a2869dbe118a69d29d9eae39df33fc6f1dd056e5440c7489694aa1e6f53705a77d7a8af7a7a48301b1a6b48577486202900de358463acc3045e82
>
> Staging site:
> https://maven.apache.org/resolver-archives/resolver-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1



-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven Reporting API version 4.0.0-M9

[Guillaume Nodet]

The JIRA title indicates doc change only... maybe it should be reworded a bit.

Le mer. 15 nov. 2023 à 10:40, Michael Osipov  a écrit :
>
> API change/update and still have to go through formal vote.
>
> On 2023/11/14 21:32:05 Guillaume Nodet wrote:
> > +1
> >
> > There's not much in this release, mostly the parent upgrade. What's
> > the expectation here ?
> >
> > Le dim. 12 nov. 2023 à 19:59, Michael Osipov  a écrit :
> > >
> > > Hi,
> > >
> > > we solved 2 issues:
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12353749
> > >
> > > There are no issues left in JIRA:
> > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-reporting-api
> > >
> > > Staging repo:
> > > https://repository.apache.org/content/repositories/maven-2027/
> > > https://repository.apache.org/content/repositories/maven-2027/org/apache/maven/reporting/maven-reporting-api/4.0.0-M9/maven-reporting-api-4.0.0-M9-source-release.zip
> > >
> > > Source release checksum(s):
> > > maven-reporting-api-4.0.0-M9-source-release.zip
> > > sha512:
> > > 2c8402b3a2fbcc30c6f2610aa24d2c02394590358a29dbffec45f701e36796fa467c4807595bfe66e4e96b139dca7a80978c050d01760d2b327b28efb6b5
> > >
> > > Staging site:
> > > https://maven.apache.org/shared-archives/maven-reporting-api-LATEST/
> > >
> > > Guide to testing staged releases:
> > > https://maven.apache.org/guides/development/guide-testing-releases.html
> > >
> > > Vote open for 72 hours.
> > >
> > > [ ] +1
> > > [ ] +0
> > > [ ] -1
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > >
> >
> >
> > --
> > 
> > Guillaume Nodet
> >
> > -----
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>


-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Maven Project Info Reports Plugin version 3.5.0

[Guillaume Nodet]

+1

Le ven. 17 nov. 2023 à 22:56, Michael Osipov  a écrit :
>
> Hi,
>
> we solved 3 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821=12353875
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MPIR/issues
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2031/
> https://repository.apache.org/content/repositories/maven-2031/org/apache/maven/plugins/maven-project-info-reports-plugin/3.5.0/maven-project-info-reports-plugin-3.5.0-source-release.zip
>
> Source release checksum(s):
> maven-project-info-reports-plugin-3.5.0-source-release.zip
> sha512:
> c5c9feedceacccfeec06bb503ec9e80f08a88671892cf260a0385cbde84f2bee3e283c8e62b3c1d20cf847af0e81033c618cf4fe6dbc20f2b56050331fb8a2d4
>
> Staging site:
> https://maven.apache.org/plugins-archives/maven-project-info-reports-plugin-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>


-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Maven Resolver 1.9.17

[Guillaume Nodet]

+1

Le sam. 18 nov. 2023 à 00:27, Tamás Cservenák  a écrit :
>
> Howdy,
>
> Note: Maven Resolver 1.x lineage is in "bugfix only" maintenance mode.
>
> We solved 4 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353659
>
> There are still some issues in JIRA:
> https://issues.apache.org/jira/projects/MRESOLVER/issues
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2032/
>
> Source release SHA512:
> c594df21e82b198abefb1fdad67d68c1c6eda69e279ebb9bd1e1c20e361ae40f4bab99dfc00f9699e9129760a864b703ced61322361debe3abeefafcd78f3633
>
> Staging site:
> https://maven.apache.org/resolver-archives/resolver-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1



-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Maven Resolver 2.0.0-alpha-2

[Guillaume Nodet]

+1

Le mer. 15 nov. 2023 à 16:21, Tamás Cservenák  a écrit :
>
> Howdy,
>
> Note: This is a second preview release of Resolver 2.0.0, that would allow
> any downstream consumers to try it out and adapt. Most of the major issues
> were fixed, almost all of the functionality is there (compare JIRA "2.0.0"
> and "2.0.0-alpha-2" versions).
>
> Relevant changes as compared to alpha-1:
> Implemented "onSessionClose" and using that in new HTTP/2 clients for
> proper client cleanup. Moreover, JDK java.net.http.HttpClient close method
> is used in jdk transport (hence Java21 build-time requirement).
> This version of resolver is still "drop in" replacement into client code IF
> it does
> not touch any deprecated thing from Resolver 1.x (as those are dropped), but
> session handling as mentioned above is changed, so integrators (like Maven)
> need to adapt: https://github.com/apache/maven/pull/1301
> Resolver client codebase like Mojos does NOT need any change.
>
> See
> https://maven.apache.org/resolver-archives/resolver-LATEST/upgrading-resolver.html
>
> IF the vote is successful, the staging site will NOT be moved to
> https://maven.apache.org/resolver/ but instead will be made reachable from
> https://maven.apache.org/resolver-archives/resolver-2.0.0-alpha-2/ only.
>
> The 1.9.16 is still the "latest stable" release of Maven Resolver.
>
> ===
>
> We solved 11 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353841
>
> There are still some issues in JIRA:
> https://issues.apache.org/jira/projects/MRESOLVER/issues
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2030
>
> Source release SHA512:
> 52c0c99b9ed78bf070551521a96efb3b5b28f55a6b8005b8d9b72f5ded8c475e5212f257c5983d06d5741cf67652e51426f7795e5fca01bd645289eba64974cb
>
> Staging site:
> https://maven.apache.org/resolver-archives/resolver-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1



-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven Reporting API version 4.0.0-M9

[Guillaume Nodet]

+1

There's not much in this release, mostly the parent upgrade. What's
the expectation here ?

Le dim. 12 nov. 2023 à 19:59, Michael Osipov  a écrit :
>
> Hi,
>
> we solved 2 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12353749
>
> There are no issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-reporting-api
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2027/
> https://repository.apache.org/content/repositories/maven-2027/org/apache/maven/reporting/maven-reporting-api/4.0.0-M9/maven-reporting-api-4.0.0-M9-source-release.zip
>
> Source release checksum(s):
> maven-reporting-api-4.0.0-M9-source-release.zip
> sha512:
> 2c8402b3a2fbcc30c6f2610aa24d2c02394590358a29dbffec45f701e36796fa467c4807595bfe66e4e96b139dca7a80978c050d01760d2b327b28efb6b5
>
> Staging site:
> https://maven.apache.org/shared-archives/maven-reporting-api-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>


-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven ASF Parent 31

[Guillaume Nodet]

+1

Le mer. 8 nov. 2023 à 23:27, Slawomir Jaranowski
 a écrit :
>
> Hi,
>
> We solved 11 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12353313
>
> Changes since the last release for Apache Maven ASF Parent:
> https://github.com/apache/maven-apache-parent/compare/apache-30...apache-31
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapacheapache-1036/
> https://repository.apache.org/content/repositories/orgapacheapache-1036/org/apache/apache/31/apache-31-source-release.zip
>
> Source release checksum(s):
> apache-31-source-release.zip - SHA-512 :
> b60e0ef1899ab77a44b9afe5af50087d353fc67bda991fca11815abc18514f4fea6e90c452a503d56bb342a2a1854f9b4a7f655ce48bda90c5dab67468a06316
>
> Staging site:
> https://maven.apache.org/pom-archives/asf-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> --
> Sławomir Jaranowski
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>


-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven POMs 41

[Guillaume Nodet]

+1

Le mer. 8 nov. 2023 à 23:56, Slawomir Jaranowski
 a écrit :
>
> Hi,
>
> NOTE: Staging of Apache ASF parent 41 is required for testing.
>
> We solved 10 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12353349
>
> Changes since the last release for Apache Maven POMs:
> https://github.com/apache/maven-parent/compare/maven-parent-40...maven-parent-41
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2026/
> https://repository.apache.org/content/repositories/maven-2026/org/apache/maven/maven-parent/41/maven-parent-41-source-release.zip
>
> Source release checksum(s):
> maven-parent-41-source-release.zip - SHA-512 :
> d3a76493f784edf7032c73b5497837d64db0441a30da1debcb99c3341748c774b791d5f88f4b825937d84394116fe72012b6da9a0dd20e5c5d890269178f6834
>
>
> Staging site:
> https://maven.apache.org/pom-archives/maven-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
> --
> Sławomir Jaranowski
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>


-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[RESULT] [VOTE] Release Apache Maven Daemon 1.0-m8

[Guillaume Nodet]

Closing this vote with 5 +1s and no other votes.
I'll publish the release asap.

Thx to everyone !
Guillaume

Le jeu. 26 oct. 2023 à 08:43, Guillaume Nodet  a écrit :
>
> I've staged a candidate release at
> https://dist.apache.org/repos/dist/dev/maven/mvnd/1.0-m8/
>
> This release provides distributions based on Maven 3.9.5 and
> 4.0.0-alpha-8 releases.
> The release notes are available at :
> 
> https://github.com/apache/maven-mvnd/releases/tag/untagged-56be0cecfa7305fcd889
>
> Please review and vote !
> --
> ----
> Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven Daemon 1.0-m8

[Guillaume Nodet]

+1

Le jeu. 26 oct. 2023 à 08:43, Guillaume Nodet  a écrit :
>
> I've staged a candidate release at
> https://dist.apache.org/repos/dist/dev/maven/mvnd/1.0-m8/
>
> This release provides distributions based on Maven 3.9.5 and
> 4.0.0-alpha-8 releases.
> The release notes are available at :
> 
> https://github.com/apache/maven-mvnd/releases/tag/untagged-56be0cecfa7305fcd889
>
> Please review and vote !
> --
> ----
> Guillaume Nodet



-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven Daemon 1.0-m8

[Guillaume Nodet]

Yes, sorry about that.  It's draft release and not visible if you're not a
member of the github apache organization.
The pages is as below:

Maven Daemon comes into two different flavours: m39 which embeds Maven
3.9.x, and m40 which embeds Maven 4.0.0-alpha-x.
What's Changed

   - [MNG-6847] Use diamond operator by @timtebeek
   <https://github.com/timtebeek> in #886
   <https://github.com/apache/maven-mvnd/pull/886>
   - Update: Maven 3.9.5 + Resolver 1.9.16 by @cstamas
   <https://github.com/cstamas> in #887
   <https://github.com/apache/maven-mvnd/pull/887>
   - Fix terminal width (fixes #870
   <https://github.com/apache/maven-mvnd/issues/870>) by @gnodet
   <https://github.com/gnodet> in #891
   <https://github.com/apache/maven-mvnd/pull/891>
   - Update build instructions for Windows by @KasNotten
   <https://github.com/KasNotten> in #890
   <https://github.com/apache/maven-mvnd/pull/890>
   - Removed superfluous public for tests by @khmarbaise
   <https://github.com/khmarbaise> in #882
   <https://github.com/apache/maven-mvnd/pull/882>
   - Support JDK 21 at build time by @gnodet <https://github.com/gnodet> in
   #894 <https://github.com/apache/maven-mvnd/pull/894>
   - Make sure the plugin works with maven 3 by @gnodet
   <https://github.com/gnodet> in #893
   <https://github.com/apache/maven-mvnd/pull/893>
   - Small improvements to DaemonPrompter by @gnodet
   <https://github.com/gnodet> in #898
   <https://github.com/apache/maven-mvnd/pull/898>
   - Switch to Maven 4.0.0-alpha-8 by @gnodet <https://github.com/gnodet> in
#895 <https://github.com/apache/maven-mvnd/pull/895>
   - Upgrade JLine from 3.23.0 to 3.24.0 by @gnodet
   <https://github.com/gnodet> in #899
   <https://github.com/apache/maven-mvnd/pull/899>

New Contributors

   - @timtebeek <https://github.com/timtebeek> made their first
   contribution in #886 <https://github.com/apache/maven-mvnd/pull/886>
   - @KasNotten <https://github.com/KasNotten> made their first
   contribution in #890 <https://github.com/apache/maven-mvnd/pull/890>
   - @khmarbaise <https://github.com/khmarbaise> made their first
   contribution in #882 <https://github.com/apache/maven-mvnd/pull/882>

*Full Changelog*: 1.0-m7...1.0-m8
<https://github.com/apache/maven-mvnd/compare/1.0-m7...1.0-m8>



Le jeu. 26 oct. 2023 à 08:48, tison  a écrit :
>
> The link to release note is broken.
>
> Best,
> tison.
>
>
> Guillaume Nodet  于2023年10月26日周四 14:44写道：
>
> > I've staged a candidate release at
> > https://dist.apache.org/repos/dist/dev/maven/mvnd/1.0-m8/
> >
> > This release provides distributions based on Maven 3.9.5 and
> > 4.0.0-alpha-8 releases.
> > The release notes are available at :
> >
> >
https://github.com/apache/maven-mvnd/releases/tag/untagged-56be0cecfa7305fcd889
> >
> > Please review and vote !
> > --
> > 
> > Guillaume Nodet
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >



-- 

Guillaume Nodet

[VOTE] Release Apache Maven Daemon 1.0-m8

[Guillaume Nodet]

I've staged a candidate release at
https://dist.apache.org/repos/dist/dev/maven/mvnd/1.0-m8/

This release provides distributions based on Maven 3.9.5 and
4.0.0-alpha-8 releases.
The release notes are available at :

https://github.com/apache/maven-mvnd/releases/tag/untagged-56be0cecfa7305fcd889

Please review and vote !
-- 

Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[ANN] Apache Maven 4.0.0-alpha-8 released

[Guillaume Nodet]

The Apache Maven team is pleased to announce the release of
Apache Maven 4.0.0-alpha-8.

Apache Maven is a software project management and comprehension tool.
Based on the concept of a project object model (POM), Maven can manage
a project's build, reporting and documentation from a central piece of
information.

Maven 4.0.0-alpha-8 is available via https://maven.apache.org/download.cgi

This is an alpha release, not suitable for production. If you hit any problem,
please raise a JIRA issue or send an email to the mailing list.

This alpha release provides new cornerstone features for the future Maven
evolution. In particular, the POM model which was set in stone to a 4.0.0
version since Maven 2.0, is now able to evolve. For modules that have a
packaging which is not POM, the flattened consumer POM is now
installed/deployed instead of the main POM, eventually translated back
into a 4.0.0 model version for consumer compatibility. The build POM is
also installed / deployed unchanged with build classifier. This allows the
introduction of the 4.1.0 model which already brings a few improvements.

The full list of changes can be found in our issue management system.
Among those are:
* switch from Plexus XML to StAX / Woodstox for XML parsing
* support for alternative POM syntaxes
* introduce a 4.1.0 model version
* add flexible goal ordering (in 4.1.0 model)
* allow glob patterns in dependency exclusions
* support proxy port interpolation in settings.xml
* add support for TRACE logging level (with style “bold,magenta”)
* add model version analysis and downgrade
* attach the build POM (with build clasifier) and simplify the
build/consumer implementation
* add a new BOM packaging
* trim down the consumer POM
* expose the rootDirectory for model processing
* support configuration in extensions.xml /  elements (in
4.1.0 model)
* generic .uri suffix to get the URI representation of any file property
* allow registering Maven core extension in .m2 directory instead of MAVEN_HOME
* colorize transfer messages
* the root attribute introduced in alpha-7 has been moved to the new 4.1.0 model

For more information read
https://maven.apache.org/docs/4.0.0-alpha-8/release-notes.html

Enjoy !
Guillaume Nodet

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[RESULT] [VOTE] Apache Maven 4.0.0-alpha-8 release

[Guillaume Nodet]

Closing this vote with 7 +1s and no other votes.
I'll continue the release process...

Thx to everyone !
Guillaume

Le ven. 20 oct. 2023 à 23:37, Guillaume Nodet  a écrit :

> I'm starting a new vote to release this new alpha.
>
> This alpha release provides new cornerstone features for the future Maven
> evolution.
> In particular, the POM model which was set in stone to a 4.0.0 version
> since Maven 3.0, is now able to evolve. For modules that have a packaging
> which is not POM, the flattened consumer POM is now installed/deployed
> instead of the main POM, eventually translated back into a 4.0.0 model
> version for consumer compatibility. The build POM is also installed /
> deployed unchanged. This allows the introduction of the 4.1.0 model which
> already brings a few improvements.
>
> 50 issues solved:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12353356
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2011
>
> Dev dist directory:
> https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-8/
>
> Source release checksums:
> apache-maven-4.0.0-alpha-8-src.zip sha512:
>
> 7264b5ae1a567ff9249f8020bc5713386f26bdd297b499e309a70897d03b647ef5a1446d10963529fd50dbab0ee56f5357ab39405462b8a5326a99bae80222c9
>
> apache-maven-4.0.0-alpha-8-src.tar.gz sha512:
>
> d645e4015119836428e16bd5d4dd29bed6d4983d552445cdf587a61f0a2347a619e9de02cdc590eda000c4561e60e33e758aa83dca3d6243ede97f5be981b322
>
>
> Binary release checksums:
> apache-maven-4.0.0-alpha-8-bin.zip sha512:
>
> 6aa9486e2d880b691580e0071347022b6426f0a6b2c6549879b6a848a4494c70ff8dff25ffe8de2edd82583d7119bf359156ece0f9ef18f1c99ff3db776461f3
>
> apache-maven-4.0.0-alpha-8-bin.tar.gz sha512:
>
> 7646b5bbaa0b81e600076055134ba88d5bd02d7a0ae03829b7e217aad9e47c25a3edbf4b091562d4bc9d93b5a50e84449a679f18052dc4f97d0314a8bc9dd961
>
>
> Staged site:
> https://maven.apache.org/ref/4-LATEST/
>
> Draft for release notes:
> https://github.com/apache/maven-site/pull/462
>
> https://github.com/apache/maven-site/blob/21deeaf4a0fc4993e0091d214f194195dc66c167/content/markdown/docs/4.0.0-alpha-8/release-notes.md
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Note that this release has been built and uploaded with 4.0.0-alpha-8
> itself, which means it uses the new build and consumer POMs...
>
> Vote open for 72h
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> Cheers
> Guillaume
>


-- 

Guillaume Nodet

Re: [VOTE] Apache Maven 4.0.0-alpha-8 release

[Guillaume Nodet]

+1

Le ven. 20 oct. 2023 à 23:37, Guillaume Nodet  a écrit :

> I'm starting a new vote to release this new alpha.
>
> This alpha release provides new cornerstone features for the future Maven
> evolution.
> In particular, the POM model which was set in stone to a 4.0.0 version
> since Maven 3.0, is now able to evolve. For modules that have a packaging
> which is not POM, the flattened consumer POM is now installed/deployed
> instead of the main POM, eventually translated back into a 4.0.0 model
> version for consumer compatibility. The build POM is also installed /
> deployed unchanged. This allows the introduction of the 4.1.0 model which
> already brings a few improvements.
>
> 50 issues solved:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12353356
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2011
>
> Dev dist directory:
> https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-8/
>
> Source release checksums:
> apache-maven-4.0.0-alpha-8-src.zip sha512:
>
> 7264b5ae1a567ff9249f8020bc5713386f26bdd297b499e309a70897d03b647ef5a1446d10963529fd50dbab0ee56f5357ab39405462b8a5326a99bae80222c9
>
> apache-maven-4.0.0-alpha-8-src.tar.gz sha512:
>
> d645e4015119836428e16bd5d4dd29bed6d4983d552445cdf587a61f0a2347a619e9de02cdc590eda000c4561e60e33e758aa83dca3d6243ede97f5be981b322
>
>
> Binary release checksums:
> apache-maven-4.0.0-alpha-8-bin.zip sha512:
>
> 6aa9486e2d880b691580e0071347022b6426f0a6b2c6549879b6a848a4494c70ff8dff25ffe8de2edd82583d7119bf359156ece0f9ef18f1c99ff3db776461f3
>
> apache-maven-4.0.0-alpha-8-bin.tar.gz sha512:
>
> 7646b5bbaa0b81e600076055134ba88d5bd02d7a0ae03829b7e217aad9e47c25a3edbf4b091562d4bc9d93b5a50e84449a679f18052dc4f97d0314a8bc9dd961
>
>
> Staged site:
> https://maven.apache.org/ref/4-LATEST/
>
> Draft for release notes:
> https://github.com/apache/maven-site/pull/462
>
> https://github.com/apache/maven-site/blob/21deeaf4a0fc4993e0091d214f194195dc66c167/content/markdown/docs/4.0.0-alpha-8/release-notes.md
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Note that this release has been built and uploaded with 4.0.0-alpha-8
> itself, which means it uses the new build and consumer POMs...
>
> Vote open for 72h
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> Cheers
> Guillaume
>


-- 

Guillaume Nodet

Re: [VOTE] Apache Maven 4.0.0-alpha-8 release

[Guillaume Nodet]

Le mar. 24 oct. 2023 à 01:22, Hervé Boutemy  a
écrit :

> Le lundi 23 octobre 2023, 10:00:59 CEST Guillaume Nodet a écrit :
> > Le sam. 21 oct. 2023 à 18:19, Herve Boutemy  a
> écrit :
> > > I updated release notes
> > >
> > > a few remarks/questions:
> > >
> > > - it would be nice to have a description in Jira issues for all the new
> > > features, because some titles are interesting but Jira is empty and I
> > > can't
> > > figure out how to use the feature (alternative pom syntax, model
> version
> > > analysis and downgrade, glob patterns in dependency exclusions)
> >
> > Sounds good, I'll try to add some.
> thank you
>

Done


>
> >
> > > - is model 4.1.0 documentation generated somewhere?
> >
> > Which documentation ?  I think we should prepare for when we'll release
> > 4.0.0 GA, but I would consider 4.1.0 as a moving target until that time.
> here is 4.0.0 reference documentation
>  https://maven.apache.org/ref/3.9.5/maven-model/maven.html
>
> i expect to have an equivalent for 4.1.0
>

The doc for the old model was still generated.
I've raised https://github.com/apache/maven/pull/1297 which should fix the
model documentation.


>
>
> >
> > > - given Plexus XML was removed in favor or StAX, is plexus-xml 4 still
> > > something useful?
> >
> > Plexus-utils has been removed as a core dependency, but it's still a
> > dependency of Sisu.
> > For plexus-xml, even if the parser used is now mostly Stax, there are
> still
> > a couple of references to the xpp3 one in XmlNodeBuilder and in
> > maven-compat.
> > For compatibility with all plugins, I don't think we'll be able to remove
> > it in the near future.
> ok, I see, thanks
>
> >
> > > - I suppose I'll have to add BOM packaging documentation to
> > > https://maven.apache.org/ref/4-LATEST/maven-core/default-bindings.html
>
> it would be nice to have reference documentation
>  https://maven.apache.org/ref/4-LATEST
> following code updates: documentation is not only when the final release
> happens
>

Got it.

Guillaume


>
> > >
> > > On 2023/10/21 14:34:32 Herve Boutemy wrote:
> > > > +1
> > > >
> > > > Reproducible Build ok: reference build done with JDK 21 on *nix with
> > >
> > > umask 022 and Maven 4.0.0-alpha-8 itself (yes...)
> > >
> > > > a few remarks:
> > > > - I'll add some updates to release notes later
> > > > - during tests, I found that an active repository configured in my
> > >
> > > settings.xml had been added to the published consumer POM: I'm
> wondering
> > > if
> > > such behaviour is not a risk of leak of personal data
> > >
> > > > - the fact that the site is borked, then maven-site-plugin seems not
> to
> > >
> > > be fully working with this release shows that changes broke some
> things:
> > > not a blocker, it's an alpha, but definitively we need people testing
> > > their
> > > own projects and reporting when they find such issues
> > >
> > > > Regards,
> > > >
> > > > Hervé
> > > >
> > > > On 2023/10/20 21:37:10 Guillaume Nodet wrote:
> > > > > I'm starting a new vote to release this new alpha.
> > > > >
> > > > > This alpha release provides new cornerstone features for the future
> > >
> > > Maven
> > >
> > > > > evolution.
> > > > > In particular, the POM model which was set in stone to a 4.0.0
> version
> > > > > since Maven 3.0, is now able to evolve. For modules that have a
> > >
> > > packaging
> > >
> > > > > which is not POM, the flattened consumer POM is now
> installed/deployed
> > > > > instead of the main POM, eventually translated back into a 4.0.0
> model
> > > > > version for consumer compatibility. The build POM is also
> installed /
> > > > > deployed unchanged. This allows the introduction of the 4.1.0 model
> > >
> > > which
> > >
> > > > > already brings a few improvements.
> > >
> > > > > 50 issues solved:
> > >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922;
> > > version=12353356>
> > > > > Staging repository:
> > > > > https://repository.apache.org/content/repositories/maven-2011
> > > > >
> > > > > Dev dist directory:
> > 

Re: [VOTE] Apache Maven 4.0.0-alpha-8 release

[Guillaume Nodet]

Le sam. 21 oct. 2023 à 18:19, Herve Boutemy  a écrit :

> I updated release notes
>
> a few remarks/questions:
>
> - it would be nice to have a description in Jira issues for all the new
> features, because some titles are interesting but Jira is empty and I can't
> figure out how to use the feature (alternative pom syntax, model version
> analysis and downgrade, glob patterns in dependency exclusions)
>

Sounds good, I'll try to add some.


>
> - is model 4.1.0 documentation generated somewhere?
>

Which documentation ?  I think we should prepare for when we'll release
4.0.0 GA, but I would consider 4.1.0 as a moving target until that time.


> - given Plexus XML was removed in favor or StAX, is plexus-xml 4 still
> something useful?
>

Plexus-utils has been removed as a core dependency, but it's still a
dependency of Sisu.
For plexus-xml, even if the parser used is now mostly Stax, there are still
a couple of references to the xpp3 one in XmlNodeBuilder and in
maven-compat.
For compatibility with all plugins, I don't think we'll be able to remove
it in the near future.


> - I suppose I'll have to add BOM packaging documentation to
> https://maven.apache.org/ref/4-LATEST/maven-core/default-bindings.html
>
> On 2023/10/21 14:34:32 Herve Boutemy wrote:
> > +1
> >
> > Reproducible Build ok: reference build done with JDK 21 on *nix with
> umask 022 and Maven 4.0.0-alpha-8 itself (yes...)
> >
> > a few remarks:
> > - I'll add some updates to release notes later
> > - during tests, I found that an active repository configured in my
> settings.xml had been added to the published consumer POM: I'm wondering if
> such behaviour is not a risk of leak of personal data
> > - the fact that the site is borked, then maven-site-plugin seems not to
> be fully working with this release shows that changes broke some things:
> not a blocker, it's an alpha, but definitively we need people testing their
> own projects and reporting when they find such issues
> >
> > Regards,
> >
> > Hervé
> >
> > On 2023/10/20 21:37:10 Guillaume Nodet wrote:
> > > I'm starting a new vote to release this new alpha.
> > >
> > > This alpha release provides new cornerstone features for the future
> Maven
> > > evolution.
> > > In particular, the POM model which was set in stone to a 4.0.0 version
> > > since Maven 3.0, is now able to evolve. For modules that have a
> packaging
> > > which is not POM, the flattened consumer POM is now installed/deployed
> > > instead of the main POM, eventually translated back into a 4.0.0 model
> > > version for consumer compatibility. The build POM is also installed /
> > > deployed unchanged. This allows the introduction of the 4.1.0 model
> which
> > > already brings a few improvements.
> > >
> > > 50 issues solved:
> > >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12353356
> > >
> > > Staging repository:
> > > https://repository.apache.org/content/repositories/maven-2011
> > >
> > > Dev dist directory:
> > > https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-8/
> > >
> > > Source release checksums:
> > > apache-maven-4.0.0-alpha-8-src.zip sha512:
> > >
> > >
> 7264b5ae1a567ff9249f8020bc5713386f26bdd297b499e309a70897d03b647ef5a1446d10963529fd50dbab0ee56f5357ab39405462b8a5326a99bae80222c9
> > >
> > > apache-maven-4.0.0-alpha-8-src.tar.gz sha512:
> > >
> > >
> d645e4015119836428e16bd5d4dd29bed6d4983d552445cdf587a61f0a2347a619e9de02cdc590eda000c4561e60e33e758aa83dca3d6243ede97f5be981b322
> > >
> > >
> > > Binary release checksums:
> > > apache-maven-4.0.0-alpha-8-bin.zip sha512:
> > >
> > >
> 6aa9486e2d880b691580e0071347022b6426f0a6b2c6549879b6a848a4494c70ff8dff25ffe8de2edd82583d7119bf359156ece0f9ef18f1c99ff3db776461f3
> > >
> > > apache-maven-4.0.0-alpha-8-bin.tar.gz sha512:
> > >
> > >
> 7646b5bbaa0b81e600076055134ba88d5bd02d7a0ae03829b7e217aad9e47c25a3edbf4b091562d4bc9d93b5a50e84449a679f18052dc4f97d0314a8bc9dd961
> > >
> > >
> > > Staged site:
> > > https://maven.apache.org/ref/4-LATEST/
> > >
> > > Draft for release notes:
> > > https://github.com/apache/maven-site/pull/462
> > >
> https://github.com/apache/maven-site/blob/21deeaf4a0fc4993e0091d214f194195dc66c167/content/markdown/docs/4.0.0-alpha-8/release-notes.md
> > >
> > > Guide to testing staged releases:
> > > http://maven.apache.org/guides/development/guide-testing-releases.html
&g

[VOTE] Apache Maven 4.0.0-alpha-8 release

[Guillaume Nodet]

I'm starting a new vote to release this new alpha.

This alpha release provides new cornerstone features for the future Maven
evolution.
In particular, the POM model which was set in stone to a 4.0.0 version
since Maven 3.0, is now able to evolve. For modules that have a packaging
which is not POM, the flattened consumer POM is now installed/deployed
instead of the main POM, eventually translated back into a 4.0.0 model
version for consumer compatibility. The build POM is also installed /
deployed unchanged. This allows the introduction of the 4.1.0 model which
already brings a few improvements.

50 issues solved:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12353356

Staging repository:
https://repository.apache.org/content/repositories/maven-2011

Dev dist directory:
https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-8/

Source release checksums:
apache-maven-4.0.0-alpha-8-src.zip sha512:

7264b5ae1a567ff9249f8020bc5713386f26bdd297b499e309a70897d03b647ef5a1446d10963529fd50dbab0ee56f5357ab39405462b8a5326a99bae80222c9

apache-maven-4.0.0-alpha-8-src.tar.gz sha512:

d645e4015119836428e16bd5d4dd29bed6d4983d552445cdf587a61f0a2347a619e9de02cdc590eda000c4561e60e33e758aa83dca3d6243ede97f5be981b322


Binary release checksums:
apache-maven-4.0.0-alpha-8-bin.zip sha512:

6aa9486e2d880b691580e0071347022b6426f0a6b2c6549879b6a848a4494c70ff8dff25ffe8de2edd82583d7119bf359156ece0f9ef18f1c99ff3db776461f3

apache-maven-4.0.0-alpha-8-bin.tar.gz sha512:

7646b5bbaa0b81e600076055134ba88d5bd02d7a0ae03829b7e217aad9e47c25a3edbf4b091562d4bc9d93b5a50e84449a679f18052dc4f97d0314a8bc9dd961


Staged site:
https://maven.apache.org/ref/4-LATEST/

Draft for release notes:
https://github.com/apache/maven-site/pull/462
https://github.com/apache/maven-site/blob/21deeaf4a0fc4993e0091d214f194195dc66c167/content/markdown/docs/4.0.0-alpha-8/release-notes.md

Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html

Note that this release has been built and uploaded with 4.0.0-alpha-8
itself, which means it uses the new build and consumer POMs...

Vote open for 72h

[ ] +1
[ ] +0
[ ] -1

Cheers
Guillaume

Re: Maven 5 pom extension for agents

[Guillaume Nodet]

If false positives are a problem, we could just have an empty default value.
Users would simply have to configure something like:
   net.bytebuddy:byte-buddy-agent
Also, a special auto-discover value  (or another predefined value of
course) could be used to discover agents in the test classpath and add them
as agents automatically.




Le ven. 20 oct. 2023 à 21:29, Romain Manni-Bucau  a
écrit :

> Guess we would get a lot of false positive and surefire already has it so
> not sure it would help to simplify, complexity seems 1-1 :s
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>
>
> Le ven. 20 oct. 2023 à 21:05, Guillaume Nodet  a écrit
> :
>
> > Not sure agents are widely used during the build either.
> > I wonder if surefire should be given a list of artifacts coordinates that
> > it would consider as agents if they are in the test class path...  The
> > default value would contain bytebuddy, but it could be changed (and
> ordered
> > considered in that list) if needed.
> > That would be very specific to surefire, but I'm not sure there are many
> > use cases...
> >
> > Guillaume
> >
> > Le ven. 20 oct. 2023, 20:44, Romain Manni-Bucau 
> a
> > écrit :
> >
> > > Can be the way to define the lookup, an heuristic will never work by
> > > design...that said, on my side, not sure JPMS will be widely adopted
> > > anytime soon so can be a false problem.
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > <https://rmannibucau.metawerx.net/> | Old Blog
> > > <http://rmannibucau.wordpress.com> | Github <
> > > https://github.com/rmannibucau> |
> > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> > > <
> > >
> >
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> > > >
> > >
> > >
> > > Le ven. 20 oct. 2023 à 20:24, Henning Schmiedehausen <
> > > henn...@schmiedehausen.org> a écrit :
> > >
> > > > I think we will need to start rethinking dependencies more. A similar
> > > > problem exists with modules; the current heuristics to decide
> whether a
> > > > dependency goes on module path or classpath will start to become
> > painful
> > > in
> > > > the very near future.
> > > >
> > > > -h
> > > >
> > > >
> > > > On Tue, Oct 17, 2023 at 10:05 PM Benjamin Marwell <
> bmarw...@apache.org
> > >
> > > > wrote:
> > > >
> > > > > If you can still use it twice, works for me, too.
> > > > >
> > > > > Either way, you'd need it both as a dependency and as an agent.
> > > > >
> > > > > Another requirement Romain mentioned is the order of agent loading.
> > > > Mockito
> > > > > wants to be first, and others can come later.
> > > > >
> > > > > - Ben
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Wed, 18 Oct 2023, 00:11 Tamás Cservenák, 
> > > wrote:
> > > > >
> > > > > > What about type=java-agent? Basically a new ArtifactHandler?
> > > > > >
> > > > > > See https://maven.apache.org/repositories/artifacts.html
> > > > > >
> > > > > > T
> > > > > >
> > > > > > On Tue, Oct 17, 2023, 23:54 Benjamin Marwell <
> bmarw...@apache.org>
> > > > > wrote:
> > > > > >
> > > > > > > Hey all,
> > > > > > >
> > > > > > > In a mockito issue, JDK maintainers suggested to differentiate
> > > > between
> > > > > > > agents and normal dependencies. Starting with JDK 21 already,
> > this
> > > > > makes
> > > > > > a
> > > > > > > lot of sense: dynamic loading of agents will be a no-go.
> > > > > > >
> > > > > > > One suggestion was:
> > > > > > >
> > > > > > > 
> > > > &g

Re: Maven 5 pom extension for agents

[Guillaume Nodet]

Not sure agents are widely used during the build either.
I wonder if surefire should be given a list of artifacts coordinates that
it would consider as agents if they are in the test class path...  The
default value would contain bytebuddy, but it could be changed (and ordered
considered in that list) if needed.
That would be very specific to surefire, but I'm not sure there are many
use cases...

Guillaume

Le ven. 20 oct. 2023, 20:44, Romain Manni-Bucau  a
écrit :

> Can be the way to define the lookup, an heuristic will never work by
> design...that said, on my side, not sure JPMS will be widely adopted
> anytime soon so can be a false problem.
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github <
> https://github.com/rmannibucau> |
> LinkedIn  | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>
>
> Le ven. 20 oct. 2023 à 20:24, Henning Schmiedehausen <
> henn...@schmiedehausen.org> a écrit :
>
> > I think we will need to start rethinking dependencies more. A similar
> > problem exists with modules; the current heuristics to decide whether a
> > dependency goes on module path or classpath will start to become painful
> in
> > the very near future.
> >
> > -h
> >
> >
> > On Tue, Oct 17, 2023 at 10:05 PM Benjamin Marwell 
> > wrote:
> >
> > > If you can still use it twice, works for me, too.
> > >
> > > Either way, you'd need it both as a dependency and as an agent.
> > >
> > > Another requirement Romain mentioned is the order of agent loading.
> > Mockito
> > > wants to be first, and others can come later.
> > >
> > > - Ben
> > >
> > >
> > >
> > >
> > > On Wed, 18 Oct 2023, 00:11 Tamás Cservenák, 
> wrote:
> > >
> > > > What about type=java-agent? Basically a new ArtifactHandler?
> > > >
> > > > See https://maven.apache.org/repositories/artifacts.html
> > > >
> > > > T
> > > >
> > > > On Tue, Oct 17, 2023, 23:54 Benjamin Marwell 
> > > wrote:
> > > >
> > > > > Hey all,
> > > > >
> > > > > In a mockito issue, JDK maintainers suggested to differentiate
> > between
> > > > > agents and normal dependencies. Starting with JDK 21 already, this
> > > makes
> > > > a
> > > > > lot of sense: dynamic loading of agents will be a no-go.
> > > > >
> > > > > One suggestion was:
> > > > >
> > > > > 
> > > > > 
> > > > > ...
> > > > > 
> > > > > 
> > > > > 
> > > > > ...
> > > > > 
> > > > > 
> > > > > 
> > > > >
> > > > > Not sure if this is the best way, but this is something similar
> might
> > > be
> > > > > needed.
> > > > > Currently, the only way to handle agents is to add them manually to
> > the
> > > > > surefire argLine. To make things worse, a deoendency goal is needed
> > > until
> > > > > Romains PR is merged:
> > > > > https://github.com/apache/maven/pull/1281
> > > > >
> > > > > Another issue is that a parent pom might not be able to easily
> define
> > > > this
> > > > > option. There were some concerns that part of the configuration
> > needed
> > > to
> > > > > be repeated in every module.
> > > > >
> > > > > So, I wrote Maven 5.
> > > > > Maven 4 is the stepping stone to the build/consumer pom. But this
> is
> > an
> > > > > extension. Not really a breaking change in terms of parsing, but in
> > > terms
> > > > > of building a project. Thus, it should go onto the roadmap.
> > > > >
> > > > > ... unless you want to keep the current status quo, which is also
> an
> > > > > option. But before making an argument here, I'd recommend reading
> the
> > > > > lengthy (sorry!) discussion on the mockito issue tracker. Since
> Karl
> > > > Heinz
> > > > > started the issue, I'd love to hear back from you, too. Link:
> > > > > https://github.com/mockito/mockito/issues/3037
> > > > >
> > > > > If no discussion is needed at this point, let's keep this as a
> > reminder
> > > > for
> > > > > the next Apero and/or Maven 5 then.
> > > > >
> > > > > - Ben
> > > > >
> > > >
> > >
> >
>

Re: Do we have a list for changes between 3.9 and 4.0?

[Guillaume Nodet]

Fwiw, I've done a bit of cleanup on this list to remove fixVersion in
version such as 4.0.x-candidate, backlog, issues to be reviewed.  If the
issue has been fixed, it should be in a release...
The full list of changes between 3.9.x and master looks like the following:

https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20status%20%3D%20Closed%20AND%20fixVersion%20%3D%204.0.0%20AND%20NOT%20fixVersion%20in%20(3.8.0%2C%203.8.1%2C%203.8.2%2C%203.8.3%2C%203.8.4%2C%203.8.5%2C%203.8.6%2C%203.8.7%2C%203.8.8%2C%203.8.9%2C%203.9.0%2C%203.9.1%2C%203.9.2%2C%203.9.3%2C%203.9.4%2C%203.9.5)

There are also a couple of issues that have been marked as resolved in
4.0.0 but in no release and should be flagged with a correct release imho:

https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20status%20%3D%20Closed%20AND%20fixVersion%20in%20(4.0.0)%20AND%20NOT%20fixVersion%20in%20(4.0.0-alpha-1%2C%204.0.0-alpha-2%2C%204.0.0-alpha-3%2C%204.0.0-alpha-4%2C%204.0.0-alpha-5%2C%204.0.0-alpha-7%2C%204.0.0-alpha-8)

Guillaume

Le ven. 20 oct. 2023 à 09:27, Tamás Cservenák  a
écrit :

> Howdy,
>
> something ike this?
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20status%20%3D%20Closed%20AND%20fixVersion%20in%20(4.0.0%2C%204.0.0-alpha-8%2C%204.0.x-candidate%2C%20%224.x%20%2F%20Backlog%22%2C%20%22Issues%20to%20be%20reviewed%20for%204.x%22%2C%204.0.0-alpha-2%2C%204.0.0-alpha-3%2C%204.0.0-alpha-4%2C%204.0.0-alpha-5%2C%204.0.0-alpha-7)
>
> HTH
> T
>
> On Fri, Oct 20, 2023 at 9:22 AM tison  wrote:
>
> > I saw somewhat
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12346477
> > now.
> >
> > Best,
> > tison.
> >
> >
> > tison  于2023年10月16日周一 13:52写道：
> >
> > > Hi,
> > >
> > > I'm going to try out the 4.0 branch, and I would like to have a list of
> > > important changes. Currently, each alpha version has its release note,
> > but
> > > that's like a log instead of a somewhat migration guide.
> > >
> > > Do we have an up-to-date list of changes between 3.9 and 4.0?
> > >
> > > Best,
> > > tison.
> > >
> >
>


-- 

Guillaume Nodet

Re: Maven 5 pom extension for agents

[Guillaume Nodet]

Le mar. 17 oct. 2023 à 23:55, Benjamin Marwell  a
écrit :

> Hey all,
>
> In a mockito issue, JDK maintainers suggested to differentiate between
> agents and normal dependencies. Starting with JDK 21 already, this makes a
> lot of sense: dynamic loading of agents will be a no-go.
>
> One suggestion was:
>
> 
> 
> ...
> 
> 
> 
> ...
> 
> 
> 
>
> Not sure if this is the best way, but this is something similar might be
> needed.
> Currently, the only way to handle agents is to add them manually to the
> surefire argLine. To make things worse, a deoendency goal is needed until
> Romains PR is merged:
> https://github.com/apache/maven/pull/1281
>
> Another issue is that a parent pom might not be able to easily define this
> option. There were some concerns that part of the configuration needed to
> be repeated in every module.
>
> So, I wrote Maven 5.
> Maven 4 is the stepping stone to the build/consumer pom. But this is an
> extension. Not really a breaking change in terms of parsing, but in terms
> of building a project. Thus, it should go onto the roadmap.
>

We could definitely do that in Maven 4.  With alpha-8, the model is now
more open to changes.
See how it's done in https://github.com/apache/maven/pull/1209/files

That said, I agree with @cstamas that it may be better represented using an
ArtifactHandler.

However, the use of agents looks like a very specific use case.  You have
very few cases where agents can be used, as the requirement is to create a
JVM.
So that would be for the whole Maven JVM and that would be handled by core
extensions, or by plugins that fork JVM.  Are there many plugins apart from
Surefire, Maven Invoker or Exec plugin ?
I suspect the configuration needs to be different for each of these tool...
 so I'm not completely sure adding an  section, or even an artifact
handler is actually the best solution.

Guillaume


>
> ... unless you want to keep the current status quo, which is also an
> option. But before making an argument here, I'd recommend reading the
> lengthy (sorry!) discussion on the mockito issue tracker. Since Karl Heinz
> started the issue, I'd love to hear back from you, too. Link:
> https://github.com/mockito/mockito/issues/3037
>
> If no discussion is needed at this point, let's keep this as a reminder for
> the next Apero and/or Maven 5 then.
>
> - Ben
>


-- 

Guillaume Nodet

Re: [VOTE] Release Maven Surefire version 3.2.0

[Guillaume Nodet]

-1
The tag does not build as the source code has some formatting problems, see

https://github.com/apache/maven-surefire/actions/runs/6525665559/job/17718595124

Le dim. 15 oct. 2023 à 20:39, Michael Osipov  a écrit :

> Hi,
>
> we solved 9 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12353389
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20resolution%20%3D%20Unresolved
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2008/
>
> https://repository.apache.org/content/repositories/maven-2008/org/apache/maven/surefire/surefire/3.2.0/surefire-3.2.0-source-release.zip
>
> Source release checksum(s):
> surefire-3.2.0-source-release.zip
> sha512:
>
> c3dea52a8ead5b8d33e6bcd8f3470be86294a1b41e562d24700b6f34c6704297e5e9694c7761f29535a00e5123eebbb1e30bc971f248f8f3616b60ad5e8c5e49
>
> Staging site:
> https://maven.apache.org/surefire-archives/surefire-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 

Guillaume Nodet

Re: [VOTE] Release Apache Maven Reporting API version 4.0.0-M8

[Guillaume Nodet]

+1

Le ven. 13 oct. 2023 à 21:43, Michael Osipov  a écrit :

> Hi,
>
> IMPORTANT: This require the following staging repositories:
>
> * Doxia 2.0.0-M12
>
> we solved 2 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12353698
>
> There are no issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-reporting-api
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2001/
>
> https://repository.apache.org/content/repositories/maven-2001/org/apache/maven/reporting/maven-reporting-api/4.0.0-M8/maven-reporting-api-4.0.0-M8-source-release.zip
>
> Source release checksum(s):
> maven-reporting-api-4.0.0-M8-source-release.zip
> sha512:
>
> 5a6dfd5dc5182cdf6567b4e0c9dfecc687369360f35a6041566233d6fb05c1eb8e2113b9a434c48acfbb316b4650fcac44e99531ea1a6b62b86fafc363c6ec5f
>
> Staging site:
> https://maven.apache.org/shared-archives/maven-reporting-api-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 

Guillaume Nodet

Re: [VOTE] Release Apache Maven Reporting Impl version 4.0.0-M11

[Guillaume Nodet]

+1


Le ven. 13 oct. 2023 à 22:40, Michael Osipov  a écrit :

> Hi,
>
> IMPORTANT: This require the following staging repositories:
>
> * Doxia 2.0.0-M8
> * Maven Reporting API 4.0.0-M8
> * Doxia Sitetools 2.0.0-M13
>
> we solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12353073
>
> There is one issue left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-reporting-impl
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2003/
>
> https://repository.apache.org/content/repositories/maven-2003/org/apache/maven/reporting/maven-reporting-impl/4.0.0-M11/maven-reporting-impl-4.0.0-M11-source-release.zip
>
> Source release checksum(s):
> maven-reporting-impl-4.0.0-M11-source-release.zip
> sha512:
>
> 82616775ae4d99aaca9d17aae8efa86c4b435206dfda8367e4e1a56bc44d12806e18566ad568673b092948772e3fcdc1b697defcb2cef51e1d7551e73eeb
>
> Staging site:
> https://maven.apache.org/shared-archives/maven-reporting-impl-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 

Guillaume Nodet

Re: [VOTE] Release Maven Site Plugin version 4.0.0-M11

[Guillaume Nodet]

+1

Le sam. 14 oct. 2023 à 00:18, Michael Osipov  a écrit :

> Hi,
>
> IMPORTANT: This require the following staging repositories:
>
> * Doxia 2.0.0-M8
> * Maven Reporting API 4.0.0-M8
> * Doxia Sitetools 2.0.0-M13
> * Maven Reporting Impl 4.0.0-M11
> * Maven Reporting Exec 4.0.0-M11
>
> we solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12353714
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution%20%3D%20Unresolved
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2005/
>
> https://repository.apache.org/content/repositories/maven-2005/org/apache/maven/plugins/maven-site-plugin/4.0.0-M11/maven-site-plugin-4.0.0-M11-source-release.zip
>
> Source release checksum(s):
> maven-site-plugin-4.0.0-M11-source-release.zip
> sha512:
>
> fc628fca1fd2c3629a89da9c44b64994e1b5478a7b8f5d465328cdde8064e3f1212768a4053e563160cf08cece96cf8af5a8cd936d9c1b5eafb90bcc922d933f
>
> Staging site:
> https://maven.apache.org/plugins-archives/maven-site-plugin-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 

Guillaume Nodet

Re: [VOTE] Release Apache Maven Doxia Sitetools version 2.0.0-M13

[Guillaume Nodet]

+1

Le ven. 13 oct. 2023 à 22:10, Michael Osipov  a écrit :

> Hi,
>
> we solved 3 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320=12353711
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317320%20AND%20status%20%3D%20Open
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2002
>
> https://repository.apache.org/content/repositories/maven-2002/org/apache/maven/doxia/doxia-sitetools/2.0.0-M13/doxia-sitetools-2.0.0-M13-source-release.zip
>
> Source release checksum(s):
> doxia-sitetools-2.0.0-M13-source-release.zip
> sha512:
>
> 0aa7aa72dd71136acd2ce207ebc01ff893b6f1dbff2a025cf998b4e06103e30924c5bd5030546c349ad7040538fb04b5b06fd877da346dda19ca68d23e08272c
>
> Staging site:
>
> https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 

Guillaume Nodet

Re: [VOTE] Release Apache Maven Reporting Exec version 2.0.0-M11

[Guillaume Nodet]

+1

Le ven. 13 oct. 2023 à 22:58, Michael Osipov  a écrit :

> Hi,
>
> IMPORTANT: This require the following staging repositories:
>
> * Doxia 2.0.0-M8
> * Maven Reporting API 4.0.0-M8
> * Doxia Sitetools 2.0.0-M13
> * Maven Reporting Impl 4.0.0-M11
>
> we solved 3 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12353712
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-reporting-exec
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2004/
>
> https://repository.apache.org/content/repositories/maven-2004/org/apache/maven/reporting/maven-reporting-exec/2.0.0-M11/maven-reporting-exec-2.0.0-M11-source-release.zip
>
> Source release checksum(s):
> maven-reporting-exec-2.0.0-M11-source-release.zip
> sha512:
>
> 824ae603848338a3b2addfd4bcdee0dbcfded1b133daf91f8b7189e7cc06b9e3ad59a916f61ee6fb02945d16075fc39edd647551b1489e5c5b22b286fea79746
>
> Staging site:
> https://maven.apache.org/shared-archives/maven-reporting-exec-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 

Guillaume Nodet

Re: [VOTE] Release Maven Doxia version 2.0.0-M8

[Guillaume Nodet]

+1

Le ven. 13 oct. 2023 à 21:32, Michael Osipov  a écrit :

> Hi,
>
> we solved 2 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317230=12353657
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20DOXIA%20AND%20resolution%20%3D%20Unresolved
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2000/
>
> https://repository.apache.org/content/repositories/maven-2000/org/apache/maven/doxia/doxia/2.0.0-M8/doxia-2.0.0-M8-source-release.zip
>
> Source release checksum(s):
> doxia-2.0.0-M8-source-release.zip
> sha512:
>
> 242d7ba2198a66957f8265812c4bafc52a2fa463bf7a5790cf55df5c8d3f0b022affe57dbaa25060790d1a53ff01c63480c4ee6b38212bd90e97a4f1f54639dd
>
> Staging site:
> https://maven.apache.org/doxia/doxia-archives/doxia-LATEST/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 

Guillaume Nodet

Re: [DISCUSS] Maven Resolver 2.x HTTP/2 transport modules

[Guillaume Nodet]

Le jeu. 12 oct. 2023 à 21:15, Tamás Cservenák  a
écrit :

> Howdy,
>
> As part of the new Resolver major version, one of the goals is to introduce
> HTTP/2 capable transports. And as always, naming...
>
> Current transport module names (==artifactId) are (already quite long for
> my taste):
> * maven-resolver-transport-classpath (CP transport, is not HTTP, just FTR)
> * maven-resolver-transport-file (file transport, is not HTTP, just FTR)
> * maven-resolver-transport-http (uses Apache HttpClient 4.x, HTTP/1.1
> capable)
> * maven-resolver-transport-wagon (uses Wagon, so is not only HTTP, HTTP/1.1
> capable)
>

Is wagon something we still want to push forward ?


>
> And now the two new contenders:
> * Java11+ java.net.http.HttpClient based (HTTP/2 capable)
> * Java11+ Jetty12 based (HTTP/2 capable)
>
> So, the major question is how to name these modules (== artifactId)?
>
> * maven-resolver-transport-java11?

* maven-resolver-transport-jetty12?
>
> Maybe some form of proto+imple?
>
> * maven-resolver-transport-http2-java11 (or shorter
> maven-resolver-transport-h2-java11)
>

Http is enough imho. Which version is supported by which implementation is
an internal detail.  Unless there are HTTP/2 server which does not support
HTTP/1.1 in which case it could become relevant.  Or any client supporting
HTTP/2 and not HTTP/1.1...



> * maven-resolver-transport-http2-jetty (or shorter
> maven-resolver-transport-h2-jetty)
>

I like the longest better because they are more descriptive of what they
actually are.
So protocol + client sounds fine.


>
> But there are not ONLY HTTP/2 (they are also HTTP/1.1 capable as well).
> Also, the Jetty version matters, so once in future there will be Jetty13
> etc...
>

Do we really care ? We need different providers if they provide different
things.  I don't think jetty 12 provides anything different than jetty 13.
In addition, we won't be able to ship both jetty 12 and jetty 13 at the
same time, so I think we can keep a single one, which means we can drop the
version.
Which version we ship is a separate discussion and it impacts the runtime
JDK requirements I suppose.

Same for java11, maybe jdk would be better to indicate this is the http
client from the jdk (if you're using jdk 17, that one will be used, not the
one from jdk 11).  I do understand it has been introduced in JDK 11, but
still...

So in short, i'd go for:
  maven-resolver-transport-http-jetty
  maven-resolver-transport-http-jdk
  maven-resolver-transport-http-httpclient
  maven-resolver-transport-file
  maven-resolver-transport-classpath

Cheers
Guillaume



>
> Ideas welcome.
>
> Thanks
> T
>
> PS: Given java.net.http.HttpClient based transport will be dependency-less,
> it reminds me of good old wagon-http-lightweight, but unlike wagon one
> (that was quite limited), this will be fully capable transport.
>


-- 

Guillaume Nodet

Re: [VOTE] Release Maven Resolver 1.9.16

[Guillaume Nodet]

+1

Le ven. 22 sept. 2023 à 20:29, Tamás Cservenák  a
écrit :

> Howdy,
>
> Note: Maven Resolver 1.x lineage after this release is going into "bugfix
> only" maintenance mode (and will be branched off as maven-resolver-1.9.x),
> while master branch will become 2.x.
>
> We solved 6 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353482
>
> There are still some issues in JIRA:
> https://issues.apache.org/jira/projects/MRESOLVER/issues
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-1991
>
> Source release SHA512:
>
> b9a03c88bcb21c6bc0af3faf0b8fdf0001e9c2250957f715333e195730350ad5e4519069786f88990f22ac87b7b513d8c84ca5ffbb160ecca2fd0986b89da3da
>
> Staging site:
> https://maven.apache.org/resolver-archives/resolver-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>


-- 

Guillaume Nodet

Re: maven shade plugin for jdk 20/21

[Guillaume Nodet]

Have you tried the current master for this plugin ?
Can I just go ahead and release it in the current state or is there
anything to fix first ?

Le mar. 19 sept. 2023 à 10:55, Delany  a écrit :

> Hi all,
>
> JDK21 reaches general availability today. Could someone provide another
> release of the shade plugin to support it?
>
> Kind regards,
> Delany
>


-- 
----
Guillaume Nodet

Re: plexus-utils 4.x and Xpp3DomBuilder

[Guillaume Nodet]

I've raised MNG-7873.
Slawomir, do you think you could create an IT for that ?
I'll try to provide a fix asap, but a clean IT would make sure the problem
is actually fixed.

I think we should also update the plexus-utils release notes with some more
information about the migration to 4.x when using the xml bits.

[1] https://issues.apache.org/jira/browse/MNG-7873

Le lun. 4 sept. 2023 à 22:50, Guillaume Nodet  a écrit :

> I think the decision to not export plexus-utils was taken some time ago.
>
> Unfortunately, the xml bits still have to be provided by the maven core
> class loader.
> I think in this case, Maven 3.9.x should also expose the builder class
>
> org.codehaus.plexus.util.xml.Xpp3DomBuilder
> I think this should work, but this would only solve the problem for the
> latest 3.9.x maven, not older versions.
>
>
> Le mar. 25 juil. 2023 à 20:56, Slawomir Jaranowski 
> a écrit :
>
>> Hi
>>
>> I'm trying to update plexus-utils 3.5.x to plexus-utils/plexus-xml 4.x in
>> maven-enforcer 
>>
>> In maven-enforcer (and in many other plugins ...) is used, code like:
>>
>> Xpp3Dom enforcerRules = Xpp3DomBuilder.build(descriptorStream,
>> "UTF-8");
>>
>> Xpp3Dom and Xpp3DomBuilder - has new implementation in plexus-xml  but
>> Maven 3.x exports
>>
>> 
>>
>> org.codehaus.plexus.util.xml.Xpp3Dom
>>
>>
>> org.codehaus.plexus.util.xml.pull.XmlPullParser
>>
>>
>> org.codehaus.plexus.util.xml.pull.XmlPullParserException
>>
>>
>> org.codehaus.plexus.util.xml.pull.XmlSerializer
>>
>> It is very magical that we export classes but not export artifact
>> which contains those classes ...
>>
>> so incompatibilite code for Xpp3Dom is used ...
>>
>> Any hints on how to process it.
>>
>> --
>> Sławomir Jaranowski
>>
>
>
> --
> 
> Guillaume Nodet
>
>

-- 

Guillaume Nodet

Re: Coming soon: Maven 3.9.5

[Guillaume Nodet]

I think we need to expose the missing class before cutting a release, see
https://lists.apache.org/thread/ltd1g1dbv0lqqdw5q941gmrkfyn6m87m

I've raised MNG-7873 for that.

Le jeu. 7 sept. 2023, 16:18, Tamás Cservenák  a écrit :

> Howdy,
>
> Just a heads up, that am targeting following releases:
>
> Maven Resolver 1.9.16:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.16
>
> Maven 3.9.5:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.5
>
> So if anyone has anything more to add, bring it up!
>
> TIA
> T
>

Re: plexus-utils 4.x and Xpp3DomBuilder

[Guillaume Nodet]

I think the decision to not export plexus-utils was taken some time ago.

Unfortunately, the xml bits still have to be provided by the maven core
class loader.
I think in this case, Maven 3.9.x should also expose the builder class

org.codehaus.plexus.util.xml.Xpp3DomBuilder
I think this should work, but this would only solve the problem for the
latest 3.9.x maven, not older versions.


Le mar. 25 juil. 2023 à 20:56, Slawomir Jaranowski 
a écrit :

> Hi
>
> I'm trying to update plexus-utils 3.5.x to plexus-utils/plexus-xml 4.x in
> maven-enforcer 
>
> In maven-enforcer (and in many other plugins ...) is used, code like:
>
> Xpp3Dom enforcerRules = Xpp3DomBuilder.build(descriptorStream,
> "UTF-8");
>
> Xpp3Dom and Xpp3DomBuilder - has new implementation in plexus-xml  but
> Maven 3.x exports
>
> 
> org.codehaus.plexus.util.xml.Xpp3Dom
>
>
> org.codehaus.plexus.util.xml.pull.XmlPullParser
>
>
> org.codehaus.plexus.util.xml.pull.XmlPullParserException
>
>
> org.codehaus.plexus.util.xml.pull.XmlSerializer
>
> It is very magical that we export classes but not export artifact
> which contains those classes ...
>
> so incompatibilite code for Xpp3Dom is used ...
>
> Any hints on how to process it.
>
> --
> Sławomir Jaranowski
>


-- 

Guillaume Nodet