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 2018/01/21 20:19:36 UTC

[sling-site] 04/04: Final touches to Sling IDE Tooling 1.2.0 release notes and documentation page

This is an automated email from the ASF dual-hosted git repository.

rombert pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git

commit baa1b855540fdd958e5c24c77098a1144a5c293e
Author: Robert Munteanu <ro...@apache.org>
AuthorDate: Sun Jan 21 22:10:43 2018 +0200

    Final touches to Sling IDE Tooling 1.2.0 release notes and documentation page
---
 .../ide-tooling/content-sync-exclusions.png           | Bin 0 -> 20864 bytes
 .../content/documentation/development/ide-tooling.md  |  18 +++++++++++++++++-
 .../content/news/sling-ide-tooling-12-released.md     |  13 +++++++------
 3 files changed, 24 insertions(+), 7 deletions(-)

diff --git a/src/main/jbake/assets/documentation/development/ide-tooling/content-sync-exclusions.png b/src/main/jbake/assets/documentation/development/ide-tooling/content-sync-exclusions.png
new file mode 100644
index 0000000..54dc226
Binary files /dev/null and b/src/main/jbake/assets/documentation/development/ide-tooling/content-sync-exclusions.png differ
diff --git a/src/main/jbake/content/documentation/development/ide-tooling.md b/src/main/jbake/content/documentation/development/ide-tooling.md
index b0e98cc..ac4577d 100644
--- a/src/main/jbake/content/documentation/development/ide-tooling.md
+++ b/src/main/jbake/content/documentation/development/ide-tooling.md
@@ -98,7 +98,9 @@ Note that deploying a project on the server publishes all the resources from the
 
 #### Automatic conversion
 
-Maven projects configured using the `com.day.jcr.vault:content-package-maven-plugin` are now automatically configured as content projects, removing the need to manually add the needed facets after importing them into Eclipse for the first time.
+_Support for the filevault-package-maven-plugin is available with Sling IDE Tooling for Eclipse 1.2 or newer_
+
+Maven projects configured using the `com.day.jcr.vault:content-package-maven-plugin` or the `org.apache.jackrabbit:filevault-package-maven-plugin` are now automatically configured as content projects, removing the need to manually add the needed facets after importing them into Eclipse for the first time.
 
 The following pom properties can be used to tweak how the project is configured
 
@@ -108,6 +110,12 @@ The following pom properties can be used to tweak how the project is configured
 | `sling.ide.m2e.contentpackage.javaFacetVersion` | Controls the version of the Java Facet which is added to the project, e.g. `8` |
 | `sling.ide.m2e.contentpackage.webFacetVersion` | Controls the version of the Web Facet which is added to the project, e.g. `3.0` |
 
+_Available with Sling IDE Tooling for Eclipse 1.2 or newer_
+
+Additionally, automatic conversion and the addition of WTP natures and facets can be disabled from the _Sling IDE_ → _Maven Project Configurators_ preferences page.
+
+![Maven Project Configurator preferences](ide-tooling/maven-configurators-preferences.png)
+
 #### Manual conversion
 
 To mark a project as being a Sling content module, click it in the Project Explorer and Select Configure -> Convert to Sling Content Project... . A dialog will pop up and will ask you to confirm the inferred location of the jcr_root directory. You can also change this from the project properties, the Sling page.
@@ -146,6 +154,14 @@ The import wizard is available under the Sling -> Import Content ... action.
 
 ![Repository import](ide-tooling/repository-import.png)
 
+### Excluding paths from the sync process
+
+_Available with Sling IDE Tooling for Eclipse 1.2 or newer_
+
+The _Sling IDE_ preferences page allows you to manage a global list of files names which will not be synchronized.
+
+![Content sync exclusions](ide-tooling/content-sync-exclusions.png)
+
 ## 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.
diff --git a/src/main/jbake/content/news/sling-ide-tooling-12-released.md b/src/main/jbake/content/news/sling-ide-tooling-12-released.md
index 9186336..4dfd570 100644
--- a/src/main/jbake/content/news/sling-ide-tooling-12-released.md
+++ b/src/main/jbake/content/news/sling-ide-tooling-12-released.md
@@ -4,7 +4,9 @@ status=published
 tags=ide,eclipse
 ~~~~~~
 
-Here are some of the more noteworthy things available in this release.
+This page contains information about the new features in the Sling IDE Tooling 1.2.0 release. For
+a full overview of the features and installation instructions, please see the 
+[Sling IDE Tooling](/documentation/development/ide-tooling.html) documentation page.
 
 # Custom contribution for provisioning model feature files
 
@@ -31,18 +33,17 @@ The Maven project configurators for content bundle projects can now be enabled a
 workspace level. Additionally, only the additional WTP natures and facets can be disabled for content
 projects.
 
-The preferences can be accesed via _Preferences_ → _Sling IDE_ → _Maven Project Configurator_.
+The preferences can be accesed via _Sling IDE_ → _Maven Project Configurator_ preference page.
 
-![Maven Project Configuratir preferences](/documentation/development/ide-tooling/maven-configurators-preferences.png)
+![Maven Project Configurator preferences](/documentation/development/ide-tooling/maven-configurators-preferences.png)
 
 # Support for the bnd-maven-plugin
 
 Projects configured usign the `bnd-maven-plugin` are now properly configured as bundle projects. Previously
 only the `maven-bundle-plugin` was supported.
 
-# Support for the new Jackrabbit content-package-plugin
+# Support for the new Jackrabbit filevault-package-maven-plugin
 
-Projects configured using the `content-package-plugin` from Apache Jackrabbit are now properly configured as
+Projects configured using the `filevault-package-maven-plugin` from Apache Jackrabbit are now properly configured as
 content projects. Previously only the `content-package-maven-plugin`
 
-For more information, see the [Sling IDE Tooling for Eclipse documentation page](/documentation/development/ide-tooling.html).

-- 
To stop receiving notification emails like this one, please contact
"commits@sling.apache.org" <co...@sling.apache.org>.