Apaprently it does not know what the element available means - Chris are you using some magic ant plug-ins or extensions?
Commented out the offending code for now, Chis can fix this in his timezone.
Well geotools has done it again, the sld parser is broken as well.
Going back to the old jars, warning the validation stuff is broken and lives in geotools (but due to thier problems we cannot get new versions ... or fix other bugs in the validations).
Might move this code back out of geotools as I put it there in the first place (Jody?)
Well geotools has done it again, the sld parser is broken as well.
I'm not positive, but I think it may be that the parser is actually fixed - which is causing problem with invalid SLD files (which used to work). The new parser code is namespace aware and this can cause some problems. Can you provide details of what now fails, ideally by adding a new unit test to the sldstyling module with the sample sld that breaks it.
Well geotools has done it again, the sld parser is broken as well.
I'm not positive, but I think it may be that the parser is actually fixed - which is causing problem with invalid SLD files (which used to work). The new parser code is namespace aware and this can cause some problems. Can you provide details of what now fails, ideally by adding a new unit test to the sldstyling module with the sample sld that breaks it.
Thanks James, we really can go back to the old jars. I think I will take a run at updating the GeoServer to work against a geotools2 refresh.
Do your release scripts (which make the nice jar files) only run on linux? Or are they implemented completly in maven?
If needed we can keep going with geoservers ant task - but using the gt2 release process would be a better long term solution.