You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@aries.apache.org by bu...@apache.org on 2011/10/12 17:44:41 UTC
svn commit: r796958 -
/websites/staging/aries/trunk/content/development/releasingaries.html
Author: buildbot
Date: Wed Oct 12 15:44:41 2011
New Revision: 796958
Log:
Staging update by buildbot
Modified:
websites/staging/aries/trunk/content/development/releasingaries.html
Modified: websites/staging/aries/trunk/content/development/releasingaries.html
==============================================================================
--- websites/staging/aries/trunk/content/development/releasingaries.html (original)
+++ websites/staging/aries/trunk/content/development/releasingaries.html Wed Oct 12 15:44:41 2011
@@ -496,6 +496,7 @@ trunk.</p>
<li>
<p>Note 3: mvn release:clean will do <em>most</em> of the cleaning up in the event of failures.</p>
</li>
+<li>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.</li>
</ul>
<p>This will put release artifacts into an Apache <a href="https://repository.apache.org/index.html#view-repositories;staging.html">staging repository </a>. You will need to log in to see it.
If nothing appears in a staging repo you should stop here and work out why.