Why do I get invalid pom due to missing dependency.version although the version is managed?

Question

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?

You will have to post your pom files here so we can see what's wrong. — maba, Jul 05 '12 at 07:52
Ok, will add pom's in a couple of minutes. I though it might be some conceptual mistake in the inheritance model or something like that. — abaelter, Jul 05 '12 at 07:58

score 3 · Accepted Answer · answered Jul 05 '12 at 08:17

3

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

answered Jul 05 '12 at 08:17

abaelter

887
1
11
22

2

A relative path should usually not been set if using a parent pom. – khmarbaise Jul 05 '12 at 08:19
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. – abaelter Jul 05 '12 at 10:51
I have however seen that some plugins don't support flat directory structure. But that's not the issue here. – abaelter Jul 05 '12 at 10:52

Why do I get invalid pom due to missing dependency.version although the version is managed?

1 Answers1

Linked