[ANN] Apache Maven 4.0.0-alpha-4 released

[Guillaume Nodet]

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

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-4 is available via
https://dlcdn.apache.org/maven/maven-4/4.0.0-alpha-4/

This in alpha release, not suitable for production. If you hit any issues
with plugins, please raise a JIRA issue, after verifying that the same
issue has not been reported yet (see JIRA issues raised on 4.0.0-alpha

).

Main changes:
* upgrade maven resolver 1.9.4
* improved resolution of modules within a multi-module build
* do not parse all projects in the reactor when building a subtree
* fix some compatibility issues (with flatten-maven-plugin)
* re-implement the consumer pom feature to support the maven-gpg-plugin

The full release notes for maven 4.0.0-alpha-4 are available at

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12352667

If you have any questions, please consult:
- the web site: https://maven.apache.org/
- the maven-user mailing list: https://maven.apache.org/mailing-lists.html
- the reference documentation: https://maven.apache.org/ref/4.0.0-alpha-3/

-- 

Guillaume Nodet

Re: extracting XML classes from plexus-utils to plexus-xml

[Herve Boutemy]

> The only "problem" is that it
> creates a cycle between maven-core and plexus-utils, but

to reduce the problem, that's why I proposed at plexus-utils level to split the 
xml part in another plexus-xml artifact, so at least the overlap is reduced and 
there is clarification about the fact that the problem is only on a few XML 
classes from Plexus that are provided by Maven core to the whole 
plugins/extensions ecosystem

Then how to solve this cycle on the Plexus-XML extract from Plexus Utils: need 
to test in a branch...

On 2023/01/31 14:43:07 Guillaume Nodet wrote:
> Le mar. 31 janv. 2023 à 15:27, Elliotte Rusty Harold  a
> écrit :
> 
> > Very roughly my suggestion is create new artifacts that do what you
> > want with completely new packages. Class names can stay the same but
> > package names must change when the artifact ID or group ID changes.
> >
> > If you want to keep the fully package qualified class names the same,
> > then don't change the artifact  IDs or class locations and live with
> > the current situation.
> >
> 
> That was actually my proposal.  I.e. keep things where they are, just
> add a dependency from plexus-utils to maven-xml-impl / maven-api-xml.
> 
> 
> >
> > Also important in Java 9+ is that all classes from a single package
> > belong to a single jar./Maven artifact. E.g. do not put one class from
> > org.apache.maven.api.xml in one artifact and other classes from that
> > package in a different artifact.
> >
> > If you're already doing all that, great. However
> > https://github.com/apache/maven/pull/975 looks to me like it's
> > renaming an artifact without  renaming any packages. That's a red
> > flag. It might be OK if org.apache.maven:plexus-utils has never been
> > published. Looks like it's only been published in alpha, so maybe OK?
> >
> 
> The other red flag is that org.apache.maven:plexus-utils is a repackaged
> version (with the modifications I was mentioning earlier) of
> org.codehaus.plexus:plexus-utils.  Which I think is a red flag too.
> 
> But yes, those artifacts have only been published as alpha.
> 
> So I think my earlier proposal is fine, i.e. remove the plexus classes from
> the maven code tree, update them where they belong (i.e. in the plexus
> code tree) by adding a dependency to the maven-xml-impl.
> This keeps org.apache.maven.* classes in maven, org.codehaus.plexus.*
> classes in plexus and everything is fine.  The only "problem" is that it
> creates a cycle between maven-core and plexus-utils, but
> 
> @hboutemy wdyt ?
> 
> 
> >
> > On Tue, Jan 31, 2023 at 7:47 AM Guillaume Nodet  wrote:
> > >
> > > Maybe I'm wrong, but I think you missed the point.
> > >
> > > We have new packages / new artifacts, mainly the xml api located in
> > > the maven-api-xml artifact [1] with a single interface XmlNode [2].
> > > The implementation is in the maven-xml-impl [3] artifact.
> > > As I said, I'd like to keep it where it is.
> > >
> > > Now, in order to get some compatibility with all the 3.x world in maven 4
> > > and achieve the goals (one of them was to have an immutable api), the
> > > old classes which were part of the maven 3 api were slightly modified
> > > to wrap the new ones.  So we have the Xpp3Node from plexus-utils which
> > > now wrap the XmlNodeImpl (implementing the new XmlNode interface
> > > which is immutable).  So far so good.
> > >
> > > However, to achieve this, I had to put those modified classes (Xpp3Node
> > > and the related Xpp3DomBuilder) inside the maven-plexus-utils artifact
> > [4]
> > > (which is currently named plexus-utils, but lives inside maven.  So now,
> > > maven has a repackaged version of plexus-utils with a few modifications
> > > that need to be maintained somewhere.  We're actually
> > > breaking https://jlbp.dev/JLBP-5, and we're trying to find a way out.
> > >
> > > Any better advice than keeping the current state ?
> > >
> > > Guillaume
> > >
> > > [1] https://github.com/apache/maven/tree/master/api/maven-api-xml
> > > [2]
> > >
> > https://github.com/apache/maven/blob/master/api/maven-api-xml/src/main/java/org/apache/maven/api/xml/XmlNode.java
> > > [3] https://github.com/apache/maven/tree/master/maven-xml-impl
> > > [4] https://github.com/apache/maven/tree/master/plexus-utils
> > >
> > > Le mar. 31 janv. 2023 à 13:28, Elliotte Rusty Harold 
> > a
> > > écrit :
> > >
> > > > Thanks for the PR. That makes this clearer. I'm now -1 (-10?) on this
> > > > entire proposal. Renaming artifact IDs without renaming packages is a
> > > > recipe for hard to debug, hard to fix problems.
> > > >
> > > > See https://jlbp.dev/JLBP-6 for detailed explanation and suggestions
> > > >
> > > > To proceed what's needed is a hard fork of everything with new package
> > > > names and artifact IDs.
> > > >
> > > > On Mon, Jan 30, 2023 at 7:31 PM Hervé Boutemy 
> > > > wrote:
> > > > >
> > > > > Le lundi 30 janvier 2023, 14:06:28 CET Guillaume Nodet a écrit :
> > > > > > Given this is
> > > > > >
> > > > > > Le lun. 30 janv. 

Re: [VOTE] Release Apache Maven Daemon 1.0.0-m4

[Herve Boutemy]

+1

Regards,

Hervé

On 2023/01/28 14:16:17 Guillaume Nodet wrote:
> I've staged a release candidate at
>   https://dist.apache.org/repos/dist/dev/maven/mvnd/1.0.0-m4/
> 
> Note that his release is based on Maven 4.0.0-alpha-4 under vote.
> The release notes are available at
>   https://github.com/apache/maven-mvnd/releases/tag/1.0.0-m4
> 
> Please review and vote !
> 
> Cheers
> 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-4 release

[Hervé Boutemy]

Le lundi 30 janvier 2023, 08:32:59 CET Guillaume Nodet a écrit :
> I'm not sure we're talking about the same thing.
I'm not sure either, I need to review even more carefully :)

> 
> The plugin's goals child has been deprecated and unused since 15 years
> afaik:
> 
> https://github.com/apache/maven/commit/d2e1f3c97556afa42972a9ef20d336fccaed4
> ad5

oh, I now see that it's declared as DOM in the model and commented as 
deprecated for a long time
https://maven.apache.org/ref/3.8.7/maven-model/maven.html#class_plugin
https://maven.apache.org/ref/3.0.1/maven-model/maven.html#class_plugin

And re-reading the misc documentations on our website, I see that we always 
show goals in execution, never outside: sorry, it's my memory that seems to 
have read too much the generated XML at the beginning of
 https://maven.apache.org/ref/3.8.7/maven-model/maven.html
without seeing that this goals field is deprecated and never used :)

Thanks for the explanation and cleanup

