[
https://issues.apache.org/jira/browse/JCRVLT-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17610371#comment-17610371
]
Konrad Windszus commented on JCRVLT-660:
----------------------------------------
One possibility is to rely on bundle fragments, so that the packaging parts
come as fragment for the core.
> Split up vault-core by server-side code and common code
> -------------------------------------------------------
>
> Key: JCRVLT-660
> URL: https://issues.apache.org/jira/browse/JCRVLT-660
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Reporter: Konrad Windszus
> Priority: Major
>
> FileVault Core is used not only on the server side (with the underlying
> repository) providing things like PackageManager, Package Registry but also
> common code used by both client side tools (e.g. Vlt, FileVault Content
> Package Maven Plugin, Sling IDE Tooling, Sling Content Package to Feature
> Model Converter, ...) and the server bundle.
> It would be good to split that up so that the latter:
> * Does not contain any OSGi Declarative Services
> * Does not have a dependency on a running JCR or Sling
> * Does have only few external dependencies
> The split up is a bit tricky though as it shouldn't lead to split packages.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
