https://issues.apache.org/bugzilla/show_bug.cgi?id=56662
--- Comment #7 from Sebb <[email protected]> --- (In reply to Kasper Janssens from comment #6) > So, do I interpret your statement correctly when I say that the current code > in the trunk IS the 2.12 version (in the future)? Not exactly. There may be additional changes before 2.12 is released. > Because in that case we > might consider using the dev version of course, I'm just a bit reluctant to > use it if there would still be considerable code flux. > > Do I also understand correctly that you don't really have a strict release This is an all-volunteer effort; releases are done when there are resources available. > date planned for 2.12 (important factor when we considering using the dev > version, if it's still quite some time away we might have to go for the dev > version as it's a bit of an annoying bug.)? Note that the nightly builds are not formal releases, and are not guaranteed. > I recall we had problems using the 2.9 version (don't recall which ones > anymore) so that's not really an option right now. I was only suggesting using 2.9 to maintain the test plans, not run them. > Thanks for the clarification. Having said tah, I have just been ahving a look at what changes could have caused the problem. It looks like it might not be a JMeter code problem, but it might be the version of XStream. It so happens that 2.10 and 2.11 switched to using XStream 1.4.4 (from 1.4.2); the current dev code uses 1.4.6. This appears to be the culprit. So try replacing lib/xstream-1.4.4.jar with version 1.4.6 It seemed to help when I just tested it. You can get the jar from http://xstream.codehaus.org/ or Maven http://repo1.maven.org/maven2/com/thoughtworks/xstream/xstream/ It looks like there is 1.4.7 also available; not yet tried. -- You are receiving this mail because: You are the assignee for the bug.
