svn commit: r819744 - in /websites/staging/stanbol/trunk/content: ./ stanbol/development/index.html

[bu...@apache.org]

Author: buildbot
Date: Thu May 31 11:55:12 2012
New Revision: 819744

Log:
Staging update by buildbot for stanbol

Modified:
    websites/staging/stanbol/trunk/content/   (props changed)
    websites/staging/stanbol/trunk/content/stanbol/development/index.html

Propchange: websites/staging/stanbol/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu May 31 11:55:12 2012
@@ -1 +1 @@
-1344208
+1344659

Modified: websites/staging/stanbol/trunk/content/stanbol/development/index.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/development/index.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/development/index.html Thu May 31 11:55:12 2012
@@ -247,6 +247,37 @@ staging repository, you start with</p>
 website and their very good
 <a href="http://sling.apache.org/site/release-management.html">documentation</a>
 of doing a release.</p>
+<h2 id="tips-tricks">Tips &amp; Tricks</h2>
+<p>Here are some tips and tricks of commands that are useful, e.g. when examing the
+code base before a release.</p>
+<h3 id="determine-snapshot-dependencies">Determine SNAPSHOT dependencies</h3>
+<p>If you want to release a component, e.g. the Entity Hub, you have to know all
+used SNAPSHOT dependencies. We are especially interested in internal dependencies
+to other Apache Stanbol components. On a Unix system something like this could
+be used:</p>
+<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">mvn</span> <span class="n">dependency:tree</span> <span class="o">|</span> <span class="nb">grep</span> <span class="o">\\-</span><span class="n">SNAPSHOT</span> <span class="o">|</span> <span class="n">sed</span> <span class="sr">s/.*org/org/</span> <span class="o">|</span> <span class="nb">sort</span> <span class="o">-</span><span class="n">u</span>
+</pre></div>
+
+
+<h3 id="update-version-of-parent-pom">Update version of parent POM</h3>
+<p>The parent POM got released and now we have to update to the new version in
+all artifacts. The
+<a href="http://www.java.net/external?url=http://mojo.codehaus.org/versions-maven-plugin/">Versions Maven Plugin</a>
+can help here. Is has a separate goal to
+<a href="http://mojo.codehaus.org/versions-maven-plugin/update-parent-mojo.html">update the parent</a>
+POM. The plugin searches in the local Maven repository for the latest available version of the
+parent POM and updates all POMs to this version. When executing this goal the parent POM itself
+must not be part of the build. So maybe you have to edit the top level reactor POM first. The 
+used command looks as follows.</p>
+<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">mvn</span> <span class="n">versions:update</span><span class="o">-</span><span class="n">parent</span> <span class="o">-</span><span class="n">DgenerateBackupPoms</span><span class="o">=</span><span class="n">false</span> <span class="o">-</span><span class="n">DallowSnapshots</span><span class="o">=</span><span class="n">true</span>
+</pre></div>
+
+
+<p>If you want to update to the latest non-SNAPSHOT version, you have to set 'allowSnapshots'
+to 'false' (default). A backup of the changed POMs is not needed when files are under
+SVN control. To revert any local changes, you could use</p>
+<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">svn</span> <span class="n">revert</span> <span class="o">-</span><span class="n">R</span> <span class="o">*</span>
+</pre></div>
   </div>
   
   <div id="footer">