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&styleName=Text&projectId=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
`<modelVersion/>` 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?
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 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:77)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:162)
```
This looks to be an issue with the invoker plugin calling the now
immutable `setFile` - anyone know if theres an alpha/snapshot build of
invoker that's compatible?
Mark
---
"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
