...
The 1.0 release will be a release with minimal release which will allow users to sync content between their IDE and the repository. Also see the Use Cases page for a list of use cases we want to support, either in the initial or in the subsequent releases.
See also the Moving forward with IDE tooling discussion on the Sling dev mailing list for a more in-depth discussion on some of the technical issues.
Naming
Our IDE tooling should not focus on a single IDE and the naming should reflect that. Possible names
...
This may or may not be the ideal format for our IDE tooling. One serious drawback is that 'dot-files' are hidden by default in IDEs and the command-line. Auto-sync is also not possible for .content.xml files for now , possibly for performance reasons
We can ( and probably should ) define our own resource serialization format. One proposal is
...
- Does not work reliably if the DefaultGetServlet is not active for a certain resource
Resource editor
Include a basic resource editor which works with the files defined by our serialization format.
Eclipse implementation
High-level pieces
...