You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by ro...@apache.org on 2016/03/14 09:55:47 UTC

svn commit: r1734893 - /sling/site/trunk/content/documentation/development/ide-tooling.mdtext

Author: rombert
Date: Mon Mar 14 08:55:47 2016
New Revision: 1734893

URL: http://svn.apache.org/viewvc?rev=1734893&view=rev
Log:
Sling IDE Tooling 1.1 - fix docs

Modified:
    sling/site/trunk/content/documentation/development/ide-tooling.mdtext

Modified: sling/site/trunk/content/documentation/development/ide-tooling.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/ide-tooling.mdtext?rev=1734893&r1=1734892&r2=1734893&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/ide-tooling.mdtext (original)
+++ sling/site/trunk/content/documentation/development/ide-tooling.mdtext Mon Mar 14 08:55:47 2016
@@ -176,6 +176,30 @@ To deploy a project on the server, open
 
 After OSGi bundle projects are deployed, each change will cause the bundle to be redeployed on the server.
 
+## Sightly support
+
+_Available with Sling IDE Tooling for Eclipse 1.1 or newer_
+
+Sightly support has been added through an additional, optional, feature named _Sling IDE Tools - Sightly Integration_.
+
+This feature provides the following enhancements:
+
+* auto-completion of tag named and attributes names in the HTML Editor
+* wizards for creating new Sightly scripts and Use Classes ( Java and Javascript )
+* Sightly-aware validation for HTML files
+
+![Sightly Editor](ide-tooling/sightly-editor.png)
+
+These enhancements are enabled once the Sightly facet is added to a project. This is done automatically when converting a project to content project, but can also be done manually via the project properties, under the _Project Facets_ page.
+
+## Debugging
+
+When first connecting to a Sling instance in debug mode, the IDE tooling tries to bind all the sources associated with the bundles deployed on the server and retrieves the associated source artifacts using Maven. Therefore, the debug classpath is as close as possible to sources used to build the bundles deployed on the server.
+
+![Debugging](ide-tooling/debug.png)
+
+Since a first source bundle resolution can potentially take a long time, this behaviour can be disabled from the server configuration page.
+
 ## Troubleshooting
 
 ### Gathering debug information
@@ -201,30 +225,6 @@ Bundle deployment assumes that the OSGi
 
 One often-occuring situation is that a Maven project using the maven-scr-plugin generates the descriptors outside of target/classes, typically in target/scr-plugin-generated. To fix this, make sure that you're using the maven-scr-plugin 1.15.0 or newer and that you have not set a custom outputDirectory.
 
-## Sightly support
-
-_Available with Sling IDE Tooling for Eclipse 1.1 or newer_
-
-Sightly support has been added through an additional, optional, feature named _Sling IDE Tools - Sightly Integration_.
-
-This feature provides the following enhancements:
-
-* auto-completion of tag named and attributes names in the HTML Editor
-* wizards for creating new Sightly scripts and Use Classes ( Java and Javascript )
-* Sightly-aware validation for HTML files
-
-![Sightly Editor](../documentation/development/ide-tooling/sightly-editor.png)
-
-These enhancements are enabled once the Sightly facet is added to a project. This is done automatically when converting a project to content project, but can also be done manually via the project properties, under the _Project Facets_ page.
-
-## Debugging
-
-When first connecting to a Sling instance in debug mode, the IDE tooling tries to bind all the sources associated with the bundles deployed on the server and retrieves the associated source artifacts using Maven. Therefore, the debug classpath is as close as possible to sources used to build the bundles deployed on the server.
-
-![Debugging](../documentation/development/ide-tooling/debug.png)
-
-Since a first source bundle resolution can potentially take a long time, this behaviour can be disabled from the server configuration page.
-
 ## Known issues
 
 The content sync implementation tries to mimic the FileVault semantics as closely as possible. However, it is possible that some more exotic content structures will not be handled properly. Some of the problems we're are of are: