Rob Atkinson ha scritto: ... > This seems to be making a mockery of both automated build and change > control concepts. It may suit a couple of developers with stable > access who work full time on this stuff, buts its a major PITA for > anyone else I suspect. Is it possible to use the logic of build > systems to only publish updates when there is in fact an update? Or is > there an inherent fragility in our setup that this is the only way we > can make it work?
I see two problems: - when you modify a module in GeoTools you have to at least rebuild all the dependent modules as well - GeoServer wise, we have SNAPSHOT dependencies towards GeoTools because most of the bug fixing happens really there, so it's never possible to use a stable release of GeoTools Soo... I don't know. I can't think of a good way to stamp a GT2 module so that it's possible to tell when it was modified, and when it's not. Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
