[MGNLSCH-54] Change groupId to info.magnolia.scheduler Created: 13/May/15  Updated: 22/May/15  Resolved: 13/May/15

Status: Closed
Project: Scheduler
Component/s: None
Affects Version/s: None
Fix Version/s: 2.2

Type: Task Priority: Critical
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
Release notes required:
Yes
Date of First Response:

 Comments   
Comment by Magnolia International [ 13/May/15 ]

Done on fix/locale-provider-and-inject branch

Comment by Mikaël Geljić [ 15/May/15 ]

Can/shouldn't we also change artifactId to magnolia-scheduler?

Comment by Magnolia International [ 19/May/15 ]

mgeljic typically (and afaik) we do this when we split a module further and/or change its scope. In this case, the module stayed exactly as-is, we just split up a Maven pom for the relocation. That said, I don't have a strong opinion; it's true that we did this for the new modules in main .... Reopen if you feel ~strongly

Comment by Mikaël Geljić [ 19/May/15 ]

I don't care much really, I thought it was some sort of more recent conventions; I mostly had those few apps as UI submodules in mind, but again, doesn't really matter

Generated at Mon Feb 12 10:45:26 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.