hello antonio. this sounds interesting!
what is the difference to the filesystem resource provider with which you can mount any folder in the filesystem to a JCR tree? the filesystem resource provider currently only supports nt:file and nt:folder nodes, but works very well for those (e.g. jsp, css, javascript files). if i find some time i planned to improve the filesystem resource provider to support other JCR content structures stored in JSON files in the file system as well. this would be independent from any IDE and its plugin system. stefan >-----Original Message----- >From: Antonio Sanso [mailto:[email protected]] >Sent: Thursday, October 25, 2012 2:34 PM >To: [email protected] >Subject: [Tooling] Experimental Plugin for Eclipse for Sling aka Slingclipse > >Hi *, > >I have started to work on an experimental plugin for Eclipse for Sling named >(at least for now :)) Slingclipse, see [0]. > >Slingclipse is an attempt to make easier the development phase while using >Sling. >The scope is still open and I would be more than glad to hear some >feedbacks/ideas. > >What I have committed for now are 3 plugins/bundles: > >- org.apache.sling.slingclipse >- org.apache.sling.slingclipse.api >- org.apache.sling.slingclipse.http > >The idea implemented for now is that at any save (this is configurable) the >correspondent "action" will be "transmitted" in the repository (only if if >this is in a project with a path name for the file that contains jcr_root to >be precise). >The "actions" implemented for now are: > >- create a new file: the file is created also in the repository (if the file >is not empty, is a bug) >- change the content of a file: the file is modified in the repository >- delete a file: the file is deleted in the repository > >The trigger is the save action in Eclipse. >At the moment there is not support for any jcr type other than nt:file (but >this is going to improve). >Another important thing to highlight for the moment is the way this >information is "transmitted" from the file system to the repository. >Slingclipse uses Declarative Service and the implemented solution uses HTTP >for now (org.apache.sling.slingclipse.http bundle). >Should somebody else would like to use some other way to achieve the same >result is enough to create another bundle implementing the api contained in >the org.apache.sling.slingclipse.api bundle, > >I would try to create some basic documentation somewhere in the wiki soon > >Regards > >Antonio > >[0] http://svn.apache.org/viewvc/sling/whiteboard/asanso/plugins/eclipse/
