<commit_before>
Also see http://bugzilla.wyona.com resp. http://yanel.wyona.org

- grep -rl TODO *
- Rename lib to conf
- deploy xml-apis, xerces and xalan as endorsed libs
- "Bug": Check if Access is being denied if no policiy configuration is being specified ...
- Add WebDAV and APP
- Downgrading/Upgrading, automatic updates, history, Maven dependency ...
- Security: Policies of Realms should NOT be inherited resp. configurable
- Make authorization and authentication implementation configurable per realm
- Implement Admin interface with listing of repositories/realms and mountpoints
- Implement Locking
- YanelServlet: if realm has no authorization specified then the ROOT one is being taken instead that access is being denied: Makes this configurable
- YanelServlet: Declare Realm for authorization on authentication screen
- YanelServlet: Unify authentication scheme
- YanelServlet: Improve exception handling (also handle <yanel ... as an XML object)
- ResourceTypeRegistry class loading needs to be improved (see Yarep how it should be done ...)
- Change rti map to XML with the possibility of resource specific path config
- Introduce Map/Realm mounting
- Introduce chain of responsibility for MapImpl (e.g. javadoc)
-- Would it make sense to put this also into the repository layer?
- Build resource implementations dynamically (based on configuration): ResourceRegistry ...
- Add yanel version (such that for instance the webapp can display the version, e.g. 0.0.1-dev-r13812)
- Make Tomcat targets configurable during configure.sh
- Specify versions of implementations explicitely and make them downloadable dynamically based on the registered resource types
- Replace most System.err/out by log4j<commit_msg>more tasks moved to Bugzilla<commit_after>
Also see http://bugzilla.wyona.com resp. http://yanel.wyona.org

- grep -rl TODO *
- deploy xml-apis, xerces and xalan as endorsed libs
- "Bug": Check if Access is being denied if no policiy configuration is being specified ...
- Downgrading/Upgrading, automatic updates, history, Maven dependency ...
- Security: Policies of Realms should NOT be inherited resp. configurable
- Make authorization and authentication implementation configurable per realm
- Implement Admin interface with listing of repositories/realms and mountpoints
- Implement Locking
- YanelServlet: if realm has no authorization specified then the ROOT one is being taken instead that access is being denied: Makes this configurable
- YanelServlet: Declare Realm for authorization on authentication screen
- YanelServlet: Unify authentication scheme
- YanelServlet: Improve exception handling (also handle <yanel ... as an XML object)
- ResourceTypeRegistry class loading needs to be improved (see Yarep how it should be done ...)
- Change rti map to XML with the possibility of resource specific path config
- Introduce Map/Realm mounting
- Introduce chain of responsibility for MapImpl (e.g. javadoc)
-- Would it make sense to put this also into the repository layer?
- Build resource implementations dynamically (based on configuration): ResourceRegistry ...
- Add yanel version (such that for instance the webapp can display the version, e.g. 0.0.1-dev-r13812)
- Make Tomcat targets configurable during configure.sh
- Specify versions of implementations explicitely and make them downloadable dynamically based on the registered resource types
- Replace most System.err/out by log4j
{'fraction_non_alphanumeric': 0.0571928800700321, 'fraction_numerical': 0.005252407353370295, 'mean_word_length': 4.4848, 'pattern_counts': {'":': 2, '<': 5, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 2}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1703411', 'n_tokens_mistral': 873, 'n_tokens_neox': 816, 'n_words': 435}