Hi all, I just wasted four hours tracking down yet another problem which resulted from the one time testing setup running into an issue with the singleton we all love: GeoServerDataDirectory. The issue is once again that the singleton holds onto state which is not properly reinintalized when the mock test data setup is recreated.
This is the third time where i have run into such an issue while working on the new config. Perhaps not any of you are running into these issues because are not developing on trunk, or only doing backports. But currently i am making some major changes and relying on these tests is starting to eat up a lot of time where i am not productive, and its not even really an issue with my code. Phew... ok apologies for the rant. But I want to drive the point home that the way that singleton works is unreliable in a test environment, and its currently at the base of all "resource loading". And i bring this up because during the code sprint we are going to be making even bigger changes, and having to deal with issues like these is going to hurt us even more. <end of rant> -Justin -- Justin Deoliveira The Open Planning Project [EMAIL PROTECTED] ------------------------------------------------------------------------- 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 Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
