You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@isis.apache.org by da...@apache.org on 2017/09/25 08:34:10 UTC
[22/24] isis-site git commit: ISIS-1712 - updates docs,
replace references to isisaddons and catalog.incode.org with
platform.incode.org
http://git-wip-us.apache.org/repos/asf/isis-site/blob/e5dcb0be/content/guides/cgcom/cgcom.html
----------------------------------------------------------------------
diff --git a/content/guides/cgcom/cgcom.html b/content/guides/cgcom/cgcom.html
index 813f9fb..48895b1 100644
--- a/content/guides/cgcom/cgcom.html
+++ b/content/guides/cgcom/cgcom.html
@@ -655,8 +655,8 @@ git checkout master && git merge --no-ff ISIS-1162_pr-31 && git
<div class="content">
<pre class="CodeRay highlight"><code data-lang="bash">cd core
export ISISTMP=/c/tmp <i class="conum" data-value="1"></i><b>(1)</b>
-export ISISDEV=1.17.0-SNAPSHOT
-export ISISREL=1.16.0
+export ISISDEV=1.16.0-SNAPSHOT
+export ISISREL=1.15.1
export ISISRC=RC1
export ISISBRANCH=release-$ISISREL-$ISISRC
export ISISJIRA=ISIS-9999 <i class="conum" data-value="2"></i><b>(2)</b>
@@ -2210,7 +2210,7 @@ popd</code></pre>
</div>
<div class="listingblock">
<div class="content">
- <pre class="CodeRay highlight"><code data-lang="bash">sh upd.sh 1.16.0 1.17.0</code></pre>
+ <pre class="CodeRay highlight"><code data-lang="bash">sh upd.sh 1.15.1 1.16.0</code></pre>
</div>
</div>
<div class="paragraph">
@@ -2469,286 +2469,7 @@ git push</code></pre>
<div class="sect2">
<h3 id="__cgcom_post-release-successful_release-non-asf-modules">6.13. Release (non-ASF) Modules</h3>
<div class="paragraph">
- <p>There are two libraries of modules, both non-ASF but open source, that should be released.</p>
- </div>
- <div class="ulist">
- <ul>
- <li> <p><a href="http://www.isisaddons.org">Isis Addons</a> - modules addressing technical concerns</p> </li>
- <li> <p><a href="http://catalog.incode.org">Incode Catalog</a> - modules for various generic business subdomains</p> </li>
- </ul>
- </div>
- <div class="paragraph">
- <p>These each use a common parent, <code>org.incode:incode-parent</code>. This must be released first, then both set of modules afterwards.</p>
- </div>
- <div class="sect3">
- <h4 id="__cgcom_post-release-successful_release-non-asf-modules_prereqs">6.13.1. Prereqs</h4>
- <div class="paragraph">
- <p>Save this <a href="https://gist.github.com/danhaywood/e80daf6d25f5c1fb1093effba85d088a">gist</a> as <code>last_modified.sh</code> in an appropriate parent directory of both sets of repos.</p>
- </div>
- <div class="paragraph">
- <p>For example, if the isisaddons modules are cloned to <code>/c/github/isisaddons/isis-module-xxx</code> and the incode catalog modules are cloned to <code>/c/github/incodehq/incode-module-xxx</code>, then save in <code>/c/github</code>.</p>
- </div>
- </div>
- <div class="sect3">
- <h4 id="__cgcom_post-release-successful_release-non-asf-modules_incode-parent">6.13.2. Release <code>incode-parent</code></h4>
- <div class="admonitionblock note">
- <table>
- <tbody>
- <tr>
- <td class="icon"> <i class="fa icon-note" title="Note"></i> </td>
- <td class="content">
- <div class="paragraph">
- <p>TODO: need to rework this and the following two sections to instead just release the incode-catalog (<code>1.16.0-SNAPSHOT</code>).</p>
- </div>
- <div class="paragraph">
- <p>This incorporates all of <code>incode-parent</code>, isisaddons.org` and <code>catalog.incode.org</code>.</p>
- </div> </td>
- </tr>
- </tbody>
- </table>
- </div>
- <div class="paragraph">
- <p>The <code>org.incode:incode-parent</code> Maven module is used as a parent for both sets of modules:</p>
- </div>
- <div class="ulist">
- <ul>
- <li> <p>update its dependency on Apache Isis to reference the newly released version:<br></p>
- <div class="listingblock">
- <div class="content">
- <pre class="CodeRay highlight"><code data-lang="bash">sh bumpver_isis.sh 1.16.0</code></pre>
- </div>
- </div> </li>
- <li> <p>update the README</p>
- <div class="ulist">
- <ul>
- <li> <p>replace each version with next (ie the "How to Configure/Use" section, and the "Release to Maven Central" section at the end):</p>
- <div class="ulist">
- <ul>
- <li> <p>replace 1.16.0-SNAPSHOT with 1.17.0-SNAPSHOT</p> </li>
- <li> <p>replace 1.15.0 with 1.16.0</p> </li>
- </ul>
- </div> </li>
- <li> <p>update the "Change Log" section</p> </li>
- </ul>
- </div> </li>
- <li> <p>Release using:<br></p>
- <div class="listingblock">
- <div class="content">
- <pre class="CodeRay highlight"><code data-lang="bash">sh release.sh "1.16.0" "1.17.0-SNAPSHOT" "dan@haywood-associates.co.uk" "this is not really my password"</code></pre>
- </div>
- </div> </li>
- </ul>
- </div>
- </div>
- <div class="sect3">
- <h4 id="__cgcom_post-release-successful_release-non-asf-modules_isisaddons">6.13.3. Release Isis Addons</h4>
- <div class="paragraph">
- <p>Once the Apache Isis release is available, all of the (non-ASF) <a href="http://www.isisaddons.org">Isis Addons</a> should also be released.</p>
- </div>
- <div class="paragraph">
- <p>Using this <a href="https://gist.github.com/danhaywood/21b5b885433fd8bc440da3fab88c91cb">gist</a> to invoke operations across all (or selected) addons:</p>
- </div>
- <div class="ulist">
- <ul>
- <li> <p>update its dependency on Apache Isis to reference the newly released version:<br></p>
- <div class="listingblock">
- <div class="content">
- <pre class="CodeRay highlight"><code data-lang="bash">foreach -g isisaddons sh bumpver_isis.sh 1.16.0</code></pre>
- </div>
- </div>
- <div class="paragraph">
- <p>and use:<br></p>
- </div>
- <div class="listingblock">
- <div class="content">
- <pre class="CodeRay highlight"><code data-lang="bash">foreach -g isisaddons git diff HEAD^ HEAD</code></pre>
- </div>
- </div>
- <div class="paragraph">
- <p>and:<br></p>
- </div>
- <div class="listingblock">
- <div class="content">
- <pre class="CodeRay highlight"><code data-lang="bash">foreach -g isisaddons git status --branch --porcelain</code></pre>
- </div>
- </div>
- <div class="paragraph">
- <p>to review changes made.</p>
- </div> </li>
- <li> <p>update the README for each repository.</p>
- <div class="ulist">
- <ul>
- <li> <p>if using Windows, then:<br></p>
- <div class="listingblock">
- <div class="content">
- <pre class="CodeRay highlight"><code data-lang="bash">"C:\Program Files (x86)\Notepad++\notepad++.exe" isisaddons/isis-m*/README.adoc isisaddons/isis-w*/README.adoc</code></pre>
- </div>
- </div> </li>
- <li> <p>replace each version with next (ie the "How to Configure/Use" section, and the "Release to Maven Central" section at the end):</p>
- <div class="ulist">
- <ul>
- <li> <p>replace <code>1.16.0</code> with <code>1.17.0</code></p> </li>
- <li> <p>replace <code>1.15.0</code> with <code>1.16.0</code> as necessary (pretty much everywhere apart from the "Change Log")</p> </li>
- </ul>
- </div> </li>
- <li> <p>update the "Change Log" section</p> </li>
- </ul>
- </div> </li>
- <li> <p>release the metamodel/module/wicket modules to mvn central (contains a sanity check before hand that everything compiles):<br></p>
- <div class="listingblock">
- <div class="content">
- <pre class="CodeRay highlight"><code data-lang="bash">foreach -g isisaddons/isis-[mw] sh release.sh "1.16.0" "1.17.0-SNAPSHOT" "dan@haywood-associates.co.uk" \"this is not really my password\"</code></pre>
- </div>
- </div> </li>
- <li> <p>In the parent directory where the <code>last_modified.sh</code> script has been saved (see <a href="../cgcom/cgcom.html#__cgcom_post-release-successful_release-non-asf-modules_prereqs">above</a>), use to check that all modules were released successfully:<br></p>
- <div class="listingblock">
- <div class="content">
- <pre class="CodeRay highlight"><code data-lang="bash">foreach -g isisaddons/isis-[mw] sh ../../last-modified.sh 1.16.0</code></pre>
- </div>
- </div>
- <div class="admonitionblock important">
- <table>
- <tbody>
- <tr>
- <td class="icon"> <i class="fa icon-important" title="Important"></i> </td>
- <td class="content">
- <div class="paragraph">
- <p>Wait at least 10 minutes to check; sync’ing to Maven central from the Sonatype OSS repository isn’t instaneous.</p>
- </div> </td>
- </tr>
- </tbody>
- </table>
- </div> </li>
- <li> <p>Assuming everything did get published ok, then push branch and tag:<br></p>
- <div class="listingblock">
- <div class="content">
- <pre class="CodeRay highlight"><code data-lang="bash">foreach -g isisaddons/isis-[mw] "git push origin master && git push origin 1.16.0"</code></pre>
- </div>
- </div> </li>
- </ul>
- </div>
- </div>
- <div class="sect3">
- <h4 id="__cgcom_post-release-successful_release-non-asf-modules_incode-catalog">6.13.4. Release Incode Catalog Modules</h4>
- <div class="paragraph">
- <p>Similarly, all of the (non-ASF) <a href="http://catalog.incode.org">Incode Catalog</a> modules should also be released.</p>
- </div>
- <div class="paragraph">
- <p>Using this <a href="https://gist.github.com/danhaywood/21b5b885433fd8bc440da3fab88c91cb">gist</a> to invoke operations across all (or selected) addons:</p>
- </div>
- <div class="ulist">
- <ul>
- <li> <p>update its dependency on Apache Isis to reference the newly released version:<br></p>
- <div class="listingblock">
- <div class="content">
- <pre class="CodeRay highlight"><code data-lang="bash">foreach -g incodehq/incode-module sh bumpver_isis.sh 1.16.0</code></pre>
- </div>
- </div> </li>
- <li> <p>update the README for each repository.<br></p>
- <div class="paragraph">
- <p>eg if using Windows, then:</p>
- </div>
- <div class="listingblock">
- <div class="content">
- <pre class="CodeRay highlight"><code data-lang="bash">"C:\Program Files (x86)\Notepad++\notepad++.exe" incodehq/incode-*/README.adoc</code></pre>
- </div>
- </div>
- <div class="ulist">
- <ul>
- <li> <p>Replace each version with next (ie the "How to Configure/Use" section, and the "Release to Maven Central" section at the end):</p>
- <div class="ulist">
- <ul>
- <li> <p>replace <code>1.16.0</code> with <code>1.17.0</code></p> </li>
- <li> <p>replace <code>1.15.0</code> with <code>1.16.0</code> as necessary (pretty much everywhere apart from the "Change Log")</p> </li>
- </ul>
- </div> </li>
- <li> <p>update the "Change Log" section</p> </li>
- </ul>
- </div> </li>
- <li> <p>update cross-module dependencies<br></p>
- <div class="paragraph">
- <p>Some of the incode catalog modules depend on isisaddons modules, and also on each other.<br></p>
- </div>
- <div class="paragraph">
- <p>eg if using Windows, then:<br></p>
- </div>
- <div class="listingblock">
- <div class="content">
- <pre class="CodeRay highlight"><code data-lang="bash">"C:\Program Files (x86)\Notepad++\notepad++.exe" incodehq/incode-module*/pom.xml incodehq/incode-module-*/dom/pom.xml incodehq/incode-module-*/module/pom.xml</code></pre>
- </div>
- </div>
- <div class="admonitionblock tip">
- <table>
- <tbody>
- <tr>
- <td class="icon"> <i class="fa icon-tip" title="Tip"></i> </td>
- <td class="content">
- <div class="paragraph">
- <p>See <a href="../cgcom/cgcom.html#__cgcom_post-release-successful_release-non-asf-modules_incode-catalog_cross-module-dependencies">below</a> for a list of the dependencies to update.</p>
- </div> </td>
- </tr>
- </tbody>
- </table>
- </div> </li>
- <li> <p>If necessary, adjust the <code>_repos.txt</code> file (used by <code>foreach</code> function) so that repositories are released in the correct sequence (with respect to their mutual dependencies). For example, <code>incode-module-base</code> must be released prior to <code>incode-module-alias</code>.</p> </li>
- <li> <p>release the <code>incode-module-???</code> modules to mvn central (contains a sanity check before hand that everything compiles):<br></p>
- <div class="listingblock">
- <div class="content">
- <pre class="CodeRay highlight"><code data-lang="bash">foreach -g incodehq/incode-module-[a-w] sh release.sh "1.16.0" "1.17.0-SNAPSHOT" "dan@haywood-associates.co.uk" \"this is not really my password\"</code></pre>
- </div>
- </div> </li>
- <li> <p>In the parent directory where the <code>last_modified.sh</code> script has been saved (see <a href="../cgcom/cgcom.html#__cgcom_post-release-successful_release-non-asf-modules_prereqs">above</a>), use to check that all modules were released successfully:<br></p>
- <div class="listingblock">
- <div class="content">
- <pre class="CodeRay highlight"><code data-lang="bash">foreach -g incodehq/incode-module-[a-w] sh ../../last-modified.sh 1.16.0</code></pre>
- </div>
- </div>
- <div class="admonitionblock important">
- <table>
- <tbody>
- <tr>
- <td class="icon"> <i class="fa icon-important" title="Important"></i> </td>
- <td class="content">
- <div class="paragraph">
- <p>Wait at least 10 minutes to check; sync’ing to Maven central from the Sonatype OSS repository isn’t instaneous.</p>
- </div> </td>
- </tr>
- </tbody>
- </table>
- </div> </li>
- <li> <p>Assuming everything did get published ok, then push branch and tag:<br></p>
- <div class="listingblock">
- <div class="content">
- <pre class="CodeRay highlight"><code data-lang="bash">foreach -g incodehq/incode-module-[a-w] "git push origin master && git push origin 1.16.0"</code></pre>
- </div>
- </div> </li>
- </ul>
- </div>
- <div class="sect4">
- <h5 id="__cgcom_post-release-successful_release-non-asf-modules_incode-catalog_cross-module-dependencies">Cross-module dependencies</h5>
- <div class="paragraph">
- <p>As of v1.16.0, the list of dependencies that needed to be updated (across all modules) were:</p>
- </div>
- <div class="ulist">
- <ul>
- <li> <p><code><isis-module-fakedata.version>1.16.0</isis-module-fakedata.version></code></p> </li>
- <li> <p><code><isis-module-freemarker.version>1.16.0</isis-module-freemarker.version></code></p> </li>
- <li> <p><code><isis-wicket-fullcalendar2-cpt.version>1.16.0</isis-wicket-fullcalendar2-cpt.version></code></p> </li>
- <li> <p><code><isis-wicket-gmap3-cpt.version>1.16.0</isis-wicket-gmap3-cpt.version></code></p> </li>
- <li> <p><code><isis-module-poly.version>1.16.0</isis-module-poly.version></code></p> </li>
- <li> <p><code><isis-module-security.version>1.16.0</isis-module-security.version></code></p> </li>
- <li> <p><code><incode-module-base.version>1.16.0</incode-module-base.version></code></p> </li>
- <li> <p><code><incode-module-fixturesupport.version>1.16.0</incode-module-fixturesupport.version></code></p> </li>
- <li> <p><code><incode-module-unittestsupport.version>1.16.0</incode-module-unittestsupport.version></code></p> </li>
- <li> <p><code><incode-module-integtestsupport.version>1.16.0</incode-module-integtestsupport.version></code></p> </li>
- <li> <p><code><incode-module-country.version>1.16.0</incode-module-country.version></code></p> </li>
- <li> <p><code><incode-module-document.version>1.16.0</incode-module-document.version></code></p> </li>
- <li> <p><code><incode-module-docrendering-freemarker.version>1.16.0</incode-module-docrendering-freemarker.version></code></p> </li>
- <li> <p><code><incode-module-docrendering-stringinterpolator.version>1.16.0</incode-module-docrendering-stringinterpolator.version></code></p> </li>
- <li> <p><code><incode-module-docrendering-xdocreport.version>1.16.0</incode-module-docrendering-xdocreport.version></code></p> </li>
- </ul>
- </div>
- </div>
+ <p>The (non-ASF) <a href="http://platform.incode.org" target="_blank">Incode Platform</a> should also be released, as per their <a href="http://platform.incode.org/pages/committers-guide/committers-guide.html#_release_to_maven_central">release guide</a>.</p>
</div>
</div>
</div>