• There is no SwitchYard or FSW application BOM today.  There is the integration platform BOM, which would have to be imported into any application BOM anyway, so users can always import that via depenencyManagement for now.
• Adding an application BOM for SY is a good thing to do.  If we must have this for FSW 6.1, then it needs to be in the PRD/ERD so that we can reflect it in the product scheduling.
• I'm not sure about anyone else, but I was never told that a BOM was required in order to work around a broken dependency chain in our enterprise Maven repository.

Hi,

Search for "${version.sun.jaxb}" :
http://maven.repository.redhat.com/techpreview/all/org/jboss/component/management/jboss-component-version-master/6.1.0-redhat-1/jboss-component-version-master-6.1.0-redhat-1.pom
http://maven.repository.redhat.com/techpreview/all/org/jboss/component/management/jboss-dependency-management-build/6.1.0-redhat-1/jboss-dependency-management-build-6.1.0-redhat-1.pom

Right.  But, the EAP 6.1.1 BOM is version 6.1.1.Final-redhat-61:

 http://maven.repository.redhat.com/techpreview/all/org/jboss/component/management/jboss-component-version-master/6.1.1.Final-redhat-61/jboss-component-version-master-6.1.1.Final-redhat-61.pom

and for EAP 6.1.1, the version is matched with the available artifact [*].
But, if you don't use the correct IP and EAP BOM's then your build is broken,
as per the original bug report.

Thanks,

J

[*] Note, that there are other bugs in the EAP 6.1.1 BOM's, but those were
fixed up in the IP BOM for the artifacts that we needed to build FSW, DV,
BPMS, BRMS.
--
Red Hat
Newcastle upon Tyne