cocoon-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From da...@cocoon.zones.apache.org
Subject [DAISY] Updated: Releasing Cocoon
Date Thu, 14 Dec 2006 07:58:57 GMT
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: 12/14/06 7:58:41 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: 4002 bytes (previous version: 3455 bytes)
Content diff:
(3 equal lines skipped)
    <p>As Cocoon uses Maven 2 as build system, the release process is very simple
    and only requires a few steps.</p>
    
--- <h1>Prepare your workstation</h1>
+++ <h1>Step 1: Prepare your workstation</h1>
    
    <p>In order to get started, you have to make sure that your work station is
    configured correctly:</p>
(5 equal lines skipped)
    (<a href="http://hacks.oreilly.com/pub/h/66">http://hacks.oreilly.com/pub/h/66</a>)
    </li>
    <li>in the case that your local username is different from your username at
--- people.apache.org, configure it at ~/.m2/settings.xml. Also note that setting a
--- mirror is helpful.</li>
+++ people.apache.org, configure it at ~/.m2/settings.xml.</li>
    <li>point to an empty local repository</li>
    </ul>
    
(10 equal lines skipped)
    &lt;/settings&gt;</pre>
    
    <p class="note">Point to an empty local repository. This ensures that you don't
--- introduce dependencies that can only be fullfilled within your environment.</p>
+++ introduce dependencies that can only be fullfilled within your local build
+++ environment or after doing the release which puts all created artifacts into
+++ your local repository.</p>
    
--- <h1>Releasing POM artifacts</h1>
+++ <h1>Step 2: Releasing POM artifacts</h1>
    
    <ol>
    <li>refer to an already released parent in pom.xml</li>
(9 equal lines skipped)
    2-SNAPSHOT. The next version increment of that pom is thus 3-SNAPSHOT, and you
    should manually change all poms that have 2-SNAPSHOT for this parent to
    3-SNAPSHOT. Otherwise the trunk build will use "old" ie already released
--- artifacts, which is not desired.</p>
+++ artifacts, which is not desired. The pu.sh script in 
+++ <tt>cocoon/trunk/tools/pom-updater</tt> helps to make the update easier.</p>
    
--- <h1>Releasing JAR artifacts</h1>
+++ <h1>Step 3: Releasing JAR artifacts</h1>
    
    <ol>
    <li>refer to an already released parent in pom.xml</li>
(4 equal lines skipped)
    </li>
    <li>if SNAPSHOT dependencies have been replaced before, point again to them</li>
    <li>Point all artifacts in trunk to the new snapshot version of this artifact.
--- </li>
+++ For this purpose find a script in <tt>cocoon/trunk/tools/pom-updater</tt>.</li>
    </ol>
    
--- <h1><strong>Tips and tricks</strong></h1>
+++ <h1>Step 4: Build Cocoon</h1>
    
+++ <p>The last step is testing whether you have set all dependencies on parent or
+++ other modules correctly. The best way to do this is pointing to an empty local
+++ repository in your ~/.m2/settings.xml file again and do a <tt>mvn install -P
+++ allblocks</tt> from <tt>./cocoon/trunk</tt>.</p>
+++ 
+++ <h1>Tips and tricks</h1>
+++ 
    <ul>
    <li>You can probably omit the username and password if you have committed to the
    cocoon repository before, SVN should have  cached your login credentials.
(20 equal lines skipped)


Mime
View raw message