Remote publishing creates config objects for target and stores them in the source system

If you publish translations with Scroll Remote Publishing plugin to a new space, the publishing code will activate Translations module and copy the language configuration (which languages should exist in the new space) to a configuration object and stores this in the (local) source system (ActivateTranslationHandler). This config object remains in the source system without effect.

It is ok that the configuration is not copied to the remote system (works as designed), but the config object will remain in the local system (2.8.x, 3.0.x), but the ActivateTranslationHandler will fail with a NullPointerException in 3.0.x (because we added code that tries to save the build timestamp for the space).