Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <85E484792BD34689866F83B61E031144@Asus>
From: "Hugh Sparks" <hugh@csparks.com>
To: <users@cocoon.apache.org>
References: <487A271E.8090505@gmail.com>
 <B511F1F8C424414898324294E9A04F5B@Asus> <48931DCD.4040406@tuffmail.com>
 <1D35FF39-642D-430E-9BE8-6CDA70ED5851@robinwyles.com>
 <4896E66E.5000906@tuffmail.com>
Subject: Re: Cocoon 2.2 flowscipt debugger possible?
Date: Mon, 4 Aug 2008 20:47:32 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit

> > Robin Wyles writes:
>> [...] So my question.... should the FlowScript  debugger really be
>> enabled by default for dev mode?
>
> Grzegorz Kossakowski replies:
> Could you elaborate on these issues you face? If there are some serious
> problems then I think we'll switch it off again.
> Actually, you can do it yourself very easily but still defaults are important.

Joy! (It works.) 

It is so easy to turn on and off now, I prefer to see it off by default even in
dev mode. It is more trouble to fuss with the mode because you have to edit the
pom and rebuild. But the property can can be changed after the webapp is
deployed if needed. I tend to leave my jetty setup in mode dev all the time and
the javaflow debugger is rather intrusive when not wanted.

Thanks for the fix!
I think this resolves JIRA COCOON-2221

-Hugh Sparks


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org