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:
<relativePath>
element in the child is properly set and that the POM at that location has actually the version you want to use.<repository>
to download the POM. Note that <pluginRepository>
declarations are not considered when looking for the POM, only <repositories>
are searched for POMs.${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.<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: