That's sound real cool.
Make sure a warning is issued with proper links:
- link to documentation explaining the reasons
- link to a front-end or other tool (e.g. an SQL suggestion generator) that can help fix
things (even to... page editor ;-))
paul
Le 4 févr. 2011 à 11:45, Vincent Massol a écrit :
Hi devs,
I'd like to explore the idea of having a xwiki-sanity module which would be in charge
of making verifications in a running XE/XEM instance and reporting issues/making fixes
were needed. We could also have a counterpart xwiki-sanity application (XAR).
Here are some potential use cases (I'm sure we can find lots of others):
* Check DB version and perform migrations of the schema accordingly (our current
migration system which is currently located in xwiki-core)
* Perform various checks on DB settings, cache settings, etc
* Perform deprecation call checks in velocity (the current deprecated uberspector)
* More specific checks. For example: intercept the call to the velocity macro and add a
check on: if the page where the velocity is executed is called Blog.BlogSheet and the
content of the velocity contains "#getEntryDate($entryDoc $entryObj $entryDate)"
and the platform version is >= 3.0M1 then don't execute the macro but instead
display the message "The Blog application is not compatible with this version of XE,
please upgrade to the latest Blog application".
WDYT?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs