You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Dominik Süß (JIRA)" <ji...@apache.org> on 2019/03/06 12:55:00 UTC
[jira] [Commented] (JCRVLT-332) JcrPackageRegistry / JcrPackageImpl
cannot deal with dependencies satisfied by FsPackageRegistry
[ https://issues.apache.org/jira/browse/JCRVLT-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16785594#comment-16785594 ]
Dominik Süß commented on JCRVLT-332:
------------------------------------
[~tripod] - patch proposal to be found under https://github.com/apache/jackrabbit-filevault/pull/41
> JcrPackageRegistry / JcrPackageImpl cannot deal with dependencies satisfied by FsPackageRegistry
> ------------------------------------------------------------------------------------------------
>
> Key: JCRVLT-332
> URL: https://issues.apache.org/jira/browse/JCRVLT-332
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: Packaging
> Affects Versions: 3.2.6
> Reporter: Dominik Süß
> Priority: Major
>
> The internal dependency checks of JcrPackageImpl as triggered via PackageManger or the JcrPackageRegistry directly are not taking the FSPackageRegistry into account. Therefore if a package installed via PackageManger might fail with the following errormessage:
> {code}
> Error: Refusing to install package test:depends-on-immutable-package:1.0.0. required dependencies missing: [test/dependency:1.0.0]
> {code}
> To resolve this the initialization of packagemanager that happens via the PackagingImpl (OSGi Service) should inject the FSPackageRegistry if present and adjust the resolution & dependency check logic to also consider packages from the FSPackageRegistry.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)