| commit | 950c3d9ed94a16d1be857cb14095b2fbd75bcf71 | [log] [tgz] |
|---|---|---|
| author | Serge Huber <shuber@apache.org> | Thu Sep 26 07:37:58 2019 +0200 |
| committer | Serge Huber <shuber@apache.org> | Thu Sep 26 07:37:58 2019 +0200 |
| tree | ae6210422b6734340c2ffae642704d2aec97303e | |
| parent | 4fa4955f133471d438d6c85cb96710fcdb18365c [diff] |
UNOMI-250 Refactoring services into seperate Java packages Right now we have a bit of a mess in our services implementation sub-project. All the service implementations are in the package: org.apache.unomi.services.services I propose that we rename this package to: org.apache.unomi.services.impl and that each service gets its own sub-package, for example the RulesServiceImpl would be in: org.apache.unomi.services.impl.rules This would make it much easier to activate/deactivate logging per service implementation, because currently it is tricky to get logging activated properly unless using configuration by class. Having it by package would be a lot better. Utility classes such as ThirdPartyService or the clustering event classes would also be moved with the service sub-package they belong to. In terms of impact this should minimal, only people activating logs should be notified that the class location has changed. Signed-off-by: Serge Huber <shuber@apache.org>
Apache Unomi stores user profile information and is mostly used to provide a backend server for A/B testing and personalization. To do so it implements the currently under development OASIS Context Server specification.
The source code is available under the Apache License V2
You can find all the updated documentation, including building and deployment instructions, on the Apache Unomi web site.