Author: buildbot
Date: Sun Jul 19 19:42:51 2015
New Revision: 958975

Log:
Staging update by buildbot for jena

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

Propchange: websites/staging/jena/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Jul 19 19:42:51 2015
@@ -1 +1 @@
-1691339
+1691848

Modified: 
websites/staging/jena/trunk/content/documentation/migrate_jena2_jena3.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/migrate_jena2_jena3.html 
(original)
+++ websites/staging/jena/trunk/content/documentation/migrate_jena2_jena3.html 
Sun Jul 19 19:42:51 2015
@@ -157,25 +157,27 @@
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, 
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, 
dt:hover > .elementid-permalink { visibility: visible }</style>
 <p>Apache Jena3 is a major version release for Jena - it is not binary 
compatibly with
 Jena2. The migration consists of package renaming and database reloading.</p>
-<blockquote>
-<p>@@ Logger name changes
-@@ java:
-@@ assemblers
-@@ version numbers</p>
-</blockquote>
 <h2 id="key-changes">Key Changes<a class="headerlink" href="#key-changes" 
title="Permanent link">&para;</a></h2>
 <ul>
 <li><a href="#packaging">Package renaming</a></li>
 <li><a href="#rdf11-plain-literals">RDF 1.1 Semantics for plain 
literals</a></li>
 <li><a href="#persistent-data">Persistent data (TDB, SDB) should be 
reloaded.</a></li>
+<li>Java8 is required.</li>
 </ul>
 <h2 id="packaging">Package Name Changes<a class="headerlink" href="#packaging" 
title="Permanent link">&para;</a></h2>
 <p>Packages with a base name of <code>com.hp.hpl.jena</code> become 
<code>org.apache.jena</code>.</p>
 <p>Global replacement of <code>import com.hp.hpl.jena.</code> with <code>import
 org.apache.jena.</code> will cover the majority of cases.</p>
 <p>The Jena APIs remain unchanged expect for this renaming.</p>
+<h3 id="vocaabularies-unchanged">Vocaabularies unchanged<a class="headerlink" 
href="#vocaabularies-unchanged" title="Permanent link">&para;</a></h3>
 <p>Only java package names are being changed.  Vocabularies are not 
affected.</p>
-<p>@@ <em>Provisional : We need to identify if any other key changes are to be 
included.</em></p>
+<h3 id="assemblers">Assemblers<a class="headerlink" href="#assemblers" 
title="Permanent link">&para;</a></h3>
+<p>Migration support is provided by mapping <code>ja:loadClass</code> names 
beginning
+<code>com.hp.hpl.jena</code> internally to <code>org.apache.jena</code>. A 
warning is logged.</p>
+<p>Any assmeeberlers that </p>
+<h3 id="logging">Logging<a class="headerlink" href="#logging" title="Permanent 
link">&para;</a></h3>
+<p>This will also affect logging: logger names reflect the java class naming
+so loggers for <code>com.hp.hpl.jena</code> become 
<code>org.apache.jena</code></p>
 <h2 id="rdf-11">RDF 1.1<a class="headerlink" href="#rdf-11" title="Permanent 
link">&para;</a></h2>
 <p>Many of the changes and refinements for RDF 1.1 are already in Jena2. The
 parsers for Turtle-family languages already follow the RDF 1.1 grammars
@@ -220,10 +222,9 @@ tag.</p>
 <p>Data that does not use explicit <code>xsd:string</code> should be safe but 
it is still
 recommended that data is reloaded at a convenient time.</p>
 <h2 id="other">Other<a class="headerlink" href="#other" title="Permanent 
link">&para;</a></h2>
-<p>Gone:
-ModelFactory.createFileModelMaker // JA.FileModel</p>
-<p>Gone:
-GraphStore</p>
+<p>The <code>GraphStore</code> interface has been removed.</p>
+<p><code>ModelFactory.createFileModelMaker</code> has been removed.</p>
+<p>See [security/] for changes to <code>jena-permission</code>.</p>
   </div>
 </div>
 


Reply via email to