[MAGNOLIA-6271] Fix groupId for new modules extracted from core to info.magnolia.core Created: 25/Jun/15 Updated: 02/Jul/15 Resolved: 25/Jun/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | build |
| Affects Version/s: | 5.4 |
| Fix Version/s: | 5.4 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Description |
|
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. |
| Comments |
| Comment by Magnolia International [ 25/Jun/15 ] |
|
Done. Required fixes in main, ui, resources, stk. |