You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by bu...@apache.org on 2013/04/25 16:46:11 UTC
svn commit: r859870 [2/2] - in /websites/staging/sling/trunk/content: ./
documentation/ documentation/bundles/ documentation/development/
documentation/the-sling-engine/
documentation/the-sling-engine/authentication/
documentation/the-sling-engine/auth...
Modified: websites/staging/sling/trunk/content/documentation/the-sling-engine/authentication/authentication-tasks.html
==============================================================================
--- websites/staging/sling/trunk/content/documentation/the-sling-engine/authentication/authentication-tasks.html (original)
+++ websites/staging/sling/trunk/content/documentation/the-sling-engine/authentication/authentication-tasks.html Thu Apr 25 14:46:10 2013
@@ -101,9 +101,9 @@
<li>Provides a JCR <code>Session</code></li>
<li>Implementation dependent process. Jackrabbit provides extensibility based on <code>LoginModules</code>; Sling's Embedded Jackrabbit Repository bundle provides extensibility with <code>LoginModulePlugin</code> services.</li>
</ul>
-<p>Currently the credentials are always verified by trying to login to the JCR repository. Once an <a href="">ResourceResolverFactory</a> API has been added, the process of validating the credentials and logging in is actualy replaced by a process of requesting a <code>ResourceResolver</code> from the <code>ResourceResolverFactory</code>. 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.</p>
+<p>Currently the credentials are always verified by trying to login to the JCR repository. Once an <a href="http://cwiki.apache.org/SLING/add-resourceresolverfactory-service-interface.html">ResourceResolverFactory</a> API has been added, the process of validating the credentials and logging in is actualy replaced by a process of requesting a <code>ResourceResolver</code> from the <code>ResourceResolverFactory</code>. 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.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1341361 by fmeschbe on Tue, 22 May 2012 08:54:04 +0000
+ Rev. 1475804 by dklco on Thu, 25 Apr 2013 14:45:50 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project
Modified: websites/staging/sling/trunk/content/documentation/the-sling-engine/filters.html
==============================================================================
--- websites/staging/sling/trunk/content/documentation/the-sling-engine/filters.html (original)
+++ websites/staging/sling/trunk/content/documentation/the-sling-engine/filters.html Thu Apr 25 14:46:10 2013
@@ -88,7 +88,7 @@
<h1>Servlet Filter Support</h1>
<p>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 <code>javax.servlet.Filter</code> which of course means that the services implement this interface.</p>
<div class="note">
-See [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.
+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>
<p>For Sling to pick up a <code>javax.servlet.Filter</code> service for filter processing two service registration properties are inspected:</p>
@@ -238,12 +238,12 @@ See [SLING-1213](), [SLING-1734|https://
<h2 id="support-in-sling-engine-210">Support in Sling Engine 2.1.0</h2>
<p>Up to and including Sling Engine 2.1.0 support for Servlet Filters has been as follows:</p>
<ul>
-<li>Any <code>javax.servlet.Filter</code> service is accepted as a filter for Sling unless the <code>pattern</code> property used by the <a href="">Apache Felix HttpService whiteboard support</a> is set in the service registration properties.</li>
+<li>Any <code>javax.servlet.Filter</code> service is accepted as a filter for Sling unless the <code>pattern</code> property used by the <a href="http://felix.apache.org/site/apache-felix-http-service.html#ApacheFelixHTTPService-UsingtheWhiteboard">Apache Felix HttpService whiteboard support</a> is set in the service registration properties.</li>
<li>The <code>filter.scope</code> property is optional and supports the case-sensitive values <code>request</code> and <code>component</code>.</li>
<li>Filter ordering is defined by the <code>filter.order</code> property whose default value is <code>Integer.MAX_VALUE</code> where smaller values have higher priority over higher values.</li>
</ul>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1464512 by bdelacretaz on Thu, 4 Apr 2013 13:03:31 +0000
+ Rev. 1475804 by dklco on Thu, 25 Apr 2013 14:45:50 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project
Modified: websites/staging/sling/trunk/content/documentation/the-sling-engine/mappings-for-resource-resolution.html
==============================================================================
--- websites/staging/sling/trunk/content/documentation/the-sling-engine/mappings-for-resource-resolution.html (original)
+++ websites/staging/sling/trunk/content/documentation/the-sling-engine/mappings-for-resource-resolution.html Thu Apr 25 14:46:10 2013
@@ -137,12 +137,12 @@
<p>This would define the following mapping entries:
| Regular Expression | Redirect | Internal | Description |
|--|--|--|--|
-| http/example.com.80 | <a href="">http://www.example.com</a> | no | Redirect all requests to the Second Level Domain to www |
+| http/example.com.80 | <a href="http://www.example.com">http://www.example.com</a> | 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 <code>/example</code> |
-| http/.+.example.com.80 | <a href="">http://www.example.com</a> | no | Redirect all requests to sub domains to www. The actual regular expression for the host.port segment is taken from the <code>sling:match</code> property. |
+| http/.+.example.com.80 | <a href="http://www.example.com">http://www.example.com</a> | no | Redirect all requests to sub domains to www. The actual regular expression for the host.port segment is taken from the <code>sling:match</code> property. |
| http/localhost.\d* | /content | yes | Prefix the URI paths with <code>/content</code> 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 <code>/cgi-bin</code>, <code>gateway</code> or <code>stories</code> because there are longer match entries. The actual regular expression for the host.port segment is taken from the <code>sling:match</code> property. |
| http/localhost.\d<em>/cgi-bin | /scripts | yes | Replace the <code>/cgi-bin</code> prefix in the URI path with <code>/scripts</code> for requests to localhost, regardless of actual port the request was received on. |
-| http/localhost.\d</em>/gateway | <a href="">http://gbiv.com</a> | yes | Replace the <code>/gateway</code> prefix in the URI path with <code>[http://gbiv.com]</code> for requests to localhost, regardless of actual port the request was received on. |
+| http/localhost.\d</em>/gateway | <a href="http://gbiv.com">http://gbiv.com</a> | yes | Replace the <code>/gateway</code> prefix in the URI path with <code>[http://gbiv.com]</code> 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 <code>/stories</code> with <code>/anecdotes</code> for requests to localhost, regardless of actual port the request was received on. |</p>
<h3 id="regular-expression-matching">Regular Expression matching</h3>
<p>As said above the mapping entries are regular expressions which are matched against path. As such these regular expressions may also contain capturing groups as shown in the example above: <code>http/localhost\.\d*/(stories)</code>. After matching the path against the regular expression, the replacement pattern is applied which allows references back to the capturing groups.</p>
@@ -211,7 +211,7 @@
<span class="p">}</span>
</pre></div>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1341376 by fmeschbe on Tue, 22 May 2012 09:41:06 +0000
+ Rev. 1475804 by dklco on Thu, 25 Apr 2013 14:45:50 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project
Modified: websites/staging/sling/trunk/content/documentation/the-sling-engine/request-parameters.html
==============================================================================
--- websites/staging/sling/trunk/content/documentation/the-sling-engine/request-parameters.html (original)
+++ websites/staging/sling/trunk/content/documentation/the-sling-engine/request-parameters.html Thu Apr 25 14:46:10 2013
@@ -170,7 +170,7 @@
<p>As of Sling Engine 2.1.0 the order or request parameters in the <code>getRequestParameterMap()</code>, <code>getParameterMap()</code>, and <code>getParameterNams()</code> is preserved as follows:</p>
<ul>
<li>The first entries are the parameters reported by the servlet container. The order of these parameters amongst each other is not defined. The <code>SlingHttpServletRequest</code> provides them in the same order as provided by the servlet container.</li>
-<li>After the servlet container provided parameters are parameters extracted from the request in case <code>multipart/form-data</code> 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: <em>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</em> (<a href="">17.13.4 Form content types</a>)</li>
+<li>After the servlet container provided parameters are parameters extracted from the request in case <code>multipart/form-data</code> 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: <em>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</em> (<a href="http://www.w3.org/TR/html401/interact/forms.html">17.13.4 Form content types</a>)</li>
</ul>
<p>Be warned: Only rely on request parameter ordering <code>multipart/form-data</code> POST requests without a query part in the request URL.</p>
<h2 id="character-encoding">Character Encoding</h2>
@@ -190,7 +190,7 @@
Up to and including Sling Engine 2.2.2 request parameters are always decoded with ISO-8859-1 encoding if the `\*charset\*` request parameter is missing. As of Sling Engine 2.2.4 the `\*charset\*` request parameter is optional. As of this version the Sling Main Servlet supports a configuration setting which allows to change the default character encoding used if the `\*charset\*` request parameter is missing. To enable this functionality set the `sling.default.parameter.encoding` parameter of the Sling Main Servlet (PID `org.apache.sling.engine.impl.SlingMainServlet`) configuration to the desired encoding, which of course must be supported by the actual Java Platform.
</div>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1464512 by bdelacretaz on Thu, 4 Apr 2013 13:03:31 +0000
+ Rev. 1475804 by dklco on Thu, 25 Apr 2013 14:45:50 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project
Modified: websites/staging/sling/trunk/content/documentation/the-sling-engine/url-decomposition.html
==============================================================================
--- websites/staging/sling/trunk/content/documentation/the-sling-engine/url-decomposition.html (original)
+++ websites/staging/sling/trunk/content/documentation/the-sling-engine/url-decomposition.html Thu Apr 25 14:46:10 2013
@@ -93,7 +93,7 @@
<li><em>Extension</em> - 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. </li>
<li><em>Suffix Path</em> - 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.</li>
</ol>
-<p>There's a cheat sheet on Day's dev page under <a href="">http://dev.day.com/content/docs/en/cq/current/developing/sling_cheatsheet.html</a> available to get you familiar with the URL decomposition of Sling.</p>
+<p>There's a cheat sheet on Day's dev page under <a href="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</a> available to get you familiar with the URL decomposition of Sling.</p>
<p><em>Examples</em>: Assume there is a Resource at <code>/a/b</code>, which has no children.</p>
<table>
<thead>
@@ -217,7 +217,7 @@
The [SlingRequestPathInfoTest](http://svn.apache.org/repos/asf/sling/trunk/bundles/engine/src/test/java/org/apache/sling/engine/impl/request/SlingRequestPathInfoTest.java) demonstrates and tests this decomposition. Feel free to suggest additional tests that help clarify how this works!
</div>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1464512 by bdelacretaz on Thu, 4 Apr 2013 13:03:31 +0000
+ Rev. 1475804 by dklco on Thu, 25 Apr 2013 14:45:50 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project
Modified: websites/staging/sling/trunk/content/links.html
==============================================================================
--- websites/staging/sling/trunk/content/links.html (original)
+++ websites/staging/sling/trunk/content/links.html Thu Apr 25 14:46:10 2013
@@ -89,30 +89,30 @@
<p>Here are some links to other resources</p>
<h2 id="articles">Articles</h2>
<ul>
-<li><a href="">Java Content Repository: The Best Of Both Worlds</a> - by Bertrand Delacretaz on Javalobby - uses the Sling HTTP interface to demonstrate JCR features.</li>
-<li><a href="">Accessing Relational Data as SLING RESTful URLs</a> - by Luca Masini</li>
-<li><a href="">Your First Day With Sakai Nakamura</a> - Sakai Nakamura is based on Sling, that introductory article has very good explanations of REST and Sling basics, and on why hierarchies are useful on the Web.</li>
+<li><a href="http://java.dzone.com/articles/java-content-repository-best">Java Content Repository: The Best Of Both Worlds</a> - by Bertrand Delacretaz on Javalobby - uses the Sling HTTP interface to demonstrate JCR features.</li>
+<li><a href="http://www.lucamasini.net/Home/sling-and-cq5/accessing-relational-data-as-sling-restful-urls">Accessing Relational Data as SLING RESTful URLs</a> - by Luca Masini</li>
+<li><a href="http://confluence.sakaiproject.org/display/KERNDOC/Your+First+Day+With+Sakai+Nakamura">Your First Day With Sakai Nakamura</a> - Sakai Nakamura is based on Sling, that introductory article has very good explanations of REST and Sling basics, and on why hierarchies are useful on the Web.</li>
</ul>
<h2 id="about-sling">About Sling</h2>
<ul>
-<li><a href="">Sling on dev.day.com</a> - Day's developers blog, regularly includes articles on Sling and JCR. Powered by Sling, of course.</li>
-<li><a href="">Sling on Lars Trieloff's Blog</a> - Lars regularly writes on his experiences with Sling. Most notably the mini series of three entries introducing Sling and microsling.</li>
-<li><a href="">Sling links at del.icio.us</a> - If you're a del.icio.us user, please tag Sling-related posts with both <em>sling</em> and <em>jcr</em> tags, so that they appear in that list.</li>
-<li><a href="">Sling on Fisheye</a> - code repository viewer, activity statistics, etc.</li>
-<li><a href="">Sling on ohloh</a> - activity and community statistics.</li>
-<li><a href="">Sling on MarkMail</a> - searchable mailing list archives.</li>
+<li><a href="http://dev.day.com/microsling/content/blogs/main.html?category=sling">Sling on dev.day.com</a> - Day's developers blog, regularly includes articles on Sling and JCR. Powered by Sling, of course.</li>
+<li><a href="http://weblogs.goshaky.com/weblogs/lars/tags/sling">Sling on Lars Trieloff's Blog</a> - Lars regularly writes on his experiences with Sling. Most notably the mini series of three entries introducing Sling and microsling.</li>
+<li><a href="http://del.icio.us/tag/sling+jcr">Sling links at del.icio.us</a> - If you're a del.icio.us user, please tag Sling-related posts with both <em>sling</em> and <em>jcr</em> tags, so that they appear in that list.</li>
+<li><a href="http://fisheye6.atlassian.com/browse/sling">Sling on Fisheye</a> - code repository viewer, activity statistics, etc.</li>
+<li><a href="https://www.ohloh.net/p/sling">Sling on ohloh</a> - activity and community statistics.</li>
+<li><a href="http://sling.markmail.org/">Sling on MarkMail</a> - searchable mailing list archives.</li>
</ul>
<h2 id="projects-using-sling">Projects using Sling</h2>
<ul>
-<li>Gert Vanthienen succeeded in installing Sling into the new Apache ServiceMix kernel and documented his experience <a href="">Sling On ServiceMix Kernel</a></li>
+<li>Gert Vanthienen succeeded in installing Sling into the new Apache ServiceMix kernel and documented his experience <a href="http://servicemix.apache.org/SMX4KNL/running-apache-sling-on-servicemix-kernel.html">Sling On ServiceMix Kernel</a></li>
</ul>
<h2 id="sling-presentations-and-screencasts">Sling Presentations and Screencasts</h2>
<ul>
-<li><a href="">Presentations tagged with "sling" at slideshare</a> </li>
+<li><a href="http://www.slideshare.net/tag/sling">Presentations tagged with "sling" at slideshare</a> </li>
</ul>
<p>The following screencasts demonstrate Day Software's CRX quickstart product, powered by Sling:
- * <a href="">First Steps with CRX Quickstart</a>
- * <a href="">TheServerSide.com in 15 minutes</a></p>
+ * <a href="http://dev.day.com/microsling/content/blogs/main/firststeps1.html">First Steps with CRX Quickstart</a>
+ * <a href="http://dev.day.com/microsling/content/blogs/main/firststeps2.html">TheServerSide.com in 15 minutes</a></p>
<h2 id="from-apachecon-eu-08">From ApacheCon EU 08</h2>
<ul>
<li><a href="">ApacheCon EU 08 Fast Feather Track Presentation on Sling</a></li>
@@ -121,17 +121,17 @@
<h2 id="from-apachecon-us-07">From ApacheCon US 07</h2>
<ul>
<li><a href="">ApacheCon US 07 Fast Feather Track Presentation on Sling</a></li>
-<li><a href="">Feathercast On Day 4 with an interview on Sling with Felix</a></li>
+<li><a href="http://feathercast.org/?p=59">Feathercast On Day 4 with an interview on Sling with Felix</a></li>
</ul>
<h2 id="technology-used-by-sling">Technology used by Sling</h2>
<ul>
-<li><a href="">Apache Jackrabbit</a> - The reference implementation of the Content Repository for Java (JCR) Specification. This implementation is used in Sling as the primary repository.</li>
-<li><a href="">JSR 170: Content Repository for Java{tm} technology API</a> - The specification of the repository API.</li>
-<li><a href="">Apache Felix</a> - The OSGi Framework implementation we use in Sling.</li>
-<li><a href="">The OSGi Alliance</a> - The OSGi Alliance is the specification body defining the OSGi Core and Compendium Services. These specifications are at the center of making Sling possible.</li>
+<li><a href="http://jackrabbit.apache.org">Apache Jackrabbit</a> - The reference implementation of the Content Repository for Java (JCR) Specification. This implementation is used in Sling as the primary repository.</li>
+<li><a href="http://www.jcp.org/en/jsr/detail?id=170">JSR 170: Content Repository for Java{tm} technology API</a> - The specification of the repository API.</li>
+<li><a href="http://felix.apache.org">Apache Felix</a> - The OSGi Framework implementation we use in Sling.</li>
+<li><a href="http://www.osgi.org">The OSGi Alliance</a> - The OSGi Alliance is the specification body defining the OSGi Core and Compendium Services. These specifications are at the center of making Sling possible.</li>
</ul>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1341361 by fmeschbe on Tue, 22 May 2012 08:54:04 +0000
+ Rev. 1475804 by dklco on Thu, 25 Apr 2013 14:45:50 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project
Modified: websites/staging/sling/trunk/content/news.html
==============================================================================
--- websites/staging/sling/trunk/content/news.html (original)
+++ websites/staging/sling/trunk/content/news.html Thu Apr 25 14:46:10 2013
@@ -124,7 +124,7 @@
<li>New Releases: Apache Sling Scripting JSP Support 2.0.16, JSP Taglib 2.1.2 (May 3rd, 2011)</li>
<li>New releases: Apache Sling Test Tools 1.0.2, JUnit Core 1.0.6, JUnit Remote Tests Runners 1.0.6, JUnit Scriptable Tests Provider 1.0.6, Sample Integration Tests 1.0.6, Sample Server-Side Tests 1.0.6, Failing Server-Side Tests 1.0.6 (April 26th, 2011)</li>
<li>New releases: Apache Sling I18N 2.1.0 (April 12, 2011)</li>
-<li>New releases: <a href="">Apache Sling 6</a>, Apache Sling Launchpad Content 2.0.6 (March 28, 2011)</li>
+<li>New releases: <a href="http://markmail.org/thread/hv5vd5774ofwqu6j">Apache Sling 6</a>, Apache Sling Launchpad Content 2.0.6 (March 28, 2011)</li>
<li>New releases: Apache Sling Launchpad Integration Tests 1.0.0, Apache Sling Launchpad Testing Services 2.0.8, Apache Sling Launchpad Testing Services WAR 2.0.8 (March 04, 2011)</li>
<li>New releases: Apache Sling Javascript 2.0.12 (February 26, 2011)</li>
<li>New releases: Apache Sling Explorer 1.0.2, Apache Sling JCR Resource 2.0.10, Apache Sling Engine 2.2.2, Apache Sling Installer IT Testing 3.1.2 (February 24, 2011)</li>
@@ -176,7 +176,7 @@
<li>Apache Sling has graduated into a top level project! (June 17, 2009)</li>
</ul>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1469719 by cziegeler on Fri, 19 Apr 2013 07:26:44 +0000
+ Rev. 1475804 by dklco on Thu, 25 Apr 2013 14:45:50 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project
Modified: websites/staging/sling/trunk/content/project-information.html
==============================================================================
--- websites/staging/sling/trunk/content/project-information.html (original)
+++ websites/staging/sling/trunk/content/project-information.html Thu Apr 25 14:46:10 2013
@@ -116,7 +116,7 @@
<td><a href="mailto:users-unsubscribe@sling.apache.org">Unsubscribe</a></td>
<td>users at sling.apache.org</td>
<td><a href="http://mail-archives.apache.org/mod_mbox/sling-users/">mail-archives.apache.org</a></td>
-<td><a href="http://www.mail-archive.com/users@sling.apache.org/">www.mail-archive.com</a> <a href="http://sling.markmail.org">MarkMail</a> <a href="http://n3.nabble.com/Sling-Users-f73968.html">Nabble</a></td>
+<td><a href="http://www.mail-archive.com/users@sling.apache.org/">www.mail-archive.com</a> <a href="http://sling.markmail.org">MarkMail</a> <a href="http://apache-sling.73963.n3.nabble.com/Sling-Users-f73968.html">Nabble</a></td>
</tr>
<tr>
<td>Sling Developers List</td>
@@ -124,7 +124,7 @@
<td><a href="mailto:dev-unsubscribe@sling.apache.org">Unsubscribe</a></td>
<td>dev at sling.apache.org</td>
<td><a href="http://mail-archives.apache.org/mod_mbox/sling-dev/">mail-archives.apache.org</a></td>
-<td><a href="http://www.mail-archive.com/dev@sling.apache.org/">www.mail-archive.com</a> <a href="http://sling.markmail.org">MarkMail</a> <a href="http://n3.nabble.com/Sling-Dev-f73966.html">Nabble</a></td>
+<td><a href="http://www.mail-archive.com/dev@sling.apache.org/">www.mail-archive.com</a> <a href="http://sling.markmail.org">MarkMail</a> <a href="http://apache-sling.73963.n3.nabble.com/Sling-Dev-f73966.html">Nabble</a></td>
</tr>
<tr>
<td>Sling Source Control List</td>
@@ -138,9 +138,9 @@
</table>
<h2 id="issue-tracking">Issue Tracking</h2>
<p>This project uses JIRA a J2EE-based, issue tracking and project management application. Issues, bugs, and feature requests should be submitted to the following issue tracking system for this project.</p>
-<p>The issue tracker can be found at <a href="">http://issues.apache.org/jira/browse/SLING</a></p>
+<p>The issue tracker can be found at <a href="http://issues.apache.org/jira/browse/SLING">http://issues.apache.org/jira/browse/SLING</a></p>
<h2 id="source-repository">Source Repository</h2>
-<p>This project uses Subversion to manage its source code. Instructions on Subversion use can be found at <a href="">http://svnbook.red-bean.com/</a>.</p>
+<p>This project uses Subversion to manage its source code. Instructions on Subversion use can be found at <a href="http://svnbook.red-bean.com/">http://svnbook.red-bean.com/</a>.</p>
<h3 id="web-access">Web Access</h3>
<p>The following is a link to the online source repository.</p>
<div class="codehilite"><pre><span class="n">http:</span><span class="sr">//s</span><span class="n">vn</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">org</span><span class="sr">/viewvc/s</span><span class="n">ling</span><span class="o">/</span><span class="n">trunk</span>
@@ -181,10 +181,10 @@
<h2 id="continuous-integration">Continuous Integration</h2>
-<p>Sling builds run automatically on the ASF's <a href="">Jenkins build server</a>, triggered by SVN changes and daily.</p>
-<p>See <a href="">SLING-920</a> for Hudson configuration information.</p>
+<p>Sling builds run automatically on the ASF's <a href="https://builds.apache.org/view/S-Z/view/Sling/">Jenkins build server</a>, triggered by SVN changes and daily.</p>
+<p>See <a href="https://issues.apache.org/jira/browse/SLING-920">SLING-920</a> for Hudson configuration information.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1420571 by fmeschbe on Wed, 12 Dec 2012 08:37:07 +0000
+ Rev. 1475804 by dklco on Thu, 25 Apr 2013 14:45:50 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project
Modified: websites/staging/sling/trunk/content/project-information/apache-sling-community-roles-and-processes.html
==============================================================================
--- websites/staging/sling/trunk/content/project-information/apache-sling-community-roles-and-processes.html (original)
+++ websites/staging/sling/trunk/content/project-information/apache-sling-community-roles-and-processes.html Thu Apr 25 14:46:10 2013
@@ -90,15 +90,15 @@
<h2 id="roles">Roles</h2>
<p>There are different roles with which Sling community members may be associated: User, Contributor, Committer, and PMC (Project Management Committee) Member. These roles are assigned and assumed based on merit. </p>
<p>The User and Contributor roles are acquired by using the software and participating in the community, but the Committer and PMC member roles can only be granted by a PMC vote.</p>
-<p>The roles defined here conform to the ASF's <a href="">definition of roles</a>.</p>
+<p>The roles defined here conform to the ASF's <a href="http://www.apache.org/foundation/how-it-works.html#roles">definition of roles</a>.</p>
<h3 id="users">Users</h3>
<p>Users are the people who use any of the products of the Sling project. People in this role are not contributing code, but they are using the products, reporting bugs, making feature requests, testing code, and such. This is by far the most important category of people, since without users there is no reason for Sling. When a user starts to contribute code or documentation patches, they become a <em>Contributor</em>.</p>
<h3 id="contributors">Contributors</h3>
<p>Contributors are the people who write code or documentation patches or contribute positively to the project in other ways. A volunteer's contribution is always recognized.</p>
<h3 id="committers">Committers</h3>
-<p>Contributors who give frequent and valuable contributions to a subproject of Sling can have their status promoted to that of a <em><a href="">Committer</a></em>. A Committer has write access to Sling's source code repository. Contributors of documentation are eligible as committers in the same way as contributors of pure code.</p>
+<p>Contributors who give frequent and valuable contributions to a subproject of Sling can have their status promoted to that of a <em><a href="http://www.apache.org/dev/committers.html">Committer</a></em>. A Committer has write access to Sling's source code repository. Contributors of documentation are eligible as committers in the same way as contributors of pure code.</p>
<h3 id="pmc-members">PMC Members</h3>
-<p>Committers showing continued interest in the project and taking an active part in the evolution of the project may be elected as <em><a href="">PMC</a> members</em>. The PMC (Project Management Committee) is the official managing body of project and is responsible for setting its overall direction.</p>
+<p>Committers showing continued interest in the project and taking an active part in the evolution of the project may be elected as <em><a href="http://www.apache.org/dev/pmc.html">PMC</a> members</em>. The PMC (Project Management Committee) is the official managing body of project and is responsible for setting its overall direction.</p>
<h2 id="processes">Processes</h2>
<h3 id="becoming-a-user-or-contributor">Becoming a User or Contributor</h3>
<p>There is no requirement for becoming a User or Contributor; these roles are open to everyone.</p>
@@ -112,7 +112,7 @@
<p>To have the Committer being accepted as a PMC member, the ASF Board has acknowledge the addition to the PMC. The Committer should not be consulted about his/her desire to become a PMC member before the board acknowledgement, or be informed that they are being considered, since this could create hard feelings if the vote does not pass.</p>
<p>Upon a positive vote result, the PMC member will be emailed by the PMC to invite him/her to become a PMC member. If the invitation is accepted, an announcement about the new PMC member is made to the developer mailing list.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1341376 by fmeschbe on Tue, 22 May 2012 09:41:06 +0000
+ Rev. 1475804 by dklco on Thu, 25 Apr 2013 14:45:50 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project
Modified: websites/staging/sling/trunk/content/project-information/project-team.html
==============================================================================
--- websites/staging/sling/trunk/content/project-information/project-team.html (original)
+++ websites/staging/sling/trunk/content/project-information/project-team.html Thu Apr 25 14:46:10 2013
@@ -250,7 +250,7 @@
</tr>
</tbody>
</table>
-<p>Committers marked with an asterisk (*) are also members of the Sling Project Management Commitee (<a href="">PMC</a>) as defined in [Apache Sling Community Roles and Processes]</p>
+<p>Committers marked with an asterisk (*) are also members of the Sling Project Management Commitee (<a href="http://www.apache.org/dev/pmc.html">PMC</a>) as defined in [Apache Sling Community Roles and Processes]</p>
<h2 id="emeritus-committers-and-pmc-members">Emeritus Committers and PMC members</h2>
<p>The following list of former committers and/or PMC members have chosen to go emeritus. We are still thankful for their help and guidance during earlier phases of the Sling project.</p>
<table>
@@ -284,7 +284,7 @@
<h2 id="contributors">Contributors</h2>
<p>There are no contributors listed for this project.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1470841 by bdelacretaz on Tue, 23 Apr 2013 08:00:34 +0000
+ Rev. 1475804 by dklco on Thu, 25 Apr 2013 14:45:50 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project
Modified: websites/staging/sling/trunk/content/project-information/security.html
==============================================================================
--- websites/staging/sling/trunk/content/project-information/security.html (original)
+++ websites/staging/sling/trunk/content/project-information/security.html Thu Apr 25 14:46:10 2013
@@ -90,7 +90,7 @@
<p>The Apache Software Foundation takes a very active stance in eliminating security problems and denial of service attacks against Apache Sling.</p>
<p>We strongly encourage folks to report such problems to our private security mailing list first, before disclosing them in a public forum.</p>
<p><em>Please note that the security mailing list should only be used for reporting undisclosed security vulnerabilities in Apache Sling and managing the process of fixing such vulnerabilities. We cannot accept regular bug reports or other queries at this address. All mail sent to this address that does not relate to an undisclosed security problem in the Apache Sling source code will be ignored.</em></p>
-<p>If you need to report a bug that isn't an undisclosed security vulnerability, please use our <a href="">public issue tracker</a>.</p>
+<p>If you need to report a bug that isn't an undisclosed security vulnerability, please use our <a href="https://issues.apache.org/jira/browse/SLING">public issue tracker</a>.</p>
<p>Questions about:</p>
<ul>
<li>how to configure Sling securely</li>
@@ -101,11 +101,11 @@
<p>should be addressed to our public users mailing list. Please see the <a href="/project-information.html">Project Information</a> page for details of how to subscribe.</p>
<p>The private security mailing address is: <a href="">mailto:security@sling.apache.org</a>.</p>
<p>Note that all networked servers are subject to denial of service attacks, and we cannot promise magic workarounds to generic problems (such as a client streaming lots of data to your server, or re-requesting the same URL repeatedly). In general our philosophy is to avoid any attacks which can cause the server to consume resources in a non-linear relationship to the size of inputs.</p>
-<p>For more information on handling security issues at the Apache Software Foundation please refer to the <a href="">ASF Security Team</a> page.</p>
+<p>For more information on handling security issues at the Apache Software Foundation please refer to the <a href="http://www.apache.org/security/">ASF Security Team</a> page.</p>
<h1 id="errors-and-omissions">Errors and omissions</h1>
<p>Please report any errors or omissions to <a href="">mailto:security@sling.apache.org</a>.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1341376 by fmeschbe on Tue, 22 May 2012 09:41:06 +0000
+ Rev. 1475804 by dklco on Thu, 25 Apr 2013 14:45:50 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project