Author: olamy
Date: Wed Dec 26 22:48:00 2012
New Revision: 1426078

URL: http://svn.apache.org/viewvc?rev=1426078&view=rev
Log:
Apache Archiva Main site deployment

Modified:
    archiva/site-content/developers/how-we-do-things.html

Modified: archiva/site-content/developers/how-we-do-things.html
URL: 
http://svn.apache.org/viewvc/archiva/site-content/developers/how-we-do-things.html?rev=1426078&r1=1426077&r2=1426078&view=diff
==============================================================================
--- archiva/site-content/developers/how-we-do-things.html (original)
+++ archiva/site-content/developers/how-we-do-things.html Wed Dec 26 22:48:00 
2012
@@ -210,7 +210,7 @@ pageTracker._trackPageview();</script>
                 
         <div id="bodyColumn" >
                                   
-            <!-- Licensed to the Apache Software Foundation (ASF) under one 
--><!-- or more contributor license agreements.  See the NOTICE file --><!-- 
distributed with this work for additional information --><!-- regarding 
copyright ownership.  The ASF licenses this file --><!-- to you under the 
Apache License, Version 2.0 (the --><!-- "License"); you may not use this file 
except in compliance --><!-- with the License.  You may obtain a copy of the 
License at --><!--  --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!--  
--><!-- Unless required by applicable law or agreed to in writing, --><!-- 
software distributed under the License is distributed on an --><!-- "AS IS" 
BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY --><!-- KIND, either express or 
implied.  See the License for the --><!-- specific language governing 
permissions and limitations --><!-- under the License. --><!-- NOTE: For help 
with the syntax of this file, see: --><!-- http://maven.apache.org/guides/mi
 ni/guide-apt-format.html --><div class="section"><h2>How We Do Things<a 
name="How_We_Do_Things"></a></h2><p>Below are the conventions we follow in 
Archiva.</p><div class="section"><h3>Continuous Integration<a 
name="Continuous_Integration"></a></h3><p>We use the Jenkins Apache instance 
for building Archiva (and redback dependencies) on scm changes.</p><p>See the 
tab with various builds: <a class="externalLink" 
href="https://builds.apache.org/view/A-F/view/Archiva/";>Archiva 
tab</a></p><p>You can test fresh builds with downloading from this Jenkins job 
<a class="externalLink" 
href="https://builds.apache.org/view/A-F/view/Archiva/job/archiva-all-maven-3.x-jdk-1.6/";>archiva-all-maven-3.x-jdk-1.6</a>:</p><ul><li><a
 class="externalLink" 
href="https://builds.apache.org/view/A-F/view/Archiva/job/archiva-all-maven-3.x-jdk-1.6/lastSuccessfulBuild/artifact/archiva-modules/archiva-web/archiva-webapp-js/target/archiva-webapp-js-1.4-M4-SNAPSHOT.war";>war
 webapp js</a></li><li><a class="exte
 rnalLink" 
href="https://builds.apache.org/view/A-F/view/Archiva/job/archiva-all-maven-3.x-jdk-1.6/lastSuccessfulBuild/artifact/archiva-jetty-js/target/apache-archiva-js-1.4-M4-SNAPSHOT-bin.zip";>standalone
 with embeded jetty</a> (unzip then cd bin;./archiva start running on 
8080)</li></ul></div><div class="section"><h3>Code Style<a 
name="Code_Style"></a></h3><p>There isn't any code style that needs to be 
followed as long as it is consistent, can be checked in checkstyle, can be 
formatted in Eclipse, IDEA and NetBeans. And the following rules must be 
followed:</p><ol style="list-style-type: decimal"><li>Use spaces, not 
tabs<ul><li>4 spaces for Java</li><li>2 spaces for XML</li></ul></li><li>120 
column wrap, not 80</li><li>Wrap on spaces, not on '.' in a method call<p>You 
can use the existing codestyle files:</p><ul><li><a 
href="./archiva-idea-codestyle.xml">idea</a></li><li><a 
href="./archiva-eclipse-codestyle.xml">eclipse</a></li></ul></li></ol></div><div
 class="section"><h3>
 Versioning<a name="Versioning"></a></h3><p>It has been established in the 
community that the following style would be followed for the versioning of 
releases:</p><div><pre>Milestones -&gt; Final -&gt; Patch releases (e.g. 
1.1-M1, 1.1-M2, 1.1, 1.1.1, 1.1.2 )</pre></div><p>As much as possible, the team 
is aiming for frequent releases. If the roadmap for the current development 
version is big, milestone releases can be applied until the final release. But 
if the roadmap is composed of just a small number of issues, we could proceed 
immediately to preparing a release candidate and push it out as the final 
release once it passes the vote.</p></div><div class="section"><h3>References<a 
name="References"></a></h3><ul><li><a class="externalLink" 
href="http://old.nabble.com/Fwd%3A-What-do-we-need-to-establish--td17098487.html";>
 Mailing list discussion regarding conventions</a></li></ul></div></div>
