With 5.4, we're introducing 3 new modules in main (resource-loader, configuration, freemarker-helper), and they currently each have their own groupId.

With modules outside of magnolia_main, we've been aggressively creating new groupIDs to stop polluting info.magnolia. However, with modules extracted out of core, I'd rather stick to a single groupID (eg info.magnolia.core), at least until any of them is mature enough to move out of magnolia_main.

I'd suggest to change to info.magnolia.core, which is likely what we'll use - at least for starters - when splitting up core.