> 
> https://github.com/apache/maven/commit/cbcc49b306ce2c6c2fb32212c089c11978524
> c92
> 
> The deprecated elements have been removed during the introduction of the v4
> api:
> 
> https://github.com/apache/maven/commit/2a9f39336cec1d8e52d30cc48503d51ed8672
> 536#diff-ccc5b1903a864adb4a01d6072c9c2ff937c71fb06bea6e5ec3df6097f0d01199
> 
> It should be quite easy to add some compatibility, if that's needed.
> 
> Guillaume
> 
> Le lun. 30 janv. 2023 à 08:02, Hervé Boutemy  a
> 
> écrit :
> > sorry, I don't get why declaring a build plugin with a goal is rejected
> > with
> > Maven 4: AFAIK, it's something that has been used since Maven 2 and I
> > don't
> > see any problem with it .
> > 
> > 
> > What's the reasoning, please?
> > (ideally what's the Jira issue leading to that effect?)
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le dimanche 29 janvier 2023, 20:24:54 CET Guillaume Nodet a écrit :
> > > Yes, I already reported and provided a fix on netty.
> > > 
> > >https://github.com/netty/netty/pull/12911
> > > 
> > > So recent netty versions don't have this problem anymore.
> > > 
> > > Le dim. 29 janv. 2023 à 19:59, Romain Manni-Bucau
> > > 
> > 
> > a
> > 
> > > écrit :
> > > > Hi Delany,
> > > > 
> > > > yes but since it is deprecated and *unused by maven*, I think it is
> > 
> > really
> > 
> > > > an error in netty pom and unintended so think it is an ok behavior (
> > 
> > https://github.com/apache/maven/commit/f153ac134c26ed89cdb7de1b294ecb61320
> > 
> > 8c22b#diff-91081af7c7d8c77b1b3cff89dd3b257e2967696c2f6d48aa65e827e1e2915a7
> > 
> > > > aR133 ).
> > > > 
> > > > Romain Manni-Bucau
> > > > @rmannibucau  |  Blog
> > > >  | Old Blog
> > > >  | Github <
> > > > https://github.com/rmannibucau> |
> > > > LinkedIn  | Book
> > > > <
> > 
> > https://www.packtpub.com/application-development/java-ee-8-high-performanc
> > 
> > > > e
> > > > 
> > > > 
> > > > 
> > > > Le dim. 29 janv. 2023 à 19:49, Delany  a
> > > > 
> > > > écrit :
> > > > > Hi Romain. As far as I know executions are not required.
> > > > > The relationship: plugin > goals is valid against
> > > > > https://maven.apache.org/maven-v4_0_0.xsd
> > > > > Delany
> > > > > 
> > > > > On Sun, 29 Jan 2023 at 16:40, Romain Manni-Bucau <
> > 
> > rmannibu...@gmail.com>
> > 
> > > > > wrote:
> > > > > > +1
> > > > > > 
> > > > > > @Delany netty bom looks incorrect (misses execution(s).
> > > > > > 
> > > > > > Le dim. 29 janv. 2023 à 13:53, Karl Heinz Marbaise <
> > 
> > khmarba...@gmx.de>
> > 
> > > > a
> > > > 
> > > > > > écrit :
> > > > > > > Hi,
> > > > > > > 
> > > > > > > +1 from me.
> > > > > > > 
> > > > > > > Kind regards
> > > > > > > Karl Heinz Marbaise
> > > > > > > 
> > > > > > > On 27.01.23 18:11, Guillaume Nodet wrote:
> > > > > > > > I've staged a release candidate at [1].  The distributions are
> > > > > > 
> > > > > > available
> > > > > > 
> > > > > > > at
> > > > > > > 
> > > > > > > > [2].
> > > > > > > > The release notes are available at [3] for JIRA and [4] for
> > > > > > > > github.
> > > > > > > > 
> > > > > > > > Please review and vote !
> > > > > > > > 
> > > > > > > > Cheers,
> > > > > > > > Guillaume
> > > > > > > > 
> > > > > > > > [1]
> > 
> > https://repository.apache.org/content/repositories/maven-1859
> > 
> > > > > > > > [2]
> > 
> > https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-4/
> > 
> > > > > > > > [3]
> > 
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352667
> > 
> > > > yleName=Text=12316922>
> > > > 
> > > > > > > > [4]
> > 
> > https://github.com/apache/maven/releases/tag/untagged-4ba8d14c9e8eb6de3887
> > 
> > 
> > 
> > 
> > > > > > > -
> > > > > > > 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-M4

[Herve Boutemy]

+1

Reproducible Builds ok: reference build done with JDK 8 on Windows

Regards,

Hervé

On 2023/01/31 20:54:14 Michael Osipov wrote:
> Hi,
> 
> IMPORTANT: Requires Doxia Sitetools 2.0.0-M5 vote/staging repo!
> 
> we solved 5 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12352864
> 
> 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-1864/
> https://repository.apache.org/content/repositories/maven-1864/org/apache/maven/reporting/maven-reporting-exec/2.0.0-M4/maven-reporting-exec-2.0.0-M4-source-release.zip
> 
> Source release checksum(s):
> maven-reporting-exec-2.0.0-M4-source-release.zip
> sha512: 
> fa023a3975be5dfb295ae191da7b3ba215a7f73291a7f204468292cb38f248bb365eca0387058eebe69e5174e372ec00919aca585ca4d8e8c81e1e2ef84291ed
> 
> 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
> 
> 

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

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

[Herve Boutemy]

+1

Reproducible Builds ok: reference build done with JDK 11 on Windows

Regards,

Hervé

On 2023/01/31 18:00:23 Michael Osipov wrote:
> Hi,
> 
> we solved 10 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320=12352573
> 
> 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-1863
> https://repository.apache.org/content/repositories/maven-1863/org/apache/maven/doxia/doxia-sitetools/2.0.0-M5/doxia-sitetools-2.0.0-M5-source-release.zip
> 
> Source release checksum(s):
> doxia-sitetools-2.0.0-M5-source-release.zip
> sha512: 
> e8d5bed5bba4b3e6ef6cb7a5d790de3e7ffea34c84ccac21f344b7b47668e52bee5575c1f5bcd5a5d90383efd3ede01d1434f3c07012381743f7dbcc8fd6d653
> 
> 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
> 
> 

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

[ANN] Apache Maven Enforcer Plugin 3.2.1 Released

[Slawomir Jaranowski]

The Apache Maven team is pleased to announce the release of the Apache
Maven Enforcer Plugin, version 3.2.1

This plugin provides goals to control certain environmental constraints
such as Maven version, JDK version and OS family
along with many more built-in rules and user created rules.

https://maven.apache.org/enforcer/maven-enforcer-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-enforcer-plugin
  3.2.1


You can download the appropriate sources etc. from the download page:

https://maven.apache.org/enforcer/download.html

Release Notes - Maven Enforcer Plugin - Version 3.2.1

** Bug
* [MENFORCER-378] - requireReleaseDeps does not support optional
dependencies or runtime scope
* [MENFORCER-407] - Enforcer 3.0.0 breaks with Maven 3.8.4
* [MENFORCER-434] - Version 3.1.0 is not enforcing bannedDependencies
rules
* [MENFORCER-437] - DependencyConvergence treats provided dependencies
are runtime dependencies
* [MENFORCER-459] - Plugin shouldn't use NullPointerException for
non-exceptional code flow
* [MENFORCER-461] - NPE in RequirePluginVersions
* [MENFORCER-462] - ReactorModuleConvergence not cached in reactor

** New Feature
* [MENFORCER-397] - allow no rules
* [MENFORCER-398] - show rules processed
* [MENFORCER-411] - DependencyConvergence should support
including/excluding certain dependencies
* [MENFORCER-422] - Support declaring external banned dependencies in
an external file/URL
* [MENFORCER-423] - Maven enforcer rule which checks that all
dependencies have an explicit scope set
* [MENFORCER-424] - Maven enforcer rule which checks that all
dependencies in dependencyManagement don't have an explicit scope set
* [MENFORCER-427] - Rule for no version ranges, version placeholders or
SNAPSHOT versions
* [MENFORCER-430] - Allow one of many files in RequireFiles rules to
pass
* [MENFORCER-431] - Skip specific rules
* [MENFORCER-455] - New Enforcer API
* [MENFORCER-456] - New Enforcer API - RuleConfigProvider
* [MENFORCER-458] - Move Built-In Rules to new API

** Improvement
* [MENFORCER-415] - Violation messages can be really hard to find in a
multi module project
* [MENFORCER-425] - Clarify class loading for custom Enforcer rules
* [MENFORCER-428] - Using junit jupiter bom instead of single artifacts.
* [MENFORCER-435] - Get rid of maven-dependency-tree dependency
* [MENFORCER-440] - Allow 8 as JDK version for requireJavaVersion
* [MENFORCER-444] - Improve error message for rule "requireJavaVersion"
* [MENFORCER-445] - Include Java Home in Message for Java Rule Failures
* [MENFORCER-452] - Manage all Maven Core dependencies as provided
* [MENFORCER-453] - Mange rules configuration by plugin
* [MENFORCER-454] - Deprecate 'rules' property and introduce
'enforcer.rules' as a replacement
* [MENFORCER-463] - Change success message from executed to passed

** Task
* [MENFORCER-447] - Verify working with Maven 4
* [MENFORCER-450] - Code cleanup
* [MENFORCER-451] - Refresh download page
* [MENFORCER-460] - Deprecate display-info mojo
* [MENFORCER-464] - Refresh site descriptors

** Dependency upgrade
* [MENFORCER-429] - Upgrade maven-plugin parent to 37
* [MENFORCER-438] - Upgrade maven-plugin parent to 38
* [MENFORCER-441] - Bump maven-common-artifact-filters from 3.2.0 to
3.3.2
* [MENFORCER-442] - Bump Mockito from 4.6.1 to 4.11.0
* [MENFORCER-443] - Bump junit-bom from 5.9.0 to 5.9.1
* [MENFORCER-446] - Bump plexus-utils from 3.4.2 to 3.5.0
* [MENFORCER-448] - Upgrade parent to version 39
* [MENFORCER-449] - Bump mrm-maven-plugin from 1.3.0 to 1.5.0
* [MENFORCER-457] - Bump assertj-core from 3.23.1 to 3.24.2

Enjoy,

-The Apache Maven team

[RESULT] [VOTE] Release Apache Maven Enforcer version 3.2.1

[Slawomir Jaranowski]

Hi,

The vote has passed with the following result:

+1: Michael Osipov, Delany, Sylwester Lachiewicz, Herve Boutemy, Guillaume
Nodet

PMC quorum: reached

I will promote the source release zip file to Apache distribution area and
the artifacts to the central repo.

-- 
Sławomir Jaranowski

Re: [VOTE] Release Apache Maven 3.9.0

[Petr Široký]

+1 (non-binding)

Tested on several projects (both small and big) and found no functional issue.

The only thing I noticed is that 3.9.0 is a bit "slower" than 3.8.7. The 
following numbers are from a very big project - Quarkus, which has ~1k modules 
(https://github.com/quarkusio/quarkus), running on Linux x64 and JDK 19.0.1:

Maven cmd  Maven 3.8.7 Maven 3.9.0
==
clean  3.5s3.5s
validate   02:27min03:08min
validate -T8   28s 35s
install -DskipTests07:40min08:39min
install -DskipTests -T802:21min02:41min

Note: I did ran 'mvn clean' before every execution to remove any artifacts from 
previous builds. The numbers are an average over 3 runs.

On small(er) projects, with far less modules, the difference is of course much 
less noticeable, or even non-existing.

I haven't (yet) looked deeper into the reasons behind this. I don't think this 
would be a blocker for the release, but it would be nice to figure out what is 
the cause.

Thanks,
Petr


--- Original Message ---
On Tuesday, January 31st, 2023 at 11:37, Tamás Cservenák  
wrote:


> 
> 
> Howdy,
> 
> We solved 95 issues:
> https://issues.apache.org/jira/issues/?jql=project %3D MNG AND fixVersion %3D 
> 3.9.0
> 
> There are still some open issues left in JIRA:
> https://issues.apache.org/jira/issues/?filter=-5=project %3D MNG AND 
> resolution %3D Unresolved order by priority DESC%2Cupdated DESC
> 
> Staging repository:
> https://repository.apache.org/content/repositories/maven-1862/
> 
> Staged site:
> https://maven.apache.org/ref/3-LATEST/
> 
> SHA512 release checksum(s):
> 1ea149f4e48bc7b34d554aef86f948eca7df4e7874e30caf449f3708e4f8487c71a5e5c072a05f17c60406176ebeeaf56b5f895090c7346f8238e2da06cf6ecd
> apache-maven-3.9.0-bin.tar.gz
> 
> 564fe44bfa9c7ad3e2703cbbac59d43a11fa39e4e68875d3d1584d0a0b7b77a1352da246b875c4c15d11ceb6b4dd9a0ce7dd7a48695725dce594f34325c9c605
> apache-maven-3.9.0-bin.zip
> 
> c9c89d49aa577223b1358f7391859535be031201eab502e0620522ceb66f2b42f6f8361764d6d627b66f6ae8c61cfe85cb51f7fb734aadd0427f10e43d5a1753
> apache-maven-3.9.0-src.tar.gz
> 
> 68b1a3cde17a42814ea28499e0c3f5cb98c343cebdfb96b52ba5acc6c2c6bac4f99dcf93177840bbc4d2b32668f73315f678ba0fef211b422303a751690a139c
> apache-maven-3.9.0-src.zip
> 
> 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
> 
> Thanks
> T

-
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.0-m4

[Slawomir Jaranowski]

+1

sob., 28 sty 2023 o 15:16 Guillaume Nodet  napisał(a):

> I've staged a release candidate at
>   https://dist.apache.org/repos/dist/dev/maven/mvnd/1.0.0-m4/
>
> Note that his release is based on Maven 4.0.0-alpha-4 under vote.
> The release notes are available at
>   https://github.com/apache/maven-mvnd/releases/tag/1.0.0-m4
>
> Please review and vote !
>
> Cheers
> Guillaume Nodet
>


-- 
Sławomir Jaranowski

[VOTE] Release Apache Maven Reporting Exec version 2.0.0-M4

[Michael Osipov]

Hi,

IMPORTANT: Requires Doxia Sitetools 2.0.0-M5 vote/staging repo!

we solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12352864

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-1864/
https://repository.apache.org/content/repositories/maven-1864/org/apache/maven/reporting/maven-reporting-exec/2.0.0-M4/maven-reporting-exec-2.0.0-M4-source-release.zip

Source release checksum(s):
maven-reporting-exec-2.0.0-M4-source-release.zip
sha512: 
fa023a3975be5dfb295ae191da7b3ba215a7f73291a7f204468292cb38f248bb365eca0387058eebe69e5174e372ec00919aca585ca4d8e8c81e1e2ef84291ed


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

Re: [VOTE] Release Apache Maven 3.9.0

[Romain Manni-Bucau]

Le mar. 31 janv. 2023 à 19:11, Michael Osipov  a
écrit :

> Am 2023-01-31 um 16:31 schrieb Tamás Cservenák:
> > Howdy,
> >
> > I always mark the JIRA version as "released" when mail the vote, as
> > "un-release" is really just a mouse click. Having this set prevents
> > inadvertent additions to the version while voting for it is ongoing,
> > nothing more.
> >
> > If you talk about 3.9.0-candidate to 3.9.1-candidate rename, that's fine,
> > those issues are NOT in 3.9.0, nor they were. If you think it is ok, just
> > close those up, but there is one issue in progress (update deps).
>
> Moved them to 3.9.0 since they are addressed implicitly.
>
> > The SVN dance is done, thanks for pointing that out.
>
> LGTM.
>
> > Finally, I have 72h for site PR, no? :)
>
> Well, it should be reviewed with the vote, no?
>

site is not "immutable" so not as critical as sources.


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

Re: [VOTE] Release Apache Maven 3.9.0

[Michael Osipov]

Am 2023-01-31 um 16:31 schrieb Tamás Cservenák:

Howdy,

I always mark the JIRA version as "released" when mail the vote, as
"un-release" is really just a mouse click. Having this set prevents
inadvertent additions to the version while voting for it is ongoing,
nothing more.

If you talk about 3.9.0-candidate to 3.9.1-candidate rename, that's fine,
those issues are NOT in 3.9.0, nor they were. If you think it is ok, just
close those up, but there is one issue in progress (update deps).


Moved them to 3.9.0 since they are addressed implicitly.


The SVN dance is done, thanks for pointing that out.


LGTM.


Finally, I have 72h for site PR, no? :)


Well, it should be reviewed with the vote, no?


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

[VOTE] Release Apache Maven Doxia Sitetools version 2.0.0-M5

[Michael Osipov]

Hi,

we solved 10 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320=12352573

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-1863
https://repository.apache.org/content/repositories/maven-1863/org/apache/maven/doxia/doxia-sitetools/2.0.0-M5/doxia-sitetools-2.0.0-M5-source-release.zip

Source release checksum(s):
doxia-sitetools-2.0.0-M5-source-release.zip
sha512: 
e8d5bed5bba4b3e6ef6cb7a5d790de3e7ffea34c84ccac21f344b7b47668e52bee5575c1f5bcd5a5d90383efd3ede01d1434f3c07012381743f7dbcc8fd6d653


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

Re: [VOTE] Release Apache Maven 3.9.0

[Slawomir Jaranowski]

+1

I use from a weeks for regular work

wt., 31 sty 2023 o 11:37 Tamás Cservenák  napisał(a):

> Howdy,
>
> We solved 95 issues:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.0
>
> There are still some open issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?filter=-5=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20order%20by%20priority%20DESC%2Cupdated%20DESC
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-1862/
>
> Staged site:
> https://maven.apache.org/ref/3-LATEST/
>
> SHA512 release checksum(s):
>
> 1ea149f4e48bc7b34d554aef86f948eca7df4e7874e30caf449f3708e4f8487c71a5e5c072a05f17c60406176ebeeaf56b5f895090c7346f8238e2da06cf6ecd
>  apache-maven-3.9.0-bin.tar.gz
>
>
> 564fe44bfa9c7ad3e2703cbbac59d43a11fa39e4e68875d3d1584d0a0b7b77a1352da246b875c4c15d11ceb6b4dd9a0ce7dd7a48695725dce594f34325c9c605
>  apache-maven-3.9.0-bin.zip
>
>
> c9c89d49aa577223b1358f7391859535be031201eab502e0620522ceb66f2b42f6f8361764d6d627b66f6ae8c61cfe85cb51f7fb734aadd0427f10e43d5a1753
>  apache-maven-3.9.0-src.tar.gz
>
>
> 68b1a3cde17a42814ea28499e0c3f5cb98c343cebdfb96b52ba5acc6c2c6bac4f99dcf93177840bbc4d2b32668f73315f678ba0fef211b422303a751690a139c
>  apache-maven-3.9.0-src.zip
>
> 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
>
> Thanks
> T
>


-- 
Sławomir Jaranowski

Re: [VOTE] Release Apache Maven 3.9.0

[Delany]

+1
Delany


On Tue, 31 Jan 2023 at 12:37, Tamás Cservenák  wrote:

> Howdy,
>
> We solved 95 issues:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.0
>
> There are still some open issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?filter=-5=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20order%20by%20priority%20DESC%2Cupdated%20DESC
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-1862/
>
> Staged site:
> https://maven.apache.org/ref/3-LATEST/
>
> SHA512 release checksum(s):
>
> 1ea149f4e48bc7b34d554aef86f948eca7df4e7874e30caf449f3708e4f8487c71a5e5c072a05f17c60406176ebeeaf56b5f895090c7346f8238e2da06cf6ecd
>  apache-maven-3.9.0-bin.tar.gz
>
>
> 564fe44bfa9c7ad3e2703cbbac59d43a11fa39e4e68875d3d1584d0a0b7b77a1352da246b875c4c15d11ceb6b4dd9a0ce7dd7a48695725dce594f34325c9c605
>  apache-maven-3.9.0-bin.zip
>
>
> c9c89d49aa577223b1358f7391859535be031201eab502e0620522ceb66f2b42f6f8361764d6d627b66f6ae8c61cfe85cb51f7fb734aadd0427f10e43d5a1753
>  apache-maven-3.9.0-src.tar.gz
>
>
> 68b1a3cde17a42814ea28499e0c3f5cb98c343cebdfb96b52ba5acc6c2c6bac4f99dcf93177840bbc4d2b32668f73315f678ba0fef211b422303a751690a139c
>  apache-maven-3.9.0-src.zip
>
> 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
>
> Thanks
> T
>

Re: [VOTE] Release Apache Maven Daemon 1.0.0-m4

[Guillaume Nodet]

+1

Le sam. 28 janv. 2023 à 15:16, Guillaume Nodet  a écrit :

> I've staged a release candidate at
>   https://dist.apache.org/repos/dist/dev/maven/mvnd/1.0.0-m4/
>
> Note that his release is based on Maven 4.0.0-alpha-4 under vote.
> The release notes are available at
>   https://github.com/apache/maven-mvnd/releases/tag/1.0.0-m4
>
> Please review and vote !
>
> Cheers
> Guillaume Nodet
>
>

-- 

Guillaume Nodet

[RESULT] [VOTE] Release Apache Maven Daemon 0.9.0

[Guillaume Nodet]

Closing this vote with the following votes:
  +1: rmannibucau, cstamas, mthmulders, hboutemy, ppalaga, gnodet,
Petr Široký

I'll publish this release asap.
Thx

Guillaume

Le mer. 25 janv. 2023 à 10:10, Guillaume Nodet  a écrit :

> I've staged a candidate release at
>   https://dist.apache.org/repos/dist/dev/maven/mvnd/0.9.0/
>
> Note that this release is based on Maven 3.8.7.
> The release notes are available at
>
> https://github.com/apache/maven-mvnd/releases/tag/untagged-7cae83258923acd48d99
>
> Please review and vote !
>
> Note that I'm planning a 0.10.0 release based on Maven 3.9.0 once it's out
> and a 1.0.0-m2 once 4.0.0-alpha-4 is out.
>
> --
> 
> Guillaume Nodet
>
>

-- 

Guillaume Nodet

Re: [VOTE] Release Apache Maven Daemon 0.9.0

[Guillaume Nodet]

+1

Le mer. 25 janv. 2023 à 10:10, Guillaume Nodet  a écrit :

> I've staged a candidate release at
>   https://dist.apache.org/repos/dist/dev/maven/mvnd/0.9.0/
>
> Note that this release is based on Maven 3.8.7.
> The release notes are available at
>
> https://github.com/apache/maven-mvnd/releases/tag/untagged-7cae83258923acd48d99
>
> Please review and vote !
>
> Note that I'm planning a 0.10.0 release based on Maven 3.9.0 once it's out
> and a 1.0.0-m2 once 4.0.0-alpha-4 is out.
>
> --
> 
> Guillaume Nodet
>
>

-- 

Guillaume Nodet

[RESULT] [VOTE] Release Apache Maven 4.0.0-alpha-4 release

[Guillaume Nodet]

Closing this vote with the following votes:
  +1: rmannibucau, hboutemy, khmarbaise, michaelo, sjaranowski, gnodet,
Delany Middleton

I'll publish this release asap.
Thx !

Guillaume

Le ven. 27 janv. 2023 à 18:11, Guillaume Nodet  a écrit :

> I've staged a release candidate at [1].  The distributions are available
> at [2].
> The release notes are available at [3] for JIRA and [4] for github.
>
> Please review and vote !
>
> Cheers,
> Guillaume
>
> [1] https://repository.apache.org/content/repositories/maven-1859
> [2] https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-4/
> [3]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352667=Text=12316922
> [4]
> https://github.com/apache/maven/releases/tag/untagged-4ba8d14c9e8eb6de3887
>
>

-- 

Guillaume Nodet

Re: [VOTE] Release Apache Maven 4.0.0-alpha-4 release

[Guillaume Nodet]

+1

Le ven. 27 janv. 2023 à 18:11, Guillaume Nodet  a écrit :

> I've staged a release candidate at [1].  The distributions are available
> at [2].
> The release notes are available at [3] for JIRA and [4] for github.
>
> Please review and vote !
>
> Cheers,
> Guillaume
>
> [1] https://repository.apache.org/content/repositories/maven-1859
> [2] https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-4/
> [3]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352667=Text=12316922
> [4]
> https://github.com/apache/maven/releases/tag/untagged-4ba8d14c9e8eb6de3887
>
>

-- 

Guillaume Nodet

Re: [VOTE] Release Apache Maven 3.9.0

[Guillaume Nodet]

+1

Le mar. 31 janv. 2023 à 11:37, Tamás Cservenák  a
écrit :

> Howdy,
>
> We solved 95 issues:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.0
>
> There are still some open issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?filter=-5=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20order%20by%20priority%20DESC%2Cupdated%20DESC
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-1862/
>
> Staged site:
> https://maven.apache.org/ref/3-LATEST/
>
> SHA512 release checksum(s):
>
> 1ea149f4e48bc7b34d554aef86f948eca7df4e7874e30caf449f3708e4f8487c71a5e5c072a05f17c60406176ebeeaf56b5f895090c7346f8238e2da06cf6ecd
>  apache-maven-3.9.0-bin.tar.gz
>
>
> 564fe44bfa9c7ad3e2703cbbac59d43a11fa39e4e68875d3d1584d0a0b7b77a1352da246b875c4c15d11ceb6b4dd9a0ce7dd7a48695725dce594f34325c9c605
>  apache-maven-3.9.0-bin.zip
>
>
> c9c89d49aa577223b1358f7391859535be031201eab502e0620522ceb66f2b42f6f8361764d6d627b66f6ae8c61cfe85cb51f7fb734aadd0427f10e43d5a1753
>  apache-maven-3.9.0-src.tar.gz
>
>
> 68b1a3cde17a42814ea28499e0c3f5cb98c343cebdfb96b52ba5acc6c2c6bac4f99dcf93177840bbc4d2b32668f73315f678ba0fef211b422303a751690a139c
>  apache-maven-3.9.0-src.zip
>
> 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
>
> Thanks
> T
>


-- 

Guillaume Nodet

Re: [VOTE] Release Apache Maven 3.9.0

[Romain Manni-Bucau]

+1 looks as planned on tested java 17 projects

Le mar. 31 janv. 2023 à 16:32, Tamás Cservenák  a
écrit :

> Howdy,
>
> I always mark the JIRA version as "released" when mail the vote, as
> "un-release" is really just a mouse click. Having this set prevents
> inadvertent additions to the version while voting for it is ongoing,
> nothing more.
>
> If you talk about 3.9.0-candidate to 3.9.1-candidate rename, that's fine,
> those issues are NOT in 3.9.0, nor they were. If you think it is ok, just
> close those up, but there is one issue in progress (update deps).
>
> The SVN dance is done, thanks for pointing that out.
>
> Finally, I have 72h for site PR, no? :)
>
> Thanks
> T
>
> On Tue, Jan 31, 2023 at 4:09 PM Michael Osipov 
> wrote:
>
> > Am 2023-01-31 um 11:37 schrieb Tamás Cservenák:
> > > Howdy,
> > >
> > > We solved 95 issues:
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.0
> >
> > Should have been:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12350913
> > I don't understand why the version is marked as released in JIRA
> > although it hasn't even passed the vote.
> >
> > MNG-7425 and MNG-7545 don't require 3.9.1 since I mentioned in the
> > issued that they are very very likely fixed with Resolver 1.7+
> implicitly.
> >
> > > There are still some open issues left in JIRA:
> > >
> >
> https://issues.apache.org/jira/issues/?filter=-5=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20order%20by%20priority%20DESC%2Cupdated%20DESC
> > >
> > > Staging repository:
> > > https://repository.apache.org/content/repositories/maven-1862/
> > >
> > > Staged site:
> > > https://maven.apache.org/ref/3-LATEST/
> > >
> > > SHA512 release checksum(s):
> > >
> >
> 1ea149f4e48bc7b34d554aef86f948eca7df4e7874e30caf449f3708e4f8487c71a5e5c072a05f17c60406176ebeeaf56b5f895090c7346f8238e2da06cf6ecd
> > >   apache-maven-3.9.0-bin.tar.gz
> > >
> > >
> >
> 564fe44bfa9c7ad3e2703cbbac59d43a11fa39e4e68875d3d1584d0a0b7b77a1352da246b875c4c15d11ceb6b4dd9a0ce7dd7a48695725dce594f34325c9c605
> > >   apache-maven-3.9.0-bin.zip
> > >
> > >
> >
> c9c89d49aa577223b1358f7391859535be031201eab502e0620522ceb66f2b42f6f8361764d6d627b66f6ae8c61cfe85cb51f7fb734aadd0427f10e43d5a1753
> > >   apache-maven-3.9.0-src.tar.gz
> > >
> > >
> >
> 68b1a3cde17a42814ea28499e0c3f5cb98c343cebdfb96b52ba5acc6c2c6bac4f99dcf93177840bbc4d2b32668f73315f678ba0fef211b422303a751690a139c
> > >   apache-maven-3.9.0-src.zip
> >
> > The dev dist collection according to our Maven Core release procedure is
> > missing:
> > https://maven.apache.org/developers/release/maven-core-release.html
> >
> > Where is the PR against Maven Site for this release?
> >
> > M
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
>

