Author: buildbot
Date: Tue Dec 23 17:47:57 2014
New Revision: 933797
Log:
Staging update by buildbot for sis
Modified:
websites/staging/sis/trunk/content/ (props changed)
websites/staging/sis/trunk/content/code-patterns.html
websites/staging/sis/trunk/content/contributor.html
Propchange: websites/staging/sis/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Dec 23 17:47:57 2014
@@ -1 +1 @@
-1647622
+1647625
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 Tue Dec 23 17:47:57
2014
@@ -162,14 +162,14 @@ Consequently, when iterating over charac
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.
The result is identical by default,
-but the SIS method gives us 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 new API.</p>
+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>
<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.
-In such case, the logger name should be the package name of the public class
that use the internal class.</p>
+In such cases, the logger name should be the package name of the public class
that use the internal class.</p>
<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>
Modified: websites/staging/sis/trunk/content/contributor.html
==============================================================================
--- websites/staging/sis/trunk/content/contributor.html (original)
+++ websites/staging/sis/trunk/content/contributor.html Tue Dec 23 17:47:57 2014
@@ -182,7 +182,7 @@ and guidelines about the way SIS source
<h1 id="commit">Committing changes</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.
-<em>Always verify on the command-line</em>, at least the first times that a
new tools is used, by executing <code>svn status</code>.
+<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>.
Files that have been moved or copied shall have a <code>A+</code> symbol in
the left margin, like below:</p>
<div class="codehilite"><pre>D my-directory/the-old-filename
A + my-directory/the-new-filename
