Repository navigation
Maven 4 stricter model validation rejects dependencies without <version> managed by BOM import #13190
Description
Summary
Maven 4 raises [ERROR] 'dependencies.dependency.version' for ... is missing during model validation for dependencies whose version is managed via a BOM (<scope>import</scope> in <dependencyManagement>). Maven 3 accepted these without error.
This causes build failures for projects that correctly rely on BOM-managed versions and omit explicit <version> declarations in their <dependencies> section.
Reproduction
Affected projects (found in maven4-testing rc-6 run):
- cassandra-java-driver — multiple
org.apache.cassandra:*artifacts with BOM-managed versions - incubator-kie-optaplanner-quickstarts — similar pattern
Error (from mvnup / Maven 4 model validation)
[ERROR] 'dependencies.dependency.version' for groupId='org.apache.cassandra', artifactId='java-driver-test-infra', type='jar' is missing. @ line 42, column 5
[ERROR] 'dependencies.dependency.version' for groupId='org.apache.cassandra', artifactId='java-driver-query-builder', type='jar' is missing. @ line 47, column 5
[ERROR] 'dependencies.dependency.version' for groupId='org.apache.cassandra', artifactId='java-driver-mapper-processor', type='jar' is missing. @ line 52, column 5
Expected behavior
Dependencies whose version is managed by an imported BOM should not trigger validation errors. The BOM provides the version; the child POM correctly omits <version> per Maven best practice. Maven 3 accepted this pattern without error.
Notes
This may be a validation timing issue: the error occurs before the BOM import has been resolved and applied to dependencyManagement. If so, the fix would be to defer or suppress this validation until after BOM imports are resolved.
Alternatively, this could be intended stricter behavior — in which case the error message should clarify that the version must be provided in dependencyManagement (not necessarily inline), and the severity should be WARNING rather than ERROR for BOM-managed cases.
Maven version
Maven 4.0.0-rc-6 / maven-4.0.x branch
Activity
Fix apache#13190: use MAVEN_2_0 validation level for BUILD_EFFECTIVE …
Fix apache#13190: introduce isFilesystemRequest() to properly classif…
Fix apache#13190: use a shared BUILD_CONSUMER session in mvnup's buil…
Fix apache#13190: use a shared BUILD_CONSUMER session in mvnup's buil…
Fix apache#13190: pre-build full reactor once using BUILD_PROJECT, dr…
Fix apache#13190: pre-build full reactor once using BUILD_PROJECT, dr…
Fix apache#13190: pre-build full reactor once using BUILD_PROJECT, dr…
Fix apache#13190: pre-build full reactor once using BUILD_PROJECT, dr…
Fix apache#13190: pre-build full reactor once using BUILD_PROJECT, dr…
Fix apache#13190: pre-build full reactor once using BUILD_PROJECT, dr…
Fix #13190: pre-build full reactor once using BUILD_PROJECT, drop tem…
Fix apache#13190: pre-build full reactor once using BUILD_PROJECT, dr…
fix: restore AbstractUpgradeStrategy reactor pre-build and related mv…