[
https://issues.apache.org/jira/browse/SLING-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-2569.
-------------------------------------
Resolution: Won't Fix
While this sounds like a good idea, I think this is probably a little bit
confusing. In the end a bundle has requirements whether that be package
imports, the java environment, or general requirements. Not installing a bundle
because *some* of them are not met while installing it while *others* like
package imports are not met is inconsistent.
> Don't install bundles under certain circumstances
> -------------------------------------------------
>
> Key: SLING-2569
> URL: https://issues.apache.org/jira/browse/SLING-2569
> Project: Sling
> Issue Type: New Feature
> Components: Installer
> Affects Versions: Installer Core 3.3.8
> Reporter: Felix Meschberger
> Priority: Major
>
> Currently bundles are always installed or updated by the OSGi Installer's
> BundleInstallTask. This should be changed to take certain bundle manifest
> headers into account:
> * The Bundle-RequiredExecutionEnvironment header should be respected
> * The new Bundle-Requirement headers should be respected
> Support for the first header is available on all framework while the second
> header can only be supported by newer platforms. The implementation should
> support both options if supported by the platform and fall back to the first
> if the second is not supported.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
