Mailing-List: contact dev-help@click.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@click.apache.org
Received-SPF: pass (athena.apache.org: domain of sabob1@gmail.com designates
 209.85.160.42 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=g8cUJSGfhqcZDUY8OAweTXYtQb6ZWZTJyk+1SXZTPQDkDZVVrvRA+7r7UPI0RZ+1+O
         K56xsHDgUy7Ij8J/ZXY0uU4EUlJS2pRFqJm4H0PLSWj+HAik/ayy4KphHKdsUKCUB8qE
         rUSJ6ZUN9d1wf15HTlUGFghvWDSCQYIp+DxlQ=
Message-ID: <4BFBA4A4.7090106@gmail.com>
Date: Tue, 25 May 2010 20:21:24 +1000
From: Bob Schellink <sabob1@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
 rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: dev@click.apache.org
Subject: Re: [jira] Commented: (CLK-671) Upgrade to Checkstyle 5.1
References: <4642024.55781273400688026.JavaMail.jira@thor>
 <15743175.30561274780064259.JavaMail.jira@thor>
In-Reply-To: <15743175.30561274780064259.JavaMail.jira@thor>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

On 25/05/2010 19:34, George Stan (JIRA) wrote:

> 2. Click catches allot of problems and it's doing allot of checks at runtime, but they consume quite a few cycles.
> What if those checks would be "configurable"/ optional at runtime (so would consume no resources/cycles at all if turned off), but instead they would be as Checkstyle based tasks, that the user can perform at build time?
> In performance intensive installations this could be a fantastic improvement.


Could you share some of the checks you are referring to? When you say fantastic performance gains
are we talking orders of magnitude? Do you have profiled data we could look at to see some of the
bottlenecks?

Kind regards

Bob