Re: [VOTE] Release Apache Maven 3.9.0

[Tamás Cservenák]

Howdy,

I always mark the JIRA version as "released" when mail the vote, as
"un-release" is really just a mouse click. Having this set prevents
inadvertent additions to the version while voting for it is ongoing,
nothing more.

If you talk about 3.9.0-candidate to 3.9.1-candidate rename, that's fine,
those issues are NOT in 3.9.0, nor they were. If you think it is ok, just
close those up, but there is one issue in progress (update deps).

The SVN dance is done, thanks for pointing that out.

Finally, I have 72h for site PR, no? :)

Thanks
T

On Tue, Jan 31, 2023 at 4:09 PM Michael Osipov  wrote:

> Am 2023-01-31 um 11:37 schrieb Tamás Cservenák:
> > Howdy,
> >
> > We solved 95 issues:
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.0
>
> Should have been:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12350913
> I don't understand why the version is marked as released in JIRA
> although it hasn't even passed the vote.
>
> MNG-7425 and MNG-7545 don't require 3.9.1 since I mentioned in the
> issued that they are very very likely fixed with Resolver 1.7+ implicitly.
>
> > There are still some open issues left in JIRA:
> >
> https://issues.apache.org/jira/issues/?filter=-5=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20order%20by%20priority%20DESC%2Cupdated%20DESC
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/maven-1862/
> >
> > Staged site:
> > https://maven.apache.org/ref/3-LATEST/
> >
> > SHA512 release checksum(s):
> >
> 1ea149f4e48bc7b34d554aef86f948eca7df4e7874e30caf449f3708e4f8487c71a5e5c072a05f17c60406176ebeeaf56b5f895090c7346f8238e2da06cf6ecd
> >   apache-maven-3.9.0-bin.tar.gz
> >
> >
> 564fe44bfa9c7ad3e2703cbbac59d43a11fa39e4e68875d3d1584d0a0b7b77a1352da246b875c4c15d11ceb6b4dd9a0ce7dd7a48695725dce594f34325c9c605
> >   apache-maven-3.9.0-bin.zip
> >
> >
> c9c89d49aa577223b1358f7391859535be031201eab502e0620522ceb66f2b42f6f8361764d6d627b66f6ae8c61cfe85cb51f7fb734aadd0427f10e43d5a1753
> >   apache-maven-3.9.0-src.tar.gz
> >
> >
> 68b1a3cde17a42814ea28499e0c3f5cb98c343cebdfb96b52ba5acc6c2c6bac4f99dcf93177840bbc4d2b32668f73315f678ba0fef211b422303a751690a139c
> >   apache-maven-3.9.0-src.zip
>
> The dev dist collection according to our Maven Core release procedure is
> missing:
> https://maven.apache.org/developers/release/maven-core-release.html
>
> Where is the PR against Maven Site for this release?
>
> M
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>

