[
https://issues.apache.org/jira/browse/SLING-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-755:
--------------------------------------
Description:
(changed title as discussion moved to creating a console plugin)
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.
was:
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.
Summary: jcrinstall console plugin (was: Move /system/sling/jcrinstall
servlet to its own bundle)
> jcrinstall console plugin
> -------------------------
>
> 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
>
>
> (changed title as discussion moved to creating a console plugin)
> 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.
