A document has been updated:
http://cocoon.zones.apache.org/daisy/documentation/1199.html
Document ID: 1199
Branch: main
Language: default
Name: Releasing Cocoon (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 10/12/07 6:10:10 AM
Updated by: Reinhard Pötz
A new version has been created, state: publish
Parts
=====
Content
-------
This part has been updated.
Mime type: text/xml (unchanged)
File name: (unchanged)
Size: 7555 bytes (previous version: 6362 bytes)
Content diff:
(54 equal lines skipped)
<p class="fixme">TBD</p>
+++ <h2>Daisy</h2>
+++
+++ <p>It's also a good idea to publish our docs while preparing a release. The
+++ reason for this is that when a release is created, the information about
+++ versions (Javadocs, dependencies overview, etc.) exactly reflects the
content of
+++ the released artifact.<br/>
+++ For that purpose configure your <tt>settings.xml</tt> as explained in
+++ <a href="daisy:1256">How to build the site locally</a> and give it a
dry-run as
+++ explained in this document before you do the actual release</p>
+++
<h1>Step 2: Releasing POM artifacts</h1>
<ol>
(29 equal lines skipped)
<li><tt>mvn -Dusername=[svn-user-name] -Dpassword=********
release:prepare</tt>
</li>
<li><tt>mvn -Dusername=[svn-user-name] -Dpassword=******** release:perform
--- -Darguments="-Dgpg.passphrase='[secret_passphrase_here]'" -P
release</tt></li>
--- <li>if SNAPSHOT dependencies have been replaced before, point again to
them</li>
+++ -Darguments="-Dgpg.passphrase='[secret_passphrase_here]' -P
+++ release,daisy,localDocs,javadocs-script" -P
+++ release,daisy,localDocs,javadocs-script</tt></li>
+++ <ul>
+++ <li><tt><tt>release </tt>... </tt>adds all plugins to the build lifecycle
which
+++ are only necessary at release time (e.g. the GPG plugin)</li>
+++ <li><tt>daisy ... </tt>adds the Daisy export plugin to the lifecycle of the
site
+++ module</li>
+++ <li><tt>j<tt>avad</tt></tt><tt>ocs-script ... </tt>adds a special report to
the
+++ report generation phase which adds an <tt>apidocs </tt>directory to the site
+++ output. This directory then contains a script which pulls the Javadocs from
a
+++ Maven repository and unpacks it.</li>
+++ <li><tt>localDocs ... </tt>configures the target directory of the deploy
+++ process. This profile has to be configured in the <em>local
+++ </em><tt>settings.xml</tt>!</li>
+++ </ul>
+++
+++ <li>if <tt>SNAPSHOT </tt>dependencies have been replaced before, point
again to
+++ them</li>
<li>Point all artifacts in trunk to the new snapshot version of this
artifact.
For this purpose update the dependencies management section of the root pom.
</li>
(42 equal lines skipped)
cocoon repository before, SVN should have cached your login credentials.
(anyway that's how it was for me on Mac OS X)</li>
<li>You can shortcut the execution by specifying both goals in one:<br/>
--- <tt>mvn -N release:prepare release:perform -Darguments="-N
--- </tt><tt>-Dgpg.passphrase='[secret_passphrase_here]'</tt><tt>"</tt></li>
--- <li>Verify a GPG signature: gpg --verify gnupg-x.x.x.tar.gz.sig
--- gnupg-x.x.x.tar.gz</li>
+++ <tt>mvn -N release:prepare release:perform ...</tt></li>
+++ <li>Verify a GPG signature: <tt>gpg --verify gnupg-x.x.x.tar.gz.sig
+++ gnupg-x.x.x.tar.gz</tt></li>
<li>You can reach the staging repository via http at
<a
href="http://people.apache.org/builds/cocoon/";>http://people.apache.org/builds/cocoon/</a>
</li>
(23 equal lines skipped)
