Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (nike.apache.org: domain of waynefay@gmail.com designates
 209.85.220.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <D036B349-DF15-4AFF-9FB8-87ECFF094756@gold-family.us>
References: <D036B349-DF15-4AFF-9FB8-87ECFF094756@gold-family.us>
From: Wayne Fay <waynefay@gmail.com>
Date: Wed, 24 Jul 2013 11:31:11 -0500
Message-ID: 
 <CALy+7U=sJDbdvxP-bpjk2y4Kt4e6tk8D3MTAyodkp5tqa_swcg@mail.gmail.com>
Subject: Re: Any reason ant should compile faster?
To: Maven Users List <users@maven.apache.org>
Content-Type: text/plain; charset=UTF-8

> The case I'm wondering about now is one where we have over 10,000
> source files in a directory, and compile them bit-by-bit. One step specifies
> about 300 files, and thanks to javac dependency logic, actually compiles
> about 4000 files in ant.

Is there any way you can break that into 10 projects with 1k files
each, or 20 projects with 500 files each, etc? I have found dramatic
improvements in (Java compiling) speed as a result of breaking huge
projects like this into a series of much smaller projects with
dependencies between the projects etc as needed.

Having said that, 20 seconds for 4k files sounds pretty quick! Sorry
but I'm not sure how to explain the 20 sec vs 90 sec results you're
experiencing. I'd check versions of everything and flags sent to
compilers etc via -X.

Wayne

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