I'll take a look. Actually, I remember thinking a while back that the best way to do this is to check each module's lib/ dir when the module is being tested, unlike the current setup, where all dirs are checked at once. That way people don't have to remember to update the global list.
> -----Original Message----- > From: dawid.we...@gmail.com [mailto:dawid.we...@gmail.com] On Behalf Of > Dawid Weiss > Sent: Friday, February 10, 2012 12:35 PM > To: dev@lucene.apache.org > Subject: Re: check-legal-lucene invoked repeatedly? > > > No, it doesn't need to be invoked multiple times - it just needs to run > once per build session. > > That's what I thought. It gets invoked a number of times -- check this > out: > https://builds.apache.org/job/Lucene-Solr-tests-only-trunk- > java7/1712/consoleFull > > and these calls are relatively costly. > > > Maybe it could be hooked into lucene core's build, with a property that > gets set and checked so it runs just once? > > I think this makes sense. Do you know how to fix it, Steven? If you do > it may be faster than me grepping through the build files :) > > Dawid > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org
