[MGNLUI-686] Move content app framework to its own maven module Created: 20/Feb/13 Updated: 07/Mar/13 Resolved: 01/Mar/13 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Tobias Mattsson | Assignee: | Daniel Lipp |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | apiteam | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Template: |
|
||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||||||
| Release notes required: |
Yes
|
||||||||||||||||||||
| Description |
|
Name of the new module should be: magnolia-ui-content-app It will have to depend on admincentral for now. We should move the following classes and packages there:
Proposed package structure:
|