cocoon-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [DAISY] Updated: Releasing Cocoon
Date Tue, 25 Mar 2008 22:29:16 GMT
A document has been updated:

Document ID: 1199
Branch: main
Language: default
Name: Releasing Cocoon (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 3/25/08 10:29:04 PM
Updated by: Reinhard Pötz

A new version has been created, state: publish


This part has been updated.
Mime type: text/xml (unchanged)
File name:  (unchanged)
Size: 10221 bytes (previous version: 8804 bytes)
Content diff:
(123 equal lines skipped)
+++ <h2>Additional instructions for special modules</h2>
+++ <h3>Multi-module release of Cocoon Core</h3>
+++ <ul>
+++ <li>Before you can invoke a multi-module release of Cocoon core, go to
+++ <tt>/trunk/core-modules/pom.xml</tt> and enable the dependency management
+++ section. This has to contain the complete list of all to be released modules.
+++ You have to use <em>the to-be-released</em> version.</li>
+++ <li>Before you can invoke the release procedure from above, run <tt>mvn clean
+++ install</tt> before. This has to be done because of a bug when Maven tries to
+++ resolve test-jar dependencies from within the release plugin.</li>
+++ <li>After the release deactivate the dependencyManagement section in
+++ <tt>/trunk/core-modules/pom.xml </tt>again.</li>
+++ </ul>
+++ <h3>Maven plugin</h3>
+++ <ul>
+++ <li>The Maven plugin is has one special dependency that MUSTN'T be declared from
+++ within its pom.xml file but is being resolved at runtime. This means that before
+++ you run invoke the release procedure, go to the file
+++ <a href=""></a>
+++ and set the constants LIB_VERSION_WRAPPER and LIB_VERSION_SPRING_RELOADER to the
+++ <em>to-be-released</em> version.</li>
+++ <li>After the release, set the version to the new SNAPSHOT version.</li>
+++ </ul>
    <h1>Step 4: Build Cocoon</h1>
    <p>The next 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>Step 5: Call for a vote</h1>
+++ <h1>Step 5: Build the Non-Maven release artifacts</h1>
+++ <p>TBD</p>
+++ <h1>Step 6: Call for a vote</h1>
    <p>Call for a vote that includes information about</p>
(7 equal lines skipped)
    <p class="fixme">Add a mail template here</p>
--- <h1>Step 6: Publish the artifacts</h1>
+++ <h1>Step 7: Publish the artifacts</h1>
    <p>If the vote passes, copy the artifacts to the Apache sync repository:</p>
(3 equal lines skipped)
    <p>If everything worked fine, you you can delete
--- <h1>Step 7: Announce the release</h1>
+++ <h1>Step 8: Announce the release</h1>
    <p class="fixme">Add a template here</p>
--- <h1>Step 8: Update JIRA fields</h1>
+++ <h1>Step 9: Update JIRA fields</h1>
    <p>Cocoon has its own JIRA fields of similar meaing to standard fields
    <em>Affects Version</em> and <em>Fix version</em> but scoped to
one component
(64 equal lines skipped)

View raw message