You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2018/01/17 21:37:06 UTC
[jira] [Updated] (SLING-4667) Allow usage of the Sling IDE tooling
in OSGi-only environments
[ https://issues.apache.org/jira/browse/SLING-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Munteanu updated SLING-4667:
-----------------------------------
Fix Version/s: (was: Sling Eclipse IDE 1.2.0)
Sling Eclipse IDE 1.2.2
> 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
> Priority: Major
> Fix For: Sling Eclipse IDE 1.2.2
>
> 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
(v7.6.3#76005)