‘ endencies.depency.version’缺少错误，但版本是在父级中管理的

小开

In theory, maven does not allow to use a property to set a parent version.

In your case, maven can simply not figure out that the 0.0.1-SNAPSHOT version of your parent pom is the one that is currently in your project, and so it tries to find it in your local repo. It probably finds one since it is a snapshot, but it is an old version that probably not contains your Dependency Management section.

There is a workaround though :

Simply change the parent section in the child pom with this :

<parent>
<groupId>com.sw.system4</groupId>
<artifactId>system4-parent</artifactId>
<version>${system4.version}</version>
<relativePath>../pom.xml</relativePath>  <!-- this must match your parent pom location -->
</parent>

小开

最佳答案

A couple things I think you could try:

Put the literal value of the version in the child pom

<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-core</artifactId>
<version>3.2.3.RELEASE</version>
<scope>runtime</scope>
</dependency>

Clear your .m2 cache normally located C:\Users\user.m2\repository. I would say I do this pretty frequently when I'm working in maven. Especially before committing so that I can be more confident CI will run. You don't have to nuke the folder every time, sometimes just your project packages and the .cache folder are enough.

Add a relativePath tag to your parent pom declaration

<parent>
<groupId>com.mycompany.app</groupId>
<artifactId>my-app</artifactId>
<version>1</version>
<relativePath>../parent/pom.xml</relativePath>
</parent>

It looks like you have 8 total errors in your poms. I would try to get some basic compilation running before adding the parent pom and properties.

小开

Right, after a lot of hair tearing I have a compiling system.

Cleaning the .m2 cache was one thing that helped (thanks to Brian)

One of the mistakes I had made was to put 2 versions of each dependency in the parent pom dependencyManagement section - one with <scope>runtime</scope> and one without - this was to try and make eclipse happy (ie not show up rogue compile errors) as well as being able to run on the command line. This was just complicating matters, so I removed the runtime ones.

Explicitly setting the version of the parent seemed to work also (it's a shame that maven doesn't have more wide-ranging support for using properties like this!)

  <parent>
<groupId>com.sw.system4</groupId>
<artifactId>system4-parent</artifactId>
<version>0.0.1-SNAPSHOT</version>
</parent>

I was then getting weird 'failed to collect dependencies for' errors in the child module for all the dependencies, saying it couldn't locate the parent - even though it was set up the same as other modules which did compile.

I finally solved things by compiling from the parent pom instead of trying to compile each module individually. This told me of an error with a relatively simple fix in a different module, which strangely then made it all compile.

In other words, if you get maven errors relating to child module A, it may actually be a problem with unrelated child module Z, so look there. (and delete your cache)

小开

If anyone finds their way here with the same problem I was having, my problem was that I was missing the <dependencyManagement> tags around dependencies I had copied from the child pom.

小开

Make sure the value in the child's project/parent/version node matches its parent's project/version value

小开

You must build parent module before doing child module.

小开

What just worked for was to delete the settings.xml in the .m2 folder: this file was telling the project to look for a versión of spring mvc and web that didn't exist.

小开

I had the same error, I forgot to add the child dependencies in the <dependencyManagement>. For example in the parent pom:

<dependencyManagement>
<dependencies>
<dependency>
<groupId>com.sw.system4</groupId>
<artifactId>system4-data</artifactId><!-- child artifact id -->
<version>${project.version}</version>
<dependency>


<!-- add all third party libraries ... -->


</dependencies>
<dependencyManagement>

小开

I had the same problem and I rename the "repository" folder on ".m2" (something like repositoryBkp the name is not important is just in case something goes wrong) and create a new "repository" folder, then I re run maven and all the project compile successfully

小开

In my case I had the same dependency listed twice in the same pom.xml. Make sure it's only used once.

小开

for me the problem related to classifier in my dependencyManagement i had dependencies of the project with (and "version" off curse) i removed from dependencyManagement which solved the problem

小开

For those using the org.codehaus.mojo:flatten-maven-plugin: Be sure to set a flattenMode which keeps the dependencyManagement if you still want to import the pom (e.g. resolveCiFriendliesOnly). Otherwise, the plugin will remove the dependencyManagement section.

小开

If you are using modules and need lombok for child module you need to explicitly declare version as well like :

<dependencies>
<dependency>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
<version>1.18.24</version>
<optional>true</optional>
</dependency>
</dependencies>

It helped in my case.

小开

In my case I was putting tomcat decency then I got the error and this what I used.

<dependency>
<groupId>org.apache.tomcat.embed</groupId>
<artifactId>tomcat-embed-core</artifactId>
<version>9.0.44</version>
</dependency>

小开

Most probably your spring-framework-bom might not be existing. Recheck for the version if it has ".RELEASE" at the end.

小开

For me the problem was that an intermediate parent had the dependency.

So my setup is:

parent.pom <- intermediateparent.pom <- child.pom

The <dependencyManagement> is defined in parent.pom

When <dependency> is defined in intermediateparent.pom and child.pom, then it is defined twice in child.pom and the error occurs.

Removing the dependency from intermediateparent.pom and only defining it in child.pom helped in my case.