[VOTE] Release Maven Fluido Skin version 2.0.0-M9

[Michael Osipov]

Hi,

we solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317926&version=12353690

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSKINS%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20%22Fluido%20Skin%22

Staging repo:
https://repository.apache.org/content/repositories/maven-2122/
https://repository.apache.org/content/repositories/maven-2122/org/apache/maven/skins/maven-fluido-skin/2.0.0-M9/maven-fluido-skin-2.0.0-M9-source-release.zip

Source release checksum(s):
maven-fluido-skin-2.0.0-M9-source-release.zip
sha512: 
73c6ddaf32433d2f24b36f838979ad60ea2c0984521e8c71c28639a20c67131884afc14b5a319e07cfc3de80d818c03c0cc73b40f29de715c4966f633cf983e6


Staging site:
https://maven.apache.org/components/skins-archives/maven-fluido-skin-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

[RESULT] [VOTE] Release Maven Doxia version 2.0.0-M12

[Michael Osipov]

Hi,

The vote has passed with the following result:

+1: Sylwester Lachiewicz, Michael Osipov, Slawomir Jaranowski, Tamás 
Cservenák


PMC quorum: reached

I will promote the artifacts to the central repo, the source release ZIP 
file and add this release the board report.

[RESULT] [VOTE] Release Apache Maven Reporting API version 4.0.0-M12

[Michael Osipov]

Hi,

The vote has passed with the following result:

+1: Sylwester Lachiewicz, Michael Osipov, Slawomir Jaranowski, Tamás 
Cservenák, Jermaine Hua


PMC quorum: reached

I will promote the artifacts to the central repo, the source release ZIP 
file and add this release the board report.


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

[ANN] Apache Maven Doxia version 2.0.0-M12 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Apache 
Maven Doxia, version 2.0.0-M12


https://maven.apache.org/doxia/


Release Notes - Maven Doxia - Version 2.0.0-M12

** Bug
* [DOXIA-737] - [REGRESSION] Making EmitAnchorsForIndexableEntries 
by default does not extract document titles anymore



Enjoy,

-The Apache Maven team

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

[ANN] Apache Maven Reporting API 4.0.0-M12 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Reporting API version 4.0.0-M12.


https://maven.apache.org/shared/maven-reporting-api/


Release Notes - Maven Shared Components - Version 
maven-reporting-api-4.0.0-M12


** Dependency upgrade
* [MSHARED-1392] - Upgrade to Parent 42 and Maven 3.6.3
* [MSHARED-1396] - Upgrade to Doxia 2.0.0-M11
* [MSHARED-1399] - Upgrade to Doxia 2.0.0-M12


Enjoy,

-The Apache Maven team

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

Re: Trying to test the reworked compiler plugin

[Tamás Cservenák]

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

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
>
>

Re: Trying to test the reworked compiler plugin

[Martin Desruisseaux]

Hello Tamas

Thanks for the explanation. Then I will pause the Maven compiler plugin 
work for now and resume after the new master branches are ready (I need 
to focus on 2 meetings in June anyway). Just for avoiding confusion, 
would it be possible to delete the current "mvn4" branches?


Side note: if the "master" branch is going to be very different than the 
current branch, would it be an opportunity to rename "master" as "main"? 
It could be done by creating a new Maven 4 branch named "main", make it 
the default when ready, then rename current "master" as "maven-3.x".


    Martin

Le 2024-05-20 à 11 h 36, 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.



-
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-beta-2

[Maarten Mulders]

Thanks for pushing the first beta, Guillaume!

+1 from me.


- Maarten

On 13/05/2024 19:40, Guillaume Nodet wrote:

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&version=
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



-
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-beta-2

[Tamás Cservenák]

+1

But as we know today, this was really too early to call it "beta". We
discovered issues that may introduce API changes...

On Mon, May 13, 2024 at 7:41 PM Guillaume Nodet  wrote:

> 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&version=
> 12354392
> <
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=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
>

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

[Mateusz Gajewski]

Can we get beta-3 soon? :)

On Mon, May 20, 2024 at 12:38 PM Tamás Cservenák 
wrote:

> +1
>
> But as we know today, this was really too early to call it "beta". We
> discovered issues that may introduce API changes...
>
> On Mon, May 13, 2024 at 7:41 PM Guillaume Nodet  wrote:
>
> > 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&version=
> > 12354392
> > <
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=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
> >
>

