svn commit: r1182443 - /aries/site/trunk/content/development/releasingaries.mdtext

[hu...@apache.org]

Author: hughesj
Date: Wed Oct 12 15:44:33 2011
New Revision: 1182443

URL: http://svn.apache.org/viewvc?rev=1182443&view=rev
Log:
Added note about the error on mvn release:prepare when there is no scm element in the pom

Modified:
    aries/site/trunk/content/development/releasingaries.mdtext

Modified: aries/site/trunk/content/development/releasingaries.mdtext
URL: http://svn.apache.org/viewvc/aries/site/trunk/content/development/releasingaries.mdtext?rev=1182443&r1=1182442&r2=1182443&view=diff
==============================================================================
--- aries/site/trunk/content/development/releasingaries.mdtext (original)
+++ aries/site/trunk/content/development/releasingaries.mdtext Wed Oct 12 15:44:33 2011
@@ -296,6 +296,7 @@ For each bundle that needs to be release
     i.e. take the default for the first two questions, and set the new development version to be the same as the one you are releasing! This is because you don't know whether the next version released from the trunk will have a major, minor or micro version number change - you won't know until those changes are made! - so leave it for the person making those changes to make the decision and move to *module*-*new version*-SNAPSHOT.
 
   * Note 3: mvn release:clean will do *most* of the cleaning up in the event of failures.
+  * Note 4: If on mvn release:prepare you get an error from SVN similar to https://svn.apache.org/repos/asf/!svn/bc/1182408/aries/tags/parent-0.5/default-parent/java5-parent/org.apache.aries.bundle.i.am.releasing does not exist then it's because there's no scm element in the pom.xml for the module you're releasing.