[ https://issues.apache.org/jira/browse/SLING-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Munteanu resolved SLING-4667. ------------------------------------ Fix Version/s: (was: Sling Eclipse IDE 2.0.0) Resolution: Won't Fix > 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 > 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 (v8.20.10#820010)