Ria tells programmers what she discovered and how she solved the case of the missing POM on Maven.
[WARNING] The POM for com.oracle:ojdbc:jar:10.1.0.4 is missing, no dependency information available
I got this warning while running mvn clean package. At first I tried the steps from an answer on this StackOverflow thread, which describes ways on how to deal with the problem when you’re on Springsource Tool Suite (and maybe Eclipse as well) with Maven integration.
At first I thought my STS was trolling me again (cause it usually does), but then apparently it was my Archiva repository with the problem all along.
I checked out the artifact on my internal Archiva site and apparently my ojdbc 10.1.0.4′s POM wasn’t there (note that only the Jar was available for download). I facepalmed when I reread the warning and it did say that the POM was missing after all.
Okay, now if you find yourself in the same situation, go to the artifact page, download the Jar file, and take note of all the artifact’s information. Usually copy-pasting the POM Snippet into gedit or notepad should be enough.
While logged in, delete the artifact, then re-upload the artifact, making sure you tick the checkbox for “Generate Maven 2 POM“.
Afterwards, check the artifact page once more and you should see something like this.
If you see the POM available for download, you should be able to run
mvn clean package without the annoying warning above popping up.
If it still doesn’t work, you can also try deleting the artifact’s folder from your local repository before trying again.