I think what is going on is that Hudson GeoServer builds are triggered by GeoTools changes but do not wait for the GeoTools build they depend on to finish before they start. Result? Bogus build breakage. The build recovers by being retriggered by the completion of the GeoTools build.
Could I be right? Can it be fixed? This hits app-schema because we fix code in GT and fix encoding tests in GS. Kind regards, Ben. On 08/04/10 14:52, Hudson wrote: > See<http://hudson.opengeo.org/hudson/job/geoserver-2.0.x/406/changes> > > Changes: > > [bencaradocdavies] Removed unnecessary comment > > [bencaradocdavies] Fixed problem handling app-schema nested feature ids that > caused filters to fail [GEOT-2969] -- Ben Caradoc-Davies <[email protected]> Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