Re: extracting XML classes from plexus-utils to plexus-xml

[Elliotte Rusty Harold]

On Tue, Jan 31, 2023 at 9:43 AM Guillaume Nodet  wrote:
>
> So I think my earlier proposal is fine, i.e. remove the plexus classes from
> the maven code tree, update them where they belong (i.e. in the plexus
> code tree) by adding a dependency to the maven-xml-impl.
> This keeps org.apache.maven.* classes in maven, org.codehaus.plexus.*
> classes in plexus and everything is fine.  The only "problem" is that it
> creates a cycle between maven-core and plexus-utils, but
>

That does sound fine to me. I think I'm simply getting confused about
who's proposing what. It sounds like gnodet@ and I are in agreement

To break the cycle, we'd need to go another step and replace
plexus-utils with new classes in the Maven tree. Whether anyone has
the spoons to do that, I don't know. "Plexus" as a project seems to be
a relic of big plans that never came to fruition. Had we a time
machine, I suppose we could tell the developers back in the aughts not
to bother splitting this out from Maven.

-- 
Elliotte Rusty Harold
elh...@ibiblio.org

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

Re: [VOTE] Release Apache Maven 3.9.0

[Michael Osipov]

Am 2023-01-31 um 11:37 schrieb Tamás Cservenák:

