I\'m facing a bunch of warnings like \"The POM for ... is missing, no dependency information available\" while building my maven java project.
The artifacts are stored
Sometimes Releases are Disposable
As the article above describes, depending on your business, you may not need to store old releases on your own repository. I'm included in this scenario.
In order to maintain, for example, only the 2 last releases from my component projects, some steps should be followed in order to avoid the maven [WARNING] messages:
You should add a task to your repository to maintain the only n release itens. This can be done by:
The "ace in the hole" for this question is to rebuild the maven metadata files (maven-metadata.xml), once they were going to maintain the old releases information until the time they are going to be rebuild. This can be done by:
Now, the local repository need to know that metadata files were updated. This can be done by the parameter:
mvn -U:
-U,--update-snapshots Forces a check for updated releases and snapshots on remote
For example:
mvn -U clean package
Check your settings.xml
, i.e. exported as such in bash:
export MVN_SETTINGS=~/.m2/settings.xml
This warning typically appears when you can't download the dependencies from the internet.