The POM for is missing no dependency information available even though it exists in Maven Repository

Question

Problem   A dependency will not download even though I copied it from the Maven Repository   When I hover over the dependency in Eclipse  it warns   Maven Missing artifact org raml jaxrs-code-generator jar 2 0 0    When I try mvn install or mvn compile it warns    WARNING  The POM for org raml jaxrs-code-generator jar 2 0 0 is missing  no dependency information available    Tried    Downloading the jar into the    m2 repository org raml jaxrs-code-generator 2 0 0 folder  then refreshing in the editor    When I install or compile it seems to ignore it   Running mvn -U    Same as with install or compile     In-depth        lt dependency gt           lt groupId gt org raml lt  groupId gt           lt artifactId gt jaxrs-code-generator lt  artifactId gt           lt version gt 2 0 0 lt  version gt       lt  dependency gt     The dependency exists in the Maven Repository  the version is also correct   Using Eclipse EE Neon 4 6 3  Apache Maven 3 3 9  Java 1 8 0 121  I have no settings xml in the    m2 folder  I don t use any other repositories  local or otherwise

User · Accepted Answer

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    https   repository mulesoft org nexus content repositories releases org raml jaxrs-code-generator 2 0 0   2  Clean workaround for a single Maven project   adding the repository declaration in your pom       In your case  add the Maven mule repositories     lt  xml version  1 0  encoding  UTF-8   gt   lt 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  gt       lt modelVersion gt 4 0 0 lt  modelVersion gt               lt repositories gt           lt repository gt               lt id gt mulesoft-releases lt  id gt               lt name gt MuleSoft Repository lt  name gt               lt url gt http   repository mulesoft org releases  lt  url gt               lt layout gt default lt  layout gt           lt  repository gt           lt repository gt               lt id gt mulesoft-snapshots lt  id gt               lt name gt MuleSoft Snapshot Repository lt  name gt               lt url gt http   repository mulesoft org snapshots  lt  url gt               lt layout gt default lt  layout gt           lt  repository gt       lt  repositories gt           lt  project gt    3  Clean workaround for any Maven projects   add the repository declaration in your settings xml    lt profile gt       lt repositories gt               lt repository gt         lt id gt mulesoft-releases lt  id gt         lt name gt MuleSoft Repository lt  name gt         lt url gt http   repository mulesoft org releases  lt  url gt         lt layout gt default lt  layout gt       lt  repository gt       lt repository gt         lt id gt mulesoft-snapshots lt  id gt         lt name gt MuleSoft Snapshot Repository lt  name gt         lt url gt http   repository mulesoft org snapshots  lt  url gt         lt layout gt default lt  layout gt       lt  repository gt              lt  repositories gt        lt  profile gt    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

User · Answer

In my case I was using Jade and I was using HTTP repository URL  Changing the Url to HTTPS worked for me

User · Answer

This is my solution  may be it can helps I use IntelliJ IDE  File -  Setting -  Maven -  Importing  change JDK for importer to 1 8  you can change to lower  higher

User · Answer

You will need to add external Repository to your pom  since this is using Mulsoft-Release repository not Maven Central   lt project gt              lt repositories gt           lt repository gt               lt id gt mulesoft-releases lt  id gt               lt name gt MuleSoft Repository lt  name gt               lt url gt http   repository mulesoft org releases  lt  url gt               lt layout gt default lt  layout gt           lt  repository gt       lt  repositories gt         lt  project gt    Dependency  Apache Maven - Setting up Multiple Repositories

User · Answer

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

User · Answer

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

User · Answer

In my case the reason was since the remote repo artifact  non-central  had dependencies from the Maven Central in the  pom file  and the older version of mvn  older than 3 6 0  was used  So  it tried to check the Maven Central artifacts mentioned in the remote repo s  pom for the specific artifact I ve added to my dependencies and faced the Maven Central http access issue behind the scenes  I believe the same as described there  Maven dependencies are failing with a 501 error - that is about using https access to Maven Central by default and prohibiting the http access   Using more recent Maven  from 3 1 to 3 6 0  made it use https to check Maven Central repo dependencies mentioned in the  pom files of the remote repositories and I no longer face the issue

[java] "The POM for ... is missing, no dependency information available" even though it exists in Maven Repository

How to solve ?

Examples related to java

Examples related to eclipse

Examples related to maven