sling-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dk...@apache.org
Subject svn commit: r1475804 [1/2] - in /sling/site: ./ trunk/content/ trunk/content/documentation/ trunk/content/documentation/bundles/ trunk/content/documentation/development/ trunk/content/documentation/the-sling-engine/ trunk/content/documentation/the-slin...
Date Thu, 25 Apr 2013 14:45:53 GMT
Author: dklco
Date: Thu Apr 25 14:45:50 2013
New Revision: 1475804

URL: http://svn.apache.org/r1475804
Log:
Fixing SLING-2838 - Fixed a number of broken links caused by the use of refs on external URLS, fixed the links to the nabble discussion list, fixed some minor spelling issues and removed a broken link to localhost:8080 in a CLI example (which just seemed unnecessary)

Added:
    sling/site/.project
Modified:
    sling/site/trunk/content/documentation.mdtext
    sling/site/trunk/content/documentation/bundles/content-loading-jcr-contentloader.mdtext
    sling/site/trunk/content/documentation/bundles/jcr-installer-provider.mdtext
    sling/site/trunk/content/documentation/bundles/managing-users-and-groups-jackrabbit-usermanager.mdtext
    sling/site/trunk/content/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.mdtext
    sling/site/trunk/content/documentation/bundles/mime-type-support-commons-mime.mdtext
    sling/site/trunk/content/documentation/bundles/scheduler-service-commons-scheduler.mdtext
    sling/site/trunk/content/documentation/bundles/web-console-extensions.mdtext
    sling/site/trunk/content/documentation/development/client-request-logging.mdtext
    sling/site/trunk/content/documentation/development/dependency-management.mdtext
    sling/site/trunk/content/documentation/development/embedding-sling.mdtext
    sling/site/trunk/content/documentation/development/getting-and-building-sling.mdtext
    sling/site/trunk/content/documentation/development/issue-tracker.mdtext
    sling/site/trunk/content/documentation/development/logging.mdtext
    sling/site/trunk/content/documentation/development/maven-archetypes.mdtext
    sling/site/trunk/content/documentation/development/maven-launchpad-plugin.mdtext
    sling/site/trunk/content/documentation/development/maventipsandtricks.mdtext
    sling/site/trunk/content/documentation/development/release-management.mdtext
    sling/site/trunk/content/documentation/development/repository-based-development.mdtext
    sling/site/trunk/content/documentation/development/sling.mdtext
    sling/site/trunk/content/documentation/development/version-policy.mdtext
    sling/site/trunk/content/documentation/getting-started.mdtext
    sling/site/trunk/content/documentation/the-sling-engine/authentication/authentication-actors.mdtext
    sling/site/trunk/content/documentation/the-sling-engine/authentication/authentication-authenticationhandler/form-based-authenticationhandler.mdtext
    sling/site/trunk/content/documentation/the-sling-engine/authentication/authentication-authenticationhandler/openid-authenticationhandler.mdtext
    sling/site/trunk/content/documentation/the-sling-engine/authentication/authentication-tasks.mdtext
    sling/site/trunk/content/documentation/the-sling-engine/filters.mdtext
    sling/site/trunk/content/documentation/the-sling-engine/mappings-for-resource-resolution.mdtext
    sling/site/trunk/content/documentation/the-sling-engine/request-parameters.mdtext
    sling/site/trunk/content/documentation/the-sling-engine/url-decomposition.mdtext
    sling/site/trunk/content/links.mdtext
    sling/site/trunk/content/news.mdtext
    sling/site/trunk/content/project-information.mdtext
    sling/site/trunk/content/project-information/apache-sling-community-roles-and-processes.mdtext
    sling/site/trunk/content/project-information/project-team.mdtext
    sling/site/trunk/content/project-information/security.mdtext

Added: sling/site/.project
URL: http://svn.apache.org/viewvc/sling/site/.project?rev=1475804&view=auto
==============================================================================
--- sling/site/.project (added)
+++ sling/site/.project Thu Apr 25 14:45:50 2013
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+	<name>site</name>
+	<comment></comment>
+	<projects>
+	</projects>
+	<buildSpec>
+	</buildSpec>
+	<natures>
+	</natures>
+</projectDescription>

Modified: sling/site/trunk/content/documentation.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation.mdtext (original)
+++ sling/site/trunk/content/documentation.mdtext Thu Apr 25 14:45:50 2013
@@ -8,14 +8,14 @@ The documentation is split into differen
    * [Development]({{ refs.development.path }}), how do I get and develop with Sling
    * [Bundles]({{ refs.bundles.path }}), which bundle delivers which features to Sling
    * [Tutorials & How-Tos]({{ refs.tutorials-how-tos.path }})
