[
https://issues.apache.org/jira/browse/SLING-11728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17695196#comment-17695196
]
Carsten Ziegeler edited comment on SLING-11728 at 3/1/23 4:36 PM:
------------------------------------------------------------------
As I said, we did this in the past without issues - why should it be one now?
If we have to change the major version, than lets forget about this change. Its
not worth breaking every use for an API which is a little bit cleaner
was (Author: cziegeler):
As I said, we did this in the past without issues - why should it be one now?
> Remove bi-directional dependencies between Engine and Servlets Resolver
> -----------------------------------------------------------------------
>
> Key: SLING-11728
> URL: https://issues.apache.org/jira/browse/SLING-11728
> Project: Sling
> Issue Type: Improvement
> Components: API, Engine, Servlets
> Affects Versions: Engine 2.12.0
> Reporter: Oliver Lietz
> Assignee: Oliver Lietz
> Priority: Major
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> *Situation*
> * bundle {{org.apache.sling.engine}} requires a {{ServletResolver}} which is
> provided by bundle {{org.apache.sling.servlets.resolver}}
> * bundle {{org.apache.sling.servlets.resolver}} depends on
> {{org.apache.sling.engine.servlets}} API
> The bi-directional dependencies between Engine and Servlets Resolver prevent
> the creation of meaningful and light deployment units (testing, features).
> *Options*
> # Merge {{org.apache.sling.engine}} and
> {{org.apache.sling.servlets.resolver}} into a single entity (bundle)
> # Move {{org.apache.sling.engine.servlets.ErrorHandler}} into Sling API
> (package {{org.apache.sling.api.servlets}}) and adjust usage in Servlets
> Resolver
> # Keep as is – leading to bigger, less manageable deployment units
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
