Maven "'dependencies.dependency.version' is missing" in CI

Maven validated the model and found a <dependency> with no <version>, and nothing in dependencyManagement, a parent, or an imported BOM supplies one. The build stops in validation before any goal runs.

What this error means

mvn fails fast with "Some problems were encountered while processing the POMs" and "'dependencies.dependency.version' for group:artifact:jar is missing". It fails identically every run until a version is provided.

[ERROR] Some problems were encountered while processing the POMs:
[ERROR] 'dependencies.dependency.version' for com.google.guava:guava:jar is missing. @ line 32, column 17
 @
[ERROR] The build could not read 1 project -> [Help 1]

Common causes

No version on the dependency and no managed version

The <dependency> omits <version> expecting dependencyManagement or a parent/BOM to set it, but none does, so the model is incomplete.

A BOM import was removed or its scope is wrong

The BOM that used to manage this version was dropped, or imported without <scope>import</scope> and <type>pom</type>, so the managed version never applies.

How to fix it

Add an explicit version or manage it

1. Add a <version> to the dependency, or
2. Declare it under <dependencyManagement> so it is inherited project-wide.
3. Re-run mvn validate to confirm the model resolves.

<dependency>
  <groupId>com.google.guava</groupId>
  <artifactId>guava</artifactId>
  <version>33.2.1-jre</version>
</dependency>

Re-import the managing BOM correctly

If a BOM should supply the version, import it with pom type and import scope inside dependencyManagement.

<dependencyManagement>
  <dependencies>
    <dependency>
      <groupId>com.example</groupId>
      <artifactId>platform-bom</artifactId>
      <version>1.4.0</version>
      <type>pom</type>
      <scope>import</scope>
    </dependency>
  </dependencies>
</dependencyManagement>

How to prevent it

• Manage versions centrally in dependencyManagement or a BOM.
• Run mvn validate locally before pushing POM edits.
• Keep BOM imports using <type>pom</type> and <scope>import</scope>.

Related guides