[
https://issues.apache.org/jira/browse/JCRVLT-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16892610#comment-16892610
]
Konrad Windszus commented on JCRVLT-232:
----------------------------------------
Removing OSGi bundles and configuration should also be forbidden in
{{application}} and {{content}} packages. In that case this must rather be a
best guess, as one cannot be sure at build time, if a filter root like
{{/apps/myapp/install}} will actually remove a bundle/config at installation
time...
[~tripod] Any idea on how to check this properly as the JCR Installer in Sling
(IMHO the only feature which deploys OSGi bundles/configuration from a
repository into the OSGi container) can be freely configured to only consider
certain node names (configuration might differ from server to server) and even
supports run mode specific deployments
(https://sling.apache.org/documentation/bundles/jcr-installer-provider.html).
> Enforce constraints for package types
> -------------------------------------
>
> Key: JCRVLT-232
> URL: https://issues.apache.org/jira/browse/JCRVLT-232
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: package maven plugin
> Affects Versions: package-maven-plugin-1.0.0
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
>
> Currently the package type only affects how the dependencies are considered
> to check for invalid filter rules (and only for package type "application").
> This contradicts the javadoc of the parameter which states that
> {quote}'application' and 'content' packages are not allowed to contain sub
> packages or embedded bundles.{quote}
> (https://github.com/apache/jackrabbit-filevault-package-maven-plugin/blob/02a853e64d985f075fe88d19101d7c66d741767f/src/main/java/org/apache/jackrabbit/filevault/maven/packaging/AbstractPackageMojo.java#L104)
> As long as this is not enforced during package build time please only list
> the enforced limitations of the according package types.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
