I added it to my pom the following dependency node from mvnrepository

<dependency>
  <groupId>.jboss.gravia</groupId>
  <artifactId>gravia-container-wildfly-extension</artifactId>
  <version>1.1.3</version>
  <scope>provided</scope>
</dependency>

I don't know how to set that up so that maven will build because it kicks an error saying it can't find the artifact in the jboss-ga-repository

how can I fix this?

I added it to my pom the following dependency node from mvnrepository

<dependency>
  <groupId>.jboss.gravia</groupId>
  <artifactId>gravia-container-wildfly-extension</artifactId>
  <version>1.1.3</version>
  <scope>provided</scope>
</dependency>

I don't know how to set that up so that maven will build because it kicks an error saying it can't find the artifact in the jboss-ga-repository

how can I fix this?

• java
• maven

Share Improve this question Follow asked Mar 20 at 13:09 dracadraca 1,41955 gold badges2020 silver badges3838 bronze badges 4

• 1 Did you add JBoss GA Repository to the pom.xml file? Could you maybe also add the part of the pom.xml where the JBoss GA Repository is added? – AztecCodes Commented Mar 20 at 13:15
• or the entry in settings.xml. – aled Commented Mar 20 at 13:33
• Idk why people voted to close this question with "needs debugging details". I tried to add the dependency and I also get the same error of OP. I'm genuinely interested in the reason. – dani-vta Commented Mar 20 at 14:07
• @AztecCodes yes, I had added the JBoss GA Repository, but that repo didn't contain the jar, I had to add the repo mentioned at the bottom. But the question is, shouldnt the repo be in the JBoss GA repo since that was listed in the repositories section with 6 others? – draca Commented Mar 21 at 11:55

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 3

I tried it myself and got the same error.

I was able to fix it after reading the notes on the page https://mvnrepository/artifact/.jboss.gravia/gravia-container-wildfly-extension/1.1.3, which mention that the artifact is hosted on https://repository.jboss./nexus/content/repositories/releases/.

To resolve the issue, you need to add the corresponding repository to your pom.xml:

<repositories>
    <repository>
        <id>jboss-releases</id>
        <url>https://repository.jboss./nexus/content/repositories/releases/</url>
        <releases>
            <enabled>true</enabled>
        </releases>
        <snapshots>
            <enabled>false</enabled>
        </snapshots>
    </repository>
</repositories>

After adding this, try running mvn clean install again, and it should work.