Description of problem: Versions on Github repo: https://github.com/jboss-developer/jboss-eap-boms/tree/6.2.x differs from maven repository. Version-Release number of selected component (if applicable): 6.2.0.Beta Steps to Reproduce: 1. Open http://maven.repository.redhat.com/techpreview/eap6/6.2.0.Beta/maven-repository/org/jboss/bom/eap/jboss-eap-bom-parent/6.2.0.Beta1/jboss-eap-bom-parent-6.2.0.Beta1.pom 2. Open https://github.com/jboss-developer/jboss-eap-boms/blob/6.2.x/pom.xml 3. Realize that version.org.jboss.jbossts.jbossjts property uses 4.17.12.Final-redhat-1 on github while it was released with 4.17.10.Final-redhat-2 4. Picketlinnk uses 2.1.9.Final-redhat-1 but it was released with 2.1.6.3.Final-redhat-2 Additional info: We need to tag the commit that was used on the Release.
Here is the Beta tag: https://github.com/jboss-developer/jboss-eap-boms/releases/tag/6.2.0.Beta1 It has: jbossts - 4.17.10.Final-redhat-2 picketlink - 2.1.6.3.Final-redhat-2 The versions of both of these were updated in the 6.2.x branch for the post-Beta ER6 release.
The tag is now available with the correct component versions.