We Are Going To Discuss About “The POM for … is missing, no dependency information available” even though it exists in Maven Repository. So lets Start this Java Article.
“The POM for … is missing, no dependency information available” even though it exists in Maven Repository
- “The POM for … is missing, no dependency information available” even though it exists in Maven Repository
I had a similar problem quite recently. In my case:
I downloaded an artifact from some less popular Maven repo
This repo dissappeared over this year
Now builds fail, even if I have this artifact and its pom.xml in my local repo - “The POM for … is missing, no dependency information available” even though it exists in Maven Repository
I had a similar problem quite recently. In my case:
I downloaded an artifact from some less popular Maven repo
This repo dissappeared over this year
Now builds fail, even if I have this artifact and its pom.xml in my local repo
Solution 1
Read carefully the warning message :
The POM for org.raml:jaxrs-code-generator:jar:2.0.0 is missing, no
dependency information available
The problem is not the jar, but the pom.xml that is missing.
The pom.xml lists the required dependencies for this jar that Maven will pull during the build and overall the packaging of your application.
So, you may really need it.
Note that this problem may of course occur for other Maven dependencies and the ideas to solve that is always the same.
The Mule website documents very well that in addition to some information related to.
How to solve ?
1) Quick workaround : looking for in the internet the pom.xml
of the artifact
Googling the artifact id, the group id and its version gives generally
interesting results : maven repository links to download it.
In the case of the org.raml:jaxrs-code-generator:jar:2.0.0
dependency, you can download the pom.xml
from the Maven mule repository :
2) Clean workaround for a single Maven project : adding the repository declaration in your pom.
In your case, add the Maven mule repositories :
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
...
<repositories>
<repository>
<id>mulesoft-releases</id>
<name>MuleSoft Repository</name>
<url>http://repository.mulesoft.org/releases/</url>
<layout>default</layout>
</repository>
<repository>
<id>mulesoft-snapshots</id>
<name>MuleSoft Snapshot Repository</name>
<url>http://repository.mulesoft.org/snapshots/</url>
<layout>default</layout>
</repository>
</repositories>
...
</project>
3) Clean workaround for any Maven projects : add the repository declaration in your settings.xml
<profile>
<repositories>
...
<repository>
<id>mulesoft-releases</id>
<name>MuleSoft Repository</name>
<url>http://repository.mulesoft.org/releases/</url>
<layout>default</layout>
</repository>
<repository>
<id>mulesoft-snapshots</id>
<name>MuleSoft Snapshot Repository</name>
<url>http://repository.mulesoft.org/snapshots/</url>
<layout>default</layout>
</repository>
...
</repositories>
</profile>
Note that in some rare cases, the pom.xml
declaring the dependencies is nowhere. So, you have to identify yourself whether the artifact requires dependencies.
Original Author davidxxx Of This Content
Solution 2
I had a similar problem quite recently. In my case:
-
I downloaded an artifact from some less popular Maven repo
-
This repo dissappeared over this year
-
Now builds fail, even if I have this artifact and its pom.xml in my local repo
Workaround:
delete _remote.repositories file in your local repo, where this artifact resides. Now the project builds.
Original Author bleju Of This Content
Solution 3
You will need to add external Repository to your pom, since this is using Mulsoft-Release
repository not Maven Central
<project>
...
<repositories>
<repository>
<id>mulesoft-releases</id>
<name>MuleSoft Repository</name>
<url>http://repository.mulesoft.org/releases/</url>
<layout>default</layout>
</repository>
</repositories>
...
</project>
Original Author XPLOT1ON Of This Content
Solution 4
If the POM missing warning is of project’s self module, the reason is that you are trying to mistakenly build from a sub-module directory. You need to run the build and install command from root directory of the project.
Original Author Sameer Sah Of This Content
Conclusion
So This is all About This Tutorial. Hope This Tutorial Helped You. Thank You.