sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r873421 - in /websites/staging/sis/trunk/content: ./ release-management.html source.html
Date Thu, 08 Aug 2013 08:55:53 GMT
Author: buildbot
Date: Thu Aug  8 08:55:53 2013
New Revision: 873421

Staging update by buildbot for sis

    websites/staging/sis/trunk/content/   (props changed)

Propchange: websites/staging/sis/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Thu Aug  8 08:55:53 2013
@@ -1 +1 @@

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 Aug  8 08:55:53 2013
@@ -328,7 +328,7 @@ The <code>RC</code> number shall corresp
 <p>Create and put the binary artifact in the distribution directory:</p>
-<div class="codehilite"><pre>mvn org.apache.sis:sis-build-helper:<span class="nv">$NEW_VERSION</span>:pack
+<div class="codehilite"><pre>mvn org.apache.sis.core:sis-build-helper:<span
class="nv">$NEW_VERSION</span>:pack --non-recursive
 mv target/bundles ../../distribution/<span class="nv">$NEW_VERSION</span>/RC<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 Aug  8 08:55:53 2013
@@ -121,9 +121,9 @@ For fetching the source code, choose one
 <li><a href="#miscellaneous">Miscellaneous</a></li>
-<li><a href="#classes-naming">Classes naming</a></li>
+<li><a href="#classes-naming">Classes naming convention</a></li>
 <h1 id="ide">Opening Apache SIS in an IDE</h1>
@@ -334,7 +334,7 @@ Instead, rely on styling. Some HTML tags
 <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>
-<h2 id="classes-naming">Classes naming</h2>
+<h1 id="classes-naming">Classes naming convention</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>
 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.
 The <code>General</code> prefix is used when an implementation is designed for
use in the general case,

View raw message