The POM for <name> is invalid, transitive dependencies (if any) will not be available

Solution 1:

One reason for this is when you rely on a project for which the parent pom is outdated. This often happens if you are updating the parent pom without installing/deploying it.

To see if this is the case, just run with mvn dependency:tree -X and search for the exact error. It will mention it misses things you know are in the parent pom, not in the artifact you depend on (e.g. a jar version).

The fix is pretty simple: install the parent pom using mvn install -N and re-try

Solution 2:

I had a similar error, In my case remove all related artifacts from the local repository was the workaround...

Solution 3:

Remove repository folder inside .m2 and launch mvn clean install.

Keep us informed by the result and Good luck

Solution 4:

Assuming that the client and server projects poms are invalid because of unsatisfied expansion, then the following should work... If the "client" and "server" projects have their dependency on "Framework" defined in a tag, then you can first install "Framework" using the -N option. First, cd to the Framework directory, then: mvn -N clean install The -N option tells maven to only install the root pom in the local repo and to skip the child modules. Now cd to your child project and rerun your install command in your client or server module. The client or server build should now find the parent pom with the properties that it needs in the local repo.

You can get the same effect by making an explicit file path reference using the relativePath tag in your child pom's parent tag:

<parent>
  <relativePath>../my-parent</relativePath>
</parent>