You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by ss...@apache.org on 2017/03/10 00:03:22 UTC
svn commit: r1786260 - in /sling/site/trunk/content/documentation:
development.mdtext development/htl-maven-plugin.mdtext
development/release-management.mdtext development/sling.mdtext
development/slingstart.mdtext
Author: sseifert
Date: Fri Mar 10 00:03:22 2017
New Revision: 1786260
URL: http://svn.apache.org/viewvc?rev=1786260&view=rev
Log:
publish maven site documentation for maven plugins:
- maven-sling-plugin
- htl-maven-plugin
- slingstart-maven-plugin
Modified:
sling/site/trunk/content/documentation/development.mdtext
sling/site/trunk/content/documentation/development/htl-maven-plugin.mdtext
sling/site/trunk/content/documentation/development/release-management.mdtext
sling/site/trunk/content/documentation/development/sling.mdtext
sling/site/trunk/content/documentation/development/slingstart.mdtext
Modified: sling/site/trunk/content/documentation/development.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development.mdtext?rev=1786260&r1=1786259&r2=1786260&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development.mdtext (original)
+++ sling/site/trunk/content/documentation/development.mdtext Fri Mar 10 00:03:22 2017
@@ -32,9 +32,10 @@ Look here for more information on develo
Sling is using Apache Maven 3 as its build system. Over time we have created a number of Maven 3 plugins and gathered a whole range of knowledge about using Maven.
-* [Maven Sling Plugin]({{ refs.sling.path }})
+* [Maven Sling Plugin](http://sling.apache.org/components/maven-sling-plugin/)
+* [HTL Maven Plugin](http://sling.apache.org/components/htl-maven-plugin/)
+* [SlingStart Maven Plugin](http://sling.apache.org/components/slingstart-maven-plugin/)
* [Maven Launchpad Plugin]({{ refs.maven-launchpad-plugin.path }})
-* [HTL Maven Plugin]({{ refs.htl-maven-plugin.path }})
* [Maven JspC Plugin]({{ refs.jspc.path }})
* [Maven Archetypes]({{ refs.maven-archetypes.path }})
* [Maven Tips & Tricks]({{ refs.maventipsandtricks.path }})
Modified: sling/site/trunk/content/documentation/development/htl-maven-plugin.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/htl-maven-plugin.mdtext?rev=1786260&r1=1786259&r2=1786260&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/htl-maven-plugin.mdtext (original)
+++ sling/site/trunk/content/documentation/development/htl-maven-plugin.mdtext Fri Mar 10 00:03:22 2017
@@ -1,81 +1,3 @@
Title: HTL Maven Plugin
-The [Apache Sling HTL Maven Plugin](https://github.com/apache/sling/tree/trunk/tooling/maven/htl-maven-plugin), M2Eclipse compatible,
-provides support for validating HTML Template Language scripts from projects during build time.
-
-## Goals overview
-
-* [`htl:validate`](#htlvalidate) - validate the scripts from the build directory (`${project.build.sourceDirectory}`)
-
-## Usage
-
- <build>
- <plugins>
- <plugin>
- <groupId>org.apache.sling</groupId>
- <artifactId>htl-maven-plugin</artifactId>
- <version>1.0.6</version>
- <executions>
- <execution>
- <id>validate-scripts</id>
- <goals>
- <goal>validate</goal>
- </goals>
- <phase>compile</phase>
- </execution>
- </executions>
- </plugin>
- </plugins>
- </build>
-
-## `htl:validate`
-**Full name:** `org.apache.sling:htl-maven-plugin:1.0.0:validate`
-
-**Description:**
-Validates HTL scripts syntax during the build process.
-
-### Optional Parameters
-
-|Name |Type |Since |Description |
-|---------------------------------------------|------------|---------|--------------------------------------------------------------------------------------------------|
-| [`sourceDirectory`](#param-sourceDirectory) | `String` | `1.0.0` | Defines the root folder where this goal expects to find Sightly scripts to validate. |
-| [`includes`](#param-includes) | `String[]` | `1.0.0` | List of files to include, specified as fileset patterns which are relative to `sourceDirectory`. |
-| [`excludes`](#param-excludes) | `String[]` | `1.0.0` | List of files to exclude, specified as fileset patterns which are relative to `sourceDirectory`. |
-| [`failOnWarnings`](#param-failOnWarnings) | `boolean` | `1.0.0` | If set to `true` it will fail the build on compiler warnings. |
-
-### Parameter Details
-
-<a name="param-sourceDirectory"><code>sourceDirectory</code></a>:
-
-Defines the root folder where this goal expects to find Sightly scripts to validate.
-
-* **Type:** `java.lang.String`
-* **Required:** No
-* **User Property:** `sourceDirectory`
-* **Default:** `${project.build.sourceDirectory}`
-
-<a name="param-includes"><code>includes</code></a>:
-
-List of files to include, specified as fileset patterns which are relative to `sourceDirectory`.
-
-* **Type:** `java.lang.String[]`
-* **Required:** No
-* **User Property:** `includes`
-* **Default:** `**/*.html`
-
-<a name="param-excludes"><code>excludes</code></a>:
-
-List of files to exclude, specified as fileset patterns which are relative to `sourceDirectory`.
-
-* **Type:** `java.lang.String[]`
-* **Required:** No
-* **User Property:** `excludes`
-
-<a name="param-failOnWarnings"><code>failOnWarnings</code></a>:
-
-If set to `true` it will fail the build on compiler warnings.
-
-* **Type:** `boolean`
-* **Required:** No
-* **User Property:** `failOnWarnings`
-* **Default:** `false`
+See [Apache Sling HTL Maven Plugin documentation](http://sling.apache.org/components/htl-maven-plugin/).
Modified: sling/site/trunk/content/documentation/development/release-management.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/release-management.mdtext?rev=1786260&r1=1786259&r2=1786260&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/release-management.mdtext (original)
+++ sling/site/trunk/content/documentation/development/release-management.mdtext Fri Mar 10 00:03:22 2017
@@ -428,3 +428,34 @@ To update the OBR you may use the Apache
Wait for the buildbot to update the staging area with your site update (see dev list for an email).
Then go to the CMS at [https://cms.apache.org/redirect?uri=http://sling.apache.org/obr](https://cms.apache.org/redirect?uri=http://sling.apache.org/obr) ,
update your checkout and then publish the site.
+
+
+## Appendix D: Deploy Maven plugin documentation
+
+For Maven plugins the Maven Site generated documentation with a list of supported goals and properties has to be published on the Slind website as well.
+
+This is currently supported for:
+
+* `maven-sling-plugin`
+* `htl-maven-plugin`
+* `slingstart-maven-plugin`
+
+To publish the plugin documentation execute the following steps after the release:
+
+1. Checkout the release tag of the released plugin (or reset your workspace)
+
+2. Build and stage the maven site of the plugin
+
+ $ mvn clean site:site site:stage scm-publish:publish-scm
+
+3. Checkout the 'components' path of the Sling website
+
+ $ svn checkout https://svn.apache.org/repos/infra/websites/production/sling/content/components
+
+4. SVN-rename the generate documenation uploaded to `<plugin-name>-archives/<plugin-name>-LATEST` to `<plugin-name>-archives/<plugin-name>-<version>`
+
+5. SVN-remove the existing folder `<plugin-name>` and SVN-copy the folder `<plugin-name>-archives/<plugin-name>-<version>` to `<plugin-name>`
+
+6. Commit the changes.
+
+7. Check the documentation at http://sling.apache.org/components/
Modified: sling/site/trunk/content/documentation/development/sling.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/sling.mdtext?rev=1786260&r1=1786259&r2=1786260&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/sling.mdtext (original)
+++ sling/site/trunk/content/documentation/development/sling.mdtext Fri Mar 10 00:03:22 2017
@@ -1,295 +1,3 @@
Title: Maven Sling Plugin
-The Maven Sling Plugin provides a number of goals which may be of help while developping bundles for Sling. To run the plugin you need at least Maven 3.x and JDK 1.6 or higher. Maven Sling Plugin provides the following goals:
-
-| Name | Description |
-|--|--|
-| [sling:deploy](#the-deploy-goal) | Deploy an OSGi-bundle into the OBR running on a Sling instance. |
-| [sling:deploy-file](#the-deploy-file-goal) | Deploy an OSGi-bundle into the OBR running on a Sling instance without requiring a project descriptor file. |
-| [sling:install](#the-install-goal) | Install an OSGi-bundle into a running Sling instance. |
-| [sling:install-file](#the-install-file-goal) | Install an OSGi-bundle into a running Sling instance without requiring a project descriptor file. |
-| [sling:uninstall](#the-uninstall-goal) | Uninstall an OSGi-bundle from a running Sling instance. |
-| [sling:validate](#the-validate-goal) | Validate JSON files in module (used for initial content loading). |
-
-## Usage
-
-You should specify the version in your project's plugin configuration:
-
- <project>
- ...
- <build>
- <!-- To define the plugin version in your parent POM -->
- <pluginManagement>
- <plugins>
- <plugin>
- <groupId>org.apache.sling</groupId>
- <artifactId>maven-sling-plugin</artifactId>
- <version>2.1.6</version>
- </plugin>
- ...
- </plugins>
- </pluginManagement>
- <!-- To use the plugin goals in your POM or parent POM -->
- <plugins>
- <plugin>
- <groupId>org.apache.sling</groupId>
- <artifactId>maven-sling-plugin</artifactId>
- </plugin>
- ...
- </plugins>
- </build>
- ...
- </project>
-
-For more information, see ["Guide to Configuring Plug-ins"](http://maven.apache.org/guides/mini/guide-configuring-plugins.html)
-
-## The `deploy` goal
-
-The `deploy` goal uploads a bundle to a Sling OSGi Bundle Repository server implemented by the *sling-obr* bundle, which may be located on a remote system. The plugin places an HTTP `POST` request to the server sending the bundle file.
-
-### Use
-
-To use the `deploy` goal of the Maven Sling Plugin define the following elements in the `<plugins>` section of the POM:
-
- <?xml version="1.0" encoding="ISO-8859-1"?>
- <project>
- ....
- <build>
- ....
- <plugins>
- ....
- <plugin>
- <groupId>org.apache.sling</groupId>
- <artifactId>maven-sling-plugin</artifactId>
- <executions>
- <execution>
- <id>deploy-bundle</id>
- <goals>
- <goal>deploy</goal>
- </goals>
- </execution>
- </executions>
- </plugin>
- ....
- <plugins>
- ....
- <build>
- ....
- <project>
-
-
-### Configuration
-
-The `deploy` goal may be configured in the `<configuration>` element using the following properties:
-
-| Parameter | Default Value | System Property Overwrite | Description |
-|--|--|--|--|
-| `skip` | `false` | `sling.deploy.skip` | Whether to skip this step even though it has been configured in the project to be executed. The main use of this setting is preventing deployment of the bundle to a Sling OSGi Bundle Repository server if it is known that there is none or if such an upload is not required. |
-| `buildDirectory` | `${project.build.directory}` | \- | The path of the file to be installed |
-| `jarName` | `${project.build.finalName}.jar` | \- | The name of the file to be installed |
-| `obr` | \- | `obr` | The URL of the running Sling instance to which the bundle is installed. Note that this parameter is required and has no default value. It must always be specified in the configuration section or on the command line. |
-
-
-## The `deploy-file` goal
-
-The `deploy-file` goal is equivalent to the `deploy` goal except, that the `deploy-file` does not require a project descriptor file while the `deploy` goal does. In other words the `deploy-file` goal may used to upload any bundle file available to a Sling OBR server instance.
-
-### Use
-
-The `deploy-file` goal may only be used from the command line by explicitly calling it as in:
-
- $ mvn org.apache.sling:maven-sling-plugin:deploy-file -Dsling.file=<file> -Dobr=<url>
-
-Specifying the bundle file to upload with the `sling.file` property is required.
-
-### Configuration
-
-The `deploy-file` supports similar configuration parameters as the `deploy` goal with the exception of the `skip` parameter which makes no sense. In addition, all parameters must be specified on the command line by setting system properties. The `bundleFileName` parameter specified as the `sling.file` system property as well as the `obr` URL are required by the `deploy-file` goal.
-
-| Parameter | Default Value | System Property Overwrite | Description |
-|--|--|--|--|
-| `bundleFileName` | `${project.build.directory}/${project.build.finalName}.jar` | `sling.file` | The path and name of the file to be installed |
-| `obr` | \- | `obr` | The URL of the running Sling instance to which the bundle is installed. Note that this parameter is required and has no defualt value. It must always be specified in the configuration section or on the command line. |
-
-Example: To deploy the bundle file `someBundle.jar` to the OBR running at `[http://obr.sample.org](http://obr.sample.org)` you might use the goal as follows:
-
- $ mvn org.apache.sling:maven-sling-plugin:deploy-file -Dsling.file=someBundle.jar -Dobr=http://obr.sample.org
-
-
-## The `install` goal
-
-The `install` goal uploads a bundle to a running sling instance, which may be located on a remote system. The plugin places an HTTP `POST` request to [Felix Web Console](http://felix.apache.org/documentation/subprojects/apache-felix-web-console/web-console-restful-api.html#post-requests). It's also possible to HTTP `PUT` instead of `POST` leveraging the [WebDAV bundle from Sling]({{ refs.repository-based-development.path }}). Since version 2.1.8 you can also leverage the Sling POST servlet for that.
-
-### Use
-
-To use the `install` goal of the Maven Sling Plugin define the following elements in the `<plugins>` section of the POM:
-
- <?xml version="1.0" encoding="ISO-8859-1"?>
- <project>
- ....
- <build>
- ....
- <plugins>
- ....
- <plugin>
- <groupId>org.apache.sling</groupId>
- <artifactId>maven-sling-plugin</artifactId>
- <executions>
- <execution>
- <id>install-bundle</id>
- <goals>
- <goal>install</goal>
- </goals>
- </execution>
- </executions>
- </plugin>
- ....
- <plugins>
- ....
- <build>
- ....
- <project>
-
-
-### Configuration
-
-The `install` goal may be configured in the `<configuration>` element using the following properties:
-
-| Parameter | Default Value | System Property Overwrite | Description |
-|--|--|--|--|
-| `skip` | `false` | `sling.install.skip` | Whether to skip this step even though it has been configured in the project to be executed. The main use of this setting is preventing installation of the bundle to a running Sling installation if it is known that there is none or if such an upload is not required, for example when building the bundle in an automated build system such as Confluence. |
-| `bundleFileName` | `${project.build.directory}/${project.build.finalName}.jar` | `sling.file` | The path and name of the file to be installed. Only applies when POSTing to Felix Web Console. |
-| `bundleStart` | `true` | `sling.bundle.start` | Whether to start the bundle after installing it. If the bundle is just updated, this parameter is ignored even if the bundle is currently stopped. Only applies when POSTing to Felix Web Console. |
-| `bundleStartLevel` | `20` | `sling.bundle.startlevel` | The start level to set on the installed bundle. If the bundle is already installed and therefore is only updated this parameter is ignored. The parameter is also ignored if the running Sling instance has no StartLevel service (which is unusual actually). Only applies when POSTing to Felix Web Console. |
-| `slingUrl` | `http://localhost:8080/system/console` | `sling.url` | The URL of the running Sling instance to which the bundle is installed. The default does only work for deployment via WebConsole. |
-| `slingUrlSuffix` | | `sling.urlSuffix` | An optional url suffix which will be appended to the `sling.url` for use as the real target url. This allows to configure different target URLs in each POM, while using the same common `sling.url` in a parent POM. This is typically only used in conjunction with `WebDAV` or `SlingPostServlet` deployment methods. |
-| `user` | `admin` | `sling.user` | The name of the user to authenticate as with the running Sling instance given by the `slingUrl` parameter |
-| `password` | `admin` | `sling.password` | The password of the user to authenticate as with the running Sling instance given by the `slingUrl` parameter |
-| `deploymentMethod` | `WebConsole` | `sling.deploy.method` | Only available since version 2.1.8 (see also [SLING-5335](https://issues.apache.org/jira/browse/SLING-5335)). <br>Allowed values:<br>**WebConsole**, uses the [Felix Web Console REST API](http://felix.apache.org/documentation/subprojects/apache-felix-web-console/web-console-restful-api.html#post-requests) for deployment (HTTP POST). This is the default. Make sure that `slingUrl` points to the Felix Web Console in that case (`http://<yourhost:yourport>/system/console`).<br>**WebDAV**, uses [WebDAV]({{ refs.repository-based-development.path }}) for deployment (HTTP PUT). Make sure that `slingUrl` points to the entry path of the Sling WebDAV bundle (usually below regular Sling root URL). Issues an HTTP Delete for the uninstall goal.<br>**SlingPostServlet**, uses the [Sling Post Servlet]({{ refs.manipulating-content-the-slingpostservlet-servlets-post.path }}) for deployment (HTTP POST). Make sure that `slingUrl` points a path
which is handled by the Sling POST Servlet (usually below regular Sling root URL). |
-| `mimeType` | `application/java-archive` | `sling.mimeType` | The content type / mime type used for WebDAV or Sling POST deployment. |
-| `usePut` | `false` | `sling.usePut` | If a simple HTTP PUT should be used instead of the standard POST to the felix console. In the uninstall goal, a HTTP DELETE will be used. Deprecated since version 2.1.8 (see also [SLING-5335](https://issues.apache.org/jira/browse/SLING-5335)). Use `deploymentMethod=WebDAV` instead. |
-| `refreshPackages` | `true` | `sling.refreshPackages` | Whether to refresh the packages after installing the uploaded bundle. If this property is set to `true`, the `PackageAdmin.refreshPackages(Bundle)` method is called after installing or updating the bundle. Only applies when POSTing to Felix Web Console |
-
-#### Intermediate Node Creation
-For all `deploymentMethod`s except WebDAV the bundle is not directly deployed within the OSGi container, but rather being uploaded to the JCR and from there on being picked up by the [JCR Installer Provider]({{ refs.jcr-installer-provider.path }}) asynchronously, which takes care of deploying it in the OSGi container.
-For both other deployment methods, intermediate nodes (i.e. inexisting parent nodes) are automatically created. The primary type of those intermediate nodes depend on the deployment method
-
-* WebDAV, uses the configured collection node type, by default `sling:Folder` (see also [WebDAV Configuration]({{ refs.repository-based-development.path }}))
-* SlingPostServlet, uses internally `ResourceResolverFactory.create(...)` without setting any `jcr:primaryType`. Therefore the `JcrResourceProviderFactory` will call `Node.addNode(String relPath)` which determines a fitting node type automatically, depending on the parents node type definition (see [Javadoc](http://www.day.com/specs/jsr170/javadocs/jcr-2.0/javax/jcr/Node.html#addNode%28java.lang.String%29)). So in most of the cases this should be a `sling:Folder`, as this is the first allowed child node definition in `sling:Folder`. This only may differ, if your existing parent node is not of type `sling:Folder` itself.
-
-## The `install-file` goal
-
-The `install-file` goal is equivalent to the `install` goal except, that the `install-file` does not require a project descriptor file while the `install` goal does. In other words the `install-file` goal may used to upload any bundle file available to a running Sling instance.
-
-### Use
-
-The `install-file` goal may only be used from the command line by explicitly calling it as in:
-
- $ mvn org.apache.sling:maven-sling-plugin:install-file -Dsling.file=<file>
-
-Specifying the bundle file to upload with the `sling.file` property is required.
-
-### Configuration
-
-The `install-file` supports the same configuration parameters as the `install` goal with the exception of the `skip` parameter which makes no sense. In addition, all parameters must be specified on the command line by setting system properties. The `bundleFileName` parameter specified as the `sling.file` system property is required by the `install-file` goal.
-
-For a description of the parameters see the configuration section of the [`install` goal](#the-install-goal) above.
-
-Example: To upload the bundle file `someBundle.jar` you might use the goal as follows:
-
- $ mvn org.apache.sling:maven-sling-plugin:install-file -Dsling.file=someBundle.jar
-
-## The `uninstall` goal
-
-The `uninstall` goal uninstalls a bundle from a running sling instance, which may be located on a remote system. The plugin uninstalles a bundle via a HTTP `POST{`}request. It's also possible to use HTTP `DELETE` instead of `POST` for WebDAV.
-
-### Use
-
-To use the `uninstall` goal of the Maven Sling Plugin define the following elements in the `<plugins>` section of the POM:
-
- <?xml version="1.0" encoding="ISO-8859-1"?>
- <project>
- ....
- <build>
- ....
- <plugins>
- ....
- <plugin>
- <groupId>org.apache.sling</groupId>
- <artifactId>maven-sling-plugin</artifactId>
- <executions>
- <execution>
- <id>uninstall-bundle</id>
- <goals>
- <goal>uninstall</goal>
- </goals>
- </execution>
- </executions>
- </plugin>
- ....
- <plugins>
- ....
- <build>
- ....
- <project>
-
-
-### Configuration
-
-The `uninstall` goal may be configured in the `<configuration>` element using the following properties:
-
-| Parameter | Default Value | System Property Overwrite | Description |
-|--|--|--|--|
-| `bundleFileName` | `${project.build.directory}/{project.build.finalName}.jar` | `sling.file` | The path and name of the file to be uninstalled |
-| `slingUrl` | `http://localhost:8080/system/console` | `sling.url` | The URL of the running Sling instance on which the bundle should be uninstalled. The default does only work for deployment via WebConsole. |
-| `slingUrlSuffix` | | `sling.urlSuffix` | An optional url suffix which will be appended to the `sling.url` for use as the real target url. This allows to configure different target URLs in each POM, while using the same common `sling.url` in a parent POM. This is typically only used in conjunction with `WebDAV` or `SlingPostServlet` deployment methods. |
-| `user` | `admin` | `sling.user` | The name of the user to authenticate as with the running Sling instance given by the `slingUrl` parameter |
-| `password` | `admin` | `sling.password` | The password of the user to authenticate as with the running Sling instance given by the `slingUrl` parameter |
-| `deploymentMethod` | `WebConsole` | `sling.deploy.method` | Only available since version 2.1.8 (see also [SLING-5335](https://issues.apache.org/jira/browse/SLING-5335)). <br>Allowed values:<br>**WebConsole**, uses the [Felix Web Console REST API](http://felix.apache.org/documentation/subprojects/apache-felix-web-console/web-console-restful-api.html#post-requests) for deployment (HTTP POST). This is the default. Make sure that `slingUrl` points to the Felix Web Console in that case (`http://<yourhost:yourport>/system/console`).<br>**WebDAV**, uses [WebDAV]({{ refs.repository-based-development.path }}) for deployment (HTTP PUT). Make sure that `slingUrl` points to the entry path of the Sling WebDAV bundle (usually below regular Sling root URL). Issues an HTTP Delete for the uninstall goal.<br>**SlingPostServlet**, uses the [Sling Post Servlet]({{ refs.manipulating-content-the-slingpostservlet-servlets-post.path }}) for deployment (HTTP POST). Make sure that `slingUrl` points a path
which is handled by the Sling POST Servlet (usually below regular Sling root URL). |
-| `usePut` | `false` | `sling.usePut` | If a simple HTTP PUT should be used instead of the standard POST to the felix console. In the uninstall goal, an HTTP DELETE will be used. Deprecated since version 2.1.8 (see also [SLING-5335](https://issues.apache.org/jira/browse/SLING-5335)). Use `deploymentMethod=WebDAV` instead. |
-
-
-
-## The `validate` goal
-
-The `validate` goal checks the JSON code of a bundle.
-
-### Use
-
-To use the `validate` goal of the Maven Sling Plugin define the following elements in the `<plugins>` section of the POM:
-
- <?xml version="1.0" encoding="ISO-8859-1"?>
- <project>
- ....
- <build>
- ....
- <plugins>
- ....
- <plugin>
- <groupId>org.apache.sling</groupId>
- <artifactId>maven-sling-plugin</artifactId>
- <executions>
- <execution>
- <id>validate-bundle</id>
- <goals>
- <goal>validate</goal>
- </goals>
- </execution>
- </executions>
- </plugin>
- ....
- <plugins>
- ....
- <build>
- ....
- <project>
-
-
-### Configuration
-
-The `validate` goal may be configured in the `<configuration>` element using the following properties:
-
-| Parameter | Default Value | System Property Overwrite | Description |
-|--|--|--|--|
-| `skip` | `false` | `sling.validation.skip` | Whether to skip the validation |
-| `skipJson` | `false` | `sling.validation.skipJson` | Whether to skip the JSON validation. At the time, there's no difference between `skip` and `skipJson` because only JSON files will be validated by now. |
\ No newline at end of file
+See [Apache Sling HTL Maven Plugin documentation](http://sling.apache.org/components/maven-sling-plugin/).
Modified: sling/site/trunk/content/documentation/development/slingstart.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/slingstart.mdtext?rev=1786260&r1=1786259&r2=1786260&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/slingstart.mdtext (original)
+++ sling/site/trunk/content/documentation/development/slingstart.mdtext Fri Mar 10 00:03:22 2017
@@ -6,7 +6,7 @@ The Apache Sling provisioning model is a
The model is describing an instance, it is not directly related to any particular tooling or packaging/provisioning vehicle.
-For Apache Maven users, the `slingstart-maven-plugin` uses the model to create an executable application and/or a web application based on the model. Sling's Launchpad is defined using the model and built by this Maven plugin.
+For Apache Maven users, the `slingstart-maven-plugin` uses the model to create an executable application and/or a web application based on the model. Sling's Launchpad is defined using the model and built by this Maven plugin. See [SlingStart Maven Plugin](http://sling.apache.org/components/slingstart-maven-plugin/) for a documentation of the supported goals and parameters.
## The Model