Thanks, Gabriel, for the quick turnaround. Setting the version to 1.3.0 did not prevent the build, it just caused GeoServer master to ignore updates to the stable branch of geowebcache and keep on using the last 1.3-SNAPSHOT from before 19 September. Now that you have reverted the change, GeoServer master will build against the most recent geowebcache stable, which is I think what you wanted.
Kind regards, Ben. On 08/10/12 12:28, Gabriel Roldan wrote: > Hey Ben, > Reverted to 1.3-SNAPSHOT. Sorry for the oversight. > Yet I don't get why it would prevent the geoserver build. Is it > because it gets the current branches git commit id? -- Ben Caradoc-Davies <[email protected]> Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
