sling_bootstrap.txt: run-once command file for the BootstrapInstaller
---------------------------------------------------------------------
Key: SLING-1101
URL: https://issues.apache.org/jira/browse/SLING-1101
Project: Sling
Issue Type: Improvement
Components: Launchpad
Affects Versions: Launchpad Base 2.0.4
Reporter: Bertrand Delacretaz
When upgrading a Sling instance, some bundles that were previously installed by
the BootstrapInstaller might need to be removed.
The BootstrapInstaller can currently update bundles, but not remove them.
To implement this in an extensible way, we can add a sling_bootstrap.txt
command file that is processed by the BootstrapInstaller once at startup, as
follows:
1. sling_bootstrap.txt is found at the root of the sling home folder
2. If it exists, it is executed if its timestamp is greater than the one stored
by the BootstrapInstaller
3. The file contains commands to uninstall bundles, we can add new commands
later if needed
4. BootstrapInstaller stores a new timestamp after executing the file
# sling_bootstrap.txt example
# comments and blank lines are ignored
uninistall org.apache.sling.somebundle 1.0.4
# VersionRanges are supported
uninistall org.apache.sling.otherbundle [1.1, 1.2)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
