JBoss Enterprise Maven Repository available with the Enterprise Application Platform 6 Beta!

Since March 15th of the JBoss Enterprise Application Platform (EAP) is available in the Version 6 Beta. The EAP is based on the Java EE 6 certified JBoss AS 7.1 community release, which impresses not only by the fast start-up time and low memory consumption but also by its new clean architecture.

At the moment, the EAP 6 Beta is pretty close to the community version. It includes a few critical bug fixes and some brandings. The differences will be larger with the on going quality assurance and maintenance phase.

A magnificent enhancement to the previous version is, that the EAP 6 ships with a Maven repository, which includes all EAP-related Maven artifacts. The missing maven repository was a big disadvantage of previous EAP versions. The required Maven artifacts had to be manually deployed from the EAP distribution into your own local Maven repository or into your enterprise Maven repository like Nexus or Artifactory.

In contrast to the public JBoss community Maven repository, the EAP 6 Maven repository is available as complete zip file download at the Redhat Customer Portal. Thus, the repository can be easily integrated into your own enterprise Maven repository or, to get started quickly, as local file system repository.

If you are not using an own enterprise Maven repository, you need to configure your local maven configuration to make the repository available. The maven settings.xml configuration file is usually located in your home directory in the folder .m2.

<settings>
   ...
   <profiles>
      ...
      <profile>
         <id>jboss-eap-repository</id>
         <repositories>
            <repository>
               <id>jboss-eap-repository</id>
               <name>JBoss EAP Maven Repository</name>
               <url>file:///path/to/repo/jboss-eap-6.0-maven-repository</url>
               <layout>default</layout>
               <releases>
                  <enabled>true</enabled>
                  <updatePolicy>never</updatePolicy>
               </releases>
               <snapshots>
                  <enabled>false</enabled>
                  <updatePolicy>never</updatePolicy>
               </snapshots>
            </repository>
         </repositories>
           
        <pluginRepositories>
           <pluginRepository>
              <id>jboss-eap-repository-group</id>
              <name>JBoss EAP Maven Repository</name>
              <url>file:///path/to/repo/jboss-eap-6.0-maven-repository</url>
              <layout>default</layout>
              <releases>
                 <enabled>true</enabled>
                 <updatePolicy>never</updatePolicy>
              </releases>
              <snapshots>
                 <enabled>false</enabled>
                 <updatePolicy>never</updatePolicy>
              </snapshots>
           </pluginRepository>
        </pluginRepositories>
     </profile>
  </profiles>

  <activeProfiles>
     <activeProfile>jboss-eap-repository</activeProfile>
  </activeProfiles>
   ...
</settings>

Using this configuration the EAP-releated Maven artifacts are available as local file-based Maven repository.

If your project follows the best practices concerning the usage of the Maven dependency management, you can now easily migrate from JBoss AS 7 to EAP 6: This is done by adding the Version numbers suffix –redhat-1 to the EAP-related maven dependencies. Below an example for the Hibernate core library and the JBoss webservice native stack libraries:

<dependencyManagement>
   <dependencies>
      ...
      <dependency>
         <groupId>org.hibernate</groupId>
         <artifactId>hibernate-core</artifactId>
         <version>4.0.2.Final-redhat-1</version>
      </dependency>

      <dependency>
         <groupId>org.jboss.ws.native</groupId>
         <artifactId>jbossws-native</artifactId>
         <version>4.0.1.GA-redhat-1</version>
      </dependency>
      ...
   </dependencies>
</dependencyManagement>

The provided EAP enterprise Maven repository makes it not only much easier to migrate from the community version to the EAP, it make is also easier to upgrade to new EAP versions.

We are looking forward to the final release of the EAP 6. But, it will probable take some time for the QA to polish the distribution.

11 thoughts on “JBoss Enterprise Maven Repository available with the Enterprise Application Platform 6 Beta!

  1. Hello there, just became aware of your blog through Google, and found that it’s really informative. Im gonna watch out for brussels. I will appreciate if you continue this in future. Numerous people will be benefited from your writing. Cheers!

  2. Overheating happens when business tools gets previous and electronic parts
    crack down. No estate is the same, so contemplate the
    existing and the long run of any land progress.
    A person of the extravagant issues to do with modest microwave
    is reheating coffee without the need of mess at a preferred
    temperature.

  3. You can mix in &frac12 of a cup of salt and &frac12 of a cup of baking soda and pour them in the drain.
    1 of its most effective variations is the Bosch Pro Energy Cylinder Vacuum Cleaner, which has classic, high stop sections to truly give you a
    superior clean up. One of the extravagant points to do with
    compact microwave is reheating espresso without mess at a
    ideal temperature.

  4. Since a few weeks there is as well an online repository available.

    At this time, the key URL is: http://maven.repository.redhat.com/techpreview/all/

    “This Repository is provided as a Technology Preview in order to gain wider exposure and customer feedback. This means that it is not fully supported and not recommended for business-critical use. Red Hat reserves the right to modify the behavior and content of this repository or remove it completely with little or no notice.”

  5. Oh my goodness! an incredible article dude.
    Thanks Nonetheless I’m experiencing situation with ur rss . Don’t know why Unable to subscribe to it. Is there anyone getting identical rss downside? Anyone who is aware of kindly respond. Thnkx

Comments are closed.