date:20230130

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

2023-01-30 Thread Herve Boutemy

there is no problem with maven-api-meta(annotations) and maven-api-xml which 
are completely new (java packages and artifactIds) and created for Maven core. 
I added links to the documentation to share where everything lives and what it 
contains
https://maven.apache.org/ref/4.0.0-alpha-4/api/index.html
= https://github.com/apache/maven/tree/master/api

The hard part, is the rewrite for Maven core immutable API of classes that are 
from the XML classes of plexus utils: by definition, on these, the situation is 
more complex
It's composed of:
- maven-xml-impl: new artifactId that reimplements a few 
org.codehaus.plexus.xml classes
https://github.com/apache/maven/tree/master/maven-xml-impl
- (maven-)plexus-utils: a new Maven core groupId/artifactId that injects 
maven-xml-impl into Plexus' plexus-utils
https://github.com/apache/maven/tree/master/plexus-utils


apparently, we'll need to go step by step for people to understand and share a 
plan

I'm starting with the basic rename of Maven's plexus-utils into 
maven-plexus-utils for critical clarity between Plexus owned artifact vs Maven 
owned one
https://github.com/apache/maven/pull/975

We'll see in another PR the eventual rename of maven-api-meta to 
maven-api-annotations, just for clarity

And the discussion about what to do on maven-xml-impl and maven-plexus-utils is 
the hard part that will require more investigation

Regards,

Hervé

On 2023/01/30 12:54:27 Elliotte Rusty Harold wrote:
> On Mon, Jan 30, 2023 at 1:53 AM Hervé Boutemy  wrote:
> >
> > 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
> >
> 
> Where do those classes live now? Is this reorganizing likely to
> produce classpath conflicts?
> 
> https://jlbp.dev/JLBP-19
> 
> -- 
> 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
> 
> 

-
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

2023-01-30 Thread 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

-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 
> > > 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  >
> > > > 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  >
> > > >>> 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: extracting XML classes from plexus-utils to plexus-xml

2023-01-30 Thread Hervé Boutemy

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
> > 
> > > > current maven-xml-impl, that I propose to name maven-plexus-utils-xml,
> > 
> > or
> > 
> > > > shorter maven-plexus-xml.
> > > > As the artifact name tells, it is maintained at Maven level. And "of
> > > > course",
> > > > it MUST NOT depend on Plexus Utils given the intent of getting out of
> > 
> > that
> > 
> > > > dependency...
> > > > It is expected to be very stable, because it is a key compatibility
> > > > contract
> > > > between Maven core and the whole plugins/extensions ecosystem:
> > > > could/should be
> > > > extracted from Maven core releases, moved to shared/ components.
> > > 
> > > Makes sense.
> > > 
> > > > At

Re: Maven 3.9,0 plan

2023-01-30 Thread Tamás Cservenák

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 
> > 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 
> > > 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 
> > >>> 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: Maven 3.9,0 plan

2023-01-30 Thread Jorge Solórzano

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 
> 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 
> > 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 
> >>> 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 4.0.0-alpha-4 release

2023-01-30 Thread Guillaume Nodet

Le sam. 28 janv. 2023 à 06:08, Mark Derricutt  a écrit :

> On 28 Jan 2023, at 6: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=Text=12316922
> > [4]
> >
> https://github.com/apache/maven/releases/tag/untagged-4ba8d14c9e8eb6de3887
>
>
> Interesting - on my project using maven-tiles-plugin (which we know had
> issues with alpha1-3) I get a different result with alpha4:
>
> ```
> [INFO] Scanning for projects...
> [INFO] --- tiles-maven-plugin: Injecting 1 tiles as intermediary parent
> artifacts for smx3:smx3.core...
> [INFO] Mixed 'smx3:smx3.core:22.7.20-SNAPSHOT' with tile
> 'com.smxemail.tiles:com.smxemail.tiles.release:2.2.62' as its new
> parent.
> [ERROR] Internal error: java.lang.IllegalStateException: Unable to set
> modelId on InputSource: NullPointerException -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> java.lang.IllegalStateException: Unable to set modelId on InputSource
>  at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:161)
>  at org.apache.maven.cli.MavenCli.execute (MavenCli.java:859)
>  at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:282)
>  at org.apache.maven.cli.MavenCli.main (MavenCli.java:198)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
>  at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
>  at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
>  at java.lang.reflect.Method.invoke (Method.java:498)
>  at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
>  at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
>  at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
>  at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by: java.lang.IllegalStateException: Unable to set modelId on
> InputSource
>  at
> org.apache.maven.model.building.DefaultModelBuilder.doReadFileModel
> (DefaultModelBuilder.java:1043)
>  at
> org.apache.maven.model.building.DefaultModelBuilder.readFileModel
> (DefaultModelBuilder.java:971)
>  at org.apache.maven.model.building.DefaultModelBuilder.readRawModel
> (DefaultModelBuilder.java:1117)
>  at
> org.apache.maven.model.building.DefaultModelBuilder.readParentExternally
> (DefaultModelBuilder.java:1550)
>  at org.apache.maven.model.building.DefaultModelBuilder.readParent
> (DefaultModelBuilder.java:1339)
>  at
> org.apache.maven.model.building.DefaultModelBuilder.readEffectiveModel
> (DefaultModelBuilder.java:798)
>  at org.apache.maven.model.building.DefaultModelBuilder.build
> (DefaultModelBuilder.java:896)
>  at org.apache.maven.model.building.DefaultModelBuilder.build
> (DefaultModelBuilder.java:885)
>  at org.codehaus.groovy.vmplugin.v8.IndyInterface.fromCache
> (IndyInterface.java:321)
>  at
> io.repaint.maven.tiles.TilesMavenLifecycleParticipant.thunkModelBuilder
> (TilesMavenLifecycleParticipant.groovy:541)
>  at
> io.repaint.maven.tiles.TilesMavenLifecycleParticipant.orchestrateMerge
> (TilesMavenLifecycleParticipant.groovy:426)
>  at
> io.repaint.maven.tiles.TilesMavenLifecycleParticipant.afterProjectsRead
> (TilesMavenLifecycleParticipant.groovy:324)
> ```
>
> Previously I've had issues with tile.xml files that didn't include a
> `` element - but what's `modelId` in this instance? Is
> this likely to be a tiles issue, or or an XML issue somewhere in my
> project chain?
>

