I've written a custom ant task that performs Checkstyle only on modified
files. Or on files modified since some revision.
The purpose is to gradually introduce a code quality policy on legacy
projects.
I plan to submit a patch back, meantime if you need it *now*, then email me
(uses Checkstyle
>
> On Tue, Nov 3, 2009 at 1:33 PM, Wray, Nathan wrote:
> Hi David,
>
> It has to do with the procedures I'm trying to piggyback onto. The ant
> target creates some required code review documentation. The goal is to
> have the ant target fail, rather than having the commit fail as you
> typically
ist
Subject: Re: Creating a fileset from a list of filenames
Just curious: Why are you using Ant for this?
Why not have a post-commit script that runs the check on these files?
Or, even better, use Hudson which is a continuous build system. It'll
automatically run your build everytime someo
Just curious: Why are you using Ant for this?
Why not have a post-commit script that runs the check on these files?
Or, even better, use Hudson which is a continuous build system. It'll
automatically run your build everytime someone does a Subversion checkin.
Plus, it has a CheckStyle plugin whic
--- On Tue, 11/3/09, Wray, Nathan wrote:
> From: Wray, Nathan
> Subject: Creating a fileset from a list of filenames
> To: user@ant.apache.org
> Date: Tuesday, November 3, 2009, 7:16 AM
> Hi All;
>
>
>
> I'm trying to identify modified java files in an SVN
> working copy and
> run checksty
