Every day we seem to build all modules from scratch - regardless of whether they have changed - which seems to mean you have to either do a full mvn install orust as bad, a full download every day you make a change.
In particular, you cant just build a module you care about and then be alerted its dependencies have changed because there is a new mvn artefact - everything is new and you have to do a full svn update first really to scan for changes. 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? Rob A ------------------------------------------------------------------------- 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
