Kenny MacLeod wrote:
> it was marked as fixed in 2.0.2, but I haven't taken the opportunity to
> verify it yet.
Yeah, it's supposed to be fix in 2.0.2. Please reopen the issue if it
hasn't.
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com