Howdy,

We solved 95 issues:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.0


Should have been: 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12350913
I don't understand why the version is marked as released in JIRA 
although it hasn't even passed the vote.


MNG-7425 and MNG-7545 don't require 3.9.1 since I mentioned in the 
issued that they are very very likely fixed with Resolver 1.7+ implicitly.



There are still some open issues left in JIRA:
https://issues.apache.org/jira/issues/?filter=-5=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20order%20by%20priority%20DESC%2Cupdated%20DESC

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

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

SHA512 release checksum(s):
1ea149f4e48bc7b34d554aef86f948eca7df4e7874e30caf449f3708e4f8487c71a5e5c072a05f17c60406176ebeeaf56b5f895090c7346f8238e2da06cf6ecd
  apache-maven-3.9.0-bin.tar.gz

564fe44bfa9c7ad3e2703cbbac59d43a11fa39e4e68875d3d1584d0a0b7b77a1352da246b875c4c15d11ceb6b4dd9a0ce7dd7a48695725dce594f34325c9c605
  apache-maven-3.9.0-bin.zip

c9c89d49aa577223b1358f7391859535be031201eab502e0620522ceb66f2b42f6f8361764d6d627b66f6ae8c61cfe85cb51f7fb734aadd0427f10e43d5a1753
  apache-maven-3.9.0-src.tar.gz

68b1a3cde17a42814ea28499e0c3f5cb98c343cebdfb96b52ba5acc6c2c6bac4f99dcf93177840bbc4d2b32668f73315f678ba0fef211b422303a751690a139c
  apache-maven-3.9.0-src.zip


The dev dist collection according to our Maven Core release procedure is 
missing: https://maven.apache.org/developers/release/maven-core-release.html


Where is the PR against Maven Site for this release?

M


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

Re: Maven 3.9,0 plan

[Michael Osipov]

Am 2023-01-31 um 13:43 schrieb Elliotte Rusty Harold:

On Mon, Jan 30, 2023 at 5:43 PM Tamás Cservenák  wrote:


Maven 3.8.x uses surefire 2.x, while 3.9.x uses surefire 3.0.0-M8... to me,
this seems like a surefire 3.0.0-M8 issue...



Is this a blocker for Maven 3.9.0 then? Should we finish surefire
3.0.0 first, then push 3.9.0? I'd prefer that Maven core not depend on
unstable dependencies.


I don't think so, milestone does not necessary imply that it is 
unstable, but simply work in progress. Moreover, we always encourage to 
explicitly set versions in the POM instead of relying on default 
versions. They will age sooner or later.


M


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

Re: Maven 3.9,0 plan

[Michael Osipov]

Am 2023-01-31 um 01:35 schrieb Dan Tran:

run into this issue

"Unable to parse maven.config file options: Unrecognized maven.config file
entries: [ -e --fail-fast -Djavax.xml.accessExternalSchema=all
-Daether.connector.resumeDownloads=false]"

The workaround is to break it into multiple lines


This is not a workaround. Your input is wrong in two ways:

1. Each arg has to be in one line: 
https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=331c5c3435cdfa8dc3f35a7b38503bdac2654206
2. Java system props must *not* be passed via maven.config, but via 
MAVEN_OPTS or jvm.config only, e.g.,  -Djavax.xml.accessExternalSchema=all


M


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

Re: extracting XML classes from plexus-utils to plexus-xml

[Guillaume Nodet]

Le mar. 31 janv. 2023 à 15:27, Elliotte Rusty Harold  a
écrit :

> Very roughly my suggestion is create new artifacts that do what you
> want with completely new packages. Class names can stay the same but
> package names must change when the artifact ID or group ID changes.
>
> If you want to keep the fully package qualified class names the same,
> then don't change the artifact  IDs or class locations and live with
> the current situation.
>

That was actually my proposal.  I.e. keep things where they are, just
add a dependency from plexus-utils to maven-xml-impl / maven-api-xml.


>
> Also important in Java 9+ is that all classes from a single package
> belong to a single jar./Maven artifact. E.g. do not put one class from
> org.apache.maven.api.xml in one artifact and other classes from that
> package in a different artifact.
>
> If you're already doing all that, great. However
> https://github.com/apache/maven/pull/975 looks to me like it's
> renaming an artifact without  renaming any packages. That's a red
> flag. It might be OK if org.apache.maven:plexus-utils has never been
> published. Looks like it's only been published in alpha, so maybe OK?
>

The other red flag is that org.apache.maven:plexus-utils is a repackaged
version (with the modifications I was mentioning earlier) of
org.codehaus.plexus:plexus-utils.  Which I think is a red flag too.

But yes, those artifacts have only been published as alpha.

So I think my earlier proposal is fine, i.e. remove the plexus classes from
the maven code tree, update them where they belong (i.e. in the plexus
code tree) by adding a dependency to the maven-xml-impl.
This keeps org.apache.maven.* classes in maven, org.codehaus.plexus.*
classes in plexus and everything is fine.  The only "problem" is that it
creates a cycle between maven-core and plexus-utils, but

@hboutemy wdyt ?


