Andrea Aime a écrit :
> I've just fixed both builds, 2.3.x and trunk.
> Both were failing for trivial errors, yet it would be nice
> if people kept an eye on the build servers and avoid committing
> last minute of the day leaving both builds unservable for the
> whole weekend.
I guess that the build has been broken by changes commited without a full "mvn
install". So maybe we should ask: what refrain peoples from running "mvn
install" before commiting? Is it because the build is too long?
If this is because the build is too long, I suggest some tips:
* "mvn clean" is not needed if there is no public API changes
(one additional reason for encouraging developper to keep more
internal logic private). But if there is API change, we need a
"mvn clean" before "mvn install".
* For Linux users, the "ReiserFS" is surprisingly good with
directories with lot of small files, as we have in Geotools :)
What we can do on the Geotools-project side:
* Disable the packaging of sources. It put significant overhead on
every developper's machine while it is needed only for the one who
deploy on Maven repository.
* Is there anyway to configure Javaloppy so that it doesn't overwrite
the files which don't have any formatting changes? It would avoid
Maven and IDE to recompile ~150 files in "main" after every
"mvn install" even if there is no changes.
Martin
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
