User facing boms were created on master and 6.0.x (multiple commits - too many to mention here)

Version properties in the parent pom have been updated to the EAP pattern "version.{groupId}"
http://github.com/droolsjbpm/droolsjbpm-build-bootstrap/compare/cc2b9b7...68e0dd7

Blocked by
https://bugzilla.redhat.com/show_bug.cgi?id=993565

Designer fixed. Found similar trouble in droolsjbpm-integration.

First set of version that are not in sync between switchyard and droolsjbpm.

Droolsjbpm needs to upgrade
- batik from 1.6.-1 to 1.7
- commons-httpclient from 3.1 to 4.2.1
- commons-net from 2.0 to 2.2
- ftpserver-core from 1.0.4 to 1.0.6
- netty from 3.2.0.Final to 3.2.6.Final
- quartz from 1.6.1 to 1.8.5
- spring from 3.0.6.RELEASE to 3.0.7.RELEASE

SwitchYard needs to upgrade
- camel from 2.10.0 to 2.10.3
- cxf from 2.6.1 to 2.6.6
- hornetq from 2.3.0.CR1 to 2.3.1.Final
- ironjacamar from 1.0.15.Final to 1.0.17.Final
- jettison from 1.2 to 1.3.1
- junit from 4.10 to 4.11
- slf4j from 1.6.4 to 1.7.2
- weld from 1.1.10.Final to 1.1.13.Final
- xmlunit from 1.1 to 1.3


Probably:
- droolsjbpm and switchyard will probably need to upgrade antlr from 3.3 to 3.5.

Under investigation:
- SwitchYard uses deltaspike already. Drools still uses Seam 3 and Solder.
- SwitchYard uses maven-plugin 3.1. Drools uses 3.0.5 to be compatible with maven 3.0.
- SY uses xalan 2.7.1-1.jbossorg. Drools uses xalan 2.7.1.

Upgraded: commons-net, ftpserver-core, netty, quartz, spring
Not needed to be upgraded: commons-httpclient 3 (because httpcomponents client 4 uses different GAV's and java packages)
Still todo for droolsjbpm: batik, see https://bugzilla.redhat.com/show_bug.cgi?id=996210

Done on droolsjbpm master and 6.0.x

Here's the location of the new bom:
  https://github.com/jboss-integration/jboss-integration-platform-bom

The BOM is in place, the test suite now uses it also. VERIFIED with ER4.