Andrea Aime a écrit :
> is it just me, or build times are out of control again?
> It took 14 minutes to build geotools this morning.
> I've attached a PDF showing build times for each module,
> sorted by build time (higher to lower), with an accumulated
> percentage showing that 70% of the total build time is spent
> is 1/4 or the modules.
I had a look to a few of them. On the top of the list is "metadata" with 91
seconds reported, but this module doesn't have expensive test (except maybe
CanonicalSetTest which take 3 seconds). "mvn clean install" in this module
consistently take 27 seconds on my slower latop. Could it be that the 91
seconds
includes the network latence when Maven checks for snapshot updates? Maybe this
latence appears in the metadata report because it is the very first GeoTools
module to be built (after our maven custom plugins).
In the case of the "referencing" module, the tests take 10 seconds on my
machine. The majority of the time is rather spent in the compilation - this
module has a high number of implementation classes and some of them are big.
In the "coverageio" module, there is some test that I can trim down. I will
commit when the SVN will be back.
For "metadata", "referencing" and other modules in the general sense, if there
is a volunter for switching the trunk to Junit 4 with latest maven-surefire
plugin, I could slowly begin to refactor some tests and make more extensive use
of @BeforeClass and @AfterClass annotations rather than overriding setUp() and
tearDown() methods.
Martin
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
