Description
When testing ~966 Apache projects against Maven 4.0.0-rc-5 (via gnodet/maven4-testing), 12 projects fail with Invalid Collect Request: null during dependency resolution. These projects all build successfully with Maven 3.
The error occurs when transitive dependencies in published POMs have ${...} version expressions that Maven 4's stricter resolver cannot resolve, resulting in a null groupId/artifactId/version in the collect request.
Affected projects
activemq-openwire, camel-quarkus, causeway-app-helloworld, causeway-app-petclinic, causeway-app-simpleapp, ctakes, incubator-streampark, logging-flume, logging-log4j-audit, mina-sshd, sling-org-apache-sling-app-cms, unomi
Build command
mvn -V -B -e clean package -DskipTests
Maven version: 4.0.0-rc-5
Summary issue
Full test run results: gnodet/maven4-testing#9485
Description
When testing ~966 Apache projects against Maven 4.0.0-rc-5 (via gnodet/maven4-testing), 12 projects fail with
Invalid Collect Request: nullduring dependency resolution. These projects all build successfully with Maven 3.The error occurs when transitive dependencies in published POMs have
${...}version expressions that Maven 4's stricter resolver cannot resolve, resulting in a null groupId/artifactId/version in the collect request.Affected projects
activemq-openwire, camel-quarkus, causeway-app-helloworld, causeway-app-petclinic, causeway-app-simpleapp, ctakes, incubator-streampark, logging-flume, logging-log4j-audit, mina-sshd, sling-org-apache-sling-app-cms, unomi
Build command
Maven version: 4.0.0-rc-5
Summary issue
Full test run results: gnodet/maven4-testing#9485