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/03/08 05:35:43 UTC
[14/15] isis-site git commit: ISIS-1594: fixes anchors for extension
point's conventions
ISIS-1594: fixes anchors for extension point's conventions
Project: http://git-wip-us.apache.org/repos/asf/isis-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/isis-site/commit/dd1ff6a4
Tree: http://git-wip-us.apache.org/repos/asf/isis-site/tree/dd1ff6a4
Diff: http://git-wip-us.apache.org/repos/asf/isis-site/diff/dd1ff6a4
Branch: refs/heads/asf-site
Commit: dd1ff6a45f5a048afb8c4adca727b983a5180ca4
Parents: 83a3755
Author: Dan Haywood <da...@haywood-associates.co.uk>
Authored: Wed Mar 8 00:55:48 2017 +0000
Committer: Dan Haywood <da...@haywood-associates.co.uk>
Committed: Wed Mar 8 00:55:48 2017 +0000
----------------------------------------------------------------------
content/guides/cgcom.html | 148 +-
content/guides/cgcom.pdf | 2812 +++++++-------
content/guides/dg.html | 164 +-
content/guides/dg.pdf | 1436 +++----
content/guides/rgant.html | 4 +-
content/guides/rgant.pdf | 1726 ++++-----
content/guides/rgcfg.html | 42 +-
content/guides/rgcfg.pdf | 532 +--
content/guides/rgcms.html | 84 +-
content/guides/rgcms.pdf | 1876 ++++-----
content/guides/rgfis.html | 4 +-
content/guides/rgfis.pdf | 584 +--
content/guides/rgmvn.html | 8 +-
content/guides/rgmvn.pdf | 426 +--
content/guides/rgsvc.html | 192 +-
content/guides/rgsvc.pdf | 7548 +++++++++++++++++++------------------
content/guides/tg.html | 2 +-
content/guides/tg.pdf | 400 +-
content/guides/ugbtb.html | 108 +-
content/guides/ugbtb.pdf | 3120 ++++++++-------
content/guides/ugfun.html | 160 +-
content/guides/ugfun.pdf | 5352 +++++++++++++-------------
content/guides/ugsec.html | 5 +-
content/guides/ugsec.pdf | 318 +-
content/guides/ugtst.html | 14 +-
content/guides/ugtst.pdf | 738 ++--
content/guides/ugvro.html | 87 +-
content/guides/ugvro.pdf | 1543 ++++----
content/guides/ugvw.html | 20 +-
content/guides/ugvw.pdf | 1050 +++---
content/migration-notes.html | 16 +-
content/powered-by.html | 2 +-
content/screencasts.html | 4 +-
33 files changed, 15123 insertions(+), 15402 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/isis-site/blob/dd1ff6a4/content/guides/cgcom.html
----------------------------------------------------------------------
diff --git a/content/guides/cgcom.html b/content/guides/cgcom.html
index cdfb151..bfc7536 100644
--- a/content/guides/cgcom.html
+++ b/content/guides/cgcom.html
@@ -683,7 +683,7 @@ git checkout master && git merge --no-ff ISIS-1162_pr-31 && git
<p>These release notes using bash command line tools. They should work on Linux and MacOS; for Windows, use mSysGit.</p>
</div>
<div class="sect2">
- <h3 id="_cgcom_cutting-a-release_obtain-consensus">3.1. Obtain Consensus</h3>
+ <h3 id="__cgcom_cutting-a-release_obtain-consensus">3.1. Obtain Consensus</h3>
<div class="paragraph">
<p>Before releasing <code>core</code>, ensure there is consensus on the <a href="../support.html">dev mailing list</a> that this is the right time for a release. The discussion should include confirming the version number to be used, and to confirm content.</p>
</div>
@@ -695,7 +695,7 @@ git checkout master && git merge --no-ff ISIS-1162_pr-31 && git
</div>
</div>
<div class="sect2">
- <h3 id="_cgcom_cutting-a-release_set-environment-variables">3.2. Set environment variables</h3>
+ <h3 id="__cgcom_cutting-a-release_set-environment-variables">3.2. Set environment variables</h3>
<div class="paragraph">
<p>We use environment variables to parameterize as many of the steps as possible. For example:</p>
</div>
@@ -722,7 +722,7 @@ env | grep ISIS | sort</code></pre>
</tr>
<tr>
<td><i class="conum" data-value="2"></i><b>2</b></td>
- <td>set to an "umbrella" ticket for all release activities. (One should exist already, <a href="#_cgcom_post-release-successful_update-jira_create-new-jira">created at</a> the beginning of the development cycle now completing).</td>
+ <td>set to an "umbrella" ticket for all release activities. (One should exist already, <a href="#__cgcom_post-release-successful_update-jira_create-new-jira">created at</a> the beginning of the development cycle now completing).</td>
</tr>
<tr>
<td><i class="conum" data-value="3"></i><b>3</b></td>
@@ -752,7 +752,7 @@ env | grep ISIS | sort</code></pre>
</div>
</div>
<div class="sect2">
- <h3 id="_cgcom_cutting-a-release_pull-down-code-to-release">3.3. Pull down code to release</h3>
+ <h3 id="__cgcom_cutting-a-release_pull-down-code-to-release">3.3. Pull down code to release</h3>
<div class="paragraph">
<p>Set the HEAD of your local git repo to the commit to be released. This will usually be the tip of the origin\u2019s <code>master</code> branch. Then, create a release branch for the version number being released; eg:</p>
</div>
@@ -805,7 +805,7 @@ git checkout -b $ISISBRANCH</code></pre>
</div>
</div>
<div class="sect2">
- <h3 id="_cgcom_cutting-a-release_releasing-core">3.4. Releasing Core</h3>
+ <h3 id="__cgcom_cutting-a-release_releasing-core">3.4. Releasing Core</h3>
<div class="paragraph">
<p>First, we release <code>core</code>. Switch to the appropriate directory:</p>
</div>
@@ -815,7 +815,7 @@ git checkout -b $ISISBRANCH</code></pre>
</div>
</div>
<div class="sect3">
- <h4 id="_cgcom_cutting-a-release_releasing-core_set-environment-variables">3.4.1. Set environment variables</h4>
+ <h4 id="__cgcom_cutting-a-release_releasing-core_set-environment-variables">3.4.1. Set environment variables</h4>
<div class="paragraph">
<p>Set additional environment variables for the core "artifact":</p>
</div>
@@ -829,7 +829,7 @@ env | grep ISIS | sort</code></pre>
</div>
</div>
<div class="sect3">
- <h4 id="_cgcom_cutting-a-release_releasing-core_license-headers">3.4.2. License headers</h4>
+ <h4 id="__cgcom_cutting-a-release_releasing-core_license-headers">3.4.2. License headers</h4>
<div class="paragraph">
<p>The Apache Release Audit Tool <code>RAT</code> (from the <a href="http://creadur.apache.org">Apache Creadur</a> project) checks for missing license header files. The parent <code>pom.xml</code> of each releasable module specifies the RAT Maven plugin, with a number of custom exclusions.</p>
</div>
@@ -875,7 +875,7 @@ for a in `find . -name rat.txt -print`; do grep '!???' $a; done</code></pre>
</div>
</div>
<div class="sect3">
- <h4 id="_cgcom_cutting-a-release_releasing-core_missing-license-check">3.4.3. Missing License Check</h4>
+ <h4 id="__cgcom_cutting-a-release_releasing-core_missing-license-check">3.4.3. Missing License Check</h4>
<div class="paragraph">
<p>Although Apache Isis has no dependencies on artifacts with incompatible licenses, the POMs for some of these dependencies (in the Maven central repo) do not necessarily contain the required license information. Without appropriate additional configuration, this would result in the generated <code>DEPENDENCIES</code> file and generated Maven site indicating dependencies as having "unknown" licenses.</p>
</div>
@@ -914,7 +914,7 @@ licenses to remove from supplemental-models.xml (are spurious):
</div>
</div>
<div class="sect3">
- <h4 id="_cgcom_cutting-a-release_releasing-core_commit-changes">3.4.4. Commit changes</h4>
+ <h4 id="__cgcom_cutting-a-release_releasing-core_commit-changes">3.4.4. Commit changes</h4>
<div class="paragraph">
<p>Commit any changes from the preceding steps:</p>
</div>
@@ -925,7 +925,7 @@ licenses to remove from supplemental-models.xml (are spurious):
</div>
</div>
<div class="sect3">
- <h4 id="_cgcom_cutting-a-release_releasing-core_sanity-check">3.4.5. Sanity check</h4>
+ <h4 id="__cgcom_cutting-a-release_releasing-core_sanity-check">3.4.5. Sanity check</h4>
<div class="paragraph">
<p>Perform one last sanity check on the codebase. Delete all Isis artifacts from your local Maven repo, then build using the <code>-o</code> offline flag:</p>
</div>
@@ -937,7 +937,7 @@ mvn clean install -o</code></pre>
</div>
</div>
<div class="sect3">
- <h4 id="_cgcom_cutting-a-release_releasing-core_release-prepare-dry-run">3.4.6. Release prepare "dry run"</h4>
+ <h4 id="__cgcom_cutting-a-release_releasing-core_release-prepare-dry-run">3.4.6. Release prepare "dry run"</h4>
<div class="paragraph">
<p>Most of the work is done using the <code>mvn release:prepare</code> goal. Since this makes a lot of changes, we run it first in "dry run" mode; only if that works do we run the goal for real.</p>
</div>
@@ -970,7 +970,7 @@ mvn clean install -o</code></pre>
</div>
</div>
<div class="sect3">
- <h4 id="_cgcom_cutting-a-release_releasing-core_release-prepare-proper">3.4.7. Release prepare "proper"</h4>
+ <h4 id="__cgcom_cutting-a-release_releasing-core_release-prepare-proper">3.4.7. Release prepare "proper"</h4>
<div class="paragraph">
<p>Assuming this completes successfully, re-run the command, but without the <code>dryRun</code> flag and specifying <code>resume=false</code> (to ignore the generated <code>release.properties</code> file that gets generated as a side-effect of using <code>git</code>). You can also set the <code>skipTests</code> flag since they would have been run during the previous dry run:</p>
</div>
@@ -997,7 +997,7 @@ mvn clean install -o</code></pre>
</div>
</div>
<div class="sect3">
- <h4 id="_cgcom_cutting-a-release_releasing-core_post-prepare-sanity-check">3.4.8. Post-prepare sanity check</h4>
+ <h4 id="__cgcom_cutting-a-release_releasing-core_post-prepare-sanity-check">3.4.8. Post-prepare sanity check</h4>
<div class="paragraph">
<p>You should end up with artifacts in your local repo with the new version (eg <code>1.15.0</code>). This is a good time to do some quick sanity checks; nothing has yet been uploaded:</p>
</div>
@@ -1036,7 +1036,7 @@ popd</code></pre>
</div>
</div>
<div class="sect3">
- <h4 id="_cgcom_cutting-a-release_releasing-core_release-perform-upload">3.4.9. Release perform (Upload)</h4>
+ <h4 id="__cgcom_cutting-a-release_releasing-core_release-perform-upload">3.4.9. Release perform (Upload)</h4>
<div class="paragraph">
<p>Once the release has been built locally, it should be uploaded for voting. This is done by deploying the Maven artifacts to a staging directory (this includes the source release ZIP file which will be voted upon).</p>
</div>
@@ -1087,7 +1087,7 @@ re
</div>
</div>
<div class="sect2">
- <h3 id="_cgcom_cutting-a-release_releasing-the-archetype">3.5. Releasing the Archetype</h3>
+ <h3 id="__cgcom_cutting-a-release_releasing-the-archetype">3.5. Releasing the Archetype</h3>
<div class="paragraph">
<p>Apache Isis archetypes are reverse engineered from example applications. Once reverse engineered, the source is checked into git (replacing any earlier version of the archetype) and released.</p>
</div>
@@ -1116,7 +1116,7 @@ re
</div>
</div>
<div class="sect3">
- <h4 id="_cgcom_cutting-a-release_releasing-the-archetype_setup-environment-variables">3.5.1. Setup environment variables</h4>
+ <h4 id="__cgcom_cutting-a-release_releasing-the-archetype_setup-environment-variables">3.5.1. Setup environment variables</h4>
<div class="paragraph">
<p>Set additional environment variables for the <code>simpleapp-archetype</code> artifact:</p>
</div>
@@ -1143,7 +1143,7 @@ env | grep ISIS | sort</code></pre>
</div>
</div>
<div class="sect3">
- <h4 id="_cgcom_cutting-a-release_releasing-the-archetype_check-the-example-app">3.5.2. Check the example app</h4>
+ <h4 id="__cgcom_cutting-a-release_releasing-the-archetype_check-the-example-app">3.5.2. Check the example app</h4>
<div class="paragraph">
<p>Update the parent <code>pom.xml</code> to reference the <em>released</em> version of Apache Isis core, eg:</p>
</div>
@@ -1248,7 +1248,7 @@ docker container run -p 8080:8080 -d test/simpleapp</code></pre>
</div>
</div>
<div class="sect3">
- <h4 id="_cgcom_cutting-a-release_releasing-the-archetype_create-the-archetype">3.5.3. Create the archetype</h4>
+ <h4 id="__cgcom_cutting-a-release_releasing-the-archetype_create-the-archetype">3.5.3. Create the archetype</h4>
<div class="paragraph">
<p>Make sure you are in the correct directory and environment variables are correct.</p>
</div>
@@ -1274,7 +1274,7 @@ env | grep ISIS | sort</code></pre>
</div>
</div>
<div class="sect3">
- <h4 id="_cgcom_cutting-a-release_releasing-the-archetype_release-prepare">3.5.4. Release prepare</h4>
+ <h4 id="__cgcom_cutting-a-release_releasing-the-archetype_release-prepare">3.5.4. Release prepare</h4>
<div class="paragraph">
<p>Switch to the <strong>archetype</strong> directory and execute the <code>release:prepare</code>:</p>
</div>
@@ -1290,7 +1290,7 @@ mvn release:prepare -P apache-release \
</div>
</div>
<div class="sect3">
- <h4 id="_cgcom_cutting-a-release_releasing-the-archetype_post-prepare-sanity-check">3.5.5. Post-prepare sanity check</h4>
+ <h4 id="__cgcom_cutting-a-release_releasing-the-archetype_post-prepare-sanity-check">3.5.5. Post-prepare sanity check</h4>
<div class="paragraph">
<p>This is a good point to test the archetype; nothing has yet been uploaded.</p>
</div>
@@ -1333,7 +1333,7 @@ mvn -pl webapp jetty:run # runs as mvn jetty plugin</code></pre>
</div>
</div>
<div class="sect3">
- <h4 id="_cgcom_cutting-a-release_releasing-the-archetype_release-perform-upload">3.5.6. Release Perform (upload)</h4>
+ <h4 id="__cgcom_cutting-a-release_releasing-the-archetype_release-perform-upload">3.5.6. Release Perform (upload)</h4>
<div class="paragraph">
<p>Back in the original session (in the <strong>archetype</strong> directory, <code>example/archetype/$ISISCPN</code>), execute <code>release:perform</code>:</p>
</div>
@@ -1349,7 +1349,7 @@ mvn -pl webapp jetty:run # runs as mvn jetty plugin</code></pre>
</div>
</div>
<div class="sect2">
- <h3 id="_cgcom_cutting-a-release_check-close-staging-repo">3.6. Check/Close Staging Repo</h3>
+ <h3 id="__cgcom_cutting-a-release_check-close-staging-repo">3.6. Check/Close Staging Repo</h3>
<div class="paragraph">
<p>The <code>mvn release:perform</code> commands will have put release artifacts for both <code>core</code> and the <code>simpleapp</code> archetype into a newly created staging repository on the ASF Nexus repository server.</p>
</div>
@@ -1431,7 +1431,7 @@ mvn -pl webapp jetty:run # runs as mvn jetty plugin</code></pre>
</div>
</div>
<div class="sect2">
- <h3 id="_cgcom_cutting-a-release_push-branches">3.7. Push branches</h3>
+ <h3 id="__cgcom_cutting-a-release_push-branches">3.7. Push branches</h3>
<div class="paragraph">
<p>Push the release branch to origin:</p>
</div>
@@ -1465,7 +1465,7 @@ git fetch</code></pre>
</div>
</div>
<div class="sect2">
- <h3 id="_cgcom_cutting-a-release_voting">3.8. Voting</h3>
+ <h3 id="__cgcom_cutting-a-release_voting">3.8. Voting</h3>
<div class="paragraph">
<p>Once the artifacts have been uploaded, you can call a vote.</p>
</div>
@@ -1473,7 +1473,7 @@ git fetch</code></pre>
<p>In all cases, votes last for 72 hours and require a +3 (binding) vote from members.</p>
</div>
<div class="sect3">
- <h4 id="_cgcom_cutting-a-release_voting-start-voting-thread">3.8.1. Start voting thread on <a href="mailto:dev@isis.apache.org">dev@isis.apache.org</a></h4>
+ <h4 id="__cgcom_cutting-a-release_voting-start-voting-thread">3.8.1. Start voting thread on <a href="mailto:dev@isis.apache.org">dev@isis.apache.org</a></h4>
<div class="paragraph">
<p>The following boilerplate is for a release of the Apache Isis Core. Adapt as required:</p>
</div>
@@ -1592,10 +1592,10 @@ gpg --import /tmp/KEYS</code></pre>
<div class="sect2">
<h3 id="_verifying_source_artifacts">4.3. Verifying source artifacts</h3>
<div class="paragraph">
- <p>You can either verify the source artifacts <a href="#_cgcom_verifying-releases_manual-procedure">manuall</a>, or use a script that <a href="#_cgcom_verifying-releases_automated-procedure">automates</a> the steps.</p>
+ <p>You can either verify the source artifacts <a href="#<em>cgcom_verifying-releases_manual-procedure">manuall</a>, or use a script that <a href="#</em>cgcom_verifying-releases_automated-procedure">automates</a> the steps.</p>
</div>
<div class="sect3">
- <h4 id="_cgcom_verifying-releases_manual-procedure">4.3.1. Manual procedure</h4>
+ <h4 id="__cgcom_verifying-releases_manual-procedure">4.3.1. Manual procedure</h4>
<div class="paragraph">
<p>The following section describes the steps to perform to manually verify a release.</p>
</div>
@@ -1683,7 +1683,7 @@ gpg --import /tmp/KEYS</code></pre>
</div>
</div>
<div class="sect3">
- <h4 id="_cgcom_verifying-releases_automated-procedure">4.3.2. Automated procedure</h4>
+ <h4 id="__cgcom_verifying-releases_automated-procedure">4.3.2. Automated procedure</h4>
<div class="paragraph">
<p>To save some time in verifying an Apache Isis release we\u2019ve assembled a script to automate the process. The script is tested on Mac OSX and Linux. Windows users can use Cygwin or <a href="http://msysgit.github.io/">msysgit</a>.</p>
</div>
@@ -1810,7 +1810,7 @@ https://repository.apache.org/content/repositories/orgapacheisis-065/org/apache/
</div>
</div>
<div class="sect2">
- <h3 id="_cgcom_verifying-releases_creadur">4.4. (Optional) Creadur Tools</h3>
+ <h3 id="__cgcom_verifying-releases_creadur">4.4. (Optional) Creadur Tools</h3>
<div class="paragraph">
<p>The <a href="http://creadur.apache.org">Apache Creadur</a> project exists to provide a set of tools to ensure compliance with Apache\u2019s licensing standards.</p>
</div>
@@ -2298,7 +2298,7 @@ git push</code></pre>
</div>
</div>
<div class="sect2">
- <h3 id="_cgcom_post-release-successful_release-non-asf-modules">5.13. Release (non-ASF) Modules</h3>
+ <h3 id="__cgcom_post-release-successful_release-non-asf-modules">5.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>
@@ -2312,7 +2312,7 @@ git push</code></pre>
<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">5.13.1. Prereqs</h4>
+ <h4 id="__cgcom_post-release-successful_release-non-asf-modules_prereqs">5.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>
@@ -2321,7 +2321,7 @@ git push</code></pre>
</div>
</div>
<div class="sect3">
- <h4 id="_cgcom_post-release-successful_release-non-asf-modules_incode-parent">5.13.2. Release <code>incode-parent</code></h4>
+ <h4 id="__cgcom_post-release-successful_release-non-asf-modules_incode-parent">5.13.2. Release <code>incode-parent</code></h4>
<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>
@@ -2356,7 +2356,7 @@ git push</code></pre>
</div>
</div>
<div class="sect3">
- <h4 id="_cgcom_post-release-successful_release-non-asf-modules_incode-mavendeps">5.13.3. Release <code>incode-mavendeps</code></h4>
+ <h4 id="__cgcom_post-release-successful_release-non-asf-modules_incode-mavendeps">5.13.3. Release <code>incode-mavendeps</code></h4>
<div class="paragraph">
<p>The three <code>org.incode:mavendeps-isisXXX</code> module should be released next.</p>
</div>
@@ -2397,7 +2397,7 @@ git push</code></pre>
</div>
</div>
<div class="sect3">
- <h4 id="_cgcom_post-release-successful_release-non-asf-modules_isisaddons">5.13.4. Release Isis Addons</h4>
+ <h4 id="__cgcom_post-release-successful_release-non-asf-modules_isisaddons">5.13.4. Release Isis Addons</h4>
<div class="paragraph">
<p>Once the Apache Isis release is available, all of the (non-ASF) <a href="http://isisaddons.org">Isis Addons</a> should also be released.</p>
</div>
@@ -2456,7 +2456,7 @@ git push</code></pre>
<pre class="CodeRay highlight"><code data-lang="bash">foreach -g isisaddons/isis-[mw] sh release.sh "1.14.0" "1.15.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_post-release-successful_release-non-asf-modules_prereqs">above</a>), use to check that all modules were released successfully:<br></p>
+ <li> <p>In the parent directory where the <code>last_modified.sh</code> script has been saved (see <a href="#__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.14.0</code></pre>
@@ -2485,7 +2485,7 @@ git push</code></pre>
</div>
</div>
<div class="sect3">
- <h4 id="_cgcom_post-release-successful_release-non-asf-modules_incode-catalog">5.13.5. Release Incode Catalog Modules</h4>
+ <h4 id="__cgcom_post-release-successful_release-non-asf-modules_incode-catalog">5.13.5. 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>
@@ -2540,7 +2540,7 @@ git push</code></pre>
<td class="icon"> <i class="fa icon-tip" title="Tip"></i> </td>
<td class="content">
<div class="paragraph">
- <p>See <a href="#_cgcom_post-release-successful_release-non-asf-modules_incode-catalog_cross-module-dependencies">below</a> for a list of the dependencies to update.</p>
+ <p>See <a href="#__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>
@@ -2553,7 +2553,7 @@ git push</code></pre>
<pre class="CodeRay highlight"><code data-lang="bash">foreach -g incodehq/incode-module-[a-w] sh release.sh "1.14.0" "1.15.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_post-release-successful_release-non-asf-modules_prereqs">above</a>), use to check that all modules were released successfully:<br></p>
+ <li> <p>In the parent directory where the <code>last_modified.sh</code> script has been saved (see <a href="#__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.14.0</code></pre>
@@ -2581,7 +2581,7 @@ git push</code></pre>
</ul>
</div>
<div class="sect4">
- <h5 id="_cgcom_post-release-successful_release-non-asf-modules_incode-catalog_cross-module-dependencies">Cross-module dependencies</h5>
+ <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.14.0, the list of dependencies that needed to be updated (across all modules) were:</p>
</div>
@@ -3715,7 +3715,7 @@ gpg --armor --export nnnnnnnn >>KEYS</code></pre>
<div class="sect2">
<h3 id="_configure_toolchains_plugin">11.1. Configure toolchains plugin</h3>
<div class="paragraph">
- <p>Apache Isis releases are built using Java 7, enforced using the maven toolchains plugin. Ensure that Java 7 is installed and the toolchains plugin is configured, as described in the <a href="#_dg_building-isis_configure-maven-toolchains-plugin">contributors' guide</a>.</p>
+ <p>Apache Isis releases are built using Java 7, enforced using the maven toolchains plugin. Ensure that Java 7 is installed and the toolchains plugin is configured, as described in the <a href="#__dg_building-isis_configure-maven-toolchains-plugin">contributors' guide</a>.</p>
</div>
</div>
<div class="sect2">
@@ -4377,35 +4377,35 @@ modify_committee.pl isis --remove joebloggs</code></pre>
</ul> </li>
<li><a href="#_cgcom_cutting-a-release">3. Cutting a Release</a>
<ul class="sectlevel2">
- <li><a href="#_cgcom_cutting-a-release_obtain-consensus">3.1. Obtain Consensus</a></li>
- <li><a href="#_cgcom_cutting-a-release_set-environment-variables">3.2. Set environment variables</a></li>
- <li><a href="#_cgcom_cutting-a-release_pull-down-code-to-release">3.3. Pull down code to release</a></li>
- <li><a href="#_cgcom_cutting-a-release_releasing-core">3.4. Releasing Core</a>
+ <li><a href="#__cgcom_cutting-a-release_obtain-consensus">3.1. Obtain Consensus</a></li>
+ <li><a href="#__cgcom_cutting-a-release_set-environment-variables">3.2. Set environment variables</a></li>
+ <li><a href="#__cgcom_cutting-a-release_pull-down-code-to-release">3.3. Pull down code to release</a></li>
+ <li><a href="#__cgcom_cutting-a-release_releasing-core">3.4. Releasing Core</a>
<ul class="sectlevel3">
- <li><a href="#_cgcom_cutting-a-release_releasing-core_set-environment-variables">3.4.1. Set environment variables</a></li>
- <li><a href="#_cgcom_cutting-a-release_releasing-core_license-headers">3.4.2. License headers</a></li>
- <li><a href="#_cgcom_cutting-a-release_releasing-core_missing-license-check">3.4.3. Missing License Check</a></li>
- <li><a href="#_cgcom_cutting-a-release_releasing-core_commit-changes">3.4.4. Commit changes</a></li>
- <li><a href="#_cgcom_cutting-a-release_releasing-core_sanity-check">3.4.5. Sanity check</a></li>
- <li><a href="#_cgcom_cutting-a-release_releasing-core_release-prepare-dry-run">3.4.6. Release prepare "dry run"</a></li>
- <li><a href="#_cgcom_cutting-a-release_releasing-core_release-prepare-proper">3.4.7. Release prepare "proper"</a></li>
- <li><a href="#_cgcom_cutting-a-release_releasing-core_post-prepare-sanity-check">3.4.8. Post-prepare sanity check</a></li>
- <li><a href="#_cgcom_cutting-a-release_releasing-core_release-perform-upload">3.4.9. Release perform (Upload)</a></li>
+ <li><a href="#__cgcom_cutting-a-release_releasing-core_set-environment-variables">3.4.1. Set environment variables</a></li>
+ <li><a href="#__cgcom_cutting-a-release_releasing-core_license-headers">3.4.2. License headers</a></li>
+ <li><a href="#__cgcom_cutting-a-release_releasing-core_missing-license-check">3.4.3. Missing License Check</a></li>
+ <li><a href="#__cgcom_cutting-a-release_releasing-core_commit-changes">3.4.4. Commit changes</a></li>
+ <li><a href="#__cgcom_cutting-a-release_releasing-core_sanity-check">3.4.5. Sanity check</a></li>
+ <li><a href="#__cgcom_cutting-a-release_releasing-core_release-prepare-dry-run">3.4.6. Release prepare "dry run"</a></li>
+ <li><a href="#__cgcom_cutting-a-release_releasing-core_release-prepare-proper">3.4.7. Release prepare "proper"</a></li>
+ <li><a href="#__cgcom_cutting-a-release_releasing-core_post-prepare-sanity-check">3.4.8. Post-prepare sanity check</a></li>
+ <li><a href="#__cgcom_cutting-a-release_releasing-core_release-perform-upload">3.4.9. Release perform (Upload)</a></li>
</ul> </li>
- <li><a href="#_cgcom_cutting-a-release_releasing-the-archetype">3.5. Releasing the Archetype</a>
+ <li><a href="#__cgcom_cutting-a-release_releasing-the-archetype">3.5. Releasing the Archetype</a>
<ul class="sectlevel3">
- <li><a href="#_cgcom_cutting-a-release_releasing-the-archetype_setup-environment-variables">3.5.1. Setup environment variables</a></li>
- <li><a href="#_cgcom_cutting-a-release_releasing-the-archetype_check-the-example-app">3.5.2. Check the example app</a></li>
- <li><a href="#_cgcom_cutting-a-release_releasing-the-archetype_create-the-archetype">3.5.3. Create the archetype</a></li>
- <li><a href="#_cgcom_cutting-a-release_releasing-the-archetype_release-prepare">3.5.4. Release prepare</a></li>
- <li><a href="#_cgcom_cutting-a-release_releasing-the-archetype_post-prepare-sanity-check">3.5.5. Post-prepare sanity check</a></li>
- <li><a href="#_cgcom_cutting-a-release_releasing-the-archetype_release-perform-upload">3.5.6. Release Perform (upload)</a></li>
+ <li><a href="#__cgcom_cutting-a-release_releasing-the-archetype_setup-environment-variables">3.5.1. Setup environment variables</a></li>
+ <li><a href="#__cgcom_cutting-a-release_releasing-the-archetype_check-the-example-app">3.5.2. Check the example app</a></li>
+ <li><a href="#__cgcom_cutting-a-release_releasing-the-archetype_create-the-archetype">3.5.3. Create the archetype</a></li>
+ <li><a href="#__cgcom_cutting-a-release_releasing-the-archetype_release-prepare">3.5.4. Release prepare</a></li>
+ <li><a href="#__cgcom_cutting-a-release_releasing-the-archetype_post-prepare-sanity-check">3.5.5. Post-prepare sanity check</a></li>
+ <li><a href="#__cgcom_cutting-a-release_releasing-the-archetype_release-perform-upload">3.5.6. Release Perform (upload)</a></li>
</ul> </li>
- <li><a href="#_cgcom_cutting-a-release_check-close-staging-repo">3.6. Check/Close Staging Repo</a></li>
- <li><a href="#_cgcom_cutting-a-release_push-branches">3.7. Push branches</a></li>
- <li><a href="#_cgcom_cutting-a-release_voting">3.8. Voting</a>
+ <li><a href="#__cgcom_cutting-a-release_check-close-staging-repo">3.6. Check/Close Staging Repo</a></li>
+ <li><a href="#__cgcom_cutting-a-release_push-branches">3.7. Push branches</a></li>
+ <li><a href="#__cgcom_cutting-a-release_voting">3.8. Voting</a>
<ul class="sectlevel3">
- <li><a href="#_cgcom_cutting-a-release_voting-start-voting-thread">3.8.1. Start voting thread on </a><a href="mailto:dev@isis.apache.org">dev@isis.apache.org</a></li>
+ <li><a href="#__cgcom_cutting-a-release_voting-start-voting-thread">3.8.1. Start voting thread on </a><a href="mailto:dev@isis.apache.org">dev@isis.apache.org</a></li>
</ul> </li>
</ul> </li>
<li><a href="#_cgcom_verifying-releases">4. Verifying a Release</a>
@@ -4414,20 +4414,20 @@ modify_committee.pl isis --remove joebloggs</code></pre>
<li><a href="#_prerequisites_2">4.2. Prerequisites</a></li>
<li><a href="#_verifying_source_artifacts">4.3. Verifying source artifacts</a>
<ul class="sectlevel3">
- <li><a href="#_cgcom_verifying-releases_manual-procedure">4.3.1. Manual procedure</a>
+ <li><a href="#__cgcom_verifying-releases_manual-procedure">4.3.1. Manual procedure</a>
<ul class="sectlevel4">
<li><a href="#_download_the_artifacts">Download the artifacts</a></li>
<li><a href="#_building_source_artifacts">Building source artifacts</a></li>
<li><a href="#_verifying_binary_artifacts">Verifying binary artifacts</a></li>
</ul> </li>
- <li><a href="#_cgcom_verifying-releases_automated-procedure">4.3.2. Automated procedure</a>
+ <li><a href="#__cgcom_verifying-releases_automated-procedure">4.3.2. Automated procedure</a>
<ul class="sectlevel4">
<li><a href="#_copy_script_to_local_machine">Copy script to local machine</a></li>
<li><a href="#_create_an_input_file">Create an input file</a></li>
<li><a href="#_execute_the_script">Execute the script</a></li>
</ul> </li>
</ul> </li>
- <li><a href="#_cgcom_verifying-releases_creadur">4.4. (Optional) Creadur Tools</a></li>
+ <li><a href="#__cgcom_verifying-releases_creadur">4.4. (Optional) Creadur Tools</a></li>
<li><a href="#_test_the_archetype">4.5. Test the archetype</a></li>
<li><a href="#_casting_a_vote">4.6. Casting a Vote</a></li>
</ul> </li>
@@ -4457,15 +4457,15 @@ modify_committee.pl isis --remove joebloggs</code></pre>
</ul> </li>
<li><a href="#_code_formatting">5.11. Code formatting</a></li>
<li><a href="#_push_changes">5.12. Push changes</a></li>
- <li><a href="#_cgcom_post-release-successful_release-non-asf-modules">5.13. Release (non-ASF) Modules</a>
+ <li><a href="#__cgcom_post-release-successful_release-non-asf-modules">5.13. Release (non-ASF) Modules</a>
<ul class="sectlevel3">
- <li><a href="#_cgcom_post-release-successful_release-non-asf-modules_prereqs">5.13.1. Prereqs</a></li>
- <li><a href="#_cgcom_post-release-successful_release-non-asf-modules_incode-parent">5.13.2. Release <code>incode-parent</code></a></li>
- <li><a href="#_cgcom_post-release-successful_release-non-asf-modules_incode-mavendeps">5.13.3. Release <code>incode-mavendeps</code></a></li>
- <li><a href="#_cgcom_post-release-successful_release-non-asf-modules_isisaddons">5.13.4. Release Isis Addons</a></li>
- <li><a href="#_cgcom_post-release-successful_release-non-asf-modules_incode-catalog">5.13.5. Release Incode Catalog Modules</a>
+ <li><a href="#__cgcom_post-release-successful_release-non-asf-modules_prereqs">5.13.1. Prereqs</a></li>
+ <li><a href="#__cgcom_post-release-successful_release-non-asf-modules_incode-parent">5.13.2. Release <code>incode-parent</code></a></li>
+ <li><a href="#__cgcom_post-release-successful_release-non-asf-modules_incode-mavendeps">5.13.3. Release <code>incode-mavendeps</code></a></li>
+ <li><a href="#__cgcom_post-release-successful_release-non-asf-modules_isisaddons">5.13.4. Release Isis Addons</a></li>
+ <li><a href="#__cgcom_post-release-successful_release-non-asf-modules_incode-catalog">5.13.5. Release Incode Catalog Modules</a>
<ul class="sectlevel4">
- <li><a href="#_cgcom_post-release-successful_release-non-asf-modules_incode-catalog_cross-module-dependencies">Cross-module dependencies</a></li>
+ <li><a href="#__cgcom_post-release-successful_release-non-asf-modules_incode-catalog_cross-module-dependencies">Cross-module dependencies</a></li>
</ul> </li>
</ul> </li>
</ul> </li>