Details
Bug
Closed
Major
Description
As from version 4.0.0, Oracle changed the Vendor name of it's JVM, Oracle JRockit. Until this point the Vendor name was "BEA" - this is for what the current 1.3.1 XStream implementation looks for while checking JVM vendors. Oracle changed this in this release to "Oracle" which now causes to fail the vendor check in XStream.
Issue Links
Activity
Thank you for the information but I think XStream itself detects the JVM Vendor information and for this reason Hudson gives me an error message that it's not compatible with my JVM.
I think the fastest and most error-proof solution will be to revert back the Oracle JVM to 3.x where the Vendor information was set to "BEA".
Also I'll give feedback to the guys developing and supporting Hudson to be aware of this issue.
Best regards,
Sandor Nemeth
Sandor Nemeth
added a comment - Thank you for the information but I think XStream itself detects the JVM Vendor information and for this reason Hudson gives me an error message that it's not compatible with my JVM.
I think the fastest and most error-proof solution will be to revert back the Oracle JVM to 3.x where the Vendor information was set to "BEA".
Also I'll give feedback to the guys developing and supporting Hudson to be aware of this issue.
Best regards,
Sandor Nemeth patch to also accept Oracle as former BEA
Markus Helbig
added a comment - patch to also accept Oracle as former BEA I guess any JVM with Oracle as vendor is now appropriate for Sun14ReflectionProvider 
Jörg Schaible
added a comment - I guess any JVM with Oracle as vendor is now appropriate for Sun14ReflectionProvider 
Again, thanks for heads-up. For the time being you can initialize XStream with a Sun14ReflectionProvider to make full advantage of XStream's enhanced mode unless XStream itself detects JRockit again.