Improve bundle update handling
------------------------------
Key: SLING-895
URL: https://issues.apache.org/jira/browse/SLING-895
Project: Sling
Issue Type: Bug
Components: JCR Install
Affects Versions: JCR Install 2.0.4
Reporter: Felix Meschberger
JCR Install's support for bundle installation, update, uninstallation currently
works on the bundle "file" names to check for bundle existence and update.
Consider the name of bundle files to contain their version numbers, so that for
example
org.apache.sling.api-2.0.2-incubator.jar
and org.apache.sling.api-2.0.3-incubator-SNAPSHOT.jar
refer to the same bundle (as per its symbolic name) but different versions of
it.
So to upgrade the org.apache.sling.api bundle we could -- in a single JCR
Session transaction -- remove the file org.apache.sling.api-2.0.2-incubator.jar
and add the new file org.apache.sling.api-2.0.3-incubator-SNAPSHOT.jar. This
causes JCR Install to recognize and act as follows:
* uninstall the bundle since the bundle file has been removed
* install the bundle since the bundle file has been added
What should in fact happen is, that JCR Install recognizes, that the new file
is really an update for the bundle installed from the old (now removed) file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
