Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 1.4.4
-
Fix Version/s: None
-
Component/s: Core
-
Labels:None
Description
Here at Jenkins we use XStream in a highly multi-threaded environment, and we found that the use of concurrency-safe data structure greatly reduces the lock contention.
I understand that historically XStream supported JDK 1.4, but now that it is 2013, where JDK 1.4 has EOLed 7 years ago, and JDK8 is on the horizon, I think it's OK to start depending on JDK 1.5 features.
(XStream itself removes deplicated APIs far more quickly than JDK does, so folks who have been using XStream long enough back from Java 1.4 days won't be able to use newer versions all that easily anyway!)
Activity
I'm OK with some patches making into releases before others. IOW, so long as eventually I can switch back to the official version, I'm happy to continue using my locally patched version for a while longer.
Kohsuke Kawaguchi
added a comment - I'm OK with some patches making into releases before others. IOW, so long as eventually I can switch back to the official version, I'm happy to continue using my locally patched version for a while longer. Reopen to attach patch that was attached at the wrong issue.
Jörg Schaible
added a comment - Reopen to attach patch that was attached at the wrong issue. 
As you can see in the announcement for 1.4.4, next major version 1.5 will depend directly on Java 6. It depends now a bit, how fast you'll need most of your stuff, because that major version will also require some internal code clean-up. Otherwise we can schedule some stuff for a 1.4.5 release, but that'll be 1.4 compatible