You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2017/03/31 05:47:42 UTC
[jira] [Updated] (SLING-6723) Make dependency to javax.jcr,
jcr.contentloader and jcr.api optional
[ https://issues.apache.org/jira/browse/SLING-6723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-6723:
------------------------------------
Description:
In order to be able to run Sling in a very minimal version, the dependencies to javax.jcr, jcr.api and jcr.contentloader should be optional. Otherwise a whole set of modules needs to be dragged in just to make the servlets post module provide the basic functionality (which is usually sufficient for most applications)
It seems with minimizing the dependency to JCR we can also clean up the code as it is quiet of often adapting to JCR objects for no real reason and in some cases mixing resource and node handling, where just sticking with one or the other would do less operations
was:In order to be able to run Sling in a very minimal version, the dependencies to javax.jcr, jcr.api and jcr.contentloader should be optional. Otherwise a whole set of modules needs to be dragged in just to make the servlets post module provide the basic functionality (which is usually sufficient for most applications)
> Make dependency to javax.jcr, jcr.contentloader and jcr.api optional
> --------------------------------------------------------------------
>
> Key: SLING-6723
> URL: https://issues.apache.org/jira/browse/SLING-6723
> Project: Sling
> Issue Type: Improvement
> Components: Servlets
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Servlets Post 2.3.16
>
>
> In order to be able to run Sling in a very minimal version, the dependencies to javax.jcr, jcr.api and jcr.contentloader should be optional. Otherwise a whole set of modules needs to be dragged in just to make the servlets post module provide the basic functionality (which is usually sufficient for most applications)
> It seems with minimizing the dependency to JCR we can also clean up the code as it is quiet of often adapting to JCR objects for no real reason and in some cases mixing resource and node handling, where just sticking with one or the other would do less operations
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)