Hi,
I'm seeing two build failures on trunk, and Hudson sees
the same. Both have to do with GeoserverDataDirectory not
being properly configured when the application context is refreshed
in the two failing tests.
Which reminds me of the issues you had some days ago, Justin...
the build can be fixed by removing the loader lazy init in
GeoServerDataDirectory.init, that is, removing "if(loader == null)",
since apparently the loader in the app context is no more the
one used by the data dir after a refresh (and thus it does not
get properly initialized).
I still haven't committed thought, would like to know your opinion.
With the above change my build works fine. Patch attached.
Cheers
Andrea
Index: src/main/java/org/vfny/geoserver/global/GeoserverDataDirectory.java
===================================================================
--- src/main/java/org/vfny/geoserver/global/GeoserverDataDirectory.java (revisione 9044)
+++ src/main/java/org/vfny/geoserver/global/GeoserverDataDirectory.java (copia locale)
@@ -272,7 +272,7 @@
// so it should always get a ServletContext in the startup routine.
// If this assumption can't be made, then we can't allow data_dir
// _and_ webapp options with relative data/ links -ch
- if (loader == null) {
+// if (loader == null) {
//get the loader from the context
loader = (GeoServerResourceLoader) context.getBean("resourceLoader");
@@ -333,7 +333,7 @@
//loader.addSearchLocation(new File(servContext.getRealPath("data")));
- }
+// }
}
/**
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
