Hi all, We currently have a multi-faceted issue: We have the Sling API bundle containing a number of utility classes (HtmlResponse, ResourceUtil). In addition there are two utility classes in the Engine bundle (RequestUtil, ResourceUtil) which are of general interest.
The problem with the locations of these classes are (1) mixing implementations into an API bundle is problematic, (2) extending implementations means increasing the API version, (3) using the Engine bundle utilities creates a dependency on the Engine bundle. I think we should create a new Utilities bundle which will host these utility classes. The classes are simply copied and then further developed in the new utilities bundle while the old classes are simply deprecated and removed in future versions. This will keep the classes distinct and not create a dependency to the new util bundle in the API bundle. WDYT ? Regards Felix
