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 2010/08/24 15:05:16 UTC

[jira] Updated: (SLING-755) jcrinstall console plugin

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

Carsten Ziegeler updated SLING-755:
-----------------------------------

    Fix Version/s:     (was: JCR Install 2.0.4)

Unscheduling this from JCR 2.0.4 as we are working on JCR 3.0.0 now

> jcrinstall console plugin
> -------------------------
>
>                 Key: SLING-755
>                 URL: https://issues.apache.org/jira/browse/SLING-755
>             Project: Sling
>          Issue Type: Improvement
>          Components: Installer
>            Reporter: Bertrand Delacretaz
>            Priority: Minor
>
> (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.