[MAGNOLIA-351] remove dependencies on ContentNode Created: 26/Apr/05 Updated: 23/Jan/13 Resolved: 27/Apr/05 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 2.1 Final |
| Fix Version/s: | 2.1 Final |
| Type: | Improvement | Priority: | Major |
| Reporter: | Sameer Charles | Assignee: | Sameer Charles |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Date of First Response: |
| Description |
|
as mentioned under http://jira.magnolia.info/browse/MAGNOLIA-340 ContentNode will be depricated since it does not make sence to have wraper classes for nodes when we have a |
| Comments |
| Comment by Sameer Charles [ 26/Apr/05 ] |
|
commited on svn 1. ContentNode deprecated ContentNode is not used anywhere in magnolia now, but I left this class as deprecated to support Issues: major part is done, now have to clean up some more. Note : I had to touch almost all packages, so you might see some instability. |
| Comment by Sameer Charles [ 27/Apr/05 ] |
|
fixed above mentioned issues! changing status to "resolved" , ll keep working on some other performance enhancement /bug fixing |
| Comment by Nicolas Modrzyk [ 28/Apr/05 ] |
|
I can indeed create a user, create a role, assign a role, edit and rename the role, which I could not do yesterday. |