THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Sling IDE tooling 1.0
Table of Contents |
---|
The 1.0 release will be a release with minimal release which will allow users to sync content between their IDE and the repository.
...
- Does not work reliably if the DefaultGetServlet is not active for a certain resource
Eclipse implementation
High-level pieces
- WST Server - we will use the Eclipse web tools platform to provide UI elements ( server definition, start/stop actions, module deployments )
- Content module - we will define a content module which uses the transport API to sync content from the workspace into the repository. The mechanism is controlled by the WST server definitions
- Transport API bridge - links between the core transport APIs and the Eclipse build/resource APIs
We will inherit some code from the current implementation, and need to work out a way to export content from the repository into the workspace with the proposed UI flow.
Intellij Implementation
High-level pieces
- Application server - uses the IntelliJ application server framework
- Transport API bridge - links between the core transport APIs and the IntelliJ build/resource APIs