[MAGNOLIA-769] Uninstall of modules Created: 15/Mar/06  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: core, updatemechanism
Affects Version/s: 3.0 Beta 1
Fix Version/s: None

Type: New Feature Priority: Major
Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MAGNOLIA-2764 Cache module configuration may refer ... Closed
relation
is related to MAGNOLIA-3170 Servlets in deployment descriptor don... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

on the modules overview page you can click uninstall:

  • check dependencies
  • delete modules node in the config
  • delete all nodes created by the additional bootsrap files
  • delete the files /templates/module, docroot/module and admintemplates/module
  • delete the additional files defined in the descriptor
  • remove servlets
  • remove repositories
  • finaly delete the jar (if it is exploded in the classes dir delete the descriptor only)
  • set the restartNeeded flag (always)


 Comments   
Comment by Philipp Bracher [ 17/May/06 ]

rescheduled: no time

Comment by Magnolia International [ 17/Sep/08 ]

Using the updatemechanism, here are some ideas to implement this:

  • a module's version handler provides "uninstall task" - which should revert to state prior to installation AND be "safe": check if value was modified etc (especially if this is about a node or property outside of the module's own node)
  • these uninstall tasks are serialized (for instance under config:/server/install
  • a modules overview page could provide an "uninstall" button and/or absence of the module's jar (i.e. of its module descriptor) could trigger the uninstall

This would also give a possibility to replace the magnolia.bootstrap.force users of 3.0 have been used too, by providing a way to completely reinstall a module.

Comment by Magnolia International [ 23/Apr/09 ]

Additionally: uninstall tasks provided by the ModuleVersionHandler could be serialized in the repository, giving the possibility to "automatically" uninstall a module who's jar was removed.

If we want to uninstall without necessarily removing a module's jar file, we 1) need a UI 2) need a way to mark a module as uninstalled/disabled (which raises the question of knowing what to do to reinstall/reenable the module)

Comment by Magnolia International [ 17/Jun/11 ]

(one could even think about a "record" mechanism, where changes operated by a version handler could be recorded and reverted later...)

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.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:20:30 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.