JBoss Maven Repositories
External
- JBoss Enterprise Maven Repository https://access.redhat.com/maven-repository
Internal
Overview
JBoss EAP comes with a publicly accessible on-line Maven repository that contains many of the dependencies Java EE developers need to build applications on JBoss EAP. Maven repository archives are also being offered for each EAP release on the JBoss Customer Portal and can be installed locally.
Repositories
RedHat General Availability Maven Repository
This repository contains supported artifacts. It is also used to publish BOMs.
settings.xml declaration:
<settings ...>
<profiles>
<profile>
<id>RedHat General Availability Repository</id>
<repositories>
<repository>
<id>redhat-ga</id>
<name>redhat-ga</name>
<url>https://maven.repository.redhat.com/ga/</url>
<layout>default</layout>
<releases>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
</releases>
<snapshots>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
</snapshots>
</repository>
</repositories>
</profile>
</profiles>
...
<activeProfiles>
<activeProfile>RedHat General Availability Repository</activeProfile>
</activeProfiles>
</settings>
JBoss EAP BOMs
JBoss BOMs
There is a dependency management BOM included in the JBoss EAP Maven repository, which specifies all the supported JBoss EAP binary artifacts. This BOM can be used in a build to ensure that Maven will prioritize supported JBoss EAP dependencies for all direct and transitive dependencies in the build. In other words, transitive dependencies will be managed to the correct supported dependency version where applicable. The version of this BOM matches the version of the JBoss EAP release.
<dependency> <groupId>org.jboss.bom</groupId> <artifactId>eap-runtime-artifacts</artifactId> <version>7.0.0.GA</version> <type>pom</type> <scope>import</scope> </dependency>
eap6-supported-artifacts
The jboss-javaee-7.0 BOM contains the Java EE Specification API JARs used by JBoss EAP.
To use this BOM in a project, add a dependency for the GAV that contains the version of the JSP and Servlet API JARs needed to build and deploy the application.
The following example uses the 1.0.3.Final-redhat-1 version of the jboss-javaee-7.0 BOM.
<dependencyManagement> <dependencies> <dependency> <groupId>org.jboss.spec</groupId> <artifactId>jboss-javaee-7.0</artifactId> <version>1.0.3.Final-redhat-1</version> <type>pom</type> <scope>import</scope> </dependency> ... </dependencies> </dependencyManagement>
<dependencies> <dependency> <groupId>org.jboss.spec.javax.servlet</groupId> <artifactId>jboss-servlet-api_3.1_spec</artifactId> <scope>provided</scope> </dependency> ... </dependencies>
Organizatorium
Repositories from .m2/settings.xml:
JBoss Public Maven Repository: https://repository.jboss.org/nexus/content/groups/public-jboss
http://repository.jboss.org/nexus/content/groups/public/
This is the repository where some of the patched JARs from EAPs are found: https://maven.repository.redhat.com/nexus/content/groups/product-techpreview/
To find whether a EAP deployment has been patched and where the patches are, see EAP Patching.
To Migrate [JBossAndMaven].
<repository> <id>jboss-public-repository-group</id> <name>JBoss Public Maven Repository Group</name> <url>https://repository.jboss.org/nexus/content/groups/public-jboss/</url> <layout>default</layout> </repository>
<repository> <id>redhat-ga</id> <name>redhat-ga</name> <url>https://maven.repository.redhat.com/ga/</url> <layout>default</layout> <releases> <enabled>true</enabled> <updatePolicy>never</updatePolicy> </releases> <snapshots> <enabled>true</enabled> <updatePolicy>never</updatePolicy> </snapshots> </repository>
BOMs
https://github.com/jboss-developer/jboss-eap-boms
See branches.