THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
This page contains a minimal test set to be executed before releasing the Sling IDE Tooling. This is of course to be done in addition to run the integration tests, which ensure a minimal baseline.
Synchronising content automatically to the server
- Start up a Sling Starter instance (from outside Eclipse)
- Use the wizard to create a new Sling content project
- Associate the module to the Sling server
- Deploy the module to Sling
- Verify that the initial changes were deployed
- Verify that incremental changes are deployed ( e.g. change jcr:description in the
.content.xml
file manually )
Importing content manually from the server
- Edit the filter.xml file and add the following filter entry
<filter root="/slingshot"/>
- Right-click on the
jcr_root
directory, select Import from server and press finish
Exporting content manually to the server
- Disable automatic sync for the server ( Publishing → Never publish automatically )
- Create a new folder under
/jcr_root/apps/example/
and add a file in it. - Right-click on
jcr_root
, select Export to server and press finish - Verify that the newly added folder and file are present in the repository
- Re-enable automatic sync
Deploying an OSGi bundle using the fileystem
- Use the wizard to create a new Sling bundle project
- Deploy it on the server from the last step
- Verify that the bundle is present in the OSGi runtime
- Uninstall the bundle from the OSGi runtime
Deploying an OSGi bundle using upload
- Change the sling server to Install bundles on server via bundle upload
- Make a change in the recently created bundle
- Verify that the bundle is present in the OSGi runtime
- Uninstall the bundle from the OSGi runtime
- Change the sling server to install bundles on server directly from the filesystem