This error is raised when your POM inherits from a parent POM or imports another POM that Maven could not download. Possible causes for this error are:

  1. You are referring to a non-existing POM, e.g. by means of a typo in its group id, artifact id or version.
  2. You intent to use a parent POM from the local filesystem but Maven didn't use that. Please verify that the <relativePath> element in the child is properly set and that the POM at that location has actually the version you want to use.
  3. Your POM/settings is missing the required <repository> to download the POM. Note that <pluginRepository> declarations are not considered when looking for the POM, only <repositories> are searched for POMs.
  4. The repository you have configured requires authentication and Maven failed to provide the correct credentials to the server. In this case, make sure your ${user.home}/.m2/settings.xml contains a <server> declaration whose <id> matches the <id> of the remote repository to use. See the Maven Settings Reference for more details.
  5. Maven failed to save the files to your local repository, see LocalRepositoryNotAccessibleException for more details.
  6. The repository you have configured is disabled for the specific version of the POM you requested. For instance, if you want to use a SNAPSHOT version of a POM, make sure you don't have <snapshots><enabled>false</enabled></snapshots> configured. Likewise, in order to resolve a released version of the POM, the remote repository should not be configured with <releases><enabled>false</enabled></releases>. See the POM Reference for more information on repository configuration.

In those cases, check your POM and/or settings for the proper contents. If you configured the repository in a profile of your settings.xml, also verify that this profile gets actually activated, e.g. via invoking mvn help:active-profiles.

For the special case of a network-related problem during download of the POM, you can also consult the following articles:

  • No labels