5

I have case that looks like this:

super

  • dependency manangement of thrid-party

parent-pom

  • child of super

projectA

  • child of parent-pom
  • dependency to third-party

projectB

  • child of parent-pom
  • dependency to projectA

projectA builds just fine, but when I try to compile projectB I get:

[WARNING] The POM for [projectA] is invalid, transitive dependencies (if any) will not be available: 1 problems were encountered while building the effective model for [projectA]

[ERROR] 'dependencies.dependency.version' for thrid-party.jar is missing. @

Any idea why?

Improve this question
8
  • Did you indicate the thrid-party.jar version in the POM? Commented Jul 5, 2012 at 7:36
  • In dependency management yes, in projectA no. Commented Jul 5, 2012 at 7:39
  • So, do it and let's see. Commented Jul 5, 2012 at 7:46
  • No, I want the version of third-party to be managed Commented Jul 5, 2012 at 7:48
  • 1
    Please, show us the Super and projectA POM files. Commented Jul 5, 2012 at 7:51

1 Answer 1

Reset to default
3

You need to install super to you local repo, just having relativePath set is not enough for this case.

Improve this answer
Sign up to request clarification or add additional context in comments.

3 Comments

A relative path should usually not been set if using a parent pom.
I can't find any information that supports this statement. From what I can find relativePath is just fine if you want a flat directory structure.
I have however seen that some plugins don't support flat directory structure. But that's not the issue here.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.