Bug 1021692

Summary: Wrong versios on github sources
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Rafael Benevides <benevides>
Component: Maven RepositoryAssignee: Paul Gier <pgier>
Status: CLOSED CURRENTRELEASE QA Contact: Nikoleta Hlavickova <nziakova>
Severity: high Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.2.0CC: bsutter
Target Milestone: ---   
Target Release: EAP 6.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-21 20:50:53 UTC Type: Task
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Rafael Benevides 2013-10-21 19:53:41 UTC 
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.
Comment 1 Paul Gier 2013-10-21 20:39:35 UTC 
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.
Comment 2 Paul Gier 2013-10-21 20:50:53 UTC 
The tag is now available with the correct component versions.