sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bertrand Delacretaz (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (SLING-755) Move /system/sling/jcrinstall servlet to its own bundle
Date Wed, 03 Dec 2008 17:41:44 GMT

     [ https://issues.apache.org/jira/browse/SLING-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bertrand Delacretaz resolved SLING-755.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: JCR Install 2.0.4

extensions/jcrinstall/servlet module added in revision 722981 - sorry, didn't take time to
look at the optional dependencies options, that's one more bundle that does not much I think
it's cleaner in this way.

> Move /system/sling/jcrinstall servlet to its own bundle
> -------------------------------------------------------
>
>                 Key: SLING-755
>                 URL: https://issues.apache.org/jira/browse/SLING-755
>             Project: Sling
>          Issue Type: Improvement
>          Components: JCR Install
>            Reporter: Bertrand Delacretaz
>            Priority: Minor
>             Fix For: JCR Install 2.0.4
>
>
> Making a servlet out of the jcrinstall RepositoryObserver class introduces dependencies
on the sling api and servlet bundles, which are not desired for jcrinstall - its dependencies
should be kept to a minimum.
> I'll move the servlet to its own bundle - it is currently only needed for integration
testing, but might be useful for other monitoring purposes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message