The missing file is a saveservice.properties file that doesn't show up combined source/lib distributions. I copied an existing one from an older distribution and that was enough to get JMeter to load my test plans. Without that properties file, the JMeter GUI declares the test plan invalid and refuses to complete the load.
As to the second point of your about "terminal paths". To properly handle set-cookie paths (the way the browsers do), the algorithm that determines what path to store really needs to trim the path to exclude the page itself. 2.1.1 did not do this, but the nightly does, and all I was saying was that I noted this when I originally put in my fix for missing paths but didn't do any work on it. Ciao, Bill -----Original Message----- From: sebb [mailto:[EMAIL PROTECTED] Sent: Thursday, January 12, 2006 2:54 PM To: JMeter Developers List Subject: Re: JMeter 2.1.2 release? On 12/01/06, Bill Herndon <[EMAIL PROTECTED]> wrote: > Sebb, > > The current nightly is in dodgy shape. Builds OK, but won't load my > existing test plans without my copying certain files from one of the > release builds. That said, the set-cookie problem seems to still be > there. Which files? Remember you need both the _bin and _lib archives. > After a quick code inspection, it looks to me like the code has been > modified to handle removing the terminal page from the stored path. Don't understand what you are getting at here. > That's good. I noted that when I did my set-cookie patch but didn't > attack that issue myself. But... it means that I'll have to redo my > patch. OK, so be it. I'll try to have the bug filed and the patch > submitted by tonight. > > A quick question though, the Junit's were originally in the > CookieManager.java file as a static subclass of TestCase. Now they're > gone. Any idea where they've moved to? I've six unit's of my own to > add to cover the bug. Looks like there might be some restructuring of > the testing hierarchy going on. Yes, there's a test/ hierarchy - quite a few of the tests have been moved there. S. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
