[jira] [Commented] (SLING-4667) Allow usage of the Sling IDE tooling in OSGi-only environments

["Robert Munteanu (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14526608#comment-14526608 ] 

Robert Munteanu commented on SLING-4667:
----------------------------------------

Attached a POC patch to be applied on top of trunk which shows where the current behaviour needs to be adjusted to support OSGi-only servers. This can also be used to test out the IDE tooling with a pure OSGi runtime ( where pure OSGi runtime means at least running the Felix console at /system/console )

> Allow usage of the Sling IDE tooling in OSGi-only environments
> --------------------------------------------------------------
>
>                 Key: SLING-4667
>                 URL: https://issues.apache.org/jira/browse/SLING-4667
>             Project: Sling
>          Issue Type: New Feature
>          Components: IDE
>    Affects Versions: Sling Eclipse IDE 1.0.6
>            Reporter: Robert Munteanu
>             Fix For: Sling Eclipse IDE 1.1.0
>
>         Attachments: SLING-4667-poc.diff
>
>
> The IDE tooling is quite usable for OSGi-only development on top of Apache Sling. However, the tooling always connects to the repository at startup:
> {code:java}Command<ResourceProxy> command = repository.newListChildrenNodeCommand("/");{code}
> We should have a more fine-grained approach and support environments where the JCR webdav entry point is not available.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)