The POM for is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details

I used to get this maven warning all the time for a project with maven 3.3.3

[WARNING] The POM for module.jar:1.5.0-20151020.091156-5 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details

I have a top level project Parent1 and Parent2.

Here I will explain the modules I have and how i tried to use them:

Parent1
com.tak:module: version
com.tak:module2:version

And module 2 created by me as another project

Parent2
com.common:module1:version
+com.common:module2:version

Whenever i changed module2 I used to do “mvn deploy” only on module2. I also had to sometimes do changes in the pom files of the parent projects of module2. And since moving to maven 3 i started to receive this warning. I checked the poms downloaded into my local repository and found out that the parent poms were quite old. Then I tried to deploy all the parents to the repository. Once I did that the error was resolved. May be this helps someone else.

2 thoughts on “The POM for is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details”

  1. Thanks for the article, but the way it is written, it is unnecessarily hard to understand. To simplify it, I suggest it be divided into four sections:
    (1) The problem statement (error).
    (2) Likely cause (old POMs).
    (3) Solution (updated POMs).
    This would massively simplify the article and make it easier to understand. The fourth & final section would be (4) Your setup. Which, for most users is not relevant because there are many different possible setups that can cause the same error. You would only add this section as a convenience to readers who want to delve deeper into the problem by comparing & contrasting their setup with yours. AND, in the current state, it is extremely hard to understand your setup. You are saying “Parent1” & “Parent2”, but I think you really mean “Project1/parent” & “Project2/parent” (for your case). To clarify this to the reader, I would maybe show some extra information like a tree structure of the POMs, or a little bit of the POMs that are relevant, or even the reactor(s) summary to show the relationship (you can get this with mvn clean if if you can’t build your project).

    Reply

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.