>
> On Tue, Jan 31, 2023 at 7:47 AM Guillaume Nodet  wrote:
> >
> > Maybe I'm wrong, but I think you missed the point.
> >
> > We have new packages / new artifacts, mainly the xml api located in
> > the maven-api-xml artifact [1] with a single interface XmlNode [2].
> > The implementation is in the maven-xml-impl [3] artifact.
> > As I said, I'd like to keep it where it is.
> >
> > Now, in order to get some compatibility with all the 3.x world in maven 4
> > and achieve the goals (one of them was to have an immutable api), the
> > old classes which were part of the maven 3 api were slightly modified
> > to wrap the new ones.  So we have the Xpp3Node from plexus-utils which
> > now wrap the XmlNodeImpl (implementing the new XmlNode interface
> > which is immutable).  So far so good.
> >
> > However, to achieve this, I had to put those modified classes (Xpp3Node
> > and the related Xpp3DomBuilder) inside the maven-plexus-utils artifact
> [4]
> > (which is currently named plexus-utils, but lives inside maven.  So now,
> > maven has a repackaged version of plexus-utils with a few modifications
> > that need to be maintained somewhere.  We're actually
> > breaking https://jlbp.dev/JLBP-5, and we're trying to find a way out.
> >
> > Any better advice than keeping the current state ?
> >
> > Guillaume
> >
> > [1] https://github.com/apache/maven/tree/master/api/maven-api-xml
> > [2]
> >
> https://github.com/apache/maven/blob/master/api/maven-api-xml/src/main/java/org/apache/maven/api/xml/XmlNode.java
> > [3] https://github.com/apache/maven/tree/master/maven-xml-impl
> > [4] https://github.com/apache/maven/tree/master/plexus-utils
> >
> > Le mar. 31 janv. 2023 à 13:28, Elliotte Rusty Harold 
> a
> > écrit :
> >
> > > Thanks for the PR. That makes this clearer. I'm now -1 (-10?) on this
> > > entire proposal. Renaming artifact IDs without renaming packages is a
> > > recipe for hard to debug, hard to fix problems.
> > >
> > > See https://jlbp.dev/JLBP-6 for detailed explanation and suggestions
> > >
> > > To proceed what's needed is a hard fork of everything with new package
> > > names and artifact IDs.
> > >
> > > On Mon, Jan 30, 2023 at 7:31 PM Hervé Boutemy 
> > > wrote:
> > > >
> > > > Le lundi 30 janvier 2023, 14:06:28 CET Guillaume Nodet a écrit :
> > > > > Given this is
> > > > >
> > > > > Le lun. 30 janv. 2023 à 07:53, Hervé Boutemy <
> herve.bout...@free.fr> a
> > > > >
> > > > > écrit :
> > > > > > I think that first steps are:
> > > > > >
> > > > > > 1. release maven-api-meta as a shared component, given it has no
> > > > > > dependency
> > > > > >
> > > > > >
> > >
> https://maven.apache.org/ref/4.0.0-alpha-4/api/maven-api-meta/dependencies
> > > > > > .html Eventually renaming it maven-api-annotations, given it's
> the
> > > Java
> > > > > > package name inside
> > > > > >
> > > > > > 2. release maven-api-xml as a shared component, given it only
> > > depends on
> > > > > > previous one
> > > > > >
> > > > > >
> > >
> https://maven.apache.org/ref/4.0.0-alpha-4/api/maven-api-xml/dependencies.
> > > > > > html
> > > > > I really think having the full API in a single tree / 

Re: extracting XML classes from plexus-utils to plexus-xml

[Elliotte Rusty Harold]

Very roughly my suggestion is create new artifacts that do what you
want with completely new packages. Class names can stay the same but
package names must change when the artifact ID or group ID changes.

If you want to keep the fully package qualified class names the same,
then don't change the artifact  IDs or class locations and live with
the current situation.

Also important in Java 9+ is that all classes from a single package
belong to a single jar./Maven artifact. E.g. do not put one class from
org.apache.maven.api.xml in one artifact and other classes from that
package in a different artifact.

If you're already doing all that, great. However
https://github.com/apache/maven/pull/975 looks to me like it's
renaming an artifact without  renaming any packages. That's a red
flag. It might be OK if org.apache.maven:plexus-utils has never been
published. Looks like it's only been published in alpha, so maybe OK?

On Tue, Jan 31, 2023 at 7:47 AM Guillaume Nodet  wrote:
>
> Maybe I'm wrong, but I think you missed the point.
>
> We have new packages / new artifacts, mainly the xml api located in
> the maven-api-xml artifact [1] with a single interface XmlNode [2].
> The implementation is in the maven-xml-impl [3] artifact.
> As I said, I'd like to keep it where it is.
>
> Now, in order to get some compatibility with all the 3.x world in maven 4
> and achieve the goals (one of them was to have an immutable api), the
> old classes which were part of the maven 3 api were slightly modified
> to wrap the new ones.  So we have the Xpp3Node from plexus-utils which
> now wrap the XmlNodeImpl (implementing the new XmlNode interface
> which is immutable).  So far so good.
>
> However, to achieve this, I had to put those modified classes (Xpp3Node
> and the related Xpp3DomBuilder) inside the maven-plexus-utils artifact [4]
> (which is currently named plexus-utils, but lives inside maven.  So now,
> maven has a repackaged version of plexus-utils with a few modifications
> that need to be maintained somewhere.  We're actually
> breaking https://jlbp.dev/JLBP-5, and we're trying to find a way out.
>
> Any better advice than keeping the current state ?
>
> Guillaume
>
> [1] https://github.com/apache/maven/tree/master/api/maven-api-xml
> [2]
> https://github.com/apache/maven/blob/master/api/maven-api-xml/src/main/java/org/apache/maven/api/xml/XmlNode.java
> [3] https://github.com/apache/maven/tree/master/maven-xml-impl
> [4] https://github.com/apache/maven/tree/master/plexus-utils
>
> Le mar. 31 janv. 2023 à 13:28, Elliotte Rusty Harold  a
> écrit :
>
> > Thanks for the PR. That makes this clearer. I'm now -1 (-10?) on this
> > entire proposal. Renaming artifact IDs without renaming packages is a
> > recipe for hard to debug, hard to fix problems.
> >
> > See https://jlbp.dev/JLBP-6 for detailed explanation and suggestions
> >
> > To proceed what's needed is a hard fork of everything with new package
> > names and artifact IDs.
> >
> > On Mon, Jan 30, 2023 at 7:31 PM Hervé Boutemy 
> > wrote:
> > >
> > > Le lundi 30 janvier 2023, 14:06:28 CET Guillaume Nodet a écrit :
> > > > Given this is
> > > >
> > > > Le lun. 30 janv. 2023 à 07:53, Hervé Boutemy  a
> > > >
> > > > écrit :
> > > > > I think that first steps are:
> > > > >
> > > > > 1. release maven-api-meta as a shared component, given it has no
> > > > > dependency
> > > > >
> > > > >
> > https://maven.apache.org/ref/4.0.0-alpha-4/api/maven-api-meta/dependencies
> > > > > .html Eventually renaming it maven-api-annotations, given it's the
> > Java
> > > > > package name inside
> > > > >
> > > > > 2. release maven-api-xml as a shared component, given it only
> > depends on
> > > > > previous one
> > > > >
> > > > >
> > https://maven.apache.org/ref/4.0.0-alpha-4/api/maven-api-xml/dependencies.
> > > > > html
> > > > I really think having the full API in a single tree / release cycle is
> > a
> > > > good thing, so I'm not really keen on such a move.
> > > > I don't care so much about the plexus classes which are not supposed
> > to be
> > > > part of the new API, so those can be moved wherever it's easier, but
> > unless
> > > > there's a very strong requirement, I'd really prefer to keep all the
> > api
> > > > packages colocated and not splitted.
> > > maven-xml-impl depends on maven-api-xml which depends on maven-api-
> > > meta(annotations)
> > > if you want maven-plexus-utils to include maven-xml-impl but without
> > having to
> > > do the repackaging inside Maven core build, I don't see how you expect
> > to do
> > >
> > > or I misunderstood the intent
> > >
> > > >
> > > > Guillaume
> > > >
> > > > > then we'll refine the plan on Maven XML reimplementation of Plexus
> > Utils
> > > > > XML classes and injection into Maven 4 distribution
> > > > >
> > > > >
> > > > > Creating new Git repositories for
> > > > > 1. maven-api-annotations
> > > > > 2. and maven-api-xml
> > > > > is easy, but it can't be deleted later: I need clear consensus on the
> > > > > creation 

Re: extracting XML classes from plexus-utils to plexus-xml

[Guillaume Nodet]

Maybe I'm wrong, but I think you missed the point.

We have new packages / new artifacts, mainly the xml api located in
the maven-api-xml artifact [1] with a single interface XmlNode [2].
The implementation is in the maven-xml-impl [3] artifact.
As I said, I'd like to keep it where it is.

Now, in order to get some compatibility with all the 3.x world in maven 4
and achieve the goals (one of them was to have an immutable api), the
old classes which were part of the maven 3 api were slightly modified
to wrap the new ones.  So we have the Xpp3Node from plexus-utils which
now wrap the XmlNodeImpl (implementing the new XmlNode interface
which is immutable).  So far so good.

However, to achieve this, I had to put those modified classes (Xpp3Node
and the related Xpp3DomBuilder) inside the maven-plexus-utils artifact [4]
(which is currently named plexus-utils, but lives inside maven.  So now,
maven has a repackaged version of plexus-utils with a few modifications
that need to be maintained somewhere.  We're actually
breaking https://jlbp.dev/JLBP-5, and we're trying to find a way out.

Any better advice than keeping the current state ?

Guillaume

[1] https://github.com/apache/maven/tree/master/api/maven-api-xml
[2]
https://github.com/apache/maven/blob/master/api/maven-api-xml/src/main/java/org/apache/maven/api/xml/XmlNode.java
[3] https://github.com/apache/maven/tree/master/maven-xml-impl
[4] https://github.com/apache/maven/tree/master/plexus-utils

Le mar. 31 janv. 2023 à 13:28, Elliotte Rusty Harold  a
écrit :

> Thanks for the PR. That makes this clearer. I'm now -1 (-10?) on this
> entire proposal. Renaming artifact IDs without renaming packages is a
> recipe for hard to debug, hard to fix problems.
>
> See https://jlbp.dev/JLBP-6 for detailed explanation and suggestions
>
> To proceed what's needed is a hard fork of everything with new package
> names and artifact IDs.
>
> On Mon, Jan 30, 2023 at 7:31 PM Hervé Boutemy 
> wrote:
> >
> > Le lundi 30 janvier 2023, 14:06:28 CET Guillaume Nodet a écrit :
> > > Given this is
> > >
> > > Le lun. 30 janv. 2023 à 07:53, Hervé Boutemy  a
> > >
> > > écrit :
> > > > I think that first steps are:
> > > >
> > > > 1. release maven-api-meta as a shared component, given it has no
> > > > dependency
> > > >
> > > >
> https://maven.apache.org/ref/4.0.0-alpha-4/api/maven-api-meta/dependencies
> > > > .html Eventually renaming it maven-api-annotations, given it's the
> Java
> > > > package name inside
> > > >
> > > > 2. release maven-api-xml as a shared component, given it only
> depends on
> > > > previous one
> > > >
> > > >
> https://maven.apache.org/ref/4.0.0-alpha-4/api/maven-api-xml/dependencies.
> > > > html
> > > I really think having the full API in a single tree / release cycle is
> a
> > > good thing, so I'm not really keen on such a move.
> > > I don't care so much about the plexus classes which are not supposed
> to be
> > > part of the new API, so those can be moved wherever it's easier, but
> unless
> > > there's a very strong requirement, I'd really prefer to keep all the
> api
> > > packages colocated and not splitted.
> > maven-xml-impl depends on maven-api-xml which depends on maven-api-
> > meta(annotations)
> > if you want maven-plexus-utils to include maven-xml-impl but without
> having to
> > do the repackaging inside Maven core build, I don't see how you expect
> to do
> >
> > or I misunderstood the intent
> >
> > >
> > > Guillaume
> > >
> > > > then we'll refine the plan on Maven XML reimplementation of Plexus
> Utils
> > > > XML classes and injection into Maven 4 distribution
> > > >
> > > >
> > > > Creating new Git repositories for
> > > > 1. maven-api-annotations
> > > > 2. and maven-api-xml
> > > > is easy, but it can't be deleted later: I need clear consensus on the
> > > > creation and their name before doing the work.
> > > >
> > > > Any objection?
> > > >
> > > > Regards,
> > > >
> > > > Hervé
> > > >
> > > > Le mercredi 25 janvier 2023, 11:15:08 CET Guillaume Nodet a écrit :
> > > > > That sounds like a good plan.
> > > > >
> > > > > A few observations:
> > > > >   * the usage of the plexus xml classes should be deprecated along
> with
> > > >
> > > > the
> > > >
> > > > > v3 model once the v4 api is stabilized and matured imho
> > > > >
> > > > >   * this will introduce a release cycle between maven-core /
> > > >
> > > > plexus-utils,
> > > >
> > > > > which is not really clean even though it should not cause any real
> > > >
> > > > problem
> > > >
> > > > > Guillaume
> > > > >
> > > > > Le ven. 30 déc. 2022 à 23:56, Hervé Boutemy 
> a
> > > > >
> > > > > écrit :
> > > > > > ok, if everyone wants to go that route of clarifying dependency
> from
> > > >
> > > > Maven
> > > >
> > > > > > on
> > > > > > plexus-utils, let's go and do it fully.
> > > > > >
> > > > > > First, I'm lost if you call "plexus-xml" an artifact that is
> > > >
> > > > maintained at
> > > >
> > > > > > Maven. So we'll need to rephrase with one strict convention:
> 

Re: Maven 3.9,0 plan

[Elliotte Rusty Harold]

On Mon, Jan 30, 2023 at 5:43 PM Tamás Cservenák  wrote:
>
> Maven 3.8.x uses surefire 2.x, while 3.9.x uses surefire 3.0.0-M8... to me,
> this seems like a surefire 3.0.0-M8 issue...
>

Is this a blocker for Maven 3.9.0 then? Should we finish surefire
3.0.0 first, then push 3.9.0? I'd prefer that Maven core not depend on
unstable dependencies.



-- 
Elliotte Rusty Harold
elh...@ibiblio.org

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

Re: extracting XML classes from plexus-utils to plexus-xml

[Elliotte Rusty Harold]

Thanks for the PR. That makes this clearer. I'm now -1 (-10?) on this
entire proposal. Renaming artifact IDs without renaming packages is a
recipe for hard to debug, hard to fix problems.

See https://jlbp.dev/JLBP-6 for detailed explanation and suggestions

To proceed what's needed is a hard fork of everything with new package
names and artifact IDs.

On Mon, Jan 30, 2023 at 7:31 PM Hervé Boutemy  wrote:
>
> Le lundi 30 janvier 2023, 14:06:28 CET Guillaume Nodet a écrit :
> > Given this is
> >
> > Le lun. 30 janv. 2023 à 07:53, Hervé Boutemy  a
> >
> > écrit :
> > > I think that first steps are:
> > >
> > > 1. release maven-api-meta as a shared component, given it has no
> > > dependency
> > >
> > > https://maven.apache.org/ref/4.0.0-alpha-4/api/maven-api-meta/dependencies
> > > .html Eventually renaming it maven-api-annotations, given it's the Java
> > > package name inside
> > >
> > > 2. release maven-api-xml as a shared component, given it only depends on
> > > previous one
> > >
> > > https://maven.apache.org/ref/4.0.0-alpha-4/api/maven-api-xml/dependencies.
> > > html
> > I really think having the full API in a single tree / release cycle is a
> > good thing, so I'm not really keen on such a move.
> > I don't care so much about the plexus classes which are not supposed to be
> > part of the new API, so those can be moved wherever it's easier, but unless
> > there's a very strong requirement, I'd really prefer to keep all the api
> > packages colocated and not splitted.
> maven-xml-impl depends on maven-api-xml which depends on maven-api-
> meta(annotations)
> if you want maven-plexus-utils to include maven-xml-impl but without having to
> do the repackaging inside Maven core build, I don't see how you expect to do
>
> or I misunderstood the intent
>
> >
> > Guillaume
> >
> > > then we'll refine the plan on Maven XML reimplementation of Plexus Utils
> > > XML classes and injection into Maven 4 distribution
> > >
> > >
> > > Creating new Git repositories for
> > > 1. maven-api-annotations
> > > 2. and maven-api-xml
> > > is easy, but it can't be deleted later: I need clear consensus on the
> > > creation and their name before doing the work.
> > >
> > > Any objection?
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le mercredi 25 janvier 2023, 11:15:08 CET Guillaume Nodet a écrit :
> > > > That sounds like a good plan.
> > > >
> > > > A few observations:
> > > >   * the usage of the plexus xml classes should be deprecated along with
> > >
> > > the
> > >
> > > > v3 model once the v4 api is stabilized and matured imho
> > > >
> > > >   * this will introduce a release cycle between maven-core /
> > >
> > > plexus-utils,
> > >
> > > > which is not really clean even though it should not cause any real
> > >
> > > problem
> > >
> > > > Guillaume
> > > >
> > > > Le ven. 30 déc. 2022 à 23:56, Hervé Boutemy  a
> > > >
> > > > écrit :
> > > > > ok, if everyone wants to go that route of clarifying dependency from
> > >
> > > Maven
> > >
> > > > > on
> > > > > plexus-utils, let's go and do it fully.
> > > > >
> > > > > First, I'm lost if you call "plexus-xml" an artifact that is
> > >
> > > maintained at
> > >
> > > > > Maven. So we'll need to rephrase with one strict convention: plexus-*
> > > > > artifacts are maintained at Plexus, maven-* are maintained at Maven.
> > > >
> > > > I was originally thinking about a new plexus artifact, but a maven one
> > > > would be better.
> > > >
> > > > > Then let's define where the strong dependency is:
> > > > > correct me if I'm wrong, Maven core provides 5 classes from
> > >
> > > plexus-utils
> > >
> > > > > 3.x
> > > > > to the whole plugins/extensions ecosystem [1]:
> > > > > 1. org.codehaus.plexus.util.xml.Xpp3Dom
> > > > > 2. org.codehaus.plexus.util.xml.Xpp3DomBuilder
> > > > > 3. org.codehaus.plexus.util.xml.pull.XmlPullParser
> > > > > 4. org.codehaus.plexus.util.xml.pull.XmlPullParserException
> > > > > 5. org.codehaus.plexus.util.xml.pull.XmlSerializer
> > > > > (it was only 4 classes in Maven 3, but Xpp3DomBuilder was added in
> > >
> > > Maven
> > >
> > > > > 4)
> > > > >
> > > > > then for compatibility reason these 5 classes can't have their public
> > >
> > > API
> > >
> > > > > changed = it is the only place where there is a strong dependency from
> > > > > whole
> > > > > Maven to Plexus Utils
> > > > > Because if any plugin uses an implementation at build time (old
> > >
> > > version,
> > >
> > > > > for
> > > > > example), at runtime, Maven core injects the Maven core provided
> > >
> > > classes.
> > >
> > > > > For everything else that is available in Plexus Utils, we have
> > > > > maven-shared-
> > > > > utils that was created years ago and that was globally ignored [2].
> > > > > If people want to migrate, they just can for years, independently in
> > >
> > > each
> > >
> > > > > plugin or even in Maven core.
> > > > >
> > > > >
> > > > > If we want to have a clean state, we can implement these 5 classes in
> > >
> > > the
> > >
> > > > > 

[VOTE] Release Apache Maven 3.9.0

[Tamás Cservenák]

Howdy,

We solved 95 issues:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.0

There are still some open issues left in JIRA:
https://issues.apache.org/jira/issues/?filter=-5=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20order%20by%20priority%20DESC%2Cupdated%20DESC

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

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

SHA512 release checksum(s):
1ea149f4e48bc7b34d554aef86f948eca7df4e7874e30caf449f3708e4f8487c71a5e5c072a05f17c60406176ebeeaf56b5f895090c7346f8238e2da06cf6ecd
 apache-maven-3.9.0-bin.tar.gz

564fe44bfa9c7ad3e2703cbbac59d43a11fa39e4e68875d3d1584d0a0b7b77a1352da246b875c4c15d11ceb6b4dd9a0ce7dd7a48695725dce594f34325c9c605
 apache-maven-3.9.0-bin.zip

c9c89d49aa577223b1358f7391859535be031201eab502e0620522ceb66f2b42f6f8361764d6d627b66f6ae8c61cfe85cb51f7fb734aadd0427f10e43d5a1753
 apache-maven-3.9.0-src.tar.gz

68b1a3cde17a42814ea28499e0c3f5cb98c343cebdfb96b52ba5acc6c2c6bac4f99dcf93177840bbc4d2b32668f73315f678ba0fef211b422303a751690a139c
 apache-maven-3.9.0-src.zip

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

Thanks
T

Re: Maven 3.9,0 plan

[Tamás Cservenák]

FTR, vote for 3.9.0 is ongoing (see staged links there)

T

On Tue, Jan 31, 2023 at 1:36 AM Dan Tran  wrote:

> run into this issue
>
> "Unable to parse maven.config file options: Unrecognized maven.config file
> entries: [ -e --fail-fast -Djavax.xml.accessExternalSchema=all
> -Daether.connector.resumeDownloads=false]"
>
> The workaround is to break it into multiple lines
>
> -D
>
>
>
> On Mon, Jan 30, 2023 at 2:43 PM Tamás Cservenák 
> wrote:
>
> > Howdy,
> >
> > commented on issue, but FTR:
> > - the refd issue MCOMPILER-481 related IT fails when run with Maven 3.9.x
> > (passes OK with Maven 3.8.7)
> > - the compilation (what IT is testing) passes OK
> > - the failure is in UT run (surefire)
> >
> > Maven 3.8.x uses surefire 2.x, while 3.9.x uses surefire 3.0.0-M8... to
> me,
> > this seems like a surefire 3.0.0-M8 issue...
> >
> > I see no other relation to Maven core here.
> >
> > Thanks
> > T
> >
> > On Mon, Jan 30, 2023 at 10:23 PM Jorge Solórzano 
> wrote:
> >
> > > Hi, what about the issue (regression) with
> > > https://issues.apache.org/jira/browse/MCOMPILER-481?
> > >
> > > Regards,
> > >
> > > On Mon, Jan 30, 2023 at 4:24 PM Tamás Cservenák 
> > > wrote:
> > > >
> > > > Howdy,
> > > >
> > > > FYI Maven 3.9.0 is good to go.
> > > >
> > > >
> > > > T
> > > >
> > > > On Thu, Jan 26, 2023 at 10:46 PM Tamás Cservenák <
> ta...@cservenak.net>
> > > > wrote:
> > > >
> > > > > Howdy,
> > > > >
> > > > > 3.9.0 on hold for a bit more, an issue (and related PR) just popped
> > in:
> > > > > https://issues.apache.org/jira/browse/MNG-7672
> > > > >
> > > > > Thanks
> > > > > T
> > > > >
> > > > > On Thu, Jan 26, 2023 at 7:49 PM Tamás Cservenák <
> ta...@cservenak.net
> > >
> > > > > wrote:
> > > > >
> > > > >> Howdy
> > > > >>
> > > > >> Tomorrow is 27th :) Staging is part of release (release + vote +
> > final
> > > > >> promotion to Central), so hopefully tomorrow will be staged
> > > > >>
> > > > >> T
> > > > >>
> > > > >> On Thu, Jan 26, 2023, 19:28 Delany 
> > > wrote:
> > > > >>
> > > > >>> Hi Tamas,
> > > > >>> Will you create a staging for 3.9.0?
> > > > >>> I don't see anything at
> > > > >>>
> > > > >>>
> > >
> >
> https://repository.apache.org/content/repositories/staging/org/apache/maven/maven/
> > > > >>> Delany
> > > > >>>
> > > > >>> On Thu, 19 Jan 2023 at 11:03, Tamás Cservenák <
> ta...@cservenak.net
> > >
> > > > >>> wrote:
> > > > >>>
> > > > >>> > Howdy,
> > > > >>> >
> > > > >>> > The 3.9.0 changelist:
> > > > >>> >
> > > > >>> >
> > > > >>>
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.0
> > > > >>> >
> > > > >>> > It received today one more PR (
> > > > >>> > https://issues.apache.org/jira/browse/MNG-7630), but the plan
> > I'd
> > > > >>> like to
> > > > >>> > propose is following:
> > > > >>> >
> > > > >>> > - Keep the "3.9.0 window" open until the end of next week (27th
> > Jan
> > > > >>> 2023).
> > > > >>> > - On 27th (or a bit after) do the 3.9.0 release
> > > > >>> >
> > > > >>> > So, please anyone able to, test 3.9.0-SNAPSHOT if you can.
> > > > >>> >
> > > > >>> > Aside of detailed changelog above, here is a high level list
> (to
> > be
> > > > >>> > reworked for site) here:
> > > > >>> >
> > > > >>> >
> > > > >>>
> > >
> >
> https://cwiki.apache.org/confluence/display/MAVEN/Notes+for+Maven+3.9.x+users
> > > > >>> >
> > > > >>> >
> > > > >>>
> > >
> >
> https://cwiki.apache.org/confluence/display/MAVEN/Notes+For+Maven+3.9.x+Plugin+Developers
> > > > >>> >
> > > > >>> > Have fun
> > > > >>> > T
> > > > >>> >
> > > > >>>
> > > > >>
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > >
> > >
> >
>

Re: [VOTE] Release Apache Maven Enforcer version 3.2.1

[Sylwester Lachiewicz]

+1

pon., 30 sty 2023, 08:08 użytkownik Herve Boutemy 
napisał:

> +1
>
> Reproducible Builds ok: reference build done with JDK 17 on *nix
>
> Regards,
>
> Hervé
>
> On 2023/01/28 21:38:50 Slawomir Jaranowski wrote:
> > Hi,
> >
> > We solved 44 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520=12352857
> >
> > There are still a couple of issues left in JIRA:
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MENFORCER%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1860/
> >
> https://repository.apache.org/content/repositories/maven-1860/org/apache/maven/enforcer/enforcer/3.2.1/enforcer-3.2.1-source-release.zip
> >
> > Source release checksum(s):
> > enforcer-3.2.1-source-release.zip - SHA-512 :
> >
> 504e6d1b2d035eed8d2326ac6e4bfdc6240a48af749b87bb94bc584899504d624cc61764efedcc6accb428d40d31270b566a8e71ded6e514b2c192fbf3e27fc6
> >
> > Staging site:
> > https://maven.apache.org/enforcer-archives/enforcer-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
>
>

Re: [VOTE] Release Apache Maven Enforcer version 3.2.1

[Guillaume Nodet]

+1

Le sam. 28 janv. 2023 à 22:39, Slawomir Jaranowski 
a écrit :

> Hi,
>
> We solved 44 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520=12352857
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MENFORCER%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1860/
>
> https://repository.apache.org/content/repositories/maven-1860/org/apache/maven/enforcer/enforcer/3.2.1/enforcer-3.2.1-source-release.zip
>
> Source release checksum(s):
> enforcer-3.2.1-source-release.zip - SHA-512 :
>
> 504e6d1b2d035eed8d2326ac6e4bfdc6240a48af749b87bb94bc584899504d624cc61764efedcc6accb428d40d31270b566a8e71ded6e514b2c192fbf3e27fc6
>
> Staging site:
> https://maven.apache.org/enforcer-archives/enforcer-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
>


-- 

Guillaume Nodet

Re: extracting XML classes from plexus-utils to plexus-xml

[Guillaume Nodet]

Le mar. 31 janv. 2023 à 01:31, Hervé Boutemy  a
écrit :

> Le lundi 30 janvier 2023, 14:06:28 CET Guillaume Nodet a écrit :
> > Given this is
> >
> > Le lun. 30 janv. 2023 à 07:53, Hervé Boutemy  a
> >
> > écrit :
> > > I think that first steps are:
> > >
> > > 1. release maven-api-meta as a shared component, given it has no
> > > dependency
> > >
> > >
> https://maven.apache.org/ref/4.0.0-alpha-4/api/maven-api-meta/dependencies
> > > .html Eventually renaming it maven-api-annotations, given it's the Java
> > > package name inside
> > >
> > > 2. release maven-api-xml as a shared component, given it only depends
> on
> > > previous one
> > >
> > >
> https://maven.apache.org/ref/4.0.0-alpha-4/api/maven-api-xml/dependencies.
> > > html
> > I really think having the full API in a single tree / release cycle is a
> > good thing, so I'm not really keen on such a move.
> > I don't care so much about the plexus classes which are not supposed to
> be
> > part of the new API, so those can be moved wherever it's easier, but
> unless
> > there's a very strong requirement, I'd really prefer to keep all the api
> > packages colocated and not splitted.
>


> maven-xml-impl depends on maven-api-xml which depends on maven-api-
> meta(annotations)
> if you want maven-plexus-utils to include maven-xml-impl but without
> having to
> do the repackaging inside Maven core build, I don't see how you expect to
> do
>
> or I misunderstood the intent
>

The quote the original plan :
> At Plexus Utils level, I propose that we (the Plexus org) do a
version 4 that
> removes the 5 classes, replacing with a dependency on maven-plexus-xml
> that was written in Maven. Then when Maven core migrates to plexus-utils
4...

Once alpha-4 is officially released, we can add a dependency on the
maven-xml-api to
plexus-utils and release a 4.0, which we'll then use instead of the
maven-plexus-utils ?

Guillaume


>
> >
> > Guillaume
> >
> > > then we'll refine the plan on Maven XML reimplementation of Plexus
> Utils
> > > XML classes and injection into Maven 4 distribution
> > >
> > >
> > > Creating new Git repositories for
> > > 1. maven-api-annotations
> > > 2. and maven-api-xml
> > > is easy, but it can't be deleted later: I need clear consensus on the
> > > creation and their name before doing the work.
> > >
> > > Any objection?
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le mercredi 25 janvier 2023, 11:15:08 CET Guillaume Nodet a écrit :
> > > > That sounds like a good plan.
> > > >
> > > > A few observations:
> > > >   * the usage of the plexus xml classes should be deprecated along
> with
> > >
> > > the
> > >
> > > > v3 model once the v4 api is stabilized and matured imho
> > > >
> > > >   * this will introduce a release cycle between maven-core /
> > >
> > > plexus-utils,
> > >
> > > > which is not really clean even though it should not cause any real
> > >
> > > problem
> > >
> > > > Guillaume
> > > >
> > > > Le ven. 30 déc. 2022 à 23:56, Hervé Boutemy 
> a
> > > >
> > > > écrit :
> > > > > ok, if everyone wants to go that route of clarifying dependency
> from
> > >
> > > Maven
> > >
> > > > > on
> > > > > plexus-utils, let's go and do it fully.
> > > > >
> > > > > First, I'm lost if you call "plexus-xml" an artifact that is
> > >
> > > maintained at
> > >
> > > > > Maven. So we'll need to rephrase with one strict convention:
> plexus-*
> > > > > artifacts are maintained at Plexus, maven-* are maintained at
> Maven.
> > > >
> > > > I was originally thinking about a new plexus artifact, but a maven
> one
> > > > would be better.
> > > >
> > > > > Then let's define where the strong dependency is:
> > > > > correct me if I'm wrong, Maven core provides 5 classes from
> > >
> > > plexus-utils
> > >
> > > > > 3.x
> > > > > to the whole plugins/extensions ecosystem [1]:
> > > > > 1. org.codehaus.plexus.util.xml.Xpp3Dom
> > > > > 2. org.codehaus.plexus.util.xml.Xpp3DomBuilder
> > > > > 3. org.codehaus.plexus.util.xml.pull.XmlPullParser
> > > > > 4. org.codehaus.plexus.util.xml.pull.XmlPullParserException
> > > > > 5. org.codehaus.plexus.util.xml.pull.XmlSerializer
> > > > > (it was only 4 classes in Maven 3, but Xpp3DomBuilder was added in
> > >
> > > Maven
> > >
> > > > > 4)
> > > > >
> > > > > then for compatibility reason these 5 classes can't have their
> public
> > >
> > > API
> > >
> > > > > changed = it is the only place where there is a strong dependency
> from
> > > > > whole
> > > > > Maven to Plexus Utils
> > > > > Because if any plugin uses an implementation at build time (old
> > >
> > > version,
> > >
> > > > > for
> > > > > example), at runtime, Maven core injects the Maven core provided
> > >
> > > classes.
> > >
> > > > > For everything else that is available in Plexus Utils, we have
> > > > > maven-shared-
> > > > > utils that was created years ago and that was globally ignored [2].
> > > > > If people want to migrate, they just can for years, independently
> in
> > >
> > > each
> > >
> > > > > plugin or even in Maven