Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1065525 - [GSS] (6.3.0) Upgrade jboss-ejb-client 1.0.24.Final-redhat-1 to jboss-ejb-client 1.0.25.Final-redhat-1
Summary: [GSS] (6.3.0) Upgrade jboss-ejb-client 1.0.24.Final-redhat-1 to jboss-ejb-cli...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB
Version: 6.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: DR1
: EAP 6.3.0
Assignee: Lin Gao
QA Contact: Michal Karm Babacek
Russell Dickenson
URL:
Whiteboard:
Depends On: 1045105
Blocks: 1065523
TreeView+ depends on / blocked
 
Reported: 2014-02-14 20:53 UTC by Derek Horton
Modified: 2014-06-28 15:25 UTC (History)
7 users (show)

Doc Type: Bug Fix
Doc Text:
Clone Of: 1065523
Environment:
Last Closed: 2014-06-28 15:25:57 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Bugzilla 1067515 None None None Never
Red Hat Bugzilla 1067516 None None None Never
Red Hat Bugzilla 1067518 None None None Never

Internal Links: 1067515 1067516 1067518

Description Derek Horton 2014-02-14 20:53:09 UTC
Description of problem:

[GSS] (6.3.0) Upgrade jboss-ejb-client

Comment 1 Derek Horton 2014-02-14 20:55:46 UTC
Need to include a fix for bz-1045105 in 6.3.0

https://bugzilla.redhat.com/show_bug.cgi?id=1045105

Comment 2 baranowb 2014-02-17 07:00:50 UTC
1.0.25.Final is not out, there is one issue still up: https://issues.jboss.org/browse/EJBCLIENT-94

Comment 3 Lin Gao 2014-02-20 14:58:03 UTC
1.0.25.Final is out: https://github.com/jbossas/jboss-ejb-client/tree/1.0.25.Final

Start prod rebuilding.

Comment 4 Michal Karm Babacek 2014-02-28 18:07:50 UTC
Component upgraded.


Note You need to log in before you can comment on or make changes to this bug.