Update mechanism improvements
(MAGNOLIA-5529)
|
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | modulemechanism, updatemechanism |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
Modules can currently declare workspaces, but they also need to declare the repository to which they're mapped. It shouldn't be any of their business, as we've seen with UGC modules, when we want these workspaces to be shared for instance. A first fix was done with An updated module descriptor might look like: <repositories>
<repository>
<name>Store</name>
<nodeTypeFile>/mgnl-nodetypes/owfe-nodetypes.xml</nodeTypeFile>
</repository>
<repository>
<name>Expressions</name>
<nodeTypeFile>/mgnl-nodetypes/owfe-nodetypes.xml</nodeTypeFile>
</repository>
</repositories>
(for the workflow module) As of yet, it's undecided if we'll use the "repository" or "workspace" name. The latter is more accurate, but the former is more understandable for mere mortals. Additionally, we'll need to check and remove public API methods which take both repository and workspace name strings, and use our repository-to-workspace mapping consistently. |
| Comments |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |