How is the open source part of PillarOne separated from the client-specific part?
Up to Table of Contents
PillarOne has a plugin mechanism. Client-specific code should be in a plugin.
To keep a PillarOne instance maintainable, we separated it into plugins: Core, application, and several business logic plugins. Typically, clients put all their proprietary components and models into a separate plugin which is of course not open sourced.
When the PillarOne framework is upgraded, then clients can load their own plugins again.