sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r965136 - /websites/staging/sis/trunk/content/
Date Fri, 11 Sep 2015 19:49:19 GMT
Author: buildbot
Date: Fri Sep 11 19:49:16 2015
New Revision: 965136

Log:
Staging update by buildbot for sis

Modified:
    websites/staging/sis/trunk/content/   (props changed)
    websites/staging/sis/trunk/content/branches.html
    websites/staging/sis/trunk/content/build.html
    websites/staging/sis/trunk/content/code-patterns.html
    websites/staging/sis/trunk/content/command-line.html
    websites/staging/sis/trunk/content/contributor.html
    websites/staging/sis/trunk/content/downloads.html
    websites/staging/sis/trunk/content/faq.html
    websites/staging/sis/trunk/content/index.html
    websites/staging/sis/trunk/content/license.html
    websites/staging/sis/trunk/content/mail-lists.html
    websites/staging/sis/trunk/content/release-management-setup.html
    websites/staging/sis/trunk/content/release-management.html
    websites/staging/sis/trunk/content/site-management.html
    websites/staging/sis/trunk/content/source.html
    websites/staging/sis/trunk/content/team-list.html

Propchange: websites/staging/sis/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Sep 11 19:49:16 2015
@@ -1 +1 @@
-1702538
+1702541

Modified: websites/staging/sis/trunk/content/branches.html
==============================================================================
--- websites/staging/sis/trunk/content/branches.html (original)
+++ websites/staging/sis/trunk/content/branches.html Fri Sep 11 19:49:16 2015
@@ -82,7 +82,18 @@
           <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, JDK7 and JDK8 branches together with the trunk.
+              <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+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>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
@@ -112,9 +123,9 @@ for making merges easier, then provides
 </li>
 </ul>
 </div>
-<h1 id="development">The development branches</h1>
+<h1 id="development">The development branches<a class="headerlink" href="#development" title="Permanent link">&para;</a></h1>
 <p>Developers are encouraged to select the first branch listed below, in that order, which meet their needs.</p>
-<h2 id="jdk8">branches/JDK8</h2>
+<h2 id="jdk8">branches/JDK8<a class="headerlink" href="#jdk8" title="Permanent link">&para;</a></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 JDK8 or JDK7-specific features like:</p>
@@ -123,12 +134,12 @@ and uses some JDK8 or JDK7-specific feat
     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>
+<h2 id="jdk7">branches/JDK7<a class="headerlink" href="#jdk7" title="Permanent link">&para;</a></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>
+<h2 id="jdk6">branches/JDK6<a class="headerlink" href="#jdk6" title="Permanent link">&para;</a></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,
 but still want to work closely with latest GeoAPI interfaces.
@@ -144,7 +155,7 @@ for building and running on a JDK6 platf
 <li>Imports of <code>java.util.Objects</code> replaced by imports of <code>org.apache.sis.internal.util.Objects</code>.</li>
 <li>Other JDK7-specific features resolved on a case-by-case basis.</li>
 </ul>
-<h2 id="trunk">trunk</h2>
+<h2 id="trunk">trunk<a class="headerlink" href="#trunk" title="Permanent link">&para;</a></h2>
 <p>The trunk is a merge of the JDK6 branch ported to the interfaces defined by the <a href="http://www.geoapi.org/3.0/index.html">GeoAPI stable release</a>.
 This is the code which is built by the continuous integration system and deployed on the Maven repository.
 The only differences (apart version number) compared to the JDK6 branch are the modifications
@@ -153,7 +164,7 @@ necessary for implementing an older vers
 <li>Usages of non-existent GeoAPI interfaces are replaced by direct usages of the
     corresponding Apache SIS implementation.</li>
 </ul>
-<h1 id="behavior">Behavioral differences between the branches</h1>
+<h1 id="behavior">Behavioral differences between the branches<a class="headerlink" href="#behavior" title="Permanent link">&para;</a></h1>
 <p>Some JDK7-specific features are reproduced on the JDK6 branch in an approximative way,
 which may cause some differences in application behavior (ignoring differences in performance).
 Most differences are about the JDK7 branch being slightly stricter than the JDK6 branch is,
@@ -174,9 +185,9 @@ or being able to handle information that
 </li>
 </ul>
 <p>Regarding all above points, the trunk is identical to the JDK6 branch.</p>
-<h1 id="recommendations">Coding recommendations</h1>
+<h1 id="recommendations">Coding recommendations<a class="headerlink" href="#recommendations" title="Permanent link">&para;</a></h1>
 <p>The following recommendations aim to make the merges easier by reducing the extend of potential conflicts.</p>
-<h2 id="formatting">Formatting</h2>
+<h2 id="formatting">Formatting<a class="headerlink" href="#formatting" title="Permanent link">&para;</a></h2>
 <p>Refrain from doing massive code reformatting unless:</p>
 <ul>
 <li>the modified files do not yet exist on the other branches;</li>
@@ -213,7 +224,7 @@ this example we aim to preserve the inde
 </pre></div>
 
 
-<h2 id="imports">Import statements</h2>
+<h2 id="imports">Import statements<a class="headerlink" href="#imports" title="Permanent link">&para;</a></h2>
 <p>Isolate at the end of the imports section any import statements that are specific to a platform.
 This separation allows any branch to re-arrange the common import statements without generating
 conflicts with the platform-dependent import statements. Example:</p>
@@ -226,16 +237,16 @@ conflicts with the platform-dependent im
 </pre></div>
 
 
-<h2 id="substitutions">Substitution for non-existent classes</h2>
+<h2 id="substitutions">Substitution for non-existent classes<a class="headerlink" href="#substitutions" title="Permanent link">&para;</a></h2>
 <p>When using a JDK7 class that does not exist on JDK6, define a class of the same name in a
 <code>org.apache.sis.internal</code> sub-package with the minimal amount of needed functionalities,
 provided that it can be done with reasonable effort. Otherwise just delete the JDK7-dependent
 code from the JDK6 branch.</p>
-<h1 id="merges">Performing the merges</h1>
+<h1 id="merges">Performing the merges<a class="headerlink" href="#merges" title="Permanent link">&para;</a></h1>
 <p>Subversion 1.5 and later maintain a <code>svn:mergeinfo</code> property which make merge operations much easier.
 In order to get those merge information properly maintained, no merge operation shall be performed
 with older Subversion tools.</p>
-<h2 id="merge-two-branches">Merging changes between two branches</h2>
+<h2 id="merge-two-branches">Merging changes between two branches<a class="headerlink" href="#merge-two-branches" title="Permanent link">&para;</a></h2>
 <p>The branches and trunk checkout directories can be located anywhere on the developer machine.
 The following example assumes that the current directory contains the following sub-directories:</p>
 <ul>
@@ -278,7 +289,7 @@ mvn install
 </pre></div>
 
 
-<h2 id="merge-record-only">Declaring that some changes shall not be merged</h2>
+<h2 id="merge-record-only">Declaring that some changes shall not be merged<a class="headerlink" href="#merge-record-only" title="Permanent link">&para;</a></h2>
 <p>If a developers wants to apply some changes specific to the JDK7 platform and tells
 Subversion to not propagate those changes to the JDK6 branch, then the following
 procedure shall be applied:</p>
@@ -304,7 +315,7 @@ svn commit --message <span class="s2">&q
 
   <footer class="footer">
     <div class="container">
-      <p>Copyright &copy; 2013-2014 The Apache Software Foundation, Licensed under the
+      <p>Copyright &copy; 2013-2015 The Apache Software Foundation, Licensed under the
         <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
           Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
     </div>

