[MAGNOLIA-3813] A variation on ModuleNodeBuilderTask which applies operation on the module's config node Created: 29/Aug/11 Updated: 07/Sep/11 Resolved: 31/Aug/11 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core, modulemechanism |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.5 |
| Type: | New Feature | Priority: | Neutral |
| Reporter: | Magnolia International | Assignee: | Jan Haderka |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Patch included: |
Yes
|
| Acceptance criteria: |
Empty
|
| Description |
|
This is a minimal, yet fairly useful, variation of info.magnolia.nodebuilder.task.ModuleNodeBuilderTask, which applies operations on the current module's config node (as opposed to the module's "root" node). This is convenient in that the operations don't need to "get or create" the config node. |
| Comments |
| Comment by Magnolia International [ 30/Aug/11 ] |
|
And here are some tests - for the new class as well as for existing. Also "fixes" info.magnolia.nodebuilder.task.NodeBuilderTaskTest#testUnknownRootThrowsException which wasn't testing much of the NodeBuilderTask at all. |