Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: "Smiley, David W." <dsmiley@mitre.org>
To: "<dev@lucene.apache.org>" <dev@lucene.apache.org>
Subject: Re: ant precommit; annoyed with "checkout is dirty"
Thread-Topic: ant precommit; annoyed with "checkout is dirty"
Thread-Index: AQHNy+TePTMjPQXDgUeno0s8URAYGpf8nLgAgAAnloA=
Date: Mon, 26 Nov 2012 18:30:26 +0000
Message-ID: <DA95D27D48C2AB4E815C79B1D473F20E1DA81F35@IMCMBX04.MITRE.ORG>
References: <1353941184623-4022362.post@n3.nabble.com>
 <CAL8PwkYVgqUyC2c-1PZWatyjjOXB7K4_6fg2fLP1PQMLQibdMQ@mail.gmail.com>
In-Reply-To: 
 <CAL8PwkYVgqUyC2c-1PZWatyjjOXB7K4_6fg2fLP1PQMLQibdMQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <EAFB82747B50C741AADDFF13B8F57021@imc.mitre.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

How about doing the dirty checks on sub-directories only?  This way I can k=
eep the random .patch files & miscellany around in the root.

The IDE files are a special circumstance for my setup because I use symboli=
c links to the IDE files in dev-tools so that I can easily see how my IDE s=
etup is different than the one in source control, and more easily commit de=
sirable changes.  I might stop doing this if this were the only thing in my=
 way from "ant precommit".

FWIW my solution has been to modify the build script to not do the dirty ch=
eck :-)

~ David =20

On Nov 26, 2012, at 11:09 AM, Michael McCandless wrote:

> I think the idea is to catch files you forgot to svn add.
>=20
> For IDE files, you should just svn ignore them?
>=20
> Mike McCandless
>=20
> http://blog.mikemccandless.com
>=20
> On Mon, Nov 26, 2012 at 9:46 AM, David Smiley (@MITRE.org)
> <DSMILEY@mitre.org> wrote:
>> "ant precommit" will check if the source tree is "dirty" (i.e. contains =
files
>> not in source control) and stop with a failure if so.  I find that rathe=
r
>> annoying since I've usually got a variety of .patch files and IDE config
>> changes.  What is the rationale behind this check?  How do people usuall=
y
>> deal with it?  Perhaps if I do my real development on another checkout (=
git
>> based), I could then patch on the svn one for the commit.  Pretty annoyi=
ng
>> though, and the 4x port is yet another step.  There sure is a lot of bur=
den
>> to getting commits in.  I no longer care to improve little javadoc and t=
ypo
>> stuff.
>>=20
>> ~ David
>>=20
>>=20
>>=20
>> -----
>> Author: http://www.packtpub.com/apache-solr-3-enterprise-search-server/b=
ook
>> --
>> View this message in context: http://lucene.472066.n3.nabble.com/ant-pre=
commit-annoyed-with-checkout-is-dirty-tp4022362.html
>> Sent from the Lucene - Java Developer mailing list archive at Nabble.com=
.
>>=20
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>=20


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org