Hi Michael,
Michael Bell wrote:
> XStream: 1.4.4
> Java (windows 64 bit/Windows 8):
>
> java version "1.6.0_39"
> Java(TM) SE Runtime Environment (build 1.6.0_39-b04)
> Java HotSpot(TM) 64-Bit Server VM (build 20.14-b01, mixed mode)
>
> Maven: 3.0.5
>
> mvn clean install gives
>
> Running com.thoughtworks.xstream.mapper.XmlFriendlyMapperTest
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec
> <<< FA ILURE!
>
testPrefixesIllegalXmlElementNamesWithValue(com.thoughtworks.xstream.mapper.XmlF
> riendlyMapperTest) Time elapsed: 0.002 sec <<< FAILURE!
> junit.framework.AssertionFailedError: Does not start with 'default-Proxy'
> : <sun .proxy.-Proxy9>
> at junit.framework.Assert.fail(Assert.java:47)
> at junit.framework.Assert.assertTrue(Assert.java:20)
> at com.thoughtworks.xstream.mapper.XmlFriendlyMapperTest.testPrefixesIll
> egalXmlElementNamesWithValue(XmlFriendlyMapperTest.java:27)
>
> Suggestions?
Use JDKs with older patch levels or patch it with the code in trunk. Or
simply ignore it. The test relied on an undocumented JDK behavior since Java
1.3 and that behavior changed suddenly with one of the last patch levels for
Java 6 and 7.
- Jörg
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
