dependencies dependency version is missing error but version is managed in parent

Question

I have a maven project that contains several modules   In Eclipse  Juno  with m2e  it seems to compile fine   But when I do a maven install on one of the modules  the build fails immediately    Parent pom      lt groupId gt com sw system4 lt  groupId gt     lt artifactId gt system4-parent lt  artifactId gt     lt version gt   system4 version  lt  version gt     lt packaging gt pom lt  packaging gt     lt name gt System 4 Parent Project lt  name gt     lt modules gt       lt module gt system4-data lt  module gt          others       lt  modules gt     lt properties gt       lt system4 version gt 0 0 1-SNAPSHOT lt  system4 version gt       lt spring version gt 3 2 3 RELEASE lt  spring version gt          others       lt  properties gt      lt dependencyManagement gt       lt dependencies gt         lt dependency gt           lt groupId gt org springframework lt  groupId gt           lt artifactId gt spring-core lt  artifactId gt           lt version gt   spring version  lt  version gt           lt scope gt runtime lt  scope gt         lt  dependency gt          lots of others          lt  dependencies gt     lt  dependencyManagement gt    Child pom      lt parent gt       lt groupId gt com sw system4 lt  groupId gt       lt artifactId gt system4-parent lt  artifactId gt       lt version gt 0 0 1-SNAPSHOT lt  version gt     lt  parent gt     lt artifactId gt system4-data lt  artifactId gt     lt dependencies gt       lt dependency gt           lt groupId gt org springframework lt  groupId gt           lt artifactId gt spring-core lt  artifactId gt           lt scope gt runtime lt  scope gt       lt  dependency gt          lots of others       lt  dependencies gt    When I build  I get the following output    ERROR  The build could not read 1 project - gt   Help 1   ERROR   ERROR    The project com sw system4 system4-data 0 0 1-SNAPSHOT  C  work eclips e workspaces systemiv system4-parent system4-data pom xml  has 8 errors   ERROR       dependencies dependency version  for org springframework spring-cor e jar is missing    line 16  column 16      others omitted for clarity       I dont understand why it doesn t even attempt to compile   Ive tried removing the runtime scope from parent and child  and it makes no difference   Please help

User · Answer

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

User · Answer

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

User · Answer

I had the same error  I forgot to add the child dependencies in the  lt dependencyManagement gt   For example in the parent pom    lt dependencyManagement gt       lt dependencies gt           lt dependency gt               lt groupId gt com sw system4 lt  groupId gt               lt artifactId gt system4-data lt  artifactId gt  lt  -- child artifact id -- gt               lt version gt   project version  lt  version gt           lt dependency gt            lt  -- add all third party libraries     -- gt        lt  dependencies gt   lt dependencyManagement gt

User · Answer

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

User · Answer

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

User · Answer

A couple things I think you could try    Put the literal value of the version in the child pom   lt dependency gt     lt groupId gt org springframework lt  groupId gt     lt artifactId gt spring-core lt  artifactId gt     lt version gt 3 2 3 RELEASE lt  version gt     lt scope gt runtime lt  scope gt   lt  dependency gt   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   lt parent gt     lt groupId gt com mycompany app lt  groupId gt     lt artifactId gt my-app lt  artifactId gt     lt version gt 1 lt  version gt    lt relativePath gt    parent pom xml lt  relativePath gt   lt  parent gt     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

User · Answer

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  lt scope gt runtime lt  scope gt  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       lt parent gt       lt groupId gt com sw system4 lt  groupId gt       lt artifactId gt system4-parent lt  artifactId gt       lt version gt 0 0 1-SNAPSHOT lt  version gt     lt  parent gt    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

User · Answer

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     lt parent gt       lt groupId gt com sw system4 lt  groupId gt       lt artifactId gt system4-parent lt  artifactId gt       lt version gt   system4 version  lt  version gt       lt relativePath gt    pom xml lt  relativePath gt    lt  -- this must match your parent pom location -- gt   lt  parent gt

User · Answer

You must build parent module before doing child module

[java] 'dependencies.dependency.version' is missing error, but version is managed in parent

Examples related to java

Examples related to maven-3