[MGNLSLOCK-5] Module naming inconsistency Created: 02/Dec/10 Updated: 26/May/15 Resolved: 19/May/15 |
|
| Status: | Closed |
| Project: | Magnolia Soft Locking Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.5 |
| Type: | Task | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Espen Jervidalo |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: |
| Description |
|
All(*) our modules are named (in terms of module descriptor <name>)
We should thus rename softLocking to soft-locking. This can be achieved by hooking deeper in the ModuleVersionHandler (i.e the default behavior would always consider this an install, we need to make it "believe" it's an update) (*) except for the soon-to-be-deprecated-or-dropped adminInterface and fckEditor |
| Comments |
| Comment by Espen Jervidalo [ 08/May/15 ] |
|
This won't work. When changing the module name, it won't find a former version of the module. |
| Comment by Espen Jervidalo [ 19/May/15 ] |
|
For QA: Add soft-locking module 2.0.3 to ee-bundle, run install, shutdown. Change version to 2.5-SNAPSHOT and re-run installation. |
| Comment by Federico Grilli [ 21/May/15 ] |
|
.addTask(new RemoveNodeTask("Remove soft-locking config node", "Removes no longer needed soft-locking config-node.", RepositoryConstants.CONFIG, "/modules/soft-locking/config")) Shouldn't the path to be removed be /modules/softLocking/config ? |