[DISCUSS] Many shared stuff should be dropped

[Tamás Cservenák]

Howdy,

I see ongoing development against many "shared" libraries, that in fact,
should be dropped instead. One notable example is "maven-dependency-tree".

This codebase was born (well, factored out) from Maven2 reporting, to be
extended with "Maven 3.0 support", then "Maven 3.1 support" and is just
collecting debt.

This library, if you look at it now, is anemic and is merely a "wrapper"
around Resolver classes, uses ancient stuff (read Maven2 classes) and
patterns, like misuse of ProjectBuildingRequest (same pattern as in ill
fated MAT), uses deprecated ArtifactRepository class for all kind of stuff
(hello split repository -- not possible to be used with these). In short,
this project does not offer any (new, not available) functionality, while
in turn, hinders and pushes for deprecated stuff. These should cease to
exist.

In fact, many shared projects should be scrutinized and most probably
declared "deprecated", as most of them were born to support Maven2 to
Maven3 transition (or maybe Maven 3.0 to 3.1+ transition like MAT was),
while today they just hinder Maven3 to Maven4 change, as many of these
shared stuff in fact still pull Maven2 classes in play.


Thanks
T

Re: [VOTE] Release Maven Fluido Skin version 2.0.0-M9

[Michael Osipov]

Am 2024-05-20 um 10:54 schrieb Michael Osipov:

Hi,

we solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317926&version=12353690

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSKINS%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20%22Fluido%20Skin%22

Staging repo:
https://repository.apache.org/content/repositories/maven-2122/
https://repository.apache.org/content/repositories/maven-2122/org/apache/maven/skins/maven-fluido-skin/2.0.0-M9/maven-fluido-skin-2.0.0-M9-source-release.zip

Source release checksum(s):
maven-fluido-skin-2.0.0-M9-source-release.zip
sha512: 
73c6ddaf32433d2f24b36f838979ad60ea2c0984521e8c71c28639a20c67131884afc14b5a319e07cfc3de80d818c03c0cc73b40f29de715c4966f633cf983e6


Staging site:
https://maven.apache.org/components/skins-archives/maven-fluido-skin-LATEST/

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

Vote open for 72 hours.


+1


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

[RESULT][VOTE] Release Maven Indexer 7.1.3

[Tamás Cservenák]

Howdy,

The vote has passed with the following result:

+1b: Michael, Slawomir, Olivier, Tamas

PMC quorum: reached

I will promote the artifacts to the central repo, the source release ZIP
file and add this release to the board report.

Thanks
T

Re: [DISCUSS] Many shared stuff should be dropped

[Hervé Boutemy]

hi Tamasz,

I think you're right on maven-dependency-tree, as it was with maven-artifact-
transfer

I'm not really convinced *many* shared stuff should be dropped: IMHO, over-
generalization

And I think that when replacing a shared stuff with direct use of an existing 
API, in fact what normal people are looking for is documentation on how to 
migrate: the shared components have one great advantage = they show a quite 
simple API that is easy to use, but it's not so easy to find the replacement 
hidden inside many big APIs

I'm supportive to deprecating maven-dependency-tree and also finally drop 
officially maven-artifact-transfer which has not been done yet.
What I'd like is that some clear documentation is written on how to migrate 
away from these deprecated components

If you see any other shared component that deserve such plan, don't hesitate 
to share: I don't see so many cases

Regards,

Hervé

Le lundi 20 mai 2024, 14:25:11 CEST Tamás Cservenák a écrit :
> Howdy,
> 
> I see ongoing development against many "shared" libraries, that in fact,
> should be dropped instead. One notable example is "maven-dependency-tree".
> 
> This codebase was born (well, factored out) from Maven2 reporting, to be
> extended with "Maven 3.0 support", then "Maven 3.1 support" and is just
> collecting debt.
> 
> This library, if you look at it now, is anemic and is merely a "wrapper"
> around Resolver classes, uses ancient stuff (read Maven2 classes) and
> patterns, like misuse of ProjectBuildingRequest (same pattern as in ill
> fated MAT), uses deprecated ArtifactRepository class for all kind of stuff
> (hello split repository -- not possible to be used with these). In short,
> this project does not offer any (new, not available) functionality, while
> in turn, hinders and pushes for deprecated stuff. These should cease to
> exist.
> 
> In fact, many shared projects should be scrutinized and most probably
> declared "deprecated", as most of them were born to support Maven2 to
> Maven3 transition (or maybe Maven 3.0 to 3.1+ transition like MAT was),
> while today they just hinder Maven3 to Maven4 change, as many of these
> shared stuff in fact still pull Maven2 classes in play.
> 
> 
> Thanks
> T





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