Not sure about that one. What's the way to reproduce the problem ?


>
> Tiles itself compiles fine with alpha4 - but I see its IT tests fail:
>
> ```
> Caused by: java.lang.IllegalStateException: transformed artifact file
> cannot be set
>  at
> org.apache.maven.internal.transformation.TransformedArtifact.setFile
> (TransformedArtifact.java:71)
>  at org.apache.maven.plugins.invoker.InstallMojo.installArtifact
> (InstallMojo.java:257)
>  at
> org.apache.maven.plugins.invoker.InstallMojo.installProjectArtifacts
> (InstallMojo.java:332)
>  at org.apache.maven.plugins.invoker.InstallMojo.execute
> (InstallMojo.java:213)
>  at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:143)
>  at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:336)
>  at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:324)
>  at

Re: Maven 3.9,0 plan

2023-01-30 Thread Tamás Cservenák

Howdy,

FYI Maven 3.9.0 is good to go.


T

On Thu, Jan 26, 2023 at 10:46 PM Tamás Cservenák 
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 
> 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 
>>> 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
>>> >
>>>
>>

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

2023-01-30 Thread Tamás Cservenák

+1

On Sat, Jan 28, 2023 at 3:16 PM 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
>

Re: [VOTE] Release Apache Maven Daemon 0.9.0

2023-01-30 Thread Peter Palaga


+1

0.9.0 seems to be faster than 0.8.2 - see 
https://github.com/apache/maven-mvnd/issues/783 for some numbers.


Thanks Guillaume!

On 25/01/2023 10:10, Guillaume Nodet wrote:

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.




-
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

2023-01-30 Thread Peter Palaga


+1

Tested with Camel Quarkus, better than 1.0.0-m4, but still slower than 
0.8.2 and 0.9.0 - see https://github.com/apache/maven-mvnd/issues/783


Thanks, Guillaume!

On 29/01/2023 19:37, Romain Manni-Bucau wrote:

+1, tested on java 17 with sdkman

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



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






-
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

2023-01-30 Thread Guillaume Nodet

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.

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
> > > current maven-xml-impl, that I propose to name maven-plexus-utils-xml,
> or
> > > shorter maven-plexus-xml.
> > > As the artifact name tells, it is maintained at Maven level. And "of
> > > course",
> > > it MUST NOT depend on Plexus Utils given the intent of getting out of
> that
> > > dependency...
> > > It is expected to be very stable, because it is a key compatibility
> > > contract
> > > between Maven core and the whole plugins/extensions ecosystem:
> > > could/should be
> > > extracted from Maven core releases, moved to shared/ components.
> >
> > Makes sense.
> >
> > > 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, it remove the current
> > > need to
> > > have inside Maven core a local shaded "plexus-utils" (that should have
> > > been
> > > named maven-plexus-utils for clarity) [3]
> > >
> > >
> > >
> > >
> > >
> > >
> > > Is that plan clear and accurate?
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > >
> > > [1]
> > >
> https://github.com/apache/maven/blob/master/maven-core/src/main/resources/
> > > META-INF/maven/extension.xml#L85
> > > <
>

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

2023-01-30 Thread Elliotte Rusty Harold

On Mon, Jan 30, 2023 at 1:53 AM Hervé Boutemy  wrote:
>
> 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
>

Where do those classes live now? Is this reorganizing likely to
produce classpath conflicts?

https://jlbp.dev/JLBP-19

-- 
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 4.0.0-alpha-4 release

2023-01-30 Thread Slawomir Jaranowski

+1

pt., 27 sty 2023 o 18:11 Guillaume Nodet  napisał(a):

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


-- 
Sławomir Jaranowski

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

Re: Maven 3.9,0 plan

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

Re: Maven 3.9,0 plan

Re: Maven 3.9,0 plan

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

Re: Maven 3.9,0 plan

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

Re: [VOTE] Release Apache Maven Daemon 0.9.0

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

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

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

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

13 matches

Site Navigation

Mail list logo

Footer information