vitro/webapp
j2blake 245763e9e7 Make DeveloperSettings a singleton, and other improvements.
By making it a singleton, we do need an explicit Setup operation. However, it means that we can refer to the settings in client code that doesn’t have access to a request or to the ServletContext.

Other refactorings to simplify the logic or make it more scalable.
2014-01-04 14:22:29 -05:00
..
config VIVO-224 Get rid of REBUILD_VCLASS_GROUP_CACHE. 2014-01-03 15:26:33 -05:00
languages/es_GO Merge branch 'maint-rel-1.6' of git+ssh://github.com/vivo-project/Vitro into maint-rel-1.6 2013-12-09 17:00:36 -05:00
lib new versions of jar files for sparql query json ld also used in vivo semantic search 2013-12-04 13:31:05 -05:00
rdf VIVO-224 Change USE_MISCELLANEOUS_EDITOR_PAGES to USE_INDIVIDUAL_CONTROL_PANEL 2014-01-03 15:40:52 -05:00
src Make DeveloperSettings a singleton, and other improvements. 2014-01-04 14:22:29 -05:00
test Make DeveloperSettings a singleton, and other improvements. 2014-01-04 14:22:29 -05:00
themes/vitro VIVO-541 First cut at the developer panel. 2013-11-17 11:52:18 -05:00
web Make DeveloperSettings a singleton, and other improvements. 2014-01-04 14:22:29 -05:00
build.xml VIVO-541 First cut at the developer panel. 2013-11-17 11:52:18 -05:00
context.xml VIVO-2 Modify the build so installers can create a container-neutral VIVO. 2013-01-16 14:54:33 -05:00
webapp.doxyfile Improve output: distinguish between failed assertions (failures) and unexpected exceptions (errors), and print a filtered stack trace for any exception. 2010-01-29 22:13:57 +00:00