Re: Maven 3.9,0 plan
Hi Tamas, Konrad
I moved a checksum-maven-plugin config to a package activated profile as
now possible in 3.9.0
But I still want control over whether it activates.
The profile always activates when packaging=jar
I can override that and turn it off with -P-checksum
But some of these plugins should be off by default, not on by default.
The only way to do that is to allow multiple properties as in
https://issues.apache.org/jira/browse/MNG-3328
I'm just reminding this issue is 16 years old with over 100 watchers
Kind regards,
Delany
On Thu, 2 Feb 2023 at 09:02, Tamás Cservenák wrote:
> Ok, I'll take a look. Mark, can you direct me to the source code?
>
> But just as a starting point: within Maven, why are you "booting" a
> completely new resolver instance using ServiceLocator?
>
> But the best would be to have access to the sources
>
> Thanks
> T
>
> On Thu, Feb 2, 2023 at 4:55 AM Mark Derricutt wrote:
>
> > Following up on this. I removed all the [] deps from my plugin but
> > still seem to get the same issue of the class missing.
> >
> > I definitely see the class in my maven 3.9-staged/lib directory, and
> > have even updated the dependency version in my plugin to match.
> >
> > The code in question that's failing is the creation of the Aether
> > repository system - it's possible this has changed:
> >
> > ```
> >private static RepositorySystem newRepositorySystem() {
> > DefaultServiceLocator locator =
> > MavenRepositorySystemUtils.newServiceLocator();
> > locator.addService(RepositoryConnectorFactory.class,
> > BasicRepositoryConnectorFactory.class);
> > locator.addService(TransporterFactory.class,
> > FileTransporterFactory.class);
> > locator.addService(TransporterFactory.class,
> > HttpTransporterFactory.class);
> > return locator.getService(RepositorySystem.class);
> >}
> > ```
> >
> > and trace was:
> >
> > ```
> > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> > (DefaultBuildPluginManager.java:149)
> > at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> > (MojoExecutor.java:341)
> > at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> > (MojoExecutor.java:329)
> > at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:212)
> > at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:174)
> > at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> > (MojoExecutor.java:75)
> > at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> > (MojoExecutor.java:162)
> > at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> > (DefaultMojosExecutionStrategy.java:37)
> > at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:159)
> > at
> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> > (LifecycleModuleBuilder.java:104)
> > at
> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> > (LifecycleModuleBuilder.java:72)
> > at
> >
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> >
> > (SingleThreadedBuilder.java:52)
> > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> > (LifecycleStarter.java:117)
> > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:259)
> > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:171)
> > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:99)
> > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:820)
> > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:269)
> > at org.apache.maven.cli.MavenCli.main (MavenCli.java:191)
> > 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.NoClassDefFoundError:
> > org/eclipse/aether/connector/basic/BasicRepositoryConnectorFactory
> > at
> > com.smxemail.rangeresolver.lang.RepositoryResolver.newRepositorySystem
> > (RepositoryResolver.java:123)
> > at com.smxemail.rangeresolver.lang.RepositoryResolver.
> > (RepositoryResolver.java:108)
> > at
> >
> com.smxemail.rangeresolver.lang.RepositoryResolver.createRepositoryResolver
> >
> > (RepositoryResolver.java:118)
> > at
Re: Maven 3.9,0 plan
Ok, I'll take a look. Mark, can you direct me to the source code?
But just as a starting point: within Maven, why are you "booting" a
completely new resolver instance using ServiceLocator?
But the best would be to have access to the sources
Thanks
T
On Thu, Feb 2, 2023 at 4:55 AM Mark Derricutt wrote:
> Following up on this. I removed all the [] deps from my plugin but
> still seem to get the same issue of the class missing.
>
> I definitely see the class in my maven 3.9-staged/lib directory, and
> have even updated the dependency version in my plugin to match.
>
> The code in question that's failing is the creation of the Aether
> repository system - it's possible this has changed:
>
> ```
>private static RepositorySystem newRepositorySystem() {
> DefaultServiceLocator locator =
> MavenRepositorySystemUtils.newServiceLocator();
> locator.addService(RepositoryConnectorFactory.class,
> BasicRepositoryConnectorFactory.class);
> locator.addService(TransporterFactory.class,
> FileTransporterFactory.class);
> locator.addService(TransporterFactory.class,
> HttpTransporterFactory.class);
> return locator.getService(RepositorySystem.class);
>}
> ```
>
> and trace was:
>
> ```
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:149)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:341)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:329)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:37)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:104)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:72)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
>
> (SingleThreadedBuilder.java:52)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:117)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:259)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:171)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:99)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:820)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:269)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:191)
> 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.NoClassDefFoundError:
> org/eclipse/aether/connector/basic/BasicRepositoryConnectorFactory
> at
> com.smxemail.rangeresolver.lang.RepositoryResolver.newRepositorySystem
> (RepositoryResolver.java:123)
> at com.smxemail.rangeresolver.lang.RepositoryResolver.
> (RepositoryResolver.java:108)
> at
> com.smxemail.rangeresolver.lang.RepositoryResolver.createRepositoryResolver
>
> (RepositoryResolver.java:118)
> at com.smxemail.rangeresolver.mojo.RangeResolverMojo.execute
> (RangeResolverMojo.java:113)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:125)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:341)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:329)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
>
Re: Maven 3.9,0 plan
Following up on this. I removed all the [] deps from my plugin but
still seem to get the same issue of the class missing.
I definitely see the class in my maven 3.9-staged/lib directory, and
have even updated the dependency version in my plugin to match.
The code in question that's failing is the creation of the Aether
repository system - it's possible this has changed:
```
private static RepositorySystem newRepositorySystem() {
DefaultServiceLocator locator =
MavenRepositorySystemUtils.newServiceLocator();
locator.addService(RepositoryConnectorFactory.class,
BasicRepositoryConnectorFactory.class);
locator.addService(TransporterFactory.class,
FileTransporterFactory.class);
locator.addService(TransporterFactory.class,
HttpTransporterFactory.class);
return locator.getService(RepositorySystem.class);
}
```
and trace was:
```
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:149)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:341)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:329)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:174)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
(MojoExecutor.java:75)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:162)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
(DefaultMojosExecutionStrategy.java:37)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:159)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:104)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:72)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:52)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:117)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:259)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:171)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:99)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:820)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:269)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:191)
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.NoClassDefFoundError:
org/eclipse/aether/connector/basic/BasicRepositoryConnectorFactory
at
com.smxemail.rangeresolver.lang.RepositoryResolver.newRepositorySystem
(RepositoryResolver.java:123)
at com.smxemail.rangeresolver.lang.RepositoryResolver.
(RepositoryResolver.java:108)
at
com.smxemail.rangeresolver.lang.RepositoryResolver.createRepositoryResolver
(RepositoryResolver.java:118)
at com.smxemail.rangeresolver.mojo.RangeResolverMojo.execute
(RangeResolverMojo.java:113)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:125)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:341)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:329)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:174)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
(MojoExecutor.java:75)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:162)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
(DefaultMojosExecutionStrategy.java:37)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:159)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:104)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:72)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:52)
at
Re: Maven 3.9,0 plan
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
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: Maven 3.9,0 plan
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: Maven 3.9,0 plan
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: Maven 3.9,0 plan
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: Maven 3.9,0 plan
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
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
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: Maven 3.9,0 plan
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: Maven 3.9,0 plan
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: Maven 3.9,0 plan
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: Maven 3.9,0 plan
Thanks Slawomir! Tested via https://github.com/gitflow-incremental-builder/gitflow-incremental-builder, no issues! Might try Quarkus next. Cheers, Falko Am 19.01.2023 um 23:11 schrieb Slawomir Jaranowski: Build on Jenkins deploys snapshot artifacts to ASF repository, https://repository.apache.org/#nexus-search;gav~org.apache.maven~apache-maven~3.9.0-SNAPSHOT~~ czw., 19 sty 2023 o 22:49 Falko Modler napisał(a): Hi there, So, please anyone able to, test 3.9.0-SNAPSHOT if you can. do I have to build it on my own? I've been looking in a few places including Jenkins but I couldn't find a pre-built archive. Thanks! Cheers, Falko - 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
On 24 Jan 2023, at 21:22, Tamás Cservenák wrote: Mark, Can you provide more information about this error? I understand if this plugin is internal (not OSS), but can you provide me the POM of it, or at least the dependencies snippet related to Maven and resolver? "A required class is missing" is strange, especially as BasicRepositoryConnectorFactory is provided by Maven itself? Thanks Tamas Have been meaning to get this open sourced for ages, I keep thinking "I should really clean up the code to be more presentable first" and it always goes on the backbench :) Ironically - pulling out these dependencies, I think I see my problem - usage of this plugin rewrites dependencies to ban transitives, and lock ranges to `[]` - and well, the plugin is used on itself - so we're locking the dependency range of resolver. I'll update it to relax the ranges in the plugin and see if that works. ``` org.apache.maven maven-artifact [3.8.5] * * org.apache.maven maven-resolver-provider [3.8.5] org.apache.maven.resolver maven-resolver-api [1.7.3] org.apache.maven.resolver maven-resolver-connector-basic [1.7.3] org.apache.maven.resolver maven-resolver-impl [1.7.3] org.apache.maven.resolver maven-resolver-spi [1.7.3] org.apache.maven.resolver maven-resolver-transport-file [1.7.3] org.apache.maven.resolver maven-resolver-transport-http [1.7.3] org.apache.maven.resolver maven-resolver-util [1.7.3] ``` --- "The ease with which a change can be implemented has no relevance at all to whether it is the right change for the (Java) Platform for all time." Mark Reinhold. Mark Derricutt http://www.chaliceofblood.net http://www.theoryinpractice.net http://twitter.com/talios http://facebook.com/mderricutt
Re: Maven 3.9,0 plan
Mark, Can you provide more information about this error? I understand if this plugin is internal (not OSS), but can you provide me the POM of it, or at least the dependencies snippet related to Maven and resolver? "A required class is missing" is strange, especially as BasicRepositoryConnectorFactory is provided by Maven itself? Thanks Tamas On Tue, Jan 24, 2023 at 5:49 AM Mark Derricutt wrote: > On 19 Jan 2023, at 22:02, Tamás Cservenák wrote: > > > So, please anyone able to, test 3.9.0-SNAPSHOT if you can. > > > Seems to run fine for my normal projects - but crashes on in my main > $work project, due to an internal Maven Plugin I have that uses the > maven resolver - and I've not released a version of that which uses the > newer dependency so gets: > > ``` > [ERROR] Failed to execute goal > com.smxemail:rangeresolver-maven-plugin:1.1.58:resolve-deps > (default-cli) on project smx3.api: Execution default-cli of goal > com.smxemail:rangeresolver-maven-plugin:1.1.58:resolve-deps failed: A > required class was missing while executing > com.smxemail:rangeresolver-maven-plugin:1.1.58:resolve-deps: > org/eclipse/aether/connector/basic/BasicRepositoryConnectorFactory > [ERROR] - > [ERROR] realm =plugin>com.smxemail:rangeresolver-maven-plugin:1.1.58 > [ERROR] strategy = > org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy > [ERROR] urls[0] = > > file:/Users/amrk/.m2/repository/com/smxemail/rangeresolver-maven-plugin/1.1.58/rangeresolver-maven-plugin-1.1.58.jar > [ERROR] urls[1] = > > file:/Users/amrk/.m2/repository/com/smxemail/com.smxemail.rangeresolver/1.1.34/com.smxemail.rangeresolver-1.1.34.jar > [ERROR] urls[2] = > > file:/Users/amrk/.m2/repository/com/google/guava/guava/31.1-jre/guava-31.1-jre.jar > [ERROR] urls[3] = > > file:/Users/amrk/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar > ``` > > Likely just requires me to update my plugin, but this will likely break > other mojos that use aether/resolver. > > Being a .0 release (even tho not a major) I think I'm fine with that - > but it might be something we want to document? > > > > > > --- > "The ease with which a change can be implemented has no relevance at all > to whether it is the right change for the (Java) Platform for all time." > Mark Reinhold. > > Mark Derricutt > http://www.chaliceofblood.net > http://www.theoryinpractice.net > http://twitter.com/talios > http://facebook.com/mderricutt >
Re: Maven 3.9,0 plan
On 19 Jan 2023, at 22:02, Tamás Cservenák wrote: So, please anyone able to, test 3.9.0-SNAPSHOT if you can. Seems to run fine for my normal projects - but crashes on in my main $work project, due to an internal Maven Plugin I have that uses the maven resolver - and I've not released a version of that which uses the newer dependency so gets: ``` [ERROR] Failed to execute goal com.smxemail:rangeresolver-maven-plugin:1.1.58:resolve-deps (default-cli) on project smx3.api: Execution default-cli of goal com.smxemail:rangeresolver-maven-plugin:1.1.58:resolve-deps failed: A required class was missing while executing com.smxemail:rangeresolver-maven-plugin:1.1.58:resolve-deps: org/eclipse/aether/connector/basic/BasicRepositoryConnectorFactory [ERROR] - [ERROR] realm =plugin>com.smxemail:rangeresolver-maven-plugin:1.1.58 [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy [ERROR] urls[0] = file:/Users/amrk/.m2/repository/com/smxemail/rangeresolver-maven-plugin/1.1.58/rangeresolver-maven-plugin-1.1.58.jar [ERROR] urls[1] = file:/Users/amrk/.m2/repository/com/smxemail/com.smxemail.rangeresolver/1.1.34/com.smxemail.rangeresolver-1.1.34.jar [ERROR] urls[2] = file:/Users/amrk/.m2/repository/com/google/guava/guava/31.1-jre/guava-31.1-jre.jar [ERROR] urls[3] = file:/Users/amrk/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar ``` Likely just requires me to update my plugin, but this will likely break other mojos that use aether/resolver. Being a .0 release (even tho not a major) I think I'm fine with that - but it might be something we want to document? --- "The ease with which a change can be implemented has no relevance at all to whether it is the right change for the (Java) Platform for all time." Mark Reinhold. Mark Derricutt http://www.chaliceofblood.net http://www.theoryinpractice.net http://twitter.com/talios http://facebook.com/mderricutt
Re: Maven 3.9,0 plan
Build on Jenkins deploys snapshot artifacts to ASF repository, https://repository.apache.org/#nexus-search;gav~org.apache.maven~apache-maven~3.9.0-SNAPSHOT~~ czw., 19 sty 2023 o 22:49 Falko Modler napisał(a): > Hi there, > > So, please anyone able to, test 3.9.0-SNAPSHOT if you can. > > do I have to build it on my own? I've been looking in a few places > including Jenkins but I couldn't find a pre-built archive. > > Thanks! > > Cheers, > > Falko > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Sławomir Jaranowski
Re: Maven 3.9,0 plan
Hi there, So, please anyone able to, test 3.9.0-SNAPSHOT if you can. do I have to build it on my own? I've been looking in a few places including Jenkins but I couldn't find a pre-built archive. Thanks! Cheers, Falko - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Maven 3.9,0 plan
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