[ANN] Apache Maven Indexer 7.1.3 released

[Tamás Cservenák]

The Apache Maven team is pleased to announce the release of the
Maven Indexer 7.1.3

https://maven.apache.org/maven-indexer/

Release Notes - Maven Indexer - Version 7.1.3

** Improvement
* [MINDEXER-222] - RR backend in case of GAVCE search should use
Last-Modified HTTP header
** Dependency upgrade
* [MINDEXER-216] - Bump commons-cli:commons-cli from 1.6.0 to 1.7.0
* [MINDEXER-217] - Bump org.apache.maven:maven-parent from 41 to 42
* [MINDEXER-218] - Bump org.jmock:jmock from 2.12.0 to 2.13.1
* [MINDEXER-219] - Bump com.google.guava:guava from 32.1.3-jre to
33.1.0-jre
* [MINDEXER-220] - Bump lucene.version from 9.9.1 to 9.10.0
* [MINDEXER-221] - (build) Bump org.gaul:modernizer-maven-plugin from
2.7.0 to 2.8.0
* [MINDEXER-223] - Upgrade slf4j to version 2.0.13

Have fun,
-The Apache Maven team

Re: [DISCUSS] Many shared stuff should be dropped

[Sylwester Lachiewicz]

Hi,
yes, it would be a good idea to review our project and at last update
README that we plan to deprecate some components - to avoid unnecessary
work on this.

A quick search for "org.apache.maven.shared.dependency.graph" for
org:apache shows that we should implement changes also in our plugins and
create docs on how to migrate. Maybe an OpenRewrite recipe?

Sylwester


pon., 20 maj 2024 o 19:41 Hervé Boutemy  napisał(a):

> hi Tamasz,
>
> I think you're right on maven-dependency-tree, as it was with
> maven-artifact-
> transfer
>
> I'm not really convinced *many* shared stuff should be dropped: IMHO, over-
> generalization
>
> And I think that when replacing a shared stuff with direct use of an
> existing
> API, in fact what normal people are looking for is documentation on how to
> migrate: the shared components have one great advantage = they show a
> quite
> simple API that is easy to use, but it's not so easy to find the
> replacement
> hidden inside many big APIs
>
> I'm supportive to deprecating maven-dependency-tree and also finally drop
> officially maven-artifact-transfer which has not been done yet.
> What I'd like is that some clear documentation is written on how to
> migrate
> away from these deprecated components
>
> If you see any other shared component that deserve such plan, don't
> hesitate
> to share: I don't see so many cases
>
> Regards,
>
> Hervé
>
> Le lundi 20 mai 2024, 14:25:11 CEST Tamás Cservenák a écrit :
> > Howdy,
> >
> > I see ongoing development against many "shared" libraries, that in fact,
> > should be dropped instead. One notable example is
> "maven-dependency-tree".
> >
> > This codebase was born (well, factored out) from Maven2 reporting, to be
> > extended with "Maven 3.0 support", then "Maven 3.1 support" and is just
> > collecting debt.
> >
> > This library, if you look at it now, is anemic and is merely a "wrapper"
> > around Resolver classes, uses ancient stuff (read Maven2 classes) and
> > patterns, like misuse of ProjectBuildingRequest (same pattern as in ill
> > fated MAT), uses deprecated ArtifactRepository class for all kind of
> stuff
> > (hello split repository -- not possible to be used with these). In short,
> > this project does not offer any (new, not available) functionality, while
> > in turn, hinders and pushes for deprecated stuff. These should cease to
> > exist.
> >
> > In fact, many shared projects should be scrutinized and most probably
> > declared "deprecated", as most of them were born to support Maven2 to
> > Maven3 transition (or maybe Maven 3.0 to 3.1+ transition like MAT was),
> > while today they just hinder Maven3 to Maven4 change, as many of these
> > shared stuff in fact still pull Maven2 classes in play.
> >
> >
> > Thanks
> > T
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>