[
https://issues.apache.org/jira/browse/JCRVLT-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated JCRVLT-660:
-----------------------------------
Description:
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 and there is also code exclusively used
on client (which requires jcr2spi and spi2dav).
It would be good to split that into three pieces
1) The server bundle
2) The common bundle-fragment
* Does not contain any OSGi Declarative Services
* Does not have a dependency on a running JCR or Sling
* Does have only few external dependencies
3) A client JAR
The split up is a bit tricky though as it shouldn't lead to split packages on
the server side.
Currently the core bundle depends on spi2dav and jcr2spi, although only really
necessary on a client.
was:
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 and there is also code exclusively used
on client (which requires jcr2spi and spi2dav).
It would be good to split that into three pieces
1) The server bundle
2) The common bundle-fragment
* Does not contain any OSGi Declarative Services
* Does not have a dependency on a running JCR or Sling
* Does have only few external dependencies
3) A client JAR
The split up is a bit tricky though as it shouldn't lead to split packages on
the server side.
Currently the core bundle depends on spi2dav and jcr2spi, although only really
necessary on a client.
> 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 and there is also code
> exclusively used on client (which requires jcr2spi and spi2dav).
> It would be good to split that into three pieces
> 1) The server bundle
> 2) The common bundle-fragment
> * Does not contain any OSGi Declarative Services
> * Does not have a dependency on a running JCR or Sling
> * Does have only few external dependencies
> 3) A client JAR
> The split up is a bit tricky though as it shouldn't lead to split packages on
> the server side.
> Currently the core bundle depends on spi2dav and jcr2spi, although only
> really necessary on a client.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
