Wednesday, May 13, 2015

JBoss BPM Suite Quick Guide: Changes You Need for Building Applications with JBoss EAP 6.4 Modules

This weeks tips & tricks article will dive in JBoss BRMS 6.1, which was released out into the wild on Thursday, April 16th.

This new release brings with it many notable improvements and features which we have highlighted previously.

While we were updating our various demo projects that we host on JBoss Demo Central, we noticed something worth mentioning when we were building our Cool Store web application code against the new JBoss EAP 6.4 that is the supported platform for JBoss BRMS 6.1.

Figure 1: JBoss BRMS modules in JBoss EAP 6.1.
If you were building your web applications against the modules installed by the JBoss BRMS or JBoss BPM Suite you would find them inside the JBoss EAP servers modules directory as shown in figure 1.

Note this figure 1 shows you the view for JBoss BRMS, but it also applies to JBoss BPM Suite where you will see a bpms folder instead of brms.

If you are looking to build your project with the same maven configuration on JBoss EAP 6.4 with JBoss BRMS 6.1 or JBoss BPM Suite 6.1, you will find that it does not work.

The reason becomes very clear when we compare figure 1 to the same modules directory on JBoss EAP 6.4 as shown in figure 2.

There are no layered modules installed for either product, so you will need to adjust your projects maven configuration to pull the dependencies from the centrally hosted JBoss Maven Repositories.

Figure 2: No modules in JBoss EAP 6.4.
How can we do that you ask?

Easy and it only takes a few minutes to update your Maven configuration.

Previously we covered the setup for you to adjust and pull dependencies on the product from the JBoss Maven repository, but for ease we will include the code you need for your configuration here:

<repositories>
 <repository>
  <id>jboss-maven-repository</id>
  <name>JBoss Maven Repository</name>
  <url>http://maven.repository.redhat.com/techpreview/all/</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-maven-repository</id>
  <name>JBoss Maven Repository</name>
  <url>http://maven.repository.redhat.com/techpreview/all/</url>
  <layout>default</layout>
  <releases>
   <enabled>true</enabled>
   <updatePolicy>never</updatePolicy>
  </releases>
  <snapshots>
   <enabled>false</enabled>
   <updatePolicy>never</updatePolicy>
  </snapshots>
 </pluginrepository>
</pluginrepositories>
Looking to Automate your business?

Once these repositories have been configured you can then pull in any dependencies you previously used from the modules directory in JBoss EAP 6.1 with the JBoss BRMS and JBoss BPM Suite products.

Feel free to comment if you have any questions around this topic.