Shared backend implementation. The elasticsearch backend e.g. is used by both the frontend api as the publisher

Currently only contains an implementation of nl.vpro.domain.api.media.MediaService, which is otherwise completely backend agnostic. It can be backed by ES and couchdb, but e.g. also by an api client.

Parent POM for POMS and related projects

The POMS Bill of Materials manages all versions of the projects in the 'POMS' universe. This can be imported in projects that are not themselves part of it. Poms modules itself will use 'poms-parent' and manage also all external dependencies.

Parent POM for private poms projects (at gitlab)

Clients for NPO APIs

Domain classes and utilities for NPO POMS projects.

Generic utility which are not quite generic enough to make it to vpro-shared. TODO: This module is very sparse, I think we should consider dropping it altogether.

Server side part needed to use an npo player

Several domains like 'media', pages' and 'subtitles' in the POMS system share some common properties which are collected here

Support for ODI authentication as required by NPO player. Not sure whether this is still needed or used. It also supports other 'location handlers'. I think this module is actually misnamed.