...
The tooling supports content and bundle modules. Content modules typically hold Sling scripts - like JSP and ESP files, client-side resources like CSS and JSS file, but also arbitrary repository content. Content modules support support setting JCR properties for nodes other than nodes and files, based on the FileVault serialization format. You can read mode about FileVault at the Apache Jackkrabit FileVault docs Bundle modules represent a single OSGi bundle.
...
- port: used for connecting to the server
- publishing interval: controls how fast the resources will be published after a change. We recommend setting the interval to 0, for fast deploy times
- username, password, context path: controls the connection details to the CQ Sling instance.
- debug port: used for connecting in debug mode
Image Removed
For working with OSGi bundles, a special support bundle must be installed to support fast bundle redeployment. If it is not present, you can install it using the hyperlink from the Install section.
Image Added
You can now connect to the server
...
Filtering topics - including filter.xml definition
Bundle sync
The only requirement for bundle projects is that they are Java projects which generate an exploded OSGi bundle in their output directory. That requires at least a valid OSGi Manifest located in META-INF/MANIFEST.MF, but typically one of more Java classes. Other
auxiliary files, such as Declarative Service descriptors, must also be placed under the project's output directory.
Troubleshooting
Gathering debug information
...