sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r870116 - in /websites/staging/sis/trunk/content: ./ source.html
Date Fri, 19 Jul 2013 09:26:14 GMT
Author: buildbot
Date: Fri Jul 19 09:26:14 2013
New Revision: 870116

Log:
Staging update by buildbot for sis

Modified:
    websites/staging/sis/trunk/content/   (props changed)
    websites/staging/sis/trunk/content/source.html

Propchange: websites/staging/sis/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jul 19 09:26:14 2013
@@ -1 +1 @@
-1501368
+1504806

Modified: websites/staging/sis/trunk/content/source.html
==============================================================================
--- websites/staging/sis/trunk/content/source.html (original)
+++ websites/staging/sis/trunk/content/source.html Fri Jul 19 09:26:14 2013
@@ -97,15 +97,15 @@
 <p>Browse SIS source repository in <a href="http://svn.apache.org/viewvc/sis/">ViewVC</a>.</p>
 <p>The SVN location is <a href="https://svn.apache.org/repos/asf/sis/">Apache
SIS SVN</a></p>
 <h2 id="checkout-source">Checkout Source</h2>
-<p>To check out the source code: svn co https://svn.apache.org/repos/asf/sis</p>
+<p>To check out the source code: svn checkout https://svn.apache.org/repos/asf/sis/trunk
sis</p>
 <h2 id="developers-guide">Developers Guide</h2>
 <p>Some coding practices:</p>
 <ul>
 <li>License Header: Always add the current ASF license header as described in <a
href="http://www.apache.org/legal/src-headers.html">ASF Source Header</a>.</li>
 <li>Trailing Whitespaces: Remove all trailing whitespaces. Eclipse users can use Source-&gt;Cleanup
option to accomplish this.</li>
-<li>Indentation: Use 4 space indents and never use tabs!</li>
+<li>Indentation: Use 4 space indents (except for XML files) and never use tabs!
+  Use 2 space indents for XML files, because ISO/OGC XML schemas tend to have a very deep
structure.</li>
 <li>Line wrapping: Use 120-column line width for Java code and Javadoc.</li>
-<li>Author Tags: Do not use Author Tags. The code is developed and owned by the community.
</li>
 </ul>
             </article>
           </section>



Mime
View raw message