Author: buildbot
Date: Tue Feb 24 07:42:41 2015
New Revision: 941277
Log:
Staging update by buildbot for isis
Modified:
websites/staging/isis/trunk/cgi-bin/ (props changed)
websites/staging/isis/trunk/content/ (props changed)
websites/staging/isis/trunk/content/contributors/release-process.html
websites/staging/isis/trunk/content/core/release-notes/about.html
websites/staging/isis/trunk/content/core/release-notes/isis-1.8.0.html
websites/staging/isis/trunk/content/documentation.html
websites/staging/isis/trunk/content/download.html
websites/staging/isis/trunk/content/intro/getting-started/simpleapp-archetype.html
Propchange: websites/staging/isis/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Feb 24 07:42:41 2015
@@ -1 +1 @@
-1661851
+1661859
Propchange: websites/staging/isis/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Feb 24 07:42:41 2015
@@ -1 +1 @@
-1661851
+1661859
Modified: websites/staging/isis/trunk/content/contributors/release-process.html
==============================================================================
--- websites/staging/isis/trunk/content/contributors/release-process.html
(original)
+++ websites/staging/isis/trunk/content/contributors/release-process.html Tue
Feb 24 07:42:41 2015
@@ -539,10 +539,10 @@ git pull --ff-only
<p>Then, determine/confirm the version number of the module being released.
This should be in line with our <a href="versioning-policy.html">semantic
versioning policy</a>.</p>
-<p>Next, create a release branch in your local Git repo, using the version
number determined and as per <a href="release-branch-and-tag-names.html">these
standards</a>. For example, to prepare release candidate #1 for a release
1.8.0 of <code>core</code>, use:</p>
+<p>Next, create a release branch in your local Git repo, using the version
number determined and as per <a href="release-branch-and-tag-names.html">these
standards</a>. For example, to prepare release candidate #1 for a release
1.9.0 of <code>core</code>, use:</p>
<pre>
-git checkout -b isis-1.8.0
+git checkout -b isis-1.9.0
</pre>
<p>All release preparation is done locally; if we are successful, this branch
will be pushed back to master.</p>
@@ -557,8 +557,8 @@ git checkout -b isis-1.8.0
export ISISTMP=/c/tmp # or whatever
export ISISART=isis
-export ISISDEV=1.9.0-SNAPSHOT
-export ISISREL=1.8.0
+export ISISDEV=1.10.0-SNAPSHOT
+export ISISREL=1.9.0
export ISISRC=RC1
export ISISCOR="Y"
@@ -577,11 +577,11 @@ Unless otherwise stated, you should assu
<p>The version number of the parent pom should reflect the branch name that
you are now on (with a <code>-SNAPSHOT</code> suffix). In many cases this will
have been done already during earlier development; but confirm that it has been
updated. If it has not, make the change.</p>
-<p>For example, if releasing <code>core</code> version <code>1.8.0</code>, the
POM should read:</p>
+<p>For example, if releasing <code>core</code> version <code>1.9.0</code>, the
POM should read:</p>
<pre><code><groupId>org.apache.isis.core</groupId>
<artifactId>isis</artifactId>
-<version>1.8.0</version>
+<version>1.9.0</version>
</code></pre>
<h3>Update parent (Isis Core)</h3>
@@ -611,7 +611,7 @@ If releasing a non-core component, then
-ca53c7f51d1fede5a199251838b12622
+4443a8bc23230ed0fd62744b1a102ac1
@@ -870,13 +870,13 @@ $ mvn release:prepare -P apache-release
[INFO] Isis Core Integration Testing Support
[INFO]
[INFO] ------------------------------------------------------------------------
-[INFO] Building Apache Isis Core 1.8.0
+[INFO] Building Apache Isis Core 1.9.0
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-release-plugin:2.3.2:prepare (default-cli) @ isis ---
[INFO] Resuming release from phase 'map-release-versions'
What is the release version for "Apache Isis Core"? (org.apache.isis.core:isis)
-1.8.0: :
+1.9.0: :
</pre>
<p>If you didn't provide the <code>releaseVersion</code>, <code>tag</code> and
<code>developmentVersion</code> tags, then you'll be prompted for them. You
can generally accept the defaults that Maven offers.</p>
@@ -895,12 +895,12 @@ What is the release version for "Apache
<h3>Post-prepare sanity check</h3>
-<p>You should end up with artifacts in your local repo with the new version
<code>1.8.0</code>. There are then a couple of sanity checks that you can
perform:</p>
+<p>You should end up with artifacts in your local repo with the new version
<code>1.9.0</code>. There are then a couple of sanity checks that you can
perform:</p>
<ul>
<li>unzip the source-release ZIP and check it builds</p>
-<p>For example, if building core, then the ZIP file will be called
<code>isis-1.8.0-source-release.zip</code> and should reside in
<code>~/.m2/repository/org/apache/isis/core/isis/1.8.0</code> directory.</p>
+<p>For example, if building core, then the ZIP file will be called
<code>isis-1.9.0-source-release.zip</code> and should reside in
<code>~/.m2/repository/org/apache/isis/core/isis/1.9.0</code> directory.</p>
<p>Unzip in a new directory, and build.</li>
<li>Inspect the <code>DEPENDENCIES</code> file.</p>
@@ -941,17 +941,17 @@ What is the release version for "Apache
[INFO] Performing a LOCAL checkout from
scm:git:file:///C:\APACHE\isis-git-rw\co
re
[INFO] Checking out the project to perform the release ...
-[INFO] Executing: cmd.exe /X /C "git clone --branch isis-1.8.0
file:///C:\APACHE\isis-git-rw\core C:\APACHE\isis-git-rw\core\target\checkout"
+[INFO] Executing: cmd.exe /X /C "git clone --branch isis-1.9.0
file:///C:\APACHE\isis-git-rw\core C:\APACHE\isis-git-rw\core\target\checkout"
[INFO] Working directory: C:\APACHE\isis-git-rw\core\target
[INFO] Performing a LOCAL checkout from scm:git:file:///C:\APACHE\isis-git-rw
[INFO] Checking out the project to perform the release ...
-[INFO] Executing: cmd.exe /X /C "git clone --branch isis-1.8.0
file:///C:\APACHE\isis-git-rw C:\APACHE\isis-git-rw\core\target\checkout"
+[INFO] Executing: cmd.exe /X /C "git clone --branch isis-1.9.0
file:///C:\APACHE\isis-git-rw C:\APACHE\isis-git-rw\core\target\checkout"
[INFO] Working directory: C:\APACHE\isis-git-rw\core\target
[INFO] Executing: cmd.exe /X /C "git ls-remote file:///C:\APACHE\isis-git-rw"
[INFO] Working directory: C:\Users\ADMINI~1\AppData\Local\Temp
[INFO] Executing: cmd.exe /X /C "git fetch file:///C:\APACHE\isis-git-rw"
[INFO] Working directory: C:\APACHE\isis-git-rw\core\target\checkout
-[INFO] Executing: cmd.exe /X /C "git checkout isis-1.8.0"
+[INFO] Executing: cmd.exe /X /C "git checkout isis-1.9.0"
[INFO] Working directory: C:\APACHE\isis-git-rw\core\target\checkout
[INFO] Executing: cmd.exe /X /C "git ls-files"
[INFO] Working directory: C:\APACHE\isis-git-rw\core\target\checkout
@@ -1049,8 +1049,8 @@ I've cut a release for Apache Isis Core
The source code artifacts have been uploaded to staging repositories on
repository.apache.org:
-*
http://repository.apache.org/content/repositories/orgapacheisis-10xx/org/apache/isis/core/isis/1.8.0/isis-1.8.0-source-release.zip
-*
http://repository.apache.org/content/repositories/orgapacheisis-10xx/org/apache/isis/archetype/simpleapp-archetype/1.8.0/simpleapp-archetype-1.8.0-source-release.zip
+*
http://repository.apache.org/content/repositories/orgapacheisis-10xx/org/apache/isis/core/isis/1.9.0/isis-1.9.0-source-release.zip
+*
http://repository.apache.org/content/repositories/orgapacheisis-10xx/org/apache/isis/archetype/simpleapp-archetype/1.9.0/simpleapp-archetype-1.9.0-source-release.zip
For each zip there is a corresponding signature file (append .asc to the zip's
url).
@@ -1068,7 +1068,7 @@ Please verify the release and cast your
<p>Remember to update:</p>
<ul>
-<li>the version number (1.8.0 or whatever)</li>
+<li>the version number (1.9.0 or whatever)</li>
<li>the release candidate number (<code>RC1</code> or whatever)</li>
<li>the repository id, as provided by Nexus earlier
(<code>orgapacheisis-10xx</code> or whatever)</li>
</ul>
@@ -1082,7 +1082,7 @@ Please verify the release and cast your
<p>For example, use the following subject for a vote on Isis Core:</p>
<pre>
-[RESULT] [VOTE] Apache Isis Core release 1.8.0
+[RESULT] [VOTE] Apache Isis Core release 1.9.0
</pre>
<p>using the body (alter last line as appropriate):</p>
@@ -1105,7 +1105,7 @@ The vote is (UN)SUCCESSFUL.
<p>You can do this using the <code>scripts/promoterctag.sh</code> script; for
example:</p>
-<pre><code>sh scripts/promoterctag isis-1.8.0 RC1 # $ISISART-$SISREL $ISISRC
+<pre><code>sh scripts/promoterctag isis-1.9.0 RC1 # $ISISART-$SISREL $ISISRC
</code></pre>
<p>Or, if you like to execute the steps in that script by hand:</p>
@@ -1115,7 +1115,7 @@ The vote is (UN)SUCCESSFUL.
</ul>
<pre>
- git push origin refs/tags/isis-1.8.0:refs/tags/isis-1.8.0
+ git push origin refs/tags/isis-1.9.0:refs/tags/isis-1.9.0
git fetch
</pre>
@@ -1124,7 +1124,7 @@ The vote is (UN)SUCCESSFUL.
</ul>
<pre>
- git push origin --delete refs/tags/isis-1.8.0-RC1 #
$ISISART-$SISREL-$ISISRC
+ git push origin --delete refs/tags/isis-1.9.0-RC1 #
$ISISART-$SISREL-$ISISRC
git fetch
</pre>
@@ -1133,7 +1133,7 @@ The vote is (UN)SUCCESSFUL.
</ul>
<pre>
- git tag -d isis-1.8.0-RC1 # $ISISART-$SISREL-$ISISRC
+ git tag -d isis-1.9.0-RC1 # $ISISART-$SISREL-$ISISRC
git fetch
</pre>
@@ -1148,7 +1148,7 @@ The vote is (UN)SUCCESSFUL.
</ul>
<pre>
- git push origin --delete isis-1.8.0 # $ISISART-$SISREL
+ git push origin --delete isis-1.9.0 # $ISISART-$SISREL
</pre>
<ul>
@@ -1156,7 +1156,7 @@ The vote is (UN)SUCCESSFUL.
</ul>
<pre>
- git branch -D isis-1.8.0 # $ISISART-$SISREL
+ git branch -D isis-1.9.0 # $ISISART-$SISREL
</pre>
<ul>
@@ -1164,7 +1164,7 @@ The vote is (UN)SUCCESSFUL.
</ul>
<pre>
- git push origin --delete refs/tags/isis-1.8.0-RC1
+ git push origin --delete refs/tags/isis-1.9.0-RC1
</pre>
<ul>
@@ -1172,7 +1172,7 @@ The vote is (UN)SUCCESSFUL.
</ul>
<pre>
- git tag -d isis-1.8.0 # $ISISART-$SISREL
+ git tag -d isis-1.9.0 # $ISISART-$SISREL
</pre>
<ul>
@@ -1250,10 +1250,10 @@ isis/
<p>Typically this be will a new page in the core section or for one of the
components. Make a note of the URL of this new page (for use in the mailing
list announcement).</p>
-<p>For example, a new release of Isis Core would have a release notes page
<code>http://isis.apache.org/core/release-notes-1.8.0.html</code></li>
+<p>For example, a new release of Isis Core would have a release notes page
<code>http://isis.apache.org/core/release-notes-1.9.0.html</code></li>
<li>Do a search for <code>x.y.0-SNAPSHOT</code> and replace with
<code>x.y.0</code></li>
<li>Update the version number on the <a
href="../intro/getting-started/simple-archetype.html">simpleapp</a> archetype
pages.</li>
-<li>For core (if released) and for each released component's about page,
update the link to the latest release notes providing details of the contents
of the release.</li>
+<li>For core and (if any) for each released component's about page, update the
link to the latest release notes providing details of the contents of the
release.</li>
<li>Update the version listed on the <a
href="../documentation.html">documentation page</a>.</li>
</ul>
@@ -1272,16 +1272,6 @@ no longer required (since everything bun
<li>The <code>STATUS</code> file (in root of Isis' source) should be updated
with details of the new release.</li>
</ul>
-<!--
-
-
-1974efeb3c28e0c118cbc388807db0fe
-
-
-
-TODO: some sort of process required here...
--->
-
<h2>Announce the release</h2>
<p>Announce the release to [email protected] mailing list.</p>
@@ -1289,37 +1279,34 @@ TODO: some sort of process required here
<p>For example, for a release of Apache Isis Core, use the following
subject:</p>
<pre>
-[ANN] Apache Isis version 1.8.0 Released
+[ANN] Apache Isis version 1.9.0 Released
</pre>
<p>And use the following body (summarizing the main points as required):</p>
<pre>
The Isis team is pleased to announce the release of:
-* Apache Isis Core version 1.8.0
-* SimpleApp Archetype 1.8.0
-
-Note that as of 1.8.0 the Wicket Viewer is bundled in with Core.
+* Apache Isis Core version 1.9.0
+* SimpleApp Archetype 1.9.0
New features in this release include:
- ...
-Full release notes are available at [1,2] on the Isis website.
+Full release notes are available on the Isis website at [1].
Note that:
* ...
-You can access this release directly from the Maven central repo [3],
-or download the release and build it from source [4].
+You can access this release directly from the Maven central repo [2],
+or download the release and build it from source [3].
Enjoy!
--The Isis team
-[1] http://isis.apache.org/core/release-notes/isis-1.x.0.html
-[2]
http://isis.apache.org/archetypes/release-notes/simpleapp-archetype-1.x.0.html
-[3] http://search.maven.org
-[4] http://isis.apache.org/download.html
+[1] http://isis.apache.org/core/release-notes/isis-1.9.0.html
+[2] http://search.maven.org
+[3] http://isis.apache.org/download.html
</pre>
<h3>Blog post</h3>
@@ -1334,9 +1321,9 @@ Enjoy!
<pre><code>git checkout master # update master with latest
git pull
-git merge isis-1.8.0 # merge branch onto master
-git branch -d isis-1.8.0 # branch no longer needed
-git push origin --delete isis-1.8.0 # remote branch no longer needed
+git merge isis-1.9.0 # merge branch onto master
+git branch -d isis-1.9.0 # branch no longer needed
+git push origin --delete isis-1.9.0 # remote branch no longer needed
</code></pre>
<p>If the core was updated, then you'll most likely need to update other POMs
to the new <code>-SNAPSHOT</code>.</p>
Modified: websites/staging/isis/trunk/content/core/release-notes/about.html
==============================================================================
--- websites/staging/isis/trunk/content/core/release-notes/about.html (original)
+++ websites/staging/isis/trunk/content/core/release-notes/about.html Tue Feb
24 07:42:41 2015
@@ -422,6 +422,8 @@
</h1>
</div>
+<p>Note that Core incorporates the Wicket viewer, the Restful Objects viewer,
Shiro Security and the JDO/DataNucleus ObjectStore. In earlier releases each
of these were released as separate components.</p>
+
<ul>
<li><a href="isis-1.8.0.html">isis-1.8.0</a> (<a
href="migrating-to-1.8.0.html">migrating from 1.7.0 to 1.8.0</a>)</li>
<li><a href="isis-1.7.0.html">isis-1.7.0</a> (<a
href="migrating-to-1.7.0.html">migrating from 1.6.0 to 1.7.0</a>)</li>
@@ -434,6 +436,12 @@
<li><a href="isis-1.0.0.html">isis-1.0.0</a></li>
</ul>
+<p>See also release notes for previous releases of:
+* <a href="../../components/viewers/wicket/release-notes/about.html">Wicket
Viewer</a>
+* <a
href="../../components/viewers/restfulobjects/release-notes/about.html">Restful
Objects Viewer</a>
+* <a href="../../components/security/shiro/release-notes/about.html">Shiro
Security</a>
+* <a
href="../../components/objectstores/jdo/release-notes/about.html">JDO/DataNucleus
ObjectStore</a></p>
+
</div>
Modified: websites/staging/isis/trunk/content/core/release-notes/isis-1.8.0.html
==============================================================================
--- websites/staging/isis/trunk/content/core/release-notes/isis-1.8.0.html
(original)
+++ websites/staging/isis/trunk/content/core/release-notes/isis-1.8.0.html Tue
Feb 24 07:42:41 2015
@@ -3,7 +3,7 @@
<head>
<meta charset="utf-8">
- <title></title>
+ <title>isis-1.8.0
</title>
<meta name="description" content="">
<meta name="author" content="">
@@ -298,7 +298,7 @@
};
function twshare () {
window.open(
-
"https://twitter.com/intent/tweet?url="+document.URL+"&text=";,
+
"https://twitter.com/intent/tweet?url="+document.URL+"&text=isis-1.8.0
",
'Share on Twitter',
'width=800,height=526');
};
@@ -417,13 +417,11 @@
<div class="page-header">
<p><a href="./../../documentation.html">Docs</a> » <a
href="./../../core/about.html">Core</a> » <a
href="./../../core/release-notes/about.html">Release Notes</a></p>
-<h1>
+<h1>isis-1.8.0
</h1>
</div>
-<p>Release Notes - Isis - Version core-1.8.0</p>
-
<p>Note that Isis 1.8.0 now incorporates the Wicket viewer, which was
previously a separately released component. Other components that are included
in core (that were previously released separately are: the Restful Objects
viewer, Shiro Security and the JDO/DataNucleus ObjectStore.</p>
<h2> New Feature
Modified: websites/staging/isis/trunk/content/documentation.html
==============================================================================
--- websites/staging/isis/trunk/content/documentation.html (original)
+++ websites/staging/isis/trunk/content/documentation.html Tue Feb 24 07:42:41
2015
@@ -442,8 +442,15 @@
<h4><a name="getting-started">Archetypes and Apps</a></h4>
<ul>
-<li><strong><a href="intro/getting-started/simpleapp-archetype.html">SimpleApp
Archetype</a> (<a
href="archetypes/release-notes/about.html">1.7.0</a>)</strong></li>
-<li><a href="http://github.com/isisaddons/isis-app-todoapp";>TodoApp Example
App</a> (not ASF)
+<li><em>*<a href="intro/getting-started/simpleapp-archetype.html">SimpleApp
Archetype</a> *</em></li>
+<li><a href="http://github.com/isisaddons/isis-app-todoapp";>TodoApp Example
App</a> (not ASF)</li>
+</ul>
+
+<h4><a name="release-notes">Release notes</a></h4>
+
+<ul>
+<li><a href="core/release-notes/about.html">Core v1.8.0</a></li>
+<li><a href="archetypes/release-notes/about.html">Simpleapp v1.8.0</a>
</div>
<div class="col-md-4"></li>
</ul>
@@ -490,7 +497,7 @@
</div>
<div class="row">
<div class="col-md-12">
-<h2><a name="core">Core Concepts <a
href="core/release-notes/about.html">1.7.0</a></a></h2></li>
+<h2><a name="core">Core Concepts</a></h2></li>
</ul>
<p></div>
@@ -900,7 +907,7 @@
<p><div class="row">
<div class="col-md-12"></p>
-<h2><a name="wicket-viewer">Wicket Viewer</a> <a
href="components/viewers/wicket/release-notes/about.html">1.7.0</a> <a
href="components/viewers/wicket/about.html">About</a></h2>
+<h2><a name="wicket-viewer">Wicket Viewer</a> <a
href="components/viewers/wicket/about.html">About</a></h2>
<p>Features, configuration and UI customisation.
</div>
Modified: websites/staging/isis/trunk/content/download.html
==============================================================================
--- websites/staging/isis/trunk/content/download.html (original)
+++ websites/staging/isis/trunk/content/download.html Tue Feb 24 07:42:41 2015
@@ -434,7 +434,7 @@
mvn archetype:generate \
-D archetypeGroupId=org.apache.isis.archetype \
-D archetypeArtifactId=simpleapp-archetype \
- -D archetypeVersion=1.7.0 \
+ -D archetypeVersion=1.8.0 \
-D groupId=com.mycompany \
-D artifactId=myapp \
-D version=1.0-SNAPSHOT \
@@ -450,25 +450,20 @@ mvn archetype:generate \
<p>Core:</p>
<ul>
-<li><a
href="https://www.apache.org/dyn/closer.cgi/isis/isis-core/isis-1.7.0-source-release.zip";>isis-1.7.0</a>
(<a
href="http://www.apache.org/dist/isis/isis-core/isis-1.7.0-source-release.zip.asc";>asc</a>,
<a
href="http://www.apache.org/dist/isis/isis-core/isis-1.7.0-source-release.zip.md5";>md5</a>)
</li>
+<li><a
href="https://www.apache.org/dyn/closer.cgi/isis/isis-core/isis-1.8.0-source-release.zip";>isis-1.8.0</a>
(<a
href="http://www.apache.org/dist/isis/isis-core/isis-1.8.0-source-release.zip.asc";>asc</a>,
<a
href="http://www.apache.org/dist/isis/isis-core/isis-1.8.0-source-release.zip.md5";>md5</a>)
</li>
</ul>
-<p>nb: In v1.6.0, core incorporates JDO/DataNucleus ObjectStore, Restful
Objects viewer and Shiro Security (previously released as separate components).
In v1.7.0, modules released (in <code>org.apache.isis.module</code> have been
moved to be [http://www.isisaddons.org](Isis add-ons) (not ASF).</p>
-
-<p>Components:</p>
-
-<ul>
-<li><a
href="https://www.apache.org/dyn/closer.cgi/isis/component/viewer/wicket/isis-viewer-wicket-1.7.0-source-release.zip";>isis-viewer-wicket-1.7.0</a>
(<a
href="http://www.apache.org/dist/isis/component/viewer/wicket/isis-viewer-wicket-1.7.0-source-release.zip.asc";>asc</a>,
<a
href="http://www.apache.org/dist/isis/component/viewer/wicket/isis-viewer-wicket-1.7.0-source-release.zip.md5";>md5</a>)</li>
-</ul>
+<p>Notes:
+* in v1.6.0, core incorporates JDO/DataNucleus ObjectStore, Restful Objects
viewer and Shiro Security (previously released as separate components).
+* in v1.7.0, modules released (in <code>org.apache.isis.module</code> have
been moved to be [http://www.isisaddons.org](Isis add-ons) (not ASF).
+* in v1.8.0, core incorporates Wicket viewer (previously released as separate
components).</p>
<p>Archetypes:</p>
<ul>
-<li><a
href="https://www.apache.org/dyn/closer.cgi/isis/archetype/simpleapp-archetype/simpleapp-archetype-1.7.0-source-release.zip";>simpleapp-archetype-1.7.0</a>
(<a
href="http://www.apache.org/dist/isis/archetype/simpleapp-archetype/simpleapp-archetype-1.7.0-source-release.zip.asc";>asc</a>,
<a
href="http://www.apache.org/dist/isis/archetype/simpleapp-archetype/simpleapp-archetype-1.7.0-source-release.zip.md5";>md5</a>)</li>
+<li><a
href="https://www.apache.org/dyn/closer.cgi/isis/archetype/simpleapp-archetype/simpleapp-archetype-1.8.0-source-release.zip";>simpleapp-archetype-1.8.0</a>
(<a
href="http://www.apache.org/dist/isis/archetype/simpleapp-archetype/simpleapp-archetype-1.8.0-source-release.zip.asc";>asc</a>,
<a
href="http://www.apache.org/dist/isis/archetype/simpleapp-archetype/simpleapp-archetype-1.8.0-source-release.zip.md5";>md5</a>)</li>
</ul>
-<p>See the <a href="release-matrix.html">release matrix</a> for details on the
dependencies between core, components and archetypes.</p>
-
<h2>Verifying Releases</h2>
<p>It is essential that you verify the integrity of any downloaded files using
@@ -482,21 +477,21 @@ why we do it, check out the
<pre>
pgpk -a KEYS
-pgpv isis-1.7.0-source-release.zip.asc
+pgpv isis-1.8.0-source-release.zip.asc
</pre>
<p>or</p>
<pre>
pgp -ka KEYS
-pgp isis-1.7.0-source-release.zip.asc
+pgp isis-1.8.0-source-release.zip.asc
</pre>
<p>or</p>
<pre>
gpg --import KEYS
-gpg --verify isis-1.7.0-source-release.zip.asc
+gpg --verify isis-1.8.0-source-release.zip.asc
</pre>
<p>Alternatively, you can verify the MD5 signature on the files. A Unix/Linux
Modified:
websites/staging/isis/trunk/content/intro/getting-started/simpleapp-archetype.html
==============================================================================
---
websites/staging/isis/trunk/content/intro/getting-started/simpleapp-archetype.html
(original)
+++
websites/staging/isis/trunk/content/intro/getting-started/simpleapp-archetype.html
Tue Feb 24 07:42:41 2015
@@ -529,7 +529,7 @@ mvn jetty:run -D jetty.port=9090
<p>Finally, you can also run the app by deploying to a standalone servlet
container such as <a href="http://tomcat.apache.org";>Tomcat</a>.</p>
-<h2>Running the App with Fixtures (1.7.0)</h2>
+<h2>Running the App with Fixtures</h2>
<p>It is also possible to start the application with a pre-defined set of
data; useful for demos or manual exploratory
testing. This is done by specifying a <em>fixture script</em> on the command
line:</p>
