Author: fchrist
Date: Thu May 31 11:55:07 2012
New Revision: 1344659
URL: http://svn.apache.org/viewvc?rev=1344659&view=rev
Log:
Added some tips and tricks commands when working on releases
Modified:
incubator/stanbol/site/trunk/content/stanbol/development/index.mdtext
Modified: incubator/stanbol/site/trunk/content/stanbol/development/index.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/development/index.mdtext?rev=1344659&r1=1344658&r2=1344659&view=diff
==============================================================================
--- incubator/stanbol/site/trunk/content/stanbol/development/index.mdtext
(original)
+++ incubator/stanbol/site/trunk/content/stanbol/development/index.mdtext Thu
May 31 11:55:07 2012
@@ -192,4 +192,38 @@ For further information we refer to the
[Apache Sling](http://sling.apache.org)
website and their very good
[documentation](http://sling.apache.org/site/release-management.html)
-of doing a release.
\ No newline at end of file
+of doing a release.
+
+## Tips & Tricks
+
+Here are some tips and tricks of commands that are useful, e.g. when examing
the
+code base before a release.
+
+### Determine SNAPSHOT dependencies
+
+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:
+
+ $ mvn dependency:tree | grep \\-SNAPSHOT | sed s/.*org/org/ | sort -u
+
+### Update version of parent POM
+
+The parent POM got released and now we have to update to the new version in
+all artifacts. The
+[Versions Maven
Plugin](http://www.java.net/external?url=http://mojo.codehaus.org/versions-maven-plugin/)
+can help here. Is has a separate goal to
+[update the
parent](http://mojo.codehaus.org/versions-maven-plugin/update-parent-mojo.html)
+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.
+
+ $ mvn versions:update-parent -DgenerateBackupPoms=false
-DallowSnapshots=true
+
+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
+
+ $ svn revert -R *
\ No newline at end of file