-   * [Wiki]({{ refs.http://cwiki.apache.org/SLING/.path }})
+   * [Wiki](http://cwiki.apache.org/SLING/)
    * [Configuration]({{ refs.configuration.path }})
-   * [API Doc]({{ refs.http://sling.apache.org/apidocs/sling5/index.html.path }})
+   * [API Doc](http://sling.apache.org/apidocs/sling5/index.html)
 
 
 # How can you contribute
 
-We're on the way to improve the documentation, but it's a long way. If you would like to contribute to the documentation you are very welcome. Please directly post your proposals to the [public wiki]({{ refs.http://cwiki.apache.org/SLING/.path }}) or post your suggestions to the mailing list.
+We're on the way to improve the documentation, but it's a long way. If you would like to contribute to the documentation you are very welcome. Please directly post your proposals to the [public wiki](http://cwiki.apache.org/SLING/) or post your suggestions to the mailing list.
 
 
 # How is the documentation generated
@@ -218,4 +218,4 @@ To prepare such Bundle Documentation I a
 | Property | Description |
 |--|--|
 | `site.jira.version.id` | The ID of the JIRA version whose bugs are to be listed in the JIRA report. This is a number, such as 12313306 (Sling API version 2.0.4). |
-| `site.javadoc.exclude` | The Java packages to not include with the JavaDoc generation. By default all packages containing `impl` or `internal` in their name are excluded. To add more packages for exclusion, list them in the format suitable for the [`excludePackageNames`]({{ refs.http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#excludePackageNames.path }}) property of the Maven JavaDoc plugin. For example, to exclude any `jsp` and `juli` packages (see the *scripting/jsp* bundle), this property would be set to `\*.jsp:\*.juli`. |
+| `site.javadoc.exclude` | The Java packages to not include with the JavaDoc generation. By default all packages containing `impl` or `internal` in their name are excluded. To add more packages for exclusion, list them in the format suitable for the [`excludePackageNames`](http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#excludePackageNames) property of the Maven JavaDoc plugin. For example, to exclude any `jsp` and `juli` packages (see the *scripting/jsp* bundle), this property would be set to `\*.jsp:\*.juli`. |

Modified: sling/site/trunk/content/documentation/bundles/content-loading-jcr-contentloader.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/content-loading-jcr-contentloader.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/content-loading-jcr-contentloader.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/content-loading-jcr-contentloader.mdtext Thu Apr 25 14:45:50 2013
@@ -155,7 +155,7 @@ The my-transform.xsl file is then respon
 
 ### JSON Descriptor Files
 
-Nodes, Properties and in fact complete subtrees may be described in JSON files using the following skeleton structure (see [http://www.json.org]({{ refs.http://www.json.org.path }}) or information on the syntax of JSON) :
+Nodes, Properties and in fact complete subtrees may be described in JSON files using the following skeleton structure (see [http://www.json.org](http://www.json.org) or information on the syntax of JSON) :
 
     {
         // optional node name on top level, default is file name without .json ext.
@@ -235,6 +235,6 @@ Support for re-registration of node type
 
 ### Automated tests
 
-The initial content found in the [sling-test folder of the launchpad initial content]({{ refs.http://svn.apache.org/repos/asf/sling/trunk/launchpad/content/src/main/resources/content/sling-test.path }}) is verified by the [InitialContentTest](http://svn.apache.org/repos/asf/sling/trunk/launchpad/testing/src/test/java/org/apache/sling/launchpad/webapp/integrationtest/InitialContentTest.java) when running the *launchpad/testing* integration tests.
+The initial content found in the [sling-test folder of the launchpad initial content](http://svn.apache.org/repos/asf/sling/trunk/launchpad/content/src/main/resources/content/sling-test) is verified by the [InitialContentTest](http://svn.apache.org/repos/asf/sling/trunk/launchpad/testing/src/test/java/org/apache/sling/launchpad/webapp/integrationtest/InitialContentTest.java) when running the *launchpad/testing* integration tests.
 
 Those tests can be used as verified examples of initial content loading. Contributions are welcome to improve the coverage of those tests.
\ No newline at end of file

Modified: sling/site/trunk/content/documentation/bundles/jcr-installer-provider.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/jcr-installer-provider.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/jcr-installer-provider.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/jcr-installer-provider.mdtext Thu Apr 25 14:45:50 2013
@@ -20,15 +20,15 @@ Artifacts from folders with a run mode g
 Here's a quick walkthrough of the JCR installer functionality.
 
 ## Installation
-Start the Sling [launchpad/app]({{ refs.http://svn.apache.org/repos/asf/sling/trunk/launchpad/app.path }}) and install and start the following additional bundles:
+Start the Sling [launchpad/app](http://svn.apache.org/repos/asf/sling/trunk/launchpad/app) and install and start the following additional bundles:
 * [RunMode service]({{ refs.run-modes-org-apache-sling-runmode.path }})
-* OSGi installer service ([org.apache.sling.osgi.installer]({{ refs.http://svn.apache.org/repos/asf/sling/trunk/installer/core.path }}))
-* JCR installer provider ([org.apache.sling.jcr.jcrinstall]({{ refs.http://svn.apache.org/repos/asf/sling/trunk/installer/providers/jcr.path }}))
+* OSGi installer service ([org.apache.sling.osgi.installer](http://svn.apache.org/repos/asf/sling/trunk/installer/core))
+* JCR installer provider ([org.apache.sling.jcr.jcrinstall](http://svn.apache.org/repos/asf/sling/trunk/installer/providers/jcr))
 
 To watch the logs produced by these modules, you can filter `sling/logs/error.log` using `egrep 'jcrinstall|osgi.installer'`.
 
 ## Install and remove a bundle
-We'll use the [Knopflerfish Desktop]({{ refs.http://www.knopflerfish.org/releases/2.0.5/jars/desktop*awt/desktop*awt_all-2.0.0.jar.path }}) bundle for this example, it is convenient as it displays a graphical user interface when started.
+We'll use the [Knopflerfish Desktop](http://www.knopflerfish.org/releases/2.0.5/jars/desktop*awt/desktop*awt_all-2.0.0.jar) bundle for this example, it is convenient as it displays a graphical user interface when started.
 
 We use `curl` to create content, to make it easy to reproduce the example by copying and pasting the `curl` commands. Any other way to create content in the repository will work, of course.
 
@@ -130,7 +130,7 @@ And verify that the corresponding config
 # Automated Tests
 The following modules contain lots of automated tests (under `src/test`, as usual):
 
-* OSGi installer integration tests ([org.apache.sling.installer.it]({{ refs.http://svn.apache.org/repos/asf/sling/trunk/installer/it.path }}))
-* JCR installer service ([org.apache.sling.installer.providers.jcr]({{ refs.http://svn.apache.org/repos/asf/sling/trunk/installer/providers/jcr.path }}))
+* OSGi installer integration tests ([org.apache.sling.installer.it](http://svn.apache.org/repos/asf/sling/trunk/installer/it))
+* JCR installer service ([org.apache.sling.installer.providers.jcr](http://svn.apache.org/repos/asf/sling/trunk/installer/providers/jcr))
 
 Many of these tests are fairly readable, and can be used to find out in more detail how these modules work.

Modified: sling/site/trunk/content/documentation/bundles/managing-users-and-groups-jackrabbit-usermanager.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/managing-users-and-groups-jackrabbit-usermanager.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/managing-users-and-groups-jackrabbit-usermanager.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/managing-users-and-groups-jackrabbit-usermanager.mdtext Thu Apr 25 14:45:50 2013
@@ -240,7 +240,7 @@ Example
 
 ## Automated Tests
 
-The [launchpad/testing]({{ refs.http://svn.apache.org/repos/asf/sling/trunk/launchpad/testing/src/test/java/org/apache/sling/launchpad/webapp/integrationtest/accessManager/.path }}) module contains test classes for various operations of the `jackrabbit-usermanager`. Such tests run as part of our continuous integration process, to demonstrate and verify the behavior of the various operations, in a way that's guaranteed to be in sync with the actual Sling core code. If you have an idea for additional tests, make sure to let us know\!
+The [launchpad/testing](http://svn.apache.org/repos/asf/sling/trunk/launchpad/testing/src/test/java/org/apache/sling/launchpad/webapp/integrationtest/accessManager/) module contains test classes for various operations of the `jackrabbit-usermanager`. Such tests run as part of our continuous integration process, to demonstrate and verify the behavior of the various operations, in a way that's guaranteed to be in sync with the actual Sling core code. If you have an idea for additional tests, make sure to let us know\!
 
 ## Permissions checking from scripts
 

Modified: sling/site/trunk/content/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.mdtext Thu Apr 25 14:45:50 2013
@@ -830,7 +830,7 @@ OSGi services of the `org.apache.sling.s
 
 Such services must have a `sling.post.operation` service registration property set to the name of the operation. This name is used as the value of the `:operation` parameter of POST requests to select the extended operation.
 
-Before version 2.1.2 of the *org.apache.sling.servlets.post* bundle, such additional operations were implemented by the `org.apache.sling.servlets.post.SlingPostOperation` interface, which is now deprecated but still supported via a bridge. See [SLING-1725](refs.https://issues.apache.org/jira/browse/SLING-1725) for details and discussions about this change.
+Before version 2.1.2 of the *org.apache.sling.servlets.post* bundle, such additional operations were implemented by the `org.apache.sling.servlets.post.SlingPostOperation` interface, which is now deprecated but still supported via a bridge. See [SLING-1725](https://issues.apache.org/jira/browse/SLING-1725) for details and discussions about this change.
 
 Two examples (old and new style) of additional POST operations are found in the [test-services](http://svn.apache.org/repos/asf/sling/trunk/launchpad/test-services/src/main/java/org/apache/sling/launchpad/testservices/post/) module, with the corresponding test code in the [integration-tests](http://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/servlets/post/CustomPostOperationTest.java) module.
 

Modified: sling/site/trunk/content/documentation/bundles/mime-type-support-commons-mime.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/mime-type-support-commons-mime.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/mime-type-support-commons-mime.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/mime-type-support-commons-mime.mdtext Thu Apr 25 14:45:50 2013
@@ -35,7 +35,7 @@ Two more method allow to programmaticall
 
 Besides the `MimeTypeService` provided by Apache Sling, there is actually more:
 
-* The [`SlingHttpServletRequest`]({{ refs.http://incubator.apache.org/sling/apidocs/sling5/org/apache/sling/api/SlingHttpServletRequest.html.path }}) provides the `getResponseContentType()` method, which returns the preferred *Content-Type* for the response based on the requests extension. This method is implemented by Apache Sling using the `MimeTypeService`. So servlets and scripts may just call this method to set the content type of the response to the desired value.
+* The [`SlingHttpServletRequest`](http://incubator.apache.org/sling/apidocs/sling5/org/apache/sling/api/SlingHttpServletRequest.html) provides the `getResponseContentType()` method, which returns the preferred *Content-Type* for the response based on the requests extension. This method is implemented by Apache Sling using the `MimeTypeService`. So servlets and scripts may just call this method to set the content type of the response to the desired value.
 * Each Servlet (and JSP scripts) is initialized by Apache Sling with a `ServletContext` instance whose implementation of the `getMimeType(String)` effectively calls the `MimeTypeService.getMimeType(String)` method.
 * The Scripting support infrastructure of Sling sets the response content type on behalf of the script to the default value as returned by the `SlingHttpServletRequest.getResponseContentType()` method. At the same time the response character set is also set to `UTF-8` for *text* content types.
 
@@ -46,11 +46,11 @@ Besides the `MimeTypeService` provided b
 
 The implementation of the `MimeTypeService` in the Apache Sling MIME type mapping support (`org.apache.sling.commons.mime`) bundle supports a numnber of ways to configure and extend the set of MIME type mappings:
 
-* Default configuration. The default configuration is based on the [`mime.types`]({{ refs.http://svn.apache.org/repos/asf/httpd/httpd/trunk/docs/conf/mime.types.path }}) file maintained by Roy Fielding for the Apache httpd project and some extensions by Apache Sling.
+* Default configuration. The default configuration is based on the [`mime.types`](http://svn.apache.org/repos/asf/httpd/httpd/trunk/docs/conf/mime.types) file maintained by Roy Fielding for the Apache httpd project and some extensions by Apache Sling.
 * Bundle provided mappings. Bundles registered in the OSGi framework may contain MIME type mappings files `META-INF/mime.types` which are loaded automatically by the Apache Sling MIME type mapping support bundle.
 * Configuration. Mappings may be supplied by configuration of the `MimeTypeService` implementation as the multi-value string property `mime.types`. Each value of the property corresponds to a line in a MIME type configuration file (see below for the format).
 * Registered Mappings. Mappings may be registered with the `MimeTypeService.registerMapping` methods.
-* [`MimeTypeProvider`]({{ refs.http://incubator.apache.org/sling/apidocs/sling5/org/apache/sling/commons/mime/MimeTypeProvider.html.path }}). Additional mappings may be provided by service implementing the `MimeTypeProvider` interface. The `MimeTypeService` implementation will call these services in turn until a service returns a mapping provided there is no static configuration to responde to the mapping request.
+* [`MimeTypeProvider`](http://incubator.apache.org/sling/apidocs/sling5/org/apache/sling/commons/mime/MimeTypeProvider.html). Additional mappings may be provided by service implementing the `MimeTypeProvider` interface. The `MimeTypeService` implementation will call these services in turn until a service returns a mapping provided there is no static configuration to responde to the mapping request.
 
 Please note, that existing mappings cannot be overwritten later. Thus mappings have an inherent priority:
 

Modified: sling/site/trunk/content/documentation/bundles/scheduler-service-commons-scheduler.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/scheduler-service-commons-scheduler.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/scheduler-service-commons-scheduler.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/scheduler-service-commons-scheduler.mdtext Thu Apr 25 14:45:50 2013
@@ -4,7 +4,7 @@ The scheduler is a service for schedulin
 
 ## The Scheduler API
 
-The scheduler has methods to execute jobs periodically, based on a cron expression or at a given time. For more details please refer to the [javadocs]({{ refs.http://sling.apache.org/apidocs/sling5/index.html?org/apache/sling/commons/scheduler/Scheduler.html.path }}).
+The scheduler has methods to execute jobs periodically, based on a cron expression or at a given time. For more details please refer to the [javadocs](http://sling.apache.org/apidocs/sling6/org/apache/sling/commons/scheduler/Scheduler.html).
 
 ## Examples of scheduled jobs registered through the scheduler API
 

Modified: sling/site/trunk/content/documentation/bundles/web-console-extensions.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/web-console-extensions.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/web-console-extensions.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/web-console-extensions.mdtext Thu Apr 25 14:45:50 2013
@@ -1,6 +1,6 @@
 Title: Web Console Extensions
 
-The Apache Sling project provides two extensions to the [Apache Felix Web Console]({{ refs.http://felix.apache.org/site/apache-felix-web-console.html.path }}) (in addition to a number of plugins, of course):
+The Apache Sling project provides two extensions to the [Apache Felix Web Console](http://felix.apache.org/site/apache-felix-web-console.html) (in addition to a number of plugins, of course):
 
 [TOC]
 

Modified: sling/site/trunk/content/documentation/development/client-request-logging.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/client-request-logging.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/client-request-logging.mdtext (original)
+++ sling/site/trunk/content/documentation/development/client-request-logging.mdtext Thu Apr 25 14:45:50 2013
@@ -48,7 +48,7 @@ In the Sling Web Console locate the Conf
 
 #### Log Format Specification
 
-The log format specification follows the [definition of the `format` argument for the `LogFormat` and `CustomLog` directives of Apache httpd]({{ refs.http://httpd.apache.org/docs/current/mod/mod*log*config.html.path }}):
+The log format specification follows the [definition of the `format` argument for the `LogFormat` and `CustomLog` directives of Apache httpd](http://httpd.apache.org/docs/current/mod/mod_log_config.html):
 
 The characteristics of the request itself are logged by placing "%" directives in the format string, which are replaced in the log file by the values as follows:
 

Modified: sling/site/trunk/content/documentation/development/dependency-management.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/dependency-management.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/dependency-management.mdtext (original)
+++ sling/site/trunk/content/documentation/development/dependency-management.mdtext Thu Apr 25 14:45:50 2013
@@ -56,5 +56,5 @@ Generally there is a constant flow of re
 
 ## References
 
-* [Dependency ManagementLink to this message]({{ refs.http://markmail.org/message/5qpmsukdk4mdacdy.path }}) -- Discussion thread about reducing Maven 2 `DependencyManagement`
-* [SLING-811]({{ refs.https://issues.apache.org/jira/browse/SLING-811.path }}) -- The actual issue governing the changes to the project descriptors
\ No newline at end of file
+* [Dependency ManagementLink to this message](http://markmail.org/message/5qpmsukdk4mdacdy) -- Discussion thread about reducing Maven 2 `DependencyManagement`
+* [SLING-811](https://issues.apache.org/jira/browse/SLING-811) -- The actual issue governing the changes to the project descriptors
\ No newline at end of file

Modified: sling/site/trunk/content/documentation/development/embedding-sling.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/embedding-sling.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/embedding-sling.mdtext (original)
+++ sling/site/trunk/content/documentation/development/embedding-sling.mdtext Thu Apr 25 14:45:50 2013
@@ -1,6 +1,6 @@
 Title: Embedding Sling
 
-The Sling Launchpad Launcher can be used to embed the OSGi Framework startup in your own Java application. This functionality is implemented in the [Sling Launchpad Base project]({{ refs.http://svn.apache.org/repos/asf/sling/trunk/launchpad/base.path }}). This project has the following features:
+The Sling Launchpad Launcher can be used to embed the OSGi Framework startup in your own Java application. This functionality is implemented in the [Sling Launchpad Base project](http://svn.apache.org/repos/asf/sling/trunk/launchpad/base). This project has the following features:
 
 * Builds three artifacts:
     * A standalone Java Application with the artifact qualifier *app*; e.g. `org.apache.sling.launchpad.base-2.3.1-SNAPSHOT-app.jar`
@@ -42,13 +42,13 @@ The bridging part is provided in the `or
 
 # The Internal Part
 
-The main class from the internal class directly used is [`Sling`]({{ refs.http://svn.apache.org/repos/asf/sling/trunk/launchpad/base/src/main/java/org/apache/sling/launchpad/base/impl/Sling.java.path }}) which instantiated to start the OSGi Framework. This class is responsible for setting up the environment to finally start the OSGi Framework:
+The main class from the internal class directly used is [`Sling`](http://svn.apache.org/repos/asf/sling/trunk/launchpad/base/src/main/java/org/apache/sling/launchpad/base/impl/Sling.java) which instantiated to start the OSGi Framework. This class is responsible for setting up the environment to finally start the OSGi Framework:
 
 * Read the `sling.properties` file
 * Ensure the presence of the JMX MBeanServer service
 * Execute the bootstrap installations, updates and uninstallations
 
-The [`SlingFelix`]({{ refs.http://svn.apache.org/repos/asf/sling/trunk/launchpad/base/src/main/java/org/apache/sling/launchpad/base/impl/SlingFelix.java.path }}) class extends the Apache Felix `Felix` class which is the actual OSGi framework implementation. We extend the class to be able to notify the `Notifiable` implementation and update the OSGi framework from within the OSGi framework by updating the system bundle.
+The [`SlingFelix`](http://svn.apache.org/repos/asf/sling/trunk/launchpad/base/src/main/java/org/apache/sling/launchpad/base/impl/SlingFelix.java) class extends the Apache Felix `Felix` class which is the actual OSGi framework implementation. We extend the class to be able to notify the `Notifiable` implementation and update the OSGi framework from within the OSGi framework by updating the system bundle.
 
 
 ## The External Part
@@ -66,12 +66,12 @@ The standalone Java Application makes us
 | MainDelegate | This class is loaded by the `Loader` from the `LauncherClassLoader` to actually complete the initial setup before creating the `Sling` class to start the framework. |
 | ControlListener | This class is used by the `Main` class to open a server socket to be able to start and stop Sling as a server. This class allows for starting (opening the server socket), status check (connecting to the socket asking for status), and shutdown (connecting to the socket asking for shutdown). |
 
-At the moment these classes are not directly suitable to be embedded in an existing application (or custom application launcher framework) unless that embedding prepares command line arguments in a `String[]({{ refs..path }})` and calls the `Main.main` method. To allow for custom embeddings or extensions, the work distriubtions between the three classes should be refactored.
+At the moment these classes are not directly suitable to be embedded in an existing application (or custom application launcher framework) unless that embedding prepares command line arguments in a `String[]({{ refs..path }})` and calls the `Main.main` method. To allow for custom embeddings or extensions, the work distributions between the three classes should be refactored.
 
 ### Embedding the Standalone Java Application
 
 <div class="info">
-This work is being done as part of [SLING-2225]({{ refs.https://issues.apache.org/jira/browse/SLING-2225.path }}) and will be officially available with the Sling Launchpad Base release 2.4.0. If you want to use the embedding before the release, you have to checkout the source from [SVN|http://svn.apache.org/repos/asf/sling/trunk/launchpad/base] and build yourself.
+This work is being done as part of [SLING-2225](https://issues.apache.org/jira/browse/SLING-2225) and will be officially available with the Sling Launchpad Base release 2.4.0. If you want to use the embedding before the release, you have to checkout the source from [SVN|http://svn.apache.org/repos/asf/sling/trunk/launchpad/base] and build yourself.
 </div>
 
 To embedd the Sling Launcher in an application, the `Main` class is extended from. To manage the launcher, the following API is available:

Modified: sling/site/trunk/content/documentation/development/getting-and-building-sling.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/getting-and-building-sling.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/getting-and-building-sling.mdtext (original)
+++ sling/site/trunk/content/documentation/development/getting-and-building-sling.mdtext Thu Apr 25 14:45:50 2013
@@ -80,7 +80,7 @@ See [MavenTipsAndTricks]({{ refs.maventi
 ### With Eclipse Subversive or Subclipse
 First note how simple the above SVN instructions are...but if you *really* want to do this, read on.
 
-If you use the Subversive plugin make sure you have installed the "Subversive Integration for M2Eclipse Project" which can be found under the following Eclipse update site: [http://community.polarion.com/projects/subversive/download/integrations/update-site/]({{ refs.http://community.polarion.com/projects/subversive/download/integrations/update-site/.path }}).
+If you use the Subversive plugin make sure you have installed the "Subversive Integration for M2Eclipse Project" which can be found under the following Eclipse update site: [http://community.polarion.com/projects/subversive/download/integrations/update-site/](http://community.polarion.com/projects/subversive/download/integrations/update-site/).
 
 Also, make sure that you have installed either the "Maven SCM handler for Subclipse" or the "Maven SCM handler for Subversive".
 
@@ -217,6 +217,6 @@ The easiest way that I found is to creat
 * Choose File/Import in Eclipse and select "Existing projects into workspace"
 * Now you can create, edit and compile the files in Eclipse
 * To create the bundle jar and install it, just use the command line "mvn clean install" in the project directory
-* If you have a running Sling app you can install the bundle from the command line with "mvn \-P autoInstallBundle clean install \-Dsling.url=[http://localhost:8080/system/console]({{ refs.http://localhost:8080/system/console.path }})"
+* If you have a running Sling app you can install the bundle from the command line with "mvn \-P autoInstallBundle clean install \-Dsling.url=http://localhost:8080/system/console"
 
 If adding dependencies to the poms, run mvn eclipse:eclipse again and refresh the project in Eclipse. Debugging works as described above.
\ No newline at end of file

Modified: sling/site/trunk/content/documentation/development/issue-tracker.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/issue-tracker.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/issue-tracker.mdtext (original)
+++ sling/site/trunk/content/documentation/development/issue-tracker.mdtext Thu Apr 25 14:45:50 2013
@@ -2,7 +2,7 @@ Title: Issue Tracker
 
 Apache Sling uses Jira for tracking bug reports and requests for improvements, new features, and other changes.
 
-The issue tracker is available at https://issues.apache.org/jira/browse/SLING and is readable by everyone. A Jira account is needed to create new issues and to comment on existing issues. Use the [registration form]({{ refs.https://issues.apache.org/jira/secure/Signup!default.jspa.path }}) to request an account if you do not already have one.
+The issue tracker is available at https://issues.apache.org/jira/browse/SLING and is readable by everyone. A Jira account is needed to create new issues and to comment on existing issues. Use the [registration form](https://issues.apache.org/jira/secure/Signup!default.jspa) to request an account if you do not already have one.
 
 See below for guidelines on creating and managing issues.
 

Modified: sling/site/trunk/content/documentation/development/logging.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/logging.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/logging.mdtext (original)
+++ sling/site/trunk/content/documentation/development/logging.mdtext Thu Apr 25 14:45:50 2013
@@ -7,9 +7,9 @@ Logging in Sling is supported by the `or
    * Implements the OSGi Log Service Specification and registers the `LogService` and `LogReader` services
    * Exports three commonly used logging APIs:
       ** [Simple Logging Facade for Java (SLF4J)]({{ refs.-http-www-slf4j-org.path }})
-      ** [Apache Commons Logging]({{ refs.http://jakarta.apache.org/commons/logging.path }})
-      ** [log4j]({{ refs.http://logging.apache.org/log4j/index.html.path }})
-      ** [java.util.logging]({{ refs.http://download.oracle.com/javase/6/docs/api/java/util/logging/package-summary.html.path }}) (as of r1169918)
+      ** [Apache Commons Logging](http://jakarta.apache.org/commons/logging)
+      ** [log4j](http://logging.apache.org/log4j/index.html)
+      ** [java.util.logging](http://download.oracle.com/javase/6/docs/api/java/util/logging/package-summary.html) (as of r1169918)
    * Configures logging through our own implementation of the SLF4J backend API
 
 

Modified: sling/site/trunk/content/documentation/development/maven-archetypes.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/maven-archetypes.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/maven-archetypes.mdtext (original)
+++ sling/site/trunk/content/documentation/development/maven-archetypes.mdtext Thu Apr 25 14:45:50 2013
@@ -1,6 +1,6 @@
 Title: Maven Archetypes
 
-Sling includes four Maven archetypes to quick start development. See [http://maven.apache.org/archetype/maven-archetype-plugin/]({{ refs.http://maven.apache.org/archetype/maven-archetype-plugin/.path }}) for general information on using Maven archetypes. The Maven groupId for all Sling archetypes is `org.apache.sling`.
+Sling includes four Maven archetypes to quick start development. See [http://maven.apache.org/archetype/maven-archetype-plugin/](http://maven.apache.org/archetype/maven-archetype-plugin/) for general information on using Maven archetypes. The Maven groupId for all Sling archetypes is `org.apache.sling`.
 
 ### sling-launchpad-standalone-archetype
 

Modified: sling/site/trunk/content/documentation/development/maven-launchpad-plugin.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/maven-launchpad-plugin.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/maven-launchpad-plugin.mdtext (original)
+++ sling/site/trunk/content/documentation/development/maven-launchpad-plugin.mdtext Thu Apr 25 14:45:50 2013
@@ -6,8 +6,8 @@ The Maven Launchpad Plugin provides goal
 * Inside Apache Karaf
 
 In addition, the Maven Launchpad Plugin supports the publishing of an application descriptor, in the form of a *bundle list*, as a Maven artifact. This descriptor can then be used by downstream application builders as the basis for other applications. In Sling, this is embodied by two Maven projects:
-* [org.apache.sling.launchpad]({{ refs.http://svn.apache.org/repos/asf/sling/trunk/launchpad/builder.path }}) - produces an application descriptor.
-* [org.apache.sling.launchpad.testing]({{ refs.http://svn.apache.org/repos/asf/sling/trunk/launchpad/builder/testing.path }}) - uses the application descriptor from `org.apache.sling.launchpad` and adds two bundles.
+* [org.apache.sling.launchpad](http://svn.apache.org/repos/asf/sling/trunk/launchpad/builder) - produces an application descriptor.
+* [org.apache.sling.launchpad.testing](http://svn.apache.org/repos/asf/sling/trunk/launchpad/builder/testing) - uses the application descriptor from `org.apache.sling.launchpad` and adds two bundles.
 
 Maven Launchpad Plugin provides the following goals: 
 | Goals | Description | 
@@ -138,7 +138,7 @@ For integration testing examples, see `/
 
 ## Bundle List Rewriting
 
-The Maven Launchpad Plugin supports the use of rules to rewrite the bundle list. These rules are executed by the [Drools]({{ refs.http://www.jboss.org/drools.path }}) rule engine. Typically, this is used along with Maven profiles. For example, Sling's testing project includes a profile called `test-reactor-sling-bundles`. When activated, this profile runs a Drools rule file which scans the project list from the Maven reactor and modifies the version number for bundles which were contained within the reactor.
+The Maven Launchpad Plugin supports the use of rules to rewrite the bundle list. These rules are executed by the [Drools](http://www.jboss.org/drools) rule engine. Typically, this is used along with Maven profiles. For example, Sling's testing project includes a profile called `test-reactor-sling-bundles`. When activated, this profile runs a Drools rule file which scans the project list from the Maven reactor and modifies the version number for bundles which were contained within the reactor.
 
 In order for rules to interact with the Maven build, the following global variables are made available:
 

Modified: sling/site/trunk/content/documentation/development/maventipsandtricks.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/maventipsandtricks.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/maventipsandtricks.mdtext (original)
+++ sling/site/trunk/content/documentation/development/maventipsandtricks.mdtext Thu Apr 25 14:45:50 2013
@@ -1,6 +1,6 @@
 Title: MavenTipsAndTricks
 
-Here's our collection of tips and tricks for building Sling with [Maven]({{ refs.http://maven.apache.org.path }}).
+Here's our collection of tips and tricks for building Sling with [Maven](http://maven.apache.org).
 
 # Maven local repository
 

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=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/release-management.mdtext (original)
+++ sling/site/trunk/content/documentation/development/release-management.mdtext Thu Apr 25 14:45:50 2013
@@ -1,7 +1,7 @@
 Title: Release Management
 
 
-Sling releases (and SNAPSHOTS) are deployed to the [Nexus repository]({{ refs.http://repository.apache.org.path }}) instead of the traditional deployment via the Maven 2 mirros source on `people.apache.org`. This makes the release process much leaner and simpler. In addtion we can benefit from the Apache Parent POM 6, which has most of the release profile setup built-in.
+Sling releases (and SNAPSHOTS) are deployed to the [Nexus repository](http://repository.apache.org) instead of the traditional deployment via the Maven 2 mirrors source on `people.apache.org`. This makes the release process much leaner and simpler. In addtion we can benefit from the Apache Parent POM 6, which has most of the release profile setup built-in.
 
 Most of the hard work of preparing and deploying the release is done by Maven.
 
@@ -12,11 +12,11 @@ Most of the hard work of preparing and d
 ## Prerequisites
 
 * To prepare or perform a release you *MUST BE* at least be an Apache Sling Committer.
-* Each and every release must be signed; therefore the public key should be cross signed by other Apache committers (not required but suggested) and this public key should be added to [http://www.apache.org/dist/sling/KEYS]({{ refs.http://www.apache.org/dist/sling/KEYS.path }}) and either on pool.sks-keyservers.net or pgp.mit.edu (See Appendix A)
+* Each and every release must be signed; therefore the public key should be cross signed by other Apache committers (not required but suggested) and this public key should be added to [http://www.apache.org/dist/sling/KEYS](http://www.apache.org/dist/sling/KEYS) and either on pool.sks-keyservers.net or pgp.mit.edu (See Appendix A)
 * When preparing the release on Mac OS X, check out Appendix B before trying the steps in the next chapter.
-* Make sure you have all Apache servers defined in your [settings.xml]({{ refs.http://maven.apache.org/developers/committer-settings.html.path }})
+* Make sure you have all Apache servers defined in your [settings.xml](http://maven.apache.org/developers/committer-settings.html)
 
-*Note*: Listing the Apache servers in the `settings.xml` file also requires adding the password to that file. Starting with Maven 2.1 this password may be encrypted and needs not be give in plaintext. Please refer to [Password Encryption]({{ refs.http://maven.apache.org/guides/mini/guide-encryption.html.path }}) for more information.
+*Note*: Listing the Apache servers in the `settings.xml` file also requires adding the password to that file. Starting with Maven 2.1 this password may be encrypted and needs not be give in plaintext. Please refer to [Password Encryption](http://maven.apache.org/guides/mini/guide-encryption.html) for more information.
 
 In the past we staged release candidates on our local machines using a semi-manual process. Now that we inherit from the Apache parent POM version 6, a repository manager will automatically handle staging for you. This means you now only need to specify your GPG passphrase in the release profile of your `$\{user.home\}/.m2/settings.xml`:
 
@@ -66,8 +66,8 @@ Compare the original `pom.xml` with the 
     ...
 
 1. * If you experience an error during deployment like a HTTP 401 check your settings for the required server entries as outlined in the *Prerequisites*
-1. * Be sure that the generated artifacts respect the Apache release [rules]({{ refs.http://www.apache.org/dev/release.html.path }}): NOTICE and LICENSE files should be present in the META-INF directory within the jar. For \-sources artifacts, be sure that your POM does not use the maven-source-plugin:2.0.3 which is broken. The recommended version at this time is 2.0.4
-1. * You should verify the deployment under the [snapshot]({{ refs.https://repository.apache.org/content/groups/snapshots/org/apache/sling.path }}) repository on Apache
+1. * Be sure that the generated artifacts respect the Apache release [rules](http://www.apache.org/dev/release.html): NOTICE and LICENSE files should be present in the META-INF directory within the jar. For \-sources artifacts, be sure that your POM does not use the maven-source-plugin:2.0.3 which is broken. The recommended version at this time is 2.0.4
+1. * You should verify the deployment under the [snapshot](https://repository.apache.org/content/groups/snapshots/org/apache/sling) repository on Apache
 1. Prepare the release
 
     $ mvn release:clean
@@ -79,10 +79,10 @@ Compare the original `pom.xml` with the 
 
     $ mvn release:perform
 
-1. * The release will automatically be inserted into a temporary staging repository for you, see the Nexus [staging documentation]({{ refs.http://www.sonatype.com/books/nexus-book/reference/staging.html.path }}) for full details
+1. * The release will automatically be inserted into a temporary staging repository for you, see the Nexus [staging documentation](http://www.sonatype.com/books/nexus-book/reference/staging.html) for full details
 1. * You can continue to use `mvn release:prepare` and `mvn release:perform` on other sub-projects as necessary on the same machine and they will be combined in the same staging repository - this is useful when making a release of multiple Sling modules.
 1. Close the staging repository
-1. * Login to [https://repository.apache.org]({{ refs.https://repository.apache.org.path }}) using your Apache SVN credentials. Click on *Staging* on the left. Then click on *org.apache.sling* in the list of repositories. In the panel below you should see an open repository that is linked to your username and IP. Right click on this repository and select *Close*. This will close the repository from future deployments and make it available for others to view. If you are staging multiple releases together, skip this step until you have staged everything
+1. * Login to [https://repository.apache.org](https://repository.apache.org) using your Apache SVN credentials. Click on *Staging* on the left. Then click on *org.apache.sling* in the list of repositories. In the panel below you should see an open repository that is linked to your username and IP. Right click on this repository and select *Close*. This will close the repository from future deployments and make it available for others to view. If you are staging multiple releases together, skip this step until you have staged everything
 1. Verify the staged artifacts
 1. * If you click on your repository, a tree view will appear below. You can then browse the contents to ensure the artifacts are as you expect them. Pay particular attention to the existence of \*.asc (signature) files. If you don't like the content of the repository, right click your repository and choose *Drop*. You can then rollback your release (see *Canceling the Release*) and repeat the process
 1. * Note the staging repository URL (especially the number at the end of the URL) you will need this in your vote email
@@ -127,7 +127,7 @@ Propose a vote on the dev list with the 
 
 ## Wait for the Results
 
-From [Votes on Package Releases]({{ refs.http://www.apache.org/foundation/voting.html.path }}):
+From [Votes on Package Releases](http://www.apache.org/foundation/voting.html):
 
 {quote}Votes on whether a package is ready to be released follow a format similar to majority approval -- except that the decision is officially determined solely by whether at least three \+1 votes were registered. Releases may not be vetoed. Generally the community will table the vote to release if anyone identifies serious problems, but in most cases the ultimate decision, once three or more positive votes have been garnered, lies with the individual serving as release manager. The specifics of the process may vary from project to project, but the 'minimum of three \+1 votes' rule is universal.{quote}
 
@@ -166,7 +166,7 @@ If the vote is successful, you need to p
 If the vote fails, or you decide to redo the release:
 
 1. Remove the release tag from Subversion (`svn del ...`)
-1. Login to [https://repository.apache.org]({{ refs.https://repository.apache.org.path }}) using your Apache SVN credentials. Click on *Staging* on the left. Then click on *org.apache.sling* in the list of repositories. In the panel below you should see a closed repository that is linked to your username and IP (if it's not yet closed you need to right click and select *Close*). Right click on this repository and select *Drop*.
+1. Login to [https://repository.apache.org](https://repository.apache.org) using your Apache SVN credentials. Click on *Staging* on the left. Then click on *org.apache.sling* in the list of repositories. In the panel below you should see a closed repository that is linked to your username and IP (if it's not yet closed you need to right click and select *Close*). Right click on this repository and select *Drop*.
 1. Rollback the version in the `pom.xml` and commit any fixes you need to make
 
 
@@ -175,9 +175,9 @@ If the vote fails, or you decide to redo
 
 If the vote passes:
 
-1. Copy the released artifacts to the Sling dist directory (`/x1/www/www.apache.org/dist/sling`) on `people.apache.org`. This folder is replicated to [http://www.apache.org/dist/sling/]({{ refs.http://www.apache.org/dist/sling/.path }}) a few times a day.
+1. Copy the released artifacts to the Sling dist directory (`/x1/www/www.apache.org/dist/sling`) on `people.apache.org`. This folder is replicated to [http://www.apache.org/dist/sling/](http://www.apache.org/dist/sling/) a few times a day.
 1. Delete the old release from the Sling dist directory (it's archived)
-1. Login to [https://repository.apache.org]({{ refs.https://repository.apache.org.path }}) with your Apache SVN credentials. Click on *Staging*. Find your closed staging repository and select it by checking the select box. Select the *Releases* repository from the drop-down list and click *Release* from the menu above.
+1. Login to [https://repository.apache.org](https://repository.apache.org) with your Apache SVN credentials. Click on *Staging*. Find your closed staging repository and select it by checking the select box. Select the *Releases* repository from the drop-down list and click *Release* from the menu above.
 1. Once the release is promoted click on *Repositories*, select the *Releases* repository and validate that your artifacts are all there.
 1. If you're releasing bundles, you should also add them to the Sling Release OBR (see *Appendix C*).
 1. Update the news section on the website at [news]({{ refs.news.path }}).
@@ -189,7 +189,7 @@ For the last two tasks, it's better to g
 
 ## Update JIRA
 
-Go to [Manage Versions]({{ refs.https://issues.apache.org/jira/plugins/servlet/project-config/SLING/versions.path }}) section on the SLING JIRA and mark the X.Y.Z version as released setting the release date to the date the vote has been closed.
+Go to [Manage Versions](https://issues.apache.org/jira/plugins/servlet/project-config/SLING/versions) section on the SLING JIRA and mark the X.Y.Z version as released setting the release date to the date the vote has been closed.
 
 Also create a new version X.Y.Z+2, if that hasn't already been done.
 
@@ -228,18 +228,18 @@ Also create a new version X.Y.Z+2, if th
 
 
 
-*Important*: Add the release to the Software section of the next board report below [Reports]({{ refs.https://cwiki.apache.org/confluence/display/SLING/Reports.path }}).
+*Important*: Add the release to the Software section of the next board report below [Reports](https://cwiki.apache.org/confluence/display/SLING/Reports).
 
 
 
 ## Related Links
 
-1. [http://www.apache.org/dev/release-signing.html]({{ refs.http://www.apache.org/dev/release-signing.html.path }})
-1. [http://wiki.apache.org/incubator/SigningReleases]({{ refs.http://wiki.apache.org/incubator/SigningReleases.path }})
+1. [http://www.apache.org/dev/release-signing.html](http://www.apache.org/dev/release-signing.html)
+1. [http://wiki.apache.org/incubator/SigningReleases](http://wiki.apache.org/incubator/SigningReleases)
 
 
 
-## Appendix A: Create and Add your key to [http://www.apache.org/dist/sling/KEYS]({{ refs.http://www.apache.org/dist/sling/KEYS.path }})
+## Appendix A: Create and Add your key to [http://www.apache.org/dist/sling/KEYS](http://www.apache.org/dist/sling/KEYS)
 
 Considering that you are using a \*nix system with a working OpenSSH, GnuPG, and bash you can create and add your own key with the following command:
 
@@ -249,13 +249,13 @@ Considering that you are using a \*nix s
 
 When gpg asks for e-mail linked the key you *MUST USE* the <committer>@apache.org one
 When gpg asks for comment linked the key you *SHOULD USE* "CODE SIGNING KEY"
-1. *Add the key to* [http://www.apache.org/dist/sling/KEYS:]({{ refs.http://www.apache.org/dist/sling/KEYS:.path }}) type the following command replacing the word e-mail with your Apache's one (<committer>@apache.org).
+1. *Add the key to* [http://www.apache.org/dist/sling/KEYS](http://www.apache.org/dist/sling/KEYS) type the following command replacing the word e-mail with your Apache's one (<committer>@apache.org).
 
     $ (gpg --list-sigs e-mail && gpg --export --armor e-mail) > toadd.key
     $ scp toadd.key people.apache.org:
     $ ssh people.apache.org "cat toadd.key >> /x1/www/www.apache.org/dist/sling/KEYS"
 
-1. You are *DONE*, but to see the changes on [http://www.apache.org/dist/sling/KEYS]({{ refs.http://www.apache.org/dist/sling/KEYS.path }}) you must wait 2 hours
+1. You are *DONE*, but to see the changes on [http://www.apache.org/dist/sling/KEYS](http://www.apache.org/dist/sling/KEYS) you must wait 2 hours
 
 You also have to add your public key either on pool.sks-keyservers.net or pgp.mit.edu (for the statging repository).
 

Modified: sling/site/trunk/content/documentation/development/repository-based-development.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/repository-based-development.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/repository-based-development.mdtext (original)
+++ sling/site/trunk/content/documentation/development/repository-based-development.mdtext Thu Apr 25 14:45:50 2013
@@ -4,7 +4,7 @@ Title: Repository Based Development
 
 ## WebDAV Support
 
-WebDAV support in Sling is based on the [Simple WebDAV]({{ refs.http://jackrabbit.apache.org/doc/components/jcr-server.html.path }}) implementation of Apache Jackrabbit which is integrated in the `jcr/webdav` project. This bundle provides WebDAV access to Sling's repository in two flavours: (1) Access to all workspaces of the repository on a separate URL space -- by default rooted at `/dav` in the Sling context -- and (2) access to the workspace used by Sling itself at the root of the Sling context.
+WebDAV support in Sling is based on the [Simple WebDAV](http://jackrabbit.apache.org/doc/components/jcr-server.html) implementation of Apache Jackrabbit which is integrated in the `jcr/webdav` project. This bundle provides WebDAV access to Sling's repository in two flavours: (1) Access to all workspaces of the repository on a separate URL space -- by default rooted at `/dav` in the Sling context -- and (2) access to the workspace used by Sling itself at the root of the Sling context.
 
 
 #### Example

Modified: sling/site/trunk/content/documentation/development/sling.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/sling.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/sling.mdtext (original)
+++ sling/site/trunk/content/documentation/development/sling.mdtext Thu Apr 25 14:45:50 2013
@@ -44,7 +44,7 @@ You should specify the version in your p
       ...
     </project>
 
-For more information, see ["Guide to Configuring Plug-ins"]({{ refs.http://maven.apache.org/guides/mini/guide-configuring-plugins.html.path }})
+For more information, see ["Guide to Configuring Plug-ins"](http://maven.apache.org/guides/mini/guide-configuring-plugins.html)
 
 {anchor:deploy}
 
@@ -113,7 +113,7 @@ The `deploy-file` supports similar confi
 |--|--|--|--|
 | `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]({{ refs.http://obr.sample.org.path }})` you might use the goal as follows:
+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
 

Modified: sling/site/trunk/content/documentation/development/version-policy.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/version-policy.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/version-policy.mdtext (original)
+++ sling/site/trunk/content/documentation/development/version-policy.mdtext Thu Apr 25 14:45:50 2013
@@ -19,7 +19,7 @@ The exports in bundle/api/pom.xml look l
 
 I agree, that this is a problem. So let me reasonate on this a bit ;-)
 
-As a reference you might want to read [my blog post on version numbers]({{ refs.http://blog.meschberger.ch/2009/10/on-version-numbers.html.path }}) and also what the [Eclipse guys have to say|http://wiki.eclipse.org/index.php/Version_Numbering] (great read, btw). The OSGi Alliance has come up with a good definition for [Semantic Versioning|http://www.osgi.org/wiki/uploads/Links/SemanticVersioning.pdf] to which the definitions described below perfectly match.
+As a reference you might want to read [my blog post on version numbers](http://blog.meschberger.ch/2009/10/on-version-numbers.html) and also what the [Eclipse guys have to say|http://wiki.eclipse.org/index.php/Version_Numbering] (great read, btw). The OSGi Alliance has come up with a good definition for [Semantic Versioning|http://www.osgi.org/wiki/uploads/Links/SemanticVersioning.pdf] to which the definitions described below perfectly match.
 
 For Sling we have three kinds of version numbers:
 
@@ -82,7 +82,7 @@ Using this syntax something like the fol
     import aQute.bnd.annotation.Export;
 
 
-See [Bnd Experimental]({{ refs.http://www.aqute.biz/Code/XBnd.path }}) for details. Unfortunately the current Maven Bundle Plugin version does not support updating to the most recent BND library versions due to incompatibilities.
+See [Bnd Experimental](http://www.aqute.biz/Code/XBnd) for details. Unfortunately the current Maven Bundle Plugin version does not support updating to the most recent BND library versions due to incompatibilities.
 
 
 ## Version Number Syntax
@@ -197,12 +197,12 @@ This allows for the implementation to wo
 
 *Future*
 
-Recent versions of the BND library support automatic differntiation between use and implementation of API and to set the import version ranges accordingly. See [Bnd Experimental]({{ refs.http://www.aqute.biz/Code/XBnd.path }}) for details. Unfortunately the current Maven Bundle Plugin version does not support updating to the most recent BND library versions due to incompatibilities.
+Recent versions of the BND library support automatic differntiation between use and implementation of API and to set the import version ranges accordingly. See [Bnd Experimental](http://www.aqute.biz/Code/XBnd) for details. Unfortunately the current Maven Bundle Plugin version does not support updating to the most recent BND library versions due to incompatibilities.
 
 ## References
 
-[Version Numbers]({{ refs.http://markmail.org/thread/zshobgjwtqrncajt.path }}) -- The mail thread discussing version numbering
-[On Version Numbers]({{ refs.http://blog.meschberger.ch/2009/10/on-version-numbers.html.path }}) -- Blog about version numbers
-[Version Numbering]({{ refs.http://wiki.eclipse.org/index.php/Version_Numbering.path }}) -- An Eclipse paper on assigning version numbers. Very good read.
-[Semantic Versioning]({{ refs.http://www.osgi.org/wiki/uploads/Links/SemanticVersioning.pdf.path }}) -- An OSGi Alliance paper on semantic versioning.
-[Bnd Experimental]({{ refs.http://www.aqute.biz/Code/XBnd.path }}) -- Experimental extensions to the BND library; unfortunately these extensions are not yet usable with Maven Bundle Plugin 2.1.0 due to API changes in the BND library not supported by the plugin.
+[Version Numbers](http://markmail.org/thread/zshobgjwtqrncajt) -- The mail thread discussing version numbering
+[On Version Numbers](http://blog.meschberger.ch/2009/10/on-version-numbers.html) -- Blog about version numbers
+[Version Numbering](http://wiki.eclipse.org/index.php/Version_Numbering) -- An Eclipse paper on assigning version numbers. Very good read.
+[Semantic Versioning](http://www.osgi.org/wiki/uploads/Links/SemanticVersioning.pdf) -- An OSGi Alliance paper on semantic versioning.
+[Bnd Experimental](http://www.aqute.biz/Code/XBnd) -- Experimental extensions to the BND library; unfortunately these extensions are not yet usable with Maven Bundle Plugin 2.1.0 due to API changes in the BND library not supported by the plugin.

Modified: sling/site/trunk/content/documentation/getting-started.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/getting-started.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/getting-started.mdtext (original)
+++ sling/site/trunk/content/documentation/getting-started.mdtext Thu Apr 25 14:45:50 2013
@@ -13,7 +13,7 @@ We recommend you read through following 
 * [Architecture]({{ refs.architecture.path }})
 * [Dispatching Requests]({{ refs.dispatching-requests.path }})
 * [Resources]({{ refs.resources.path }})
-* [Setting up an Sling-Project with Eclipse]({{ refs.http://cwiki.apache.org/SLING/setting-up-eclipse-34-for-sling.html.path }})
+* [Setting up an Sling-Project with Eclipse](http://cwiki.apache.org/SLING/setting-up-eclipse-34-for-sling.html)
 * [Manipulating Content - The SlingPostServlet (servlets.post)]({{ refs.manipulating-content-the-slingpostservlet-servlets-post.path }})
 * [Request Parameters]({{ refs.request-parameters.path }})
 * [Authentication]({{ refs.authentication.path }})

Modified: sling/site/trunk/content/documentation/the-sling-engine/authentication/authentication-actors.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/the-sling-engine/authentication/authentication-actors.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/the-sling-engine/authentication/authentication-actors.mdtext (original)
+++ sling/site/trunk/content/documentation/the-sling-engine/authentication/authentication-actors.mdtext Thu Apr 25 14:45:50 2013
@@ -41,13 +41,13 @@ The actual process of logging into the r
 
 The Sling Jackrabbit Embedded Repository bundle provides additional plugin interfaces to extend the login process dynamically using OSGi services. To this avail the bundle configures a `LoginModule` with the provided default Jackrabbit configuration supporting these plugins:
 
-  * `LoginModulePlugin` -- The main service interface. Plugins must implement this interface to be able to extend the login process. See for example the [Sling OpenID authentication handler]({{ refs.http://svn.apache.org/repos/asf/sling/trunk/bundles/extensions/openidauth/.path }}), which implements this interface to support OpenID authentication.
+  * `LoginModulePlugin` -- The main service interface. Plugins must implement this interface to be able to extend the login process. See for example the [Sling OpenID authentication handler](http://svn.apache.org/repos/asf/sling/trunk/bundles/extensions/openidauth/), which implements this interface to support OpenID authentication.
   * `AuthenticationPlugin` -- Helper interface for the `LoginModulePlugin`.
 
 
 ## Sling Applications
 
-Sling Applications requiring authenticed requests should not care about how authentication is implemented. To support such functionality the `Authenticator` service is provided with two methods:
+Sling Applications requiring authenticated requests should not care about how authentication is implemented. To support such functionality the `Authenticator` service is provided with two methods:
 
   * `login` -- allows the application to ensure requests are authenticated. This involves selecting an `AuthenticationHandler` to request credentials for authentication.
 

Modified: sling/site/trunk/content/documentation/the-sling-engine/authentication/authentication-authenticationhandler/form-based-authenticationhandler.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/the-sling-engine/authentication/authentication-authenticationhandler/form-based-authenticationhandler.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/the-sling-engine/authentication/authentication-authenticationhandler/form-based-authenticationhandler.mdtext (original)
+++ sling/site/trunk/content/documentation/the-sling-engine/authentication/authentication-authenticationhandler/form-based-authenticationhandler.mdtext Thu Apr 25 14:45:50 2013
@@ -9,7 +9,7 @@ The implementation of the Form Based Aut
 * For the initial form submission, the request URL must end with `/j*security*check` and the user name and password names must be `j*username` and `j*password`, resp.
 * The authentication type as returned by `HttpServletRequest.getAuthType()` is set to `HttpServletRequest.FORM_AUTH`.
 
-The Form Based Authentication Handler is maintained in the [Sling SVN]({{ refs.http://svn.apache.org/repos/asf/sling/trunk/bundles/auth/form.path }})
+The Form Based Authentication Handler is maintained in the [Sling SVN](http://svn.apache.org/repos/asf/sling/trunk/bundles/auth/form)
 
 
 ### AuthenticationHandler implementation
@@ -62,7 +62,7 @@ If the `j_validate` parameter is not set
 
 The `resource` and `sling.auth.redirect` parameters provide similar functionality but with differing historical backgrounds. The `resource` parameter is based on the `resource` request attribute which is set by the login servlet to indicate the original target resource the client desired when it was forced to authenticate. The `sling.auth.redirect` parameter can be used by clients (applications like cURL or plain HTML forms) to request being redirected after successful login. If both parameters are set, the `sling.auth.redirect` parameter takes precedence.
 
-The Form Based Authentication Handler contains a [default form servlet]({{ refs.http://http://svn.apache.org/repos/asf/sling/trunk/bundles/auth/form/src/main/java/org/apache/sling/auth/form/impl/AuthenticationFormServlet.java.path }}) and [HTML form template from|http://svn.apache.org/repos/asf/sling/trunk/bundles/auth/form/src/main/resources/org/apache/sling/auth/form/impl/login.html].
+The Form Based Authentication Handler contains a [default form servlet](http://svn.apache.org/repos/asf/sling/trunk/bundles/auth/form/src/main/java/org/apache/sling/auth/form/impl/AuthenticationFormServlet.java) and [HTML form template from|http://svn.apache.org/repos/asf/sling/trunk/bundles/auth/form/src/main/resources/org/apache/sling/auth/form/impl/login.html].
 
 
 ### Phase 2: Authenticated Requests

Modified: sling/site/trunk/content/documentation/the-sling-engine/authentication/authentication-authenticationhandler/openid-authenticationhandler.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/the-sling-engine/authentication/authentication-authenticationhandler/openid-authenticationhandler.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/the-sling-engine/authentication/authentication-authenticationhandler/openid-authenticationhandler.mdtext (original)
+++ sling/site/trunk/content/documentation/the-sling-engine/authentication/authentication-authenticationhandler/openid-authenticationhandler.mdtext Thu Apr 25 14:45:50 2013
@@ -2,13 +2,13 @@ Title: OpenID AuthenticationHandler
 
 [TOC]
 
-The OpenID Authentication Handler supports authentication of request users using the [OpenID]({{ refs.http://www.openid.net.path }}) authentication protocol. If the user has successfully authenticated with his OpenID provider a signed OpenID identity is further used to identify the user.
+The OpenID Authentication Handler supports authentication of request users using the [OpenID](http://www.openid.net) authentication protocol. If the user has successfully authenticated with his OpenID provider a signed OpenID identity is further used to identify the user.
 
 Since generally an OpenID identity is an URL and URLs may not be used as JCR user names, an association mechanism is used by the OpenID authentication handler to associate an OpenID identity with an existing JCR user: The OpenID identity URL is set as the value of a JCR user property. When a user authenticates with his OpenID identity the matching user searched for by looking for a match in this property.
 
 *NOTE:* This association currently only works with Jackrabbit (or Jackrabbit based repositories) because user management is not part of the JCR 2 specification and the OpenID authentication handler uses the Jackrabbit `UserManager` to find users by a user property value.
 
-The OpenID Authentication Handler is maintained in the [Sling SVN]({{ refs.http://svn.apache.org/repos/asf/sling/trunk/bundles/auth/openid/.path }})
+The OpenID Authentication Handler is maintained in the [Sling SVN](http://svn.apache.org/repos/asf/sling/trunk/bundles/auth/openid/)
 
 
 ### Credentials Extraction

Modified: sling/site/trunk/content/documentation/the-sling-engine/authentication/authentication-tasks.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/the-sling-engine/authentication/authentication-tasks.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/the-sling-engine/authentication/authentication-tasks.mdtext (original)
+++ sling/site/trunk/content/documentation/the-sling-engine/authentication/authentication-tasks.mdtext Thu Apr 25 14:45:50 2013
@@ -18,4 +18,4 @@ Authentication of HTTP Requests is gener
  * Provides a JCR `Session`
  * Implementation dependent process. Jackrabbit provides extensibility based on `LoginModules`; Sling's Embedded Jackrabbit Repository bundle provides extensibility with `LoginModulePlugin` services.
 
-Currently the credentials are always verified by trying to login to the JCR repository. Once an [ResourceResolverFactory]({{ refs.http://cwiki.apache.org/SLING/add-resourceresolverfactory-service-interface.html.path }}) API has been added, the process of validating the credentials and logging in is actualy replaced by a process of requesting a `ResourceResolver` from the `ResourceResolverFactory`. Of course, the JCR Repository will still be the main underlying repository and as such be used to validate the credentials and get a JCR Session.
\ No newline at end of file
+Currently the credentials are always verified by trying to login to the JCR repository. Once an [ResourceResolverFactory](http://cwiki.apache.org/SLING/add-resourceresolverfactory-service-interface.html) API has been added, the process of validating the credentials and logging in is actualy replaced by a process of requesting a `ResourceResolver` from the `ResourceResolverFactory`. Of course, the JCR Repository will still be the main underlying repository and as such be used to validate the credentials and get a JCR Session.
\ No newline at end of file

Modified: sling/site/trunk/content/documentation/the-sling-engine/filters.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/the-sling-engine/filters.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/the-sling-engine/filters.mdtext (original)
+++ sling/site/trunk/content/documentation/the-sling-engine/filters.mdtext Thu Apr 25 14:45:50 2013
@@ -3,7 +3,7 @@ Title: Servlet Filter Support
 Sling supports filter processing by applying filter chains to the requests before actually dispatching to the servlet or script for processing. Filters to be used in such filter processing are plain OSGi services of type `javax.servlet.Filter` which of course means that the services implement this interface.
 
 <div class="note">
-See [SLING-1213]({{ refs.https://issues.apache.org/jira/browse/SLING-1213.path }}), [SLING-1734|https://issues.apache.org/jira/browse/SLING-1734], and [Registering filters with Sling|http://markmail.org/message/quxhm7d5s6u66crr] for more details.
+See [SLING-1213](https://issues.apache.org/jira/browse/SLING-1213), [SLING-1734|https://issues.apache.org/jira/browse/SLING-1734], and [Registering filters with Sling|http://markmail.org/message/quxhm7d5s6u66crr] for more details.
 </div>
 
 For Sling to pick up a `javax.servlet.Filter` service for filter processing two service registration properties are inspected:
@@ -109,6 +109,6 @@ The first numbers on those lines are the
 
 Up to and including Sling Engine 2.1.0 support for Servlet Filters has been as follows:
 
-* Any `javax.servlet.Filter` service is accepted as a filter for Sling unless the `pattern` property used by the [Apache Felix HttpService whiteboard support]({{ refs.http://felix.apache.org/site/apache-felix-http-service.html#ApacheFelixHTTPService-UsingtheWhiteboard.path }}) is set in the service registration properties.
+* Any `javax.servlet.Filter` service is accepted as a filter for Sling unless the `pattern` property used by the [Apache Felix HttpService whiteboard support](http://felix.apache.org/site/apache-felix-http-service.html#ApacheFelixHTTPService-UsingtheWhiteboard) is set in the service registration properties.
 * The `filter.scope` property is optional and supports the case-sensitive values `request` and `component`.
 * Filter ordering is defined by the `filter.order` property whose default value is `Integer.MAX_VALUE` where smaller values have higher priority over higher values.

Modified: sling/site/trunk/content/documentation/the-sling-engine/mappings-for-resource-resolution.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/the-sling-engine/mappings-for-resource-resolution.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/the-sling-engine/mappings-for-resource-resolution.mdtext (original)
+++ sling/site/trunk/content/documentation/the-sling-engine/mappings-for-resource-resolution.mdtext Thu Apr 25 14:45:50 2013
@@ -71,12 +71,12 @@ Consider the following content
 This would define the following mapping entries:
 | Regular Expression | Redirect | Internal | Description |
 |--|--|--|--|
-| http/example.com.80 | [http://www.example.com]({{ refs.http://www.example.com.path }}) | no | Redirect all requests to the Second Level Domain to www |
+| http/example.com.80 | [http://www.example.com](http://www.example.com) | no | Redirect all requests to the Second Level Domain to www |
 | http/www.example.com.80 | /example | yes | Prefix the URI paths of the requests sent to this domain with the string `/example` |
-| http/.+\.example\.com\.80 | [http://www.example.com]({{ refs.http://www.example.com.path }}) | no | Redirect all requests to sub domains to www. The actual regular expression for the host.port segment is taken from the `sling:match` property. |
+| http/.+\.example\.com\.80 | [http://www.example.com](http://www.example.com) | no | Redirect all requests to sub domains to www. The actual regular expression for the host.port segment is taken from the `sling:match` property. |
 | http/localhost\.\d\* | /content | yes | Prefix the URI paths with `/content` for requests to localhost, regardless of actual port the request was received on. This entry only applies if the URI path does not start with `/cgi-bin`, `gateway` or `stories` because there are longer match entries. The actual regular expression for the host.port segment is taken from the `sling:match` property. |
 | http/localhost\.\d*/cgi-bin | /scripts | yes | Replace the `/cgi-bin` prefix in the URI path with `/scripts` for requests to localhost, regardless of actual port the request was received on. |
-| http/localhost\.\d*/gateway | [http://gbiv.com]({{ refs.http://gbiv.com.path }}) | yes | Replace the `/gateway` prefix in the URI path with `[http://gbiv.com]` for requests to localhost, regardless of actual port the request was received on. |
+| http/localhost\.\d*/gateway | [http://gbiv.com](http://gbiv.com) | yes | Replace the `/gateway` prefix in the URI path with `[http://gbiv.com]` for requests to localhost, regardless of actual port the request was received on. |
 | http/localhost\.\d*/(stories) | /anecdotes/stories | yes | Prepend the URI paths starting with `/stories` with `/anecdotes` for requests to localhost, regardless of actual port the request was received on. |
 
 ### Regular Expression matching

Modified: sling/site/trunk/content/documentation/the-sling-engine/request-parameters.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/the-sling-engine/request-parameters.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/the-sling-engine/request-parameters.mdtext (original)
+++ sling/site/trunk/content/documentation/the-sling-engine/request-parameters.mdtext Thu Apr 25 14:45:50 2013
@@ -40,7 +40,7 @@ All parameters are handled the same, tha
 As of Sling Engine 2.1.0 the order or request parameters in the `getRequestParameterMap()`, `getParameterMap()`, and `getParameterNams()` is preserved as follows:
 
 * The first entries are the parameters reported by the servlet container. The order of these parameters amongst each other is not defined. The `SlingHttpServletRequest` provides them in the same order as provided by the servlet container.
-* After the servlet container provided parameters are parameters extracted from the request in case `multipart/form-data` POST requests. The order of these parameters is preserved as they are submitted in the request. This conforms to HTML 4.01 spec on forms submitted with multipart/form-data encoding: *A "multipart/form-data" message contains a series of parts, each representing a successful control. The parts are sent to the processing agent in the same order the corresponding controls appear in the document stream. Part boundaries should not occur in any of the data; how this is done lies outside the scope of this specification* ([17.13.4 Form content types]({{ refs.http://www.w3.org/TR/html401/interact/forms.html.path }}))
+* After the servlet container provided parameters are parameters extracted from the request in case `multipart/form-data` POST requests. The order of these parameters is preserved as they are submitted in the request. This conforms to HTML 4.01 spec on forms submitted with multipart/form-data encoding: *A "multipart/form-data" message contains a series of parts, each representing a successful control. The parts are sent to the processing agent in the same order the corresponding controls appear in the document stream. Part boundaries should not occur in any of the data; how this is done lies outside the scope of this specification* ([17.13.4 Form content types](http://www.w3.org/TR/html401/interact/forms.html))
 
 Be warned: Only rely on request parameter ordering `multipart/form-data` POST requests without a query part in the request URL.
 

Modified: sling/site/trunk/content/documentation/the-sling-engine/url-decomposition.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/the-sling-engine/url-decomposition.mdtext?rev=1475804&r1=1475803&r2=1475804&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/the-sling-engine/url-decomposition.mdtext (original)
+++ sling/site/trunk/content/documentation/the-sling-engine/url-decomposition.mdtext Thu Apr 25 14:45:50 2013
@@ -7,7 +7,7 @@ During the *Resource Resolution* step, t
 1. *Extension* -  The string after the last dot after the resource path in the request URL but before the end of the request URL or the next slash after the resource path in the request URL. 
 1. *Suffix Path* -  If the request URL contains a slash character after the resource path and optional selectors and extension, the path starting with the slash up to the end of the request URL is the suffix path. Otherwise, the suffix path is empty. Note, that after the resource path at least a dot must be in the URL to let Sling detect the resource path.
 
-There's a cheat sheet on Day's dev page under [http://dev.day.com/content/docs/en/cq/current/developing/sling_cheatsheet.html]({{ refs.http://dev.day.com/content/docs/en/cq/current/developing/sling_cheatsheet.html.path }}) available to get you familiar with the URL decomposition of Sling.
+There's a cheat sheet on Day's dev page under [http://dev.day.com/content/docs/en/cq/current/developing/sling_cheatsheet.html](http://dev.day.com/content/docs/en/cq/current/developing/sling_cheatsheet.html) available to get you familiar with the URL decomposition of Sling.
 
 *Examples*: Assume there is a Resource at `/a/b`, which has no children.
 



Mime
View raw message