[
https://issues.apache.org/jira/browse/SLING-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778898#action_12778898
]
Felix Meschberger commented on SLING-1189:
------------------------------------------
> Felix - I don't understand what you mean here:
> > To ensure no bundles from a launcher will ever be installed, I suggest the
> > bar launcher application (or launcher web
> > application) from the launchpad/base module is used for launching.
The launchpad/base module generates three artifacts:
(1) the "launcher JAR", which actually is the OSGi framework plus the common
boot strap stuff, including the BootstrapInstaller class
(2) the standalone application, which is just the Main class and cuntionality
to load the launcher JAR and kick the OSGi framework
(2) the web application, which is the same as the standalone application but
for deployment in a servlet container
The launchpad/app and launchpad/webapp modules currently take the bare
launchers from the base module and glue them together into a fat jar or war
file containing a set of bundles and the launcher JAR file for launching.
What I mean is, that instead of running the result of launchpad/app or
launchpad/webapp build you may as well run the bare application (1) or web
application (2) from the launchpad/base -- provided you of course have a
configured ${sling.home} folder. This way, nothing will ever be
installed/updated unless explicitly placed into the ${sling.home}/startup
folder.
> When comparing SNAPSHOT-versioned bundles, also check the Bnd-LastModified
> Header
> ---------------------------------------------------------------------------------
>
> Key: SLING-1189
> URL: https://issues.apache.org/jira/browse/SLING-1189
> Project: Sling
> Issue Type: Improvement
> Components: Launchpad
> Reporter: Justin Edelson
> Attachments: SLING-1189.patch
>
>
> As an enhancement to the functionality provided with SLING-1162, if a bundle
> in resources/bundles/<startlevel> is already installed with the same version
> and the version ends in SNAPSHOT, if both bundles include a Bnd-LastModified
> header, use that header as an additional check.
> The current implementation fails under this use case:
> 1) SNAPSHOT included in the WAR/JAR file.
> 2) newer SNAPSHOT installed via console/shell
> 3) App is restarted
> At this point, the original SNAPSHOT will be installed, not the newer one
> included.
> I'll have a patch for this soonish.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