+            <!-- Licensed to the Apache Software Foundation (ASF) under one 
--><!-- or more contributor license agreements.  See the NOTICE file --><!-- 
distributed with this work for additional information --><!-- regarding 
copyright ownership.  The ASF licenses this file --><!-- to you under the 
Apache License, Version 2.0 (the --><!-- "License"); you may not use this file 
except in compliance --><!-- with the License.  You may obtain a copy of the 
License at --><!--  --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!--  
--><!-- Unless required by applicable law or agreed to in writing, --><!-- 
software distributed under the License is distributed on an --><!-- "AS IS" 
BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY --><!-- KIND, either express or 
implied.  See the License for the --><!-- specific language governing 
permissions and limitations --><!-- under the License. --><!-- NOTE: For help 
with the syntax of this file, see: --><!-- http://maven.apache.org/guides/mi
 ni/guide-apt-format.html --><div class="section"><h2>How We Do Things<a 
name="How_We_Do_Things"></a></h2><p>Below are the conventions we follow in 
Archiva.</p><div class="section"><h3>Continuous Integration<a 
name="Continuous_Integration"></a></h3><p>We use the Jenkins Apache instance 
for building Archiva (and redback dependencies) on scm changes.</p><p>See the 
tab with various builds: <a class="externalLink" 
href="https://builds.apache.org/view/A-F/view/Archiva/";>Archiva 
tab</a></p><p>You can test fresh builds with downloading from this Jenkins job 
<a class="externalLink" 
href="https://builds.apache.org/view/A-F/view/Archiva/job/archiva-all-maven-3.x-jdk-1.6/";>archiva-all-maven-3.x-jdk-1.6</a>:</p><ul><li><a
 class="externalLink" 
href="https://builds.apache.org/view/A-F/view/Archiva/job/archiva-all-maven-3.x-jdk-1.6/lastSuccessfulBuild/artifact/archiva-modules/archiva-web/archiva-webapp-js/target/archiva-webapp-js-1.4-M4-SNAPSHOT.war";>war
 webapp js</a></li><li><a class="exte
 rnalLink" 
href="https://builds.apache.org/view/A-F/view/Archiva/job/archiva-all-maven-3.x-jdk-1.6/lastSuccessfulBuild/artifact/archiva-jetty/target/apache-archiva-js-1.4-M4-SNAPSHOT-bin.zip";>standalone
 with embeded jetty</a> (unzip then cd bin;./archiva start running on 
8080)</li></ul></div><div class="section"><h3>Code Style<a 
name="Code_Style"></a></h3><p>There isn't any code style that needs to be 
followed as long as it is consistent, can be checked in checkstyle, can be 
formatted in Eclipse, IDEA and NetBeans. And the following rules must be 
followed:</p><ol style="list-style-type: decimal"><li>Use spaces, not 
tabs<ul><li>4 spaces for Java</li><li>2 spaces for XML</li></ul></li><li>120 
column wrap, not 80</li><li>Wrap on spaces, not on '.' in a method call<p>You 
can use the existing codestyle files:</p><ul><li><a 
href="./archiva-idea-codestyle.xml">idea</a></li><li><a 
href="./archiva-eclipse-codestyle.xml">eclipse</a></li></ul></li></ol></div><div
 class="section"><h3>Ver
 sioning<a name="Versioning"></a></h3><p>It has been established in the 
community that the following style would be followed for the versioning of 
releases:</p><div><pre>Milestones -&gt; Final -&gt; Patch releases (e.g. 
1.1-M1, 1.1-M2, 1.1, 1.1.1, 1.1.2 )</pre></div><p>As much as possible, the team 
is aiming for frequent releases. If the roadmap for the current development 
version is big, milestone releases can be applied until the final release. But 
if the roadmap is composed of just a small number of issues, we could proceed 
immediately to preparing a release candidate and push it out as the final 
release once it passes the vote.</p></div><div class="section"><h3>References<a 
name="References"></a></h3><ul><li><a class="externalLink" 
href="http://old.nabble.com/Fwd%3A-What-do-we-need-to-establish--td17098487.html";>
 Mailing list discussion regarding conventions</a></li></ul></div></div>
                   </div>
           </div>
 


Reply via email to