You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by ra...@apache.org on 2016/11/01 10:15:03 UTC
svn commit: r1767468 -
/sling/site/trunk/content/documentation/bundles/scripting/scripting-htl.mdtext
Author: radu
Date: Tue Nov 1 10:15:03 2016
New Revision: 1767468
URL: http://svn.apache.org/viewvc?rev=1767468&view=rev
Log:
CMS commit to sling by radu
Modified:
sling/site/trunk/content/documentation/bundles/scripting/scripting-htl.mdtext
Modified: sling/site/trunk/content/documentation/bundles/scripting/scripting-htl.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/scripting/scripting-htl.mdtext?rev=1767468&r1=1767467&r2=1767468&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/scripting/scripting-htl.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/scripting/scripting-htl.mdtext Tue Nov 1 10:15:03 2016
@@ -397,7 +397,7 @@ The following table summarises the pros
<tr>
<td>Sling Models Use Provider</td>
<td><ul><li>convenient injection annotations for data retrieval</li><li>easy to extend from other Sling Models</li><li>simple setup for unit testing</li></ul></td>
- <td><ul><li>lacks flexibility in terms of component overlaying, relying on <code>service.ranking</code> configurations</li></ul></td>
+ <td><ul><li>lacks flexibility in terms of component overlaying, relying on <code>service.ranking</code> configurations; this was solved for Sling Models 1.3.0 by <a href="https://issues.apache.org/jira/browse/SLING-5992">SLING-5992</a></li></ul></td>
</tr>
<tr>
<td>Java Use Provider</td>