svn commit: r875905 - in /websites/staging/jena/trunk/content: ./ documentation/jdbc/index.html

[bu...@apache.org]

Author: buildbot
Date: Fri Aug 23 21:17:50 2013
New Revision: 875905

Log:
Staging update by buildbot for jena

Modified:
    websites/staging/jena/trunk/content/   (props changed)
    websites/staging/jena/trunk/content/documentation/jdbc/index.html

Propchange: websites/staging/jena/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Aug 23 21:17:50 2013
@@ -1 +1 @@
-1517041
+1517042

Modified: websites/staging/jena/trunk/content/documentation/jdbc/index.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/jdbc/index.html (original)
+++ websites/staging/jena/trunk/content/documentation/jdbc/index.html Fri Aug 23 21:17:50 2013
@@ -114,6 +114,7 @@ are supported.  Otherwise it is a fully 
 <li><a href="#making-queries">Making Queries</a></li>
 <li><a href="#alternatives">Alternatives</a></li>
 <li><a href="drivers.html">Jena JDBC Drivers</a></li>
+<li><a href="artifacts.html">Maven Artifacts for Jena JDBC</a></li>
 <li><a href="custom_driver.html">Implementing a custom Jena JDBC Driver</a></li>
 </ul>
 <h2 id="overview">Overview</h2>
@@ -128,6 +129,8 @@ either SPARQL queries or updates and pro
 <p>These are all built on a core library which can be used to build <a href="custom_driver.html">custom drivers</a>
 if desired.  This means that all drivers share common infrastructure and thus exhibit broadly speaking
 the same behavior around handling queries, updates and results.</p>
+<p>Jena JDBC is part of the standard Jena distributions and may be <a href="/download/">downloaded</a> as normal or used
+via its <a href="artifacts.html">maven artifacts</a>.</p>
 <h3 id="treatment-of-results">Treatment of Results</h3>
 <p>One important behavioral aspect to understand is how results are treated compared to a traditional
 JDBC driver.  SPARQL provides four query forms and thus four forms of results while JDBC assumes all