Modified: websites/staging/sis/trunk/content/build.html
==============================================================================
--- websites/staging/sis/trunk/content/build.html (original)
+++ websites/staging/sis/trunk/content/build.html Fri Sep 11 19:49:16 2015
@@ -82,7 +82,18 @@
           <section id="content" class="row">
             <article class="span12">
               <p class="page-title">Build from source</p>
-              <p>Apache SIS is built by Maven.
+              <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+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 SIS is built by Maven.
 For installing the JAR files in the local Maven repository, execute the following command
 from the SIS project root:</p>
 <div class="codehilite"><pre>mvn install
@@ -104,7 +115,7 @@ from the SIS project root:</p>
 </li>
 </ul>
 </div>
-<h1 id="dist">Distribution file and Pack200 bundle</h1>
+<h1 id="dist">Distribution file and Pack200 bundle<a class="headerlink" href="#dist" title="Permanent link">&para;</a></h1>
 <p>The Pack200 bundle is a file with the <code>.pack.gz</code> extension containing all SIS modules except <code>sis-webapp</code>
 (because Web applications use an other packaging) together with their dependencies.
 Pack200 files are uncompressed by the <code>unpack200</code> command provided in JDK/JRE installation.
@@ -121,7 +132,7 @@ if there is many versions of the plugin
 <p>The result will be created in the <code>target/distribution/apache-sis-&lt;version&gt;.zip</code> file.
 To test, uncompress in any directory and execute <code>apache-sis-&lt;version&gt;/bin/sis</code>.
 The Pack200 file will be automatically uncompressed when first needed.</p>
-<h2 id="pack200">Generating the Pack200 file alone</h2>
+<h2 id="pack200">Generating the Pack200 file alone<a class="headerlink" href="#pack200" title="Permanent link">&para;</a></h2>
 <p>If only the Pack200 file is desired, without the distribution ZIP file,
 one can use the following command:</p>
 <div class="codehilite"><pre>mvn org.apache.sis.core:sis-build-helper:pack --non-recursive
@@ -136,19 +147,19 @@ To uncompress that file, use the followi
 
 <p>The Pack200 bundle does not include the <code>sis-webapp</code> module because the later can be downloaded
 as a <code>WAR</code> file from the Maven repository.</p>
-<h2 id="limitations">Known limitations</h2>
+<h2 id="limitations">Known limitations<a class="headerlink" href="#limitations" title="Permanent link">&para;</a></h2>
 <p>The current plugin implementation has some hard-coded values, especially:</p>
 <ul>
 <li>The ZIP file content is copied from the <code>application/sis-console/src/main/artifact</code> directory.</li>
 <li>The Pack200 file path inside the ZIP file is hard-coded to <code>lib/sis.pack.gz</code>.</li>
 <li>The final filename is hard-coded to <code>apache-sis-&lt;version&gt;.zip</code>.</li>
 </ul>
-<h1 id="build-helper">SIS-specific Maven plugin</h1>
+<h1 id="build-helper">SIS-specific Maven plugin<a class="headerlink" href="#build-helper" title="Permanent link">&para;</a></h1>
 <p>Apache SIS uses a <code>sis-build-helper</code> plugin for SIS-specific tasks and Javadoc customization.
 This plugin is used automatically by <code>mvn install</code>. Consequently the remaining of this page
 can be safely ignored. This page is provided only as a reference for developers wanting to
 take a closer look to SIS <code>pom.xml</code> file.</p>
-<h2 id="resources">Localized resources compiler</h2>
+<h2 id="resources">Localized resources compiler<a class="headerlink" href="#resources" title="Permanent link">&para;</a></h2>
 <p>Localized resources are provided in <code>*.properties</code> files as specified by the <code>java.util.PropertyResourceBundle</code> standard class.
 However SIS does not use those resources files directly. Instead <code>*.properties</code> files are transformed into binary files having
 the same filename but the <code>.utf</code> extension. This conversion is done for efficiency, for convenience (the compiler applies the
@@ -187,7 +198,7 @@ the constants in the <code>Keys</code> i
 </pre></div>
 
 
-<h2 id="jar-collect">JAR files collector</h2>
+<h2 id="jar-collect">JAR files collector<a class="headerlink" href="#jar-collect" title="Permanent link">&para;</a></h2>
 <p>Links or lists all JAR files (including dependencies) in the <code>target/binaries</code> directory of the parent project.
 This plugin performs a work similar to the standard Maven assembly plugin work, with the following differences:</p>
 <ul>
@@ -225,7 +236,7 @@ This plugin performs a work similar to t
 
   <footer class="footer">
     <div class="container">
-      <p>Copyright &copy; 2013-2014 The Apache Software Foundation, Licensed under the
+      <p>Copyright &copy; 2013-2015 The Apache Software Foundation, Licensed under the
         <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
           Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
     </div>

Modified: websites/staging/sis/trunk/content/code-patterns.html
==============================================================================
--- websites/staging/sis/trunk/content/code-patterns.html (original)
+++ websites/staging/sis/trunk/content/code-patterns.html Fri Sep 11 19:49:16 2015
@@ -82,7 +82,18 @@
           <section id="content" class="row">
             <article class="span12">
               <p class="page-title">Recommended code patterns</p>
-              <p>This page lists some recommended code pattern for developing or using Apache SIS.</p>
+              <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+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>This page lists some recommended code pattern for developing or using Apache SIS.</p>
 <div class="toc">
 <ul>
 <li><a href="#referencing">Referencing</a><ul>
@@ -106,28 +117,28 @@
 </li>
 </ul>
 </div>
-<h1 id="referencing">Referencing</h1>
+<h1 id="referencing">Referencing<a class="headerlink" href="#referencing" title="Permanent link">&para;</a></h1>
 <p>Recommended code pattern when using the <code>sis-referencing</code> module.</p>
-<h2 id="axisOrder">Never explicitely swap ordinates for axis order</h2>
+<h2 id="axisOrder">Never explicitely swap ordinates for axis order<a class="headerlink" href="#axisOrder" title="Permanent link">&para;</a></h2>
 <p>The <a href="faq.html#axisOrder">axis order issue</a> causes lot of confusion,
 and developers are sometime tempted to swap their ordinate values in order to comply with some expected axis ordering.
 It should never be necessary, since the Apache SIS referencing engine manages axis order transparently — provided that
 the Coordinate Reference System (<abbr title="Coordinate Reference System">CRS</abbr>) definition is accurate. If a code needs to swap ordinates, this is probably an
 indication that the <abbr title="Coordinate Reference System">CRS</abbr> has not been properly defined. Instead than patching the coordinate values, try to make sure
-that the <em>Source <abbr title="Coordinate Reference System"><abbr title="Coordinate Reference System">CRS</abbr></abbr></em> (associated to the original data) and the <em>Target <abbr title="Coordinate Reference System"><abbr title="Coordinate Reference System">CRS</abbr></abbr></em> (the coordinate space where to perform the
+that the <em>Source <abbr title="Coordinate Reference System">CRS</abbr></em> (associated to the original data) and the <em>Target <abbr title="Coordinate Reference System">CRS</abbr></em> (the coordinate space where to perform the
 work) are properly defined, and let the referencing engine performs the conversion from the source to the target <abbr title="Coordinate Reference System">CRS</abbr>.</p>
-<h1 id="coverage">Coverages</h1>
+<h1 id="coverage">Coverages<a class="headerlink" href="#coverage" title="Permanent link">&para;</a></h1>
 <p>Recommended code pattern when using the <code>sis-coverage</code> module.</p>
-<h2 id="gridToCRS">Georeference images with affine transforms, <em>not</em> bounding boxes</h2>
+<h2 id="gridToCRS">Georeference images with affine transforms, <em>not</em> bounding boxes<a class="headerlink" href="#gridToCRS" title="Permanent link">&para;</a></h2>
 <p>Many users define the geographic extent of an image by its corner locations.
 This approach is not sufficient as it does not specify if the (<var>x</var>,<var>y</var>) axes are interchanged
 (see the <a href="faq.html#axisOrder">axis order issue</a>) or if the <var>y</var> axis is oriented downward.
 All images in SIS shall be georeferenced by at least an affine transform (more complex transforms are also possible),
 never by a rectangle or bounding box.
 In the two-dimensional case, the standard <code>java.awt.geom.AffineTransform</code> class can be used.</p>
-<h1 id="international">International</h1>
+<h1 id="international">International<a class="headerlink" href="#international" title="Permanent link">&para;</a></h1>
 <p>Recommended code pattern for internationalization.</p>
-<h2 id="timezone">Specify timezone</h2>
+<h2 id="timezone">Specify timezone<a class="headerlink" href="#timezone" title="Permanent link">&para;</a></h2>
 <p>Geospatial data often cover a wide geographic area, spanning many time zones.
 Timezone are sometime specified as metadata in the header of data files to be read,
 or is sometime fixed to <abbr title="Universal Time Coordinated">UTC</abbr> by applications managing world-wide data.
@@ -137,14 +148,14 @@ Such locale and timezone shall be given
 accepting a <code>Calendar</code> argument, when such method is available.
 For example prefer the <code>getTimestamp(int, Calendar)</code> method instead than <code>getTimestamp(int)</code>.
 The <code>Calendar</code> object shall has been created with the appropriate timezone.</p>
-<h2 id="sort">Replace underscores by spaces before sorting</h2>
+<h2 id="sort">Replace underscores by spaces before sorting<a class="headerlink" href="#sort" title="Permanent link">&para;</a></h2>
 <p>Before to sort programmatic names for human reading, consider replacing all occurrences of the underscore character
 (<code>'_'</code>) by the space character (<code>' '</code>). The ASCII value of the underscore character is greater than <code>'Z'</code> but lower
 than <code>'a'</code>, which sometime produce unexpected sort results.
 For example <code>"Foo_bar"</code> is sorted <em>between</em> <code>"FooBar"</code> and <code>"Foobar"</code>.
 The space character produces more consistent sort results because its ASCII value is less than any printable character,
 so <code>"Foo bar"</code> is sorted before both <code>"FooBar"</code> and <code>"Foobar"</code>.</p>
-<h2 id="unicode-loop">Loop over character sequences using code points</h2>
+<h2 id="unicode-loop">Loop over character sequences using code points<a class="headerlink" href="#unicode-loop" title="Permanent link">&para;</a></h2>
 <p>Since Java 1.5, characters are no longer restricted to 16 bits.
 Some "characters" are actually represented using two consecutive <code>char</code> elements.
 Those "characters" are called <cite>code points</cite>.
@@ -157,7 +168,7 @@ Consequently, when iterating over charac
 </pre></div>
 
 
-<h1 id="logging">Logging</h1>
+<h1 id="logging">Logging<a class="headerlink" href="#logging" title="Permanent link">&para;</a></h1>
 <p>Apache SIS uses the <code>java.util.logging</code> framework with one minor difference:
 instead of invoking the <code>getLogger(String)</code> method provided by the <code>java.util.logging.Logger</code> class,
 we rather invoke the method provided by the <code>apache.sis.util.logging.Logging</code> class.
@@ -165,7 +176,7 @@ The result is identical by default,
 but the SIS method gives a chance to redirect the logging to an other framework like Log4J if desired.
 The difference between the SIS approach and other facades like <code>common-logging</code> is that SIS uses the
 standard Java API (except for the above-cited <code>getLogger</code> method) instead than defining a new API.</p>
-<h2 id="logger-name">Logger name</h2>
+<h2 id="logger-name">Logger name<a class="headerlink" href="#logger-name" title="Permanent link">&para;</a></h2>
 <p>The name given in argument to the <code>getLogger(String)</code> method is usually the package name of the class
 emitting the log messages, but not necessarily. In particular, we do not follow this convention if the class
 is located in an internal package (<code>org.apache.sis.internal.*</code>) since those packages are considered privates.
@@ -173,7 +184,7 @@ In such cases, the logger name should be
 <p>The reason for the above rule is that logger names are considered part of the public API,
 since developers use them for configuring their logging (verbosity, destination, <i>etc.</i>).
 Note that the "real" package name of the emitter is available by <code>LogRecord.getSourceClassName()</code>.</p>
-<h2 id="logging-level">Logging level</h2>
+<h2 id="logging-level">Logging level<a class="headerlink" href="#logging-level" title="Permanent link">&para;</a></h2>
 <p>All logging at <code>Level.INFO</code> or above shall be targeted to users or administrators, not to developers.
 In particular <code>Level.SEVERE</code> shall be reserved for critical errors that compromise the application stability —
 it shall not be used for exceptions thrown while parsing user data (file or database).</p>
@@ -185,7 +196,7 @@ it shall not be used for exceptions thro
 
   <footer class="footer">
     <div class="container">
-      <p>Copyright &copy; 2013-2014 The Apache Software Foundation, Licensed under the
+      <p>Copyright &copy; 2013-2015 The Apache Software Foundation, Licensed under the
         <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
           Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
     </div>

Modified: websites/staging/sis/trunk/content/command-line.html
==============================================================================
--- websites/staging/sis/trunk/content/command-line.html (original)
+++ websites/staging/sis/trunk/content/command-line.html Fri Sep 11 19:49:16 2015
@@ -203,7 +203,7 @@ a small Java program using the <a href="
 
   <footer class="footer">
     <div class="container">
-      <p>Copyright &copy; 2013-2014 The Apache Software Foundation, Licensed under the
+      <p>Copyright &copy; 2013-2015 The Apache Software Foundation, Licensed under the
         <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
           Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
     </div>

Modified: websites/staging/sis/trunk/content/contributor.html
==============================================================================
--- websites/staging/sis/trunk/content/contributor.html (original)
+++ websites/staging/sis/trunk/content/contributor.html Fri Sep 11 19:49:16 2015
@@ -82,7 +82,18 @@
           <section id="content" class="row">
             <article class="span12">
               <p class="page-title">New contributor</p>
-              <p>Improving and extending SIS requires extensive knowledge of geographic information science,
+              <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+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>Improving and extending SIS requires extensive knowledge of geographic information science,
 object oriented programming, the Java language, and of the library itself. Contributors should
 expect that they will need to learn a great deal before being able to become productive.
 However, the effort required to become productive should improve the contributor's understanding
@@ -107,14 +118,14 @@ effective computer programming.</p>
 </li>
 </ul>
 </div>
-<h1 id="knowledge">Background Knowledge</h1>
+<h1 id="knowledge">Background Knowledge<a class="headerlink" href="#knowledge" title="Permanent link">&para;</a></h1>
 <p>All contributors arrive to the project with different knowledge bases, some with scientific
 backgrounds, some with a background in computer science, and others with geographic backgrounds
 or even no training in geographic information science at all. By sharing the richness of our
 individual backgrounds we have acquired a list of subjects which we consider critical to fully
 understanding the SIS project. New contributors are highly encouraged to explore these
 areas if they have no or little knowledge of them.</p>
-<h2 id="science">Geographic Information Systems and Science</h2>
+<h2 id="science">Geographic Information Systems and Science<a class="headerlink" href="#science" title="Permanent link">&para;</a></h2>
 <p>While a background in the field is not required, it nonetheless proves exceedingly useful along the way.
 GIS has developed its own language and has particular concerns which return frequently.
 Issues of spatial representation, data size, spatial scale, information workflows and other topics
@@ -123,17 +134,17 @@ arise frequently and are worth understan
 by Paul A. Longley, Michael F. Goodchild, David J. Maguire and David W. Rhind published in its
 second edition by John Wiley and Sons Ltd. in 2004.
 Apache SIS also provides an introduction in the <a href="book/en/developer-guide.html">Developer guide</a>.</p>
-<h2 id="ogc">The <abbr title="International Organization for Standardization">ISO</abbr>/<abbr title="Open Geospatial Consortium">OGC</abbr> Geospatial Model</h2>
+<h2 id="ogc">The <abbr title="International Organization for Standardization">ISO</abbr>/<abbr title="Open Geospatial Consortium">OGC</abbr> Geospatial Model<a class="headerlink" href="#ogc" title="Permanent link">&para;</a></h2>
 <p>SIS builds on the standards developed through a collaboration between the International
 Organization for Standardization (<abbr title="International Organization for Standardization">ISO</abbr>) and the Open Geospatial Consortium (<abbr title="Open Geospatial Consortium">OGC</abbr>).
 Contributors to SIS should have at least a basic understanding of the model developed in the
 <abbr title="International Organization for Standardization">ISO</abbr> 19000 series of specifications, starting with the Abstract model and working through the
 <em>Feature</em> model. While the <abbr title="International Organization for Standardization">ISO</abbr> specifications are sold, the <abbr title="Open Geospatial Consortium">OGC</abbr> releases its own, essentially
 identical versions of standards which have evolved from the collaboration. The <abbr title="Open Geospatial Consortium">OGC</abbr> specifications
-are available for the <a href="http://www.opengeospatial.org/standards"><abbr title="Open Geospatial Consortium"><abbr title="Open Geospatial Consortium">OGC</abbr></abbr> standards and specification</a> page.</p>
+are available for the <a href="http://www.opengeospatial.org/standards"><abbr title="Open Geospatial Consortium">OGC</abbr> standards and specification</a> page.</p>
 <p>As time progresses, we hope to develop documentation material to introduce the <abbr title="International Organization for Standardization">ISO</abbr> 19000 specification series.
 Most of the documentation provided by SIS can be found in the <a href="book/en/developer-guide.html">Developer guide</a>.</p>
-<h2 id="java">Object-Oriented Programming in Java</h2>
+<h2 id="java">Object-Oriented Programming in Java<a class="headerlink" href="#java" title="Permanent link">&para;</a></h2>
 <p>SIS is a library designed to be used by other programmers. To play this role effectively,
 SIS must consider the various ways that users can reuse Java code: not only through object
 instantiation and method calls but also through inheritance. SIS pays special attention to
@@ -145,7 +156,7 @@ elements in the Java language and discus
 Most importantly, the book reveals the full scope a programmer must consider when developing a code library.</p>
 <p>The <a href="code-patterns.html">Recommended code patterns</a> page also discusses some elements
 of special importance to Apache SIS.</p>
-<h2 id="math">Mathematical Background</h2>
+<h2 id="math">Mathematical Background<a class="headerlink" href="#math" title="Permanent link">&para;</a></h2>
 <p>SIS frequently deals with complex calculations using relatively simple mathematics of
 trigonometry and matrix algebra. The coordinate operations of the Referencing modules involve
 trigonometric transformations on a flattened ellipsoid of rotation, the image transformations in
@@ -159,16 +170,16 @@ shear, though this latter component is u
 affine transformations are usually applied as a matrix operation applied to a coordinate vector.
 There are numerous introductions to affine transformations available on the World Wide Web since
 the concept is central to all graphics programming.</p>
-<h2 id="geoapi">The GeoAPI Interfaces</h2>
+<h2 id="geoapi">The GeoAPI Interfaces<a class="headerlink" href="#geoapi" title="Permanent link">&para;</a></h2>
 <p>SIS is build partially as an implementation of the GeoAPI interfaces. GeoAPI defines a set
 of objects offering particular methods thereby providing an interpretation of the <abbr title="International Organization for Standardization">ISO</abbr>/<abbr title="Open Geospatial Consortium">OGC</abbr>
 standards in the Java language. GeoAPI therefore defines the core of the model implemented
 by Apache SIS.</p>
 <p>GeoAPI can most easily be learned by exploring the <a href="http://www.geoapi.org/3.0/javadoc/index.html">GeoAPI Javadoc</a>.</p>
-<h2 id="modules">The SIS library modules</h2>
+<h2 id="modules">The SIS library modules<a class="headerlink" href="#modules" title="Permanent link">&para;</a></h2>
 <p>Contributors should gain a basic understanding of the core library including the separation into modules,
 the functionality available in the base module, and the functioning of the modules of interest.</p>
-<h1 id="source">Fetching and editing source code</h1>
+<h1 id="source">Fetching and editing source code<a class="headerlink" href="#source" title="Permanent link">&para;</a></h1>
 <p>Different SIS <a href="branches.html">branches</a> are available depending on the target platforms.
 Unless working on a SIS port (e.g. the Android platform), contributors are encouraged
 to work on the SIS branch targeting the most recent JDK platform (currently JDK8):</p>
@@ -180,7 +191,7 @@ mvn install
 
 <p>The <a href="source.html">Source code</a> page provides tips for opening the files in an IDE,
 and guidelines about the way SIS source code is organized.</p>
-<h1 id="commit">Committing changes</h1>
+<h1 id="commit">Committing changes<a class="headerlink" href="#commit" title="Permanent link">&para;</a></h1>
 <p>Copies or displacements of files shall be done with the <code>svn copy</code> or <code>svn move</code> command, respectively.
 Be aware that not all IDE or graphical tools perform this action appropriately.
 <strong>Always verify on the command-line</strong>, at least the first times that a new tools is used, by executing <code>svn status</code>.
@@ -192,7 +203,7 @@ A  +    my-directory/the-new-filename
 
 <p>Using the proper SVN command is necessary for preserving the history, preserving the <a href="#svn-config">SVN properties</a>,
 and consuming less space on the Apache server hosting the source code repository.</p>
-<h2 id="svn-config">Configuring Subversion properties</h2>
+<h2 id="svn-config">Configuring Subversion properties<a class="headerlink" href="#svn-config" title="Permanent link">&para;</a></h2>
 <p>Subversion can associate properties to each tracked files. Those properties tell to Subversion
 how to handle platform-specific aspects like end-of-line characters, and how to serve the files
 to web browsers (MIME type, encoding, <i>etc.</i>).
@@ -253,7 +264,7 @@ Developers can specify default propertie
 
   <footer class="footer">
     <div class="container">
-      <p>Copyright &copy; 2013-2014 The Apache Software Foundation, Licensed under the
+      <p>Copyright &copy; 2013-2015 The Apache Software Foundation, Licensed under the
         <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
           Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
     </div>

Modified: websites/staging/sis/trunk/content/downloads.html
==============================================================================
--- websites/staging/sis/trunk/content/downloads.html (original)
+++ websites/staging/sis/trunk/content/downloads.html Fri Sep 11 19:49:16 2015
@@ -192,7 +192,7 @@ Below are examples of declarations in a
 
   <footer class="footer">
     <div class="container">
-      <p>Copyright &copy; 2013-2014 The Apache Software Foundation, Licensed under the
+      <p>Copyright &copy; 2013-2015 The Apache Software Foundation, Licensed under the
         <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
           Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
     </div>

Modified: websites/staging/sis/trunk/content/faq.html
==============================================================================
--- websites/staging/sis/trunk/content/faq.html (original)
+++ websites/staging/sis/trunk/content/faq.html Fri Sep 11 19:49:16 2015
@@ -82,7 +82,18 @@
           <section id="content" class="row">
             <article class="span12">
               <p class="page-title">Frequently asked questions</p>
-              <p>This page lists some Frequently Asked Questions (FAQ) when using Apache SIS.</p>
+              <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+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>This page lists some Frequently Asked Questions (FAQ) when using Apache SIS.</p>
 <div class="toc">
 <ul>
 <li><a href="#metadata">Metadata</a><ul>
@@ -99,11 +110,11 @@
 </li>
 </ul>
 </div>
-<h1 id="metadata">Metadata</h1>
+<h1 id="metadata">Metadata<a class="headerlink" href="#metadata" title="Permanent link">&para;</a></h1>
 <p>Frequently asked questions about the <code>sis-metadata</code> module.</p>
-<h2 id="metadata-implementation">Custom implementations</h2>
+<h2 id="metadata-implementation">Custom implementations<a class="headerlink" href="#metadata-implementation" title="Permanent link">&para;</a></h2>
 <p>Frequently asked questions custom implementations of <code>org.opengis.metadata</code> interfaces.</p>
-<h3 id="metadata-proxy">My metadata are stored in a database-like framework. Implementing every GeoAPI interfaces for them is impractical.</h3>
+<h3 id="metadata-proxy">My metadata are stored in a database-like framework. Implementing every GeoAPI interfaces for them is impractical.<a class="headerlink" href="#metadata-proxy" title="Permanent link">&para;</a></h3>
 <p>Developers do not need to implement directly the metadata interfaces.
 If the underlying storage framework can access metadata from their class and attribute names (either Java names
 or <abbr title="International Organization for Standardization">ISO</abbr>/<abbr title="Open Geospatial Consortium">OGC</abbr> names), then it is possible to implement a single engine accessing any kind of metadata and let the
@@ -120,7 +131,7 @@ See the <code>Proxy</code> Javadoc for d
 
 <p>This is indeed the approach taken by the <code>org.apache.sis.metadata.sql</code> package for providing an implementation
 of all GeoAPI metadata interfaces reading their values directly from a SQL database.</p>
-<h3 id="metadata-unknownClass">I can't marshall my custom implementation.</h3>
+<h3 id="metadata-unknownClass">I can't marshall my custom implementation.<a class="headerlink" href="#metadata-unknownClass" title="Permanent link">&para;</a></h3>
 <p>The classes given to the JAXB marshaller shall contain JAXB annotations,
 otherwise the following exception is thrown:</p>
 <div class="codehilite"><pre>javax.xml.bind.JAXBException: class MyCustomClass nor any of its super class is known to this context.
@@ -132,9 +143,9 @@ provided in the <code>org.apache.metadat
 All those SIS implementation classes provide shallow copy constructor for making that easy.
 Note that you need to wrap only the root class, not the attributes.
 The attribute values will be wrapped automatically as needed by JAXB adapters.</p>
-<h1 id="referencing">Referencing</h1>
+<h1 id="referencing">Referencing<a class="headerlink" href="#referencing" title="Permanent link">&para;</a></h1>
 <p>Frequently asked questions about the <code>sis-referencing</code> module.</p>
-<h3 id="axisOrder">Axis order</h3>
+<h3 id="axisOrder">Axis order<a class="headerlink" href="#axisOrder" title="Permanent link">&para;</a></h3>
 <p>(... to be provided later ...)</p>
             </article>
           </section>
@@ -144,7 +155,7 @@ The attribute values will be wrapped aut
 
   <footer class="footer">
     <div class="container">
-      <p>Copyright &copy; 2013-2014 The Apache Software Foundation, Licensed under the
+      <p>Copyright &copy; 2013-2015 The Apache Software Foundation, Licensed under the
         <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
           Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
     </div>

Modified: websites/staging/sis/trunk/content/index.html
==============================================================================
--- websites/staging/sis/trunk/content/index.html (original)
+++ websites/staging/sis/trunk/content/index.html Fri Sep 11 19:49:16 2015
@@ -147,7 +147,7 @@ The version under development is 0.6-SNA
 
   <footer class="footer">
     <div class="container">
-      <p>Copyright &copy; 2013-2014 The Apache Software Foundation, Licensed under the
+      <p>Copyright &copy; 2013-2015 The Apache Software Foundation, Licensed under the
         <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
           Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
     </div>

Modified: websites/staging/sis/trunk/content/license.html
==============================================================================
--- websites/staging/sis/trunk/content/license.html (original)
+++ websites/staging/sis/trunk/content/license.html Fri Sep 11 19:49:16 2015
@@ -82,9 +82,20 @@
           <section id="content" class="row">
             <article class="span12">
               <p class="page-title">Apache License</p>
-              <p>Version 2.0, January 2004<br/>
+              <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+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>Version 2.0, January 2004<br/>
 <a href="http://www.apache.org/licenses/">http://www.apache.org/licenses/</a></p>
-<h2 id="terms-and-conditions-for-use-reproduction-and-distribution">TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION</h2>
+<h2 id="terms-and-conditions-for-use-reproduction-and-distribution">TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION<a class="headerlink" href="#terms-and-conditions-for-use-reproduction-and-distribution" title="Permanent link">&para;</a></h2>
 <p><strong><a name="definitions">1. Definitions</a></strong>.</p>
 <p>"License" shall mean the terms and conditions for use, reproduction, and
 distribution as defined by Sections 1 through 9 of this document.</p>
@@ -236,7 +247,7 @@ harmless for any liability incurred by,
 Contributor by reason of your accepting any such warranty or additional
 liability.</p>
 <p>END OF TERMS AND CONDITIONS</p>
-<h2 id="apply">APPENDIX: How to apply the Apache License to your work</h2>
+<h2 id="apply">APPENDIX: How to apply the Apache License to your work<a class="headerlink" href="#apply" title="Permanent link">&para;</a></h2>
 <p>To apply the Apache License to your work, attach the following boilerplate
 notice, with the fields enclosed by brackets "[]" replaced with your own
 identifying information. (Don't include the brackets!) The text should be
@@ -266,7 +277,7 @@ limitations under the License.
 
   <footer class="footer">
     <div class="container">
-      <p>Copyright &copy; 2013-2014 The Apache Software Foundation, Licensed under the
+      <p>Copyright &copy; 2013-2015 The Apache Software Foundation, Licensed under the
         <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
           Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
     </div>

Modified: websites/staging/sis/trunk/content/mail-lists.html
==============================================================================
--- websites/staging/sis/trunk/content/mail-lists.html (original)
+++ websites/staging/sis/trunk/content/mail-lists.html Fri Sep 11 19:49:16 2015
@@ -82,8 +82,19 @@
           <section id="content" class="row">
             <article class="span12">
               <p class="page-title">Mailing lists</p>
-              <p>We welcome you to join mailing lists and let us know about your thoughts or ideas about Apache SIS.</p>
-<h2 id="user">Apache SIS User Mailing List</h2>
+              <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+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>We welcome you to join mailing lists and let us know about your thoughts or ideas about Apache SIS.</p>
+<h2 id="user">Apache SIS User Mailing List<a class="headerlink" href="#user" title="Permanent link">&para;</a></h2>
 <p>This is where user can ask questions about how to use SIS.</p>
 <ul>
 <li>Subscribe: <a href="mailto:user-subscribe@sis.apache.org">user-subscribe@sis.apache.org</a></li>
@@ -95,7 +106,7 @@
 </ul>
 </li>
 </ul>
-<h2 id="developer">Apache SIS Developer Mailing List</h2>
+<h2 id="developer">Apache SIS Developer Mailing List<a class="headerlink" href="#developer" title="Permanent link">&para;</a></h2>
 <p>This is where the community hangs out and SIS development happens.</p>
 <ul>
 <li>Subscribe: <a href="mailto:dev-subscribe@sis.apache.org">dev-subscribe@sis.apache.org</a></li>
@@ -107,7 +118,7 @@
 </ul>
 </li>
 </ul>
-<h2 id="commit">Apache SIS Commit Mailing List</h2>
+<h2 id="commit">Apache SIS Commit Mailing List<a class="headerlink" href="#commit" title="Permanent link">&para;</a></h2>
 <p>This is where the community receives automated notifications of
 any changes to the sis code and documentation.</p>
 <ul>
@@ -127,7 +138,7 @@ any changes to the sis code and document
 
   <footer class="footer">
     <div class="container">
-      <p>Copyright &copy; 2013-2014 The Apache Software Foundation, Licensed under the
+      <p>Copyright &copy; 2013-2015 The Apache Software Foundation, Licensed under the
         <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
           Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
     </div>

Modified: websites/staging/sis/trunk/content/release-management-setup.html
==============================================================================
--- websites/staging/sis/trunk/content/release-management-setup.html (original)
+++ websites/staging/sis/trunk/content/release-management-setup.html Fri Sep 11 19:49:16 2015
@@ -82,7 +82,18 @@
           <section id="content" class="row">
             <article class="span12">
               <p class="page-title">Release management setup</p>
-              <p>The following instructions need to be done only once by new release managers,
+              <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+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>The following instructions need to be done only once by new release managers,
 or when configuring a new machine for performing the releases.
 If those steps have already been done, jump directly to the <a href="release-management.html">Release Management</a> page.</p>
 <div class="toc">
@@ -96,7 +107,7 @@ If those steps have already been done, j
 <li><a href="#maven">Maven Configuration &amp; Nexus Setup</a></li>
 </ul>
 </div>
-<h1 id="directory-layout">Directory layout</h1>
+<h1 id="directory-layout">Directory layout<a class="headerlink" href="#directory-layout" title="Permanent link">&para;</a></h1>
 <p>The steps described in the <em>release management</em> page assume the following directory layout.
 Some directories are SVN checkout, other are ordinary directories. Any other layout can be used.
 However in the later case, all relative paths in the <em>release management</em> page will need to be adjusted accordingly.</p>
@@ -120,14 +131,14 @@ mkdir tags
 </pre></div>
 
 
-<h1 id="shell">Shell configuration</h1>
+<h1 id="shell">Shell configuration<a class="headerlink" href="#shell" title="Permanent link">&para;</a></h1>
 <p>It is better for Unix shells to contain the following line in their initialization file
 (typically <code>~/.bashrc</code> or <code>~/.profile</code>, where <code>~</code> stands for the user's home directory):</p>
 <div class="codehilite"><pre><span class="nb">export </span><span class="nv">GPG_TTY</span><span class="o">=</span><span class="k">$(</span>tty<span class="k">)</span>
 </pre></div>
 
 
-<h1 id="generate-key">Generate GPG key</h1>
+<h1 id="generate-key">Generate GPG key<a class="headerlink" href="#generate-key" title="Permanent link">&para;</a></h1>
 <p>The releases have to be signed by public key cryptography signatures.
 Detailed instructions about why releases have to be signed are provided on the <a href="http://www.apache.org/dev/release-signing.html">Release Signing</a> page.
 The standard used is OpenPGP (<em>Open Pretty Good Privacy</em>), and a popular software implementation of that standard is GPG (<em>GNU Privacy Guard</em>).
@@ -188,7 +199,7 @@ preferably on a removable device.</p>
 </pre></div>
 
 
-<h2 id="trust">Web of trust</h2>
+<h2 id="trust">Web of trust<a class="headerlink" href="#trust" title="Permanent link">&para;</a></h2>
 <p>Have the key signed by at least three Apache commiters. This can be done by executing the following commands on
 the machine of the other Apache commiter, where <code>&lt;key_to_use&gt;</code> is the identifier of the other commiter's key.
 Those operation should preferably be done in some event where the commiters can meet face-to-face.
@@ -203,7 +214,7 @@ gpg --send-key &lt;key_id&gt;
 <p>The above-cited <em>Release Signing</em> page provides more instructions.
 Then, the signed public key shall be appended to the <code>KEYS</code> file on the <a href="https://svn.apache.org/repos/asf/sis/trunk/">SIS source code repository</a>,
 then copied to the <a href="http://dist.apache.org/repos/dist/release/sis/">SIS distribution directory</a>.</p>
-<h1 id="maven">Maven Configuration &amp; Nexus Setup</h1>
+<h1 id="maven">Maven Configuration &amp; Nexus Setup<a class="headerlink" href="#maven" title="Permanent link">&para;</a></h1>
 <p>Detailed instructions are at <a href="http://www.apache.org/dev/publishing-maven-artifacts.html">Publishing Maven Artifacts</a>.
 In summary, the developer needs to specify his Apache username and password (<strong>not</strong> the PGP passphrase)
 in his local <code>~/.m2</code> directory, and the GPG key identifier.
@@ -272,7 +283,7 @@ together with the PGP key name:</p>
 
   <footer class="footer">
     <div class="container">
-      <p>Copyright &copy; 2013-2014 The Apache Software Foundation, Licensed under the
+      <p>Copyright &copy; 2013-2015 The Apache Software Foundation, Licensed under the
         <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
           Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
     </div>

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 Fri Sep 11 19:49:16 2015
@@ -644,7 +644,7 @@ all directories starting with the old ve
 
   <footer class="footer">
     <div class="container">
-      <p>Copyright &copy; 2013-2014 The Apache Software Foundation, Licensed under the
+      <p>Copyright &copy; 2013-2015 The Apache Software Foundation, Licensed under the
         <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
           Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
     </div>

Modified: websites/staging/sis/trunk/content/site-management.html
==============================================================================
--- websites/staging/sis/trunk/content/site-management.html (original)
+++ websites/staging/sis/trunk/content/site-management.html Fri Sep 11 19:49:16 2015
@@ -82,7 +82,18 @@
           <section id="content" class="row">
             <article class="span12">
               <p class="page-title">Site management</p>
-              <p>This page explains how the Apache SIS web site is created and how to update the site.
+              <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+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>This page explains how the Apache SIS web site is created and how to update the site.
 The intended audiences are SIS release managers and SIS web site maintainers.</p>
 <p>General documentation about Apache Content Management System (CMS) can be found in the <a href="http://www.apache.org/dev/cmsref.html">CMS reference</a> page.
 The remaining of this page is specific to the SIS project.</p>
@@ -96,7 +107,7 @@ The remaining of this page is specific t
 </li>
 </ul>
 </div>
-<h1 id="directory-layout">Directory layout</h1>
+<h1 id="directory-layout">Directory layout<a class="headerlink" href="#directory-layout" title="Permanent link">&para;</a></h1>
 <p>The source files for the Apache SIS web site can be fetched from Subversion using the following command:</p>
 <div class="codehilite"><pre>svn checkout https://svn.apache.org/repos/asf/sis/site/trunk site
 </pre></div>
@@ -137,7 +148,7 @@ Once a staging site has been approved, i
 <li>Login to the <a href="https://cms.apache.org/sis/">ASF Content Management System</a>.</li>
 <li>Click on <em>Publish sis site</em>.</li>
 </ul>
-<h1 id="content">Content</h1>
+<h1 id="content">Content<a class="headerlink" href="#content" title="Permanent link">&para;</a></h1>
 <p>All <code>.mdtext</code> files should start as below (replace the <code>&lt;...&gt;</code> block by the corresponding content):</p>
 <div class="codehilite"><pre><span class="n">Title</span><span class="p">:</span>  <span class="o">&lt;</span><span class="n">put</span> <span class="n">the</span> <span class="n">page</span> <span class="n">title</span> <span class="n">here</span><span class="o">&gt;</span>
 <span class="n">Notice</span><span class="p">:</span> <span class="o">&lt;</span><span class="n">copy</span> <span class="n">the</span> <span class="n">notice</span> <span class="n">from</span> <span class="n">an</span> <span class="n">existing</span> <span class="n">page</span><span class="o">&gt;</span>
@@ -160,11 +171,11 @@ Example:</p>
 </pre></div>
 
 
-<h1 id="style-sheets">Style sheets</h1>
+<h1 id="style-sheets">Style sheets<a class="headerlink" href="#style-sheets" title="Permanent link">&para;</a></h1>
 <p>The following table lists the style sheets used by Apache SIS.
 The Maven and Javadoc style sheets are mentioned for completeness, but are not located on the web site repository.
 They are rather located together with the SIS library source code.</p>
-<table>
+<table class="table">
 <thead>
 <tr>
 <th>Page set</th>
@@ -206,7 +217,7 @@ They are rather located together with th
 </tr>
 </tbody>
 </table>
-<h2 id="bootstrap">Updating bootstrap</h2>
+<h2 id="bootstrap">Updating bootstrap<a class="headerlink" href="#bootstrap" title="Permanent link">&para;</a></h2>
 <p>If the <code>bootstrap.min.css</code> file needs to be updated, then visit the <a href="http://twitter.github.io/bootstrap/customize.html">Bootstrap</a> web site
 and select the following options:</p>
 <ul>
@@ -257,7 +268,7 @@ Then:</p>
 
   <footer class="footer">
     <div class="container">
-      <p>Copyright &copy; 2013-2014 The Apache Software Foundation, Licensed under the
+      <p>Copyright &copy; 2013-2015 The Apache Software Foundation, Licensed under the
         <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
           Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
     </div>

Modified: websites/staging/sis/trunk/content/source.html
==============================================================================
--- websites/staging/sis/trunk/content/source.html (original)
+++ websites/staging/sis/trunk/content/source.html Fri Sep 11 19:49:16 2015
@@ -82,7 +82,18 @@
           <section id="content" class="row">
             <article class="span12">
               <p class="page-title">Source code</p>
-              <p>Apache SIS source code is maintained using Apache Subversion version control, and mirrored on Git.
+              <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+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 SIS source code is maintained using Apache Subversion version control, and mirrored on Git.
 For browsing the source code on-line, see <a href="http://svn.apache.org/viewvc/sis/">ViewVC</a>.
 For fetching the source code, choose one of the following commands:</p>
 <p><a href="http://subversion.apache.org">Subversion</a>:</p>
@@ -125,7 +136,7 @@ For fetching the source code, choose one
 </li>
 </ul>
 </div>
-<h1 id="ide">Opening Apache SIS in an IDE</h1>
+<h1 id="ide">Opening Apache SIS in an IDE<a class="headerlink" href="#ide" title="Permanent link">&para;</a></h1>
 <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,
@@ -139,7 +150,7 @@ mvn install
 </pre></div>
 
 
-<h2 id="netbeans">NetBeans</h2>
+<h2 id="netbeans">NetBeans<a class="headerlink" href="#netbeans" title="Permanent link">&para;</a></h2>
 <p>NetBeans can open Maven projects natively. This is the recommended approach for casual working in a small amount of SIS modules.
 For extensive work on Apache SIS or for work impacting many modules, it may be more convenient and faster to open Apache SIS as a NetBeans project.
 Such pre-configured NetBeans project is available in the <code>ide-project/NetBeans</code> directory.
@@ -156,7 +167,7 @@ one can use:</p>
 </pre></div>
 
 
-<h2 id="eclipse">Eclipse</h2>
+<h2 id="eclipse">Eclipse<a class="headerlink" href="#eclipse" title="Permanent link">&para;</a></h2>
 <p>Execute the <code>svn checkout</code> to <code>mvn install</code> commands documented in the beginning of this section,
 then execute the following steps:</p>
 <ul>
@@ -167,7 +178,7 @@ then execute the following steps:</p>
 <li>Go to <em>File</em> → <em>Import</em> → <em>General</em> → <em>Existing Projects in Workspace</em>.</li>
 <li>Choose the <code>sis</code> directory and import.</li>
 </ul>
-<h1 id="license">License header</h1>
+<h1 id="license">License header<a class="headerlink" href="#license" title="Permanent link">&para;</a></h1>
 <p>All Java source files (<code>*.java</code>) shall begin with the current ASF license header as described in <a href="http://www.apache.org/legal/src-headers.html">ASF Source Header</a>.
 Properties source files (<code>*.properties</code>) used as inputs to some processor (e.g. the resource compiler)
 shall have the same license header, but with lines prefixed by <code>#</code> instead of <code>*</code>.
@@ -177,7 +188,7 @@ as below:</p>
 </pre></div>
 
 
-<h1 id="naming">Naming convention</h1>
+<h1 id="naming">Naming convention<a class="headerlink" href="#naming" title="Permanent link">&para;</a></h1>
 <p>Implementations of GeoAPI interfaces usually (but not always) begin with <code>Abstract</code>, <code>Default</code>, <code>Simple</code> or <code>General</code> prefixes.</p>
 <ul>
 <li>The <code>Abstract</code> prefix is used when a class is abstract according <abbr title="International Organization for Standardization">ISO</abbr> specifications — it may or may not be be abstract in the Java sense.</li>
@@ -186,11 +197,11 @@ as below:</p>
 <li>Implementations specialized for a fixed number of dimensions are suffixed with <code>1D</code>, <code>2D</code>, <code>3D</code> or <code>4D</code> rather than being prefixed.</li>
 </ul>
 <p>Classes that do not implement an interface are usually not prefixed, even if abstract.</p>
-<h1 id="formatting">Code formatting</h1>
+<h1 id="formatting">Code formatting<a class="headerlink" href="#formatting" title="Permanent link">&para;</a></h1>
 <p>Apache SIS uses the standard Java conventions, except for the 80 characters line length restriction.
 The conventions listed below are guidelines. Some exceptions to those conventions can occur but should
 be rare (see <a href="#tabular-formatting">exceptions to coding conventions</a>).</p>
-<h2 id="spaces">Spaces and line length</h2>
+<h2 id="spaces">Spaces and line length<a class="headerlink" href="#spaces" title="Permanent link">&para;</a></h2>
 <ul>
 <li><strong>Indentation:</strong> Use a consistent space indents and never use tabs.<ul>
 <li>Use 4 space indents for Java files.</li>
@@ -208,12 +219,12 @@ be rare (see <a href="#tabular-formattin
 <li><strong>Line wrapping:</strong> Use 120-column line width for Java code and Javadoc.
     Some exceptions to this rule may exist for preserving tabular structures, but should be rare.</li>
 </ul>
-<h2 id="brackets">Brackets</h2>
+<h2 id="brackets">Brackets<a class="headerlink" href="#brackets" title="Permanent link">&para;</a></h2>
 <ul>
 <li><strong>Curly brackets:</strong> The <code>{</code> and <code>}</code> brackets are mandatory for <code>if</code>, <code>else</code>, <code>while</code> and other blocks,
     except if the instruction after the keyword is on the same line (e.g. <code>else if</code>).</li>
 </ul>
-<h2 id="declarations">Member declarations</h2>
+<h2 id="declarations">Member declarations<a class="headerlink" href="#declarations" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Class, method and field declarations shall use the keywords in the following order.
     This is known as the "customary order" in the <a href="http://docs.oracle.com/javase/specs/jls/se8/html/jls-8.html#jls-8.1.1">Java Language Specification</a>:<ul>
@@ -225,7 +236,7 @@ be rare (see <a href="#tabular-formattin
 </li>
 <li>Member fields do not have any particular prefix (no <code>m_</code> prefix).</li>
 </ul>
-<h2 id="tabular-formatting">Exceptions to coding conventions</h2>
+<h2 id="tabular-formatting">Exceptions to coding conventions<a class="headerlink" href="#tabular-formatting" title="Permanent link">&para;</a></h2>
 <p>Many mathematical operations in a two-dimensional space (or more) have symmetry.
 Formatting the code in a way that emphase their symmetrical nature, for example
 aligning identical terms in columns, can help to understand the overall pattern
@@ -239,11 +250,11 @@ and to identify bugs. Example:</p>
 
 <p>The decision to use standard or tabular format is made on a case-by-case basis.
 Of course, tabular format shall not be abused.</p>
-<h1 id="javadoc">Documentation formatting</h1>
+<h1 id="javadoc">Documentation formatting<a class="headerlink" href="#javadoc" title="Permanent link">&para;</a></h1>
 <p>Apache SIS uses the standard Javadoc conventions, except for the 80 characters line length restriction.
 Javadoc lines should not exceed 120 characters, but exceptions to this rule may exist for preserving the
 structure of <code>&lt;table&gt;</code> elements.</p>
-<h2 id="javadoc-tags">Javadoc annotations</h2>
+<h2 id="javadoc-tags">Javadoc annotations<a class="headerlink" href="#javadoc-tags" title="Permanent link">&para;</a></h2>
 <p>SIS uses standard javadoc annotations. The meaning of some tags are refined as below:</p>
 <ul>
 <li><code>@since</code>   - the SIS version when the annotated element (class, method, <i>etc.</i>) was first introduced.</li>
@@ -253,7 +264,7 @@ structure of <code>&lt;table&gt;</code>
                  The intend is to allow other developers to know to who to ask questions if needed.</li>
 </ul>
 <p>In addition, the <code>sis-build-helper</code> modules provides the following custom javadoc taglets:</p>
-<table>
+<table class="table">
 <thead>
 <tr>
 <th>Javadoc tag</th>
@@ -275,7 +286,7 @@ structure of <code>&lt;table&gt;</code>
 </tr>
 </tbody>
 </table>
-<h2 id="html">HTML elements</h2>
+<h2 id="html">HTML elements<a class="headerlink" href="#html" title="Permanent link">&para;</a></h2>
 <p>HTML tags and entities shall be used only when there is no equivalent Javadoc tag.
 For example:</p>
 <ul>
@@ -284,7 +295,7 @@ For example:</p>
 <li>Instead of "<code>&lt;pre&gt;✎&lt;/pre&gt;</code>" for a Java listing, use "<code>{@preformat java ✎}</code>"
      (this Javadoc tag is specific to Apache SIS — see above table).</li>
 </ul>
-<h3 id="paragraph">Paragraphs</h3>
+<h3 id="paragraph">Paragraphs<a class="headerlink" href="#paragraph" title="Permanent link">&para;</a></h3>
 <p>Usages of the <code>&lt;p&gt;</code> tag should be relatively rare, since we use CSS styles (see below)
 as much as possible for controlling the margin between elements like lists and tables.
 Do <strong>not</strong> use <code>&lt;p&gt;</code> for the first paragraph in a package, class or member documentation,
@@ -292,10 +303,10 @@ or for the first paragraph after a <code
 or <code>{@preformat}</code> element.
 The <code>&lt;p&gt;</code> tag shall be used only for separating a new paragraph from a previous one.
 In such cases, <code>&lt;p&gt;</code> shall have a matching <code>&lt;/p&gt;</code> tag at the paragraph end in order to form valid HTML.</p>
-<h3 id="css">Javadoc CSS</h3>
+<h3 id="css">Javadoc CSS<a class="headerlink" href="#css" title="Permanent link">&para;</a></h3>
 <p>Avoid using HTML attributes other than <code>class</code> as much as possible.
 Instead, rely on styling. Some HTML tags having a style definition in Apache SIS are:</p>
-<table>
+<table class="table">
 <thead>
 <tr>
 <th>HTML tag</th>
@@ -345,7 +356,7 @@ Instead, rely on styling. Some HTML tags
 </tr>
 </tbody>
 </table>
-<h2 id="mathml">MathML elements</h2>
+<h2 id="mathml">MathML elements<a class="headerlink" href="#mathml" title="Permanent link">&para;</a></h2>
 <p>The source code occasionally uses MathML for formulas that are difficult to render with only Unicode characters.
 PNG images are not extensively used for formulas because they are difficult to edit after creation,
 and their content are invisible to search operations (for example when a variable is renamed).
@@ -368,7 +379,7 @@ Note that a <a href="http://www.mathjax.
 
   <footer class="footer">
     <div class="container">
-      <p>Copyright &copy; 2013-2014 The Apache Software Foundation, Licensed under the
+      <p>Copyright &copy; 2013-2015 The Apache Software Foundation, Licensed under the
         <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
           Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
     </div>

Modified: websites/staging/sis/trunk/content/team-list.html
==============================================================================
--- websites/staging/sis/trunk/content/team-list.html (original)
+++ websites/staging/sis/trunk/content/team-list.html Fri Sep 11 19:49:16 2015
@@ -82,7 +82,18 @@
           <section id="content" class="row">
             <article class="span12">
               <p class="page-title">Team</p>
-              <h2 id="pmc">Project Management Committee / Committers</h2>
+              <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+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>
+<h2 id="pmc">Project Management Committee / Committers<a class="headerlink" href="#pmc" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Adam Estrada</li>
 <li>Andrew Hart</li>
@@ -103,7 +114,7 @@
 <li><a href="http://people.apache.org/~smarru/">Suresh Marru</a></li>
 <li>Travis Pinney</li>
 </ul>
-<h2 id="contributors">Contributors</h2>
+<h2 id="contributors">Contributors<a class="headerlink" href="#contributors" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Christina Hough (translation of developer guide)</li>
 </ul>
@@ -115,7 +126,7 @@
 
   <footer class="footer">
     <div class="container">
-      <p>Copyright &copy; 2013-2014 The Apache Software Foundation, Licensed under the
+      <p>Copyright &copy; 2013-2015 The Apache Software Foundation, Licensed under the
         <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
           Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
     </div>



Mime
View raw message