[MAGNOLIA-5433] As a developer it's clear that I cannot use same name siblings in Magnolia Created: 31/Oct/13 Updated: 05/Dec/16 Resolved: 18/Nov/13 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 4.5, 5.0 |
| Fix Version/s: | 5.2 |
| Type: | Story | Priority: | Major |
| Reporter: | Christopher Zimmermann | Assignee: | Jozef Chocholacek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | jcr | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Issue Links: |
|
||||||||||||||||||||
| Sub-Tasks: |
|
||||||||||||||||||||
| Template: |
|
||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||||||
| Release notes required: |
Yes
|
||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||
| Sprint: | 5.2-rc2 | ||||||||||||||||||||
| Description |
|
A decision was made in the architecture meeting on October 31, 2013 with at least Philipp, Jan and Daniel present that same name siblings in JCR will officially not be supported in Magnolia. As i understand it, in many ways same name siblings are already not supported in many specific cases. And now we can simplify the system by enforcing this policy. Tasks:
Also, it was decided that changing the nodetype will only be done in 5 series. For 4 series we have the fix in the linked ticket: http://jira.magnolia-cms.com/browse/MAGNOLIA-5311 |
| Comments |
| Comment by Christopher Zimmermann [ 31/Oct/13 ] |
|
Once we enforce that an import cannot create same name siblings, we should enforce that policy everywhere in magnolia. |
| Comment by Eric Hechinger [ 12/Nov/13 ] |
|
Can not be closed as sub task are still in progress |
| Comment by Jozef Chocholacek [ 18/Nov/13 ] |
|
Documentation updated in |