Wiki source code of Extension Manager - Installed extensions
Last modified by Vincent Massol on 2024/11/19 16:12
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | Should be separated from the local repository: | ||
| 2 | |||
| 3 | = XWiki databse = | ||
| 4 | |||
| 5 | Pros: | ||
| 6 | |||
| 7 | * easier to backup | ||
| 8 | * when a wiki is removed associated installed extensions index are automatically removed | ||
| 9 | * can be searched | ||
| 10 | |||
| 11 | Cons: | ||
| 12 | |||
| 13 | * takes more time to list all installed extensions since all wikis have to be requested one by one | ||
| 14 | * the database need to be ready before loading jar extensions which mean having more components impossible to install with extension manager if extension manager requires them | ||
| 15 | |||
| 16 | = Separated database = | ||
| 17 | |||
| 18 | Pros: | ||
| 19 | |||
| 20 | * can be searched | ||
| 21 | |||
| 22 | Cons: | ||
| 23 | |||
| 24 | * one more thing to backup | ||
| 25 | |||
| 26 | = Lucene index = | ||
| 27 | |||
| 28 | Pros: | ||
| 29 | |||
| 30 | * quickest search | ||
| 31 | |||
| 32 | Cons: | ||
| 33 | |||
| 34 | * one more thing to backup | ||
| 35 | * hard to link extension with each other by dependencies | ||
| 36 | |||
| 37 | = Local repository = | ||
| 38 | |||
| 39 | Pros: | ||
| 40 | |||
| 41 | * current state :) | ||
| 42 | |||
| 43 | Cons: | ||
| 44 | |||
| 45 | * cannot search in it | ||
| 46 | * one more thing to backup |
