sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r921266 - in /websites/staging/sis/trunk/content: ./ book/en/developer-guide.html branches.html index.html release-management.html source.html
Date Thu, 04 Sep 2014 22:29:55 GMT
Author: buildbot
Date: Thu Sep  4 22:29:55 2014
New Revision: 921266

Log:
Staging update by buildbot for sis

Modified:
    websites/staging/sis/trunk/content/   (props changed)
    websites/staging/sis/trunk/content/book/en/developer-guide.html
    websites/staging/sis/trunk/content/branches.html
    websites/staging/sis/trunk/content/index.html
    websites/staging/sis/trunk/content/release-management.html
    websites/staging/sis/trunk/content/source.html

Propchange: websites/staging/sis/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Sep  4 22:29:55 2014
@@ -1 +1 @@
-1621162
+1622571

Modified: websites/staging/sis/trunk/content/book/en/developer-guide.html
==============================================================================
Binary files - no diff available.

Modified: websites/staging/sis/trunk/content/branches.html
==============================================================================
--- websites/staging/sis/trunk/content/branches.html (original)
+++ websites/staging/sis/trunk/content/branches.html Thu Sep  4 22:29:55 2014
@@ -82,7 +82,7 @@
           <section id="content" class="row">
             <article class="span12">
               <p class="page-title">Apache SIS branches</p>
-              <p>The <a href="source.html">source code repository</a> contains
JDK6 and JDK7 branches together with the trunk.
+              <p>The <a href="source.html">source code repository</a> contains
JDK6, JDK7 and JDK8 branches together with the trunk.
 The Apache SIS releases are created from the code on the trunk only.
 However the actual development often occur on a branch before to be merged to the trunk.
 Those branches exist in order to experiment early the new technologies — since it may
impact
@@ -92,6 +92,7 @@ for making merges easier, then provides 
 <div class="toc">
 <ul>
 <li><a href="#development">The development branches</a><ul>
+<li><a href="#jdk8">branches/JDK8</a></li>
 <li><a href="#jdk7">branches/JDK7</a></li>
 <li><a href="#jdk6">branches/JDK6</a></li>
 <li><a href="#trunk">trunk</a></li>
@@ -113,15 +114,20 @@ for making merges easier, then provides 
 </div>
 <h1 id="development">The development branches</h1>
 <p>Developers are encouraged to select the first branch listed below, in that order,
which meet their needs.</p>
-<h2 id="jdk7">branches/JDK7</h2>
-<p>The JDK7 branch is the recommended development branch for developers who can use
a JDK7 environment.
+<h2 id="jdk8">branches/JDK8</h2>
+<p>The JDK8 branch is the recommended development branch for developers who can use
a JDK8 environment.
 This branch implements the interfaces defined in the <a href="http://www.geoapi.org/snapshot/index.html">GeoAPI
snapshot</a> milestones
-and uses some JDK7-specific features like:</p>
+and uses some JDK8 or JDK7-specific features like:</p>
 <ul>
 <li>Syntax enhancements, mostly in exception handling (<em>try-with-resources</em>,
<em>multi-catches</em>)
     but also on other aspects like <em>diamond operator</em>.</li>
 <li>Leveraging of new API (<em>suppressed exceptions</em>, <em>file
systems</em>, <em>fork join</em>).</li>
 </ul>
+<h2 id="jdk7">branches/JDK7</h2>
+<p>The JDK7 branch is a merge of the JDK8 branch ported to the JDK7 platform.
+The JDK7 branch implements the same GeoAPI interfaces than the JDK8 branch;
+the only differences (apart version number) are the modifications necessary
+for building and running on a JDK7 platform.</p>
 <h2 id="jdk6">branches/JDK6</h2>
 <p>The JDK6 branch is a merge of the JDK7 branch ported to the JDK6 platform.
 This is the recommended development branch for developers who can not use a JDK7 environment,

Modified: websites/staging/sis/trunk/content/index.html
==============================================================================
--- websites/staging/sis/trunk/content/index.html (original)
+++ websites/staging/sis/trunk/content/index.html Thu Sep  4 22:29:55 2014
@@ -108,7 +108,7 @@ The version under development is 0.5-SNA
 <ul>
 <li><a href="source.html">Source code</a>: fetching the code, opening in
an IDE, developing, formatting.</li>
 <li><a href="build.html">Build</a>: build from the source, create the PACK200
file.</li>
-<li><a href="branches.html">Branches</a>: trunk, JDK6, JDK7.</li>
+<li><a href="branches.html">Branches</a>: trunk, JDK6, JDK7, JDK8.</li>
 <li><a href="http://issues.apache.org/jira/browse/SIS">Issue tracking</a>:
JIRA.</li>
 <li><a href="http://reviews.apache.org/groups/sis">Code review</a></li>
 <li><a href="release-management.html">Release management</a> (for release
managers)</li>

Modified: websites/staging/sis/trunk/content/release-management.html
==============================================================================
--- websites/staging/sis/trunk/content/release-management.html (original)
+++ websites/staging/sis/trunk/content/release-management.html Thu Sep  4 22:29:55 2014
@@ -379,12 +379,12 @@ This will also verify the checksums.</p>
 
 
 <h1 id="stage">Stage the source, binary and javadoc artifacts</h1>
-<p>Generate the Javadoc. While not mandatory, we suggest to use JDK 7 or above for
getting the new look and feel,
+<p>Generate the Javadoc. While not mandatory, we suggest to use JDK 8 or above for
getting the new look and feel,
 getting the Javadoc enhancements expected in future JDK releases (more dynamic pages),
 avoiding the security vulnerability discovered in the Javadoc tools of older JDK releases,
 and keeping the <code>diff</code> smaller on the SVN repository of SIS web site.
-If JDK7 is <em>not</em> used, then omit the <code>cp</code> command
below.</p>
-<div class="codehilite"><pre>cp ../../JDK7/src/main/javadoc/stylesheet.css src/main/javadoc/
+If JDK8 is <em>not</em> used, then omit the <code>cp</code> command
below.</p>
+<div class="codehilite"><pre>cp ../../JDK8/src/main/javadoc/stylesheet.css src/main/javadoc/
 mvn site --define <span class="nv">skipTests</span><span class="o">=</span><span
class="nb">true</span>
 svn revert src/main/javadoc/stylesheet.css
 <span class="nb">cd </span>target/site
@@ -593,7 +593,7 @@ svn delete https://dist.apache.org/repos
 
 
 <p>Edit the version number in the <code>application/sis-console/src/main/artifact/README</code>
file.
-Report the changes manually on the JDK6 and JDK7 branches.</p>
+Report the changes manually on the JDK6, JDK7 and JDK8 branches.</p>
             </article>
           </section>
         </div><!--/span-->

Modified: websites/staging/sis/trunk/content/source.html
==============================================================================
--- websites/staging/sis/trunk/content/source.html (original)
+++ websites/staging/sis/trunk/content/source.html Thu Sep  4 22:29:55 2014
@@ -128,7 +128,7 @@ For fetching the source code, choose one
 </ul>
 </div>
 <h1 id="ide">Opening Apache SIS in an IDE</h1>
-<p>Different SIS branches are available depending on the target platforms (JDK6 versus
JDK7, or GeoAPI versions).
+<p>Different SIS branches are available depending on the target platforms (JDK6 versus
JDK7 or JDK8, or GeoAPI versions).
 The alternatives are listed in the <a href="branches.html">branches page</a>.
 This section documents how to checkout the trunk for development with Subversion,
 but the same instructions should work for any branch or for Git.</p>



Mime
View raw message