You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2009/11/26 17:24:39 UTC
[jira] Resolved: (SLING-1101) sling_bootstrap.txt: run-once command
file for the BootstrapInstaller
[ https://issues.apache.org/jira/browse/SLING-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz resolved SLING-1101.
----------------------------------------
Resolution: Fixed
Fix Version/s: Launchpad Base 2.2.0
Assignee: Bertrand Delacretaz
Implemented in revision 884622
One slight difference with the above "spec", if the version of the bundle used in the uninstall command is a simple version number like 1.0.0 it is transformed to a range like [1.0.0,1.0.0] to mean "1.0.0 and nothing else". The default behavior of the VersionRange in this case would be to say "1.0.0 and everything above that" which is IMO counter-intuitive in this case.
To put it simply, just a version means "exactly this" whereas a range (i.e. a string that contains a comma) is handled by the org.apache.felix.framework.util.VersionRange class.
> 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
> Assignee: Bertrand Delacretaz
> Fix For: Launchpad Base 2.2.0
>
>
> 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.