[
http://jira.jboss.com/jira/browse/JBREM-129?page=all ]
Ron Sigal resolved JBREM-129.
-----------------------------
Resolution: Won't Fix
Assignee: (was: Tom Elrod)
The premise of this issue, that oswego-concurrent jar is only being used by test code, is
no longer true: org.jboss.remoting.Client uses org.jboss.util.id.GUID (from the
common-core project) for its sessionId, and GUID uses org.jboss.util.id.UID, which uses an
EDU.oswego.cs.dl.util.concurrent.SynchronizedLong.
remove oswego-concurrent lib
----------------------------
Key: JBREM-129
URL:
http://jira.jboss.com/jira/browse/JBREM-129
Project: JBoss Remoting
Issue Type: Task
Components: general
Affects Versions: 1.2.0 final
Reporter: Tom Elrod
Priority: Optional
Fix For: 2.4.0.CR1 (Pinto)
The oswego-concurrent jar is only being used by test code. If change this code to not
use concurrent then can remove jar from remoting project (and distribution).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira