Author: buildbot
Date: Mon Jul 13 14:55:40 2015
New Revision: 958152
Log:
Staging update by buildbot for taverna
Modified:
websites/staging/taverna/trunk/cgi-bin/ (props changed)
websites/staging/taverna/trunk/content/ (props changed)
websites/staging/taverna/trunk/content/about/index.html
websites/staging/taverna/trunk/content/community/edit.html
websites/staging/taverna/trunk/content/community/index.html
websites/staging/taverna/trunk/content/community/irc.html
websites/staging/taverna/trunk/content/community/lists.html
websites/staging/taverna/trunk/content/community/news.html
websites/staging/taverna/trunk/content/community/releasing.html
websites/staging/taverna/trunk/content/doc/edit.html
websites/staging/taverna/trunk/content/doc/index.html
websites/staging/taverna/trunk/content/documentation/404.html
websites/staging/taverna/trunk/content/documentation/api-consumer-tool/index.html
websites/staging/taverna/trunk/content/documentation/command-line-tool/index.html
websites/staging/taverna/trunk/content/documentation/command-line/index.html
websites/staging/taverna/trunk/content/documentation/components/component-profile-editor.html
websites/staging/taverna/trunk/content/documentation/components/component-validator.html
websites/staging/taverna/trunk/content/documentation/components/index.html
websites/staging/taverna/trunk/content/documentation/dataviewer-tool/index.html
websites/staging/taverna/trunk/content/documentation/example-workflows/index.html
websites/staging/taverna/trunk/content/documentation/glossary/index.html
websites/staging/taverna/trunk/content/documentation/index.html
websites/staging/taverna/trunk/content/documentation/interaction/index.html
websites/staging/taverna/trunk/content/documentation/online.html
websites/staging/taverna/trunk/content/documentation/plugins/index.html
websites/staging/taverna/trunk/content/documentation/provenance/index.html
websites/staging/taverna/trunk/content/documentation/quick-start-guide/index.html
websites/staging/taverna/trunk/content/documentation/scufl2/api.html
websites/staging/taverna/trunk/content/documentation/scufl2/bundle.html
websites/staging/taverna/trunk/content/documentation/scufl2/combined.html
websites/staging/taverna/trunk/content/documentation/scufl2/datalink.html
websites/staging/taverna/trunk/content/documentation/scufl2/index.html
websites/staging/taverna/trunk/content/documentation/scufl2/language.html
websites/staging/taverna/trunk/content/documentation/scufl2/ontology.html
websites/staging/taverna/trunk/content/documentation/scufl2/processors.html
websites/staging/taverna/trunk/content/documentation/scufl2/profile.html
websites/staging/taverna/trunk/content/documentation/scufl2/taverna_bundle.html
websites/staging/taverna/trunk/content/documentation/scufl2/uris.html
websites/staging/taverna/trunk/content/documentation/scufl2/workflow.html
websites/staging/taverna/trunk/content/documentation/server/index.html
websites/staging/taverna/trunk/content/documentation/service-sets/index.html
websites/staging/taverna/trunk/content/documentation/taverna-galaxy/index.html
websites/staging/taverna/trunk/content/documentation/taverna-player/index.html
websites/staging/taverna/trunk/content/documentation/training-and-workshops/index.html
websites/staging/taverna/trunk/content/documentation/tutorials/index.html
websites/staging/taverna/trunk/content/documentation/videos/index.html
websites/staging/taverna/trunk/content/documentation/web-service-developers/index.html
websites/staging/taverna/trunk/content/download/code/index.html
websites/staging/taverna/trunk/content/download/code/oldindex.html
websites/staging/taverna/trunk/content/download/command-line-tool/index.html
websites/staging/taverna/trunk/content/download/index.html
websites/staging/taverna/trunk/content/download/maven/index.html
websites/staging/taverna/trunk/content/download/pre-apache.html
websites/staging/taverna/trunk/content/download/scufl2/index.html
websites/staging/taverna/trunk/content/download/server/index.html
websites/staging/taverna/trunk/content/download/system-requirements/index.html
websites/staging/taverna/trunk/content/download/workbench/index.html
websites/staging/taverna/trunk/content/download/workbench/release-notes.html
websites/staging/taverna/trunk/content/error_pages/404.html
websites/staging/taverna/trunk/content/error_pages/a.html
websites/staging/taverna/trunk/content/index.html
websites/staging/taverna/trunk/content/introduction/chemistry-web-services.html
websites/staging/taverna/trunk/content/introduction/how-can-taverna-help-me.html
websites/staging/taverna/trunk/content/introduction/index.html
websites/staging/taverna/trunk/content/introduction/related-projects.html
websites/staging/taverna/trunk/content/introduction/roadmap.html
websites/staging/taverna/trunk/content/introduction/services-in-taverna.html
websites/staging/taverna/trunk/content/introduction/taverna-features.html
websites/staging/taverna/trunk/content/introduction/taverna-in-use/annotation.html
websites/staging/taverna/trunk/content/introduction/taverna-in-use/arts.html
websites/staging/taverna/trunk/content/introduction/taverna-in-use/astronomy.html
websites/staging/taverna/trunk/content/introduction/taverna-in-use/biodiversity.html
websites/staging/taverna/trunk/content/introduction/taverna-in-use/bioinformatics.html
websites/staging/taverna/trunk/content/introduction/taverna-in-use/biology.html
websites/staging/taverna/trunk/content/introduction/taverna-in-use/chemistry.html
websites/staging/taverna/trunk/content/introduction/taverna-in-use/data-and-text-mining.html
websites/staging/taverna/trunk/content/introduction/taverna-in-use/databases.html
websites/staging/taverna/trunk/content/introduction/taverna-in-use/disease-research.html
websites/staging/taverna/trunk/content/introduction/taverna-in-use/document-analysis.html
websites/staging/taverna/trunk/content/introduction/taverna-in-use/education.html
websites/staging/taverna/trunk/content/introduction/taverna-in-use/engineering.html
websites/staging/taverna/trunk/content/introduction/taverna-in-use/genome-and-gene-expression/index.html
websites/staging/taverna/trunk/content/introduction/taverna-in-use/geoinformatics.html
websites/staging/taverna/trunk/content/introduction/taverna-in-use/index.html
websites/staging/taverna/trunk/content/introduction/taverna-in-use/information-quality.html
websites/staging/taverna/trunk/content/introduction/taverna-in-use/medicine.html
websites/staging/taverna/trunk/content/introduction/taverna-in-use/multimedia.html
websites/staging/taverna/trunk/content/introduction/taverna-in-use/natural-language-processing.html
websites/staging/taverna/trunk/content/introduction/taverna-in-use/other.html
websites/staging/taverna/trunk/content/introduction/taverna-in-use/protein-and-proteomics.html
websites/staging/taverna/trunk/content/introduction/taverna-in-use/service-provision.html
websites/staging/taverna/trunk/content/introduction/taverna-in-use/service-testing.html
websites/staging/taverna/trunk/content/introduction/taverna-in-use/social-sciences.html
websites/staging/taverna/trunk/content/introduction/taverna-in-use/systems-biology.html
websites/staging/taverna/trunk/content/introduction/what-is-a-workflow-management-system.html
websites/staging/taverna/trunk/content/introduction/what-is-in-silico-experimentation.html
websites/staging/taverna/trunk/content/introduction/why-use-workflows.html
websites/staging/taverna/trunk/content/introduction/works-with.html
websites/staging/taverna/trunk/content/news/2015-03-04-google-summer-of-code-taverna-projects.html
websites/staging/taverna/trunk/content/news/index.html
websites/staging/taverna/trunk/content/ns/index.html
websites/staging/taverna/trunk/content/scufl2info/README.html
websites/staging/taverna/trunk/content/sitemap.html
websites/staging/taverna/trunk/content/websiteMigration/index.html
websites/staging/taverna/trunk/content/websiteMigration/sitemap.html
websites/staging/taverna/trunk/content/websiteMigration/test.html
Propchange: websites/staging/taverna/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Jul 13 14:55:40 2015
@@ -1 +1 @@
-1690684
+1690689
Propchange: websites/staging/taverna/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Jul 13 14:55:40 2015
@@ -1 +1 @@
-1690684
+1690689
Modified: websites/staging/taverna/trunk/content/about/index.html
==============================================================================
--- websites/staging/taverna/trunk/content/about/index.html (original)
+++ websites/staging/taverna/trunk/content/about/index.html Mon Jul 13 14:55:40
2015
@@ -127,6 +127,7 @@
<li><a href="/community">Community
home</a></li>
<li><a
href="/community#mailinglists">Mailing Lists</a></li>
<li><a
href="/community#contribute">Contribute</a></li>
+ <li><a
href="/community/releasing">Release procedure</a></li>
<li><a
href="/community#reportbugs">Report a Bug</a></li>
<li><a
href="/community/news">News</a></li>
<li><a href="/community/irc">IRC
chat</a></li>
@@ -162,13 +163,24 @@
<div id="page" class="container">
<h1>About Apache Taverna</h1>
- <div id="content"><p>Apache Taverna is a <a
href="http://incubator.apache.org/";>incubator project</a> within the
+ <div id="content"><style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>Apache Taverna is a <a href="http://incubator.apache.org/";>incubator
project</a> within the
<a href="http://www.apache.org/";>The Apache Software Foundation (ASF)</a>.</p>
-<h2 id="incubator-status">Incubator status</h2>
+<h2 id="incubator-status">Incubator status<a class="headerlink"
href="#incubator-status" title="Permanent link">¶</a></h2>
<ul>
<li><a href="http://incubator.apache.org/projects/taverna.html";>Taverna
incubator status</a>.</li>
</ul>
-<h2 id="who-are-we">Who are we?</h2>
+<h2 id="who-are-we">Who are we?<a class="headerlink" href="#who-are-we"
title="Permanent link">¶</a></h2>
<p>The current <a
href="http://people.apache.org/committers-by-project.html#taverna";>Taverna
committers</a> (and
PPMC) are:</p>
<p></style>
Modified: websites/staging/taverna/trunk/content/community/edit.html
==============================================================================
--- websites/staging/taverna/trunk/content/community/edit.html (original)
+++ websites/staging/taverna/trunk/content/community/edit.html Mon Jul 13
14:55:40 2015
@@ -127,6 +127,7 @@
<li><a href="/community">Community
home</a></li>
<li><a
href="/community#mailinglists">Mailing Lists</a></li>
<li><a
href="/community#contribute">Contribute</a></li>
+ <li><a
href="/community/releasing">Release procedure</a></li>
<li><a
href="/community#reportbugs">Report a Bug</a></li>
<li><a
href="/community/news">News</a></li>
<li><a href="/community/irc">IRC
chat</a></li>
@@ -162,14 +163,25 @@
<div id="page" class="container">
<h1>Edit Instructions</h1>
- <div id="content"><p>The Apache Taverna website is maintained as a
community effort.
+ <div id="content"><style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>The Apache Taverna website is maintained as a community effort.
No matter your affiliation to the project, please help us improve the website
by
suggesting edits of any of the pages!</p>
-<h1 id="overview">Overview</h1>
+<h1 id="overview">Overview<a class="headerlink" href="#overview"
title="Permanent link">¶</a></h1>
<p>Apache Taverna's webpages are managed by the <a
href="http://www.apache.org/dev/cmsref.html";>Apache CMS</a> system, and
(if the file extension is <code>.md</code>) written in the <a
href="https://www.apache.org/dev/cmsref.html#markdown";>Markdown format</a>. </p>
<p>The raw pages are stored in the <a
href="http://svn.apache.org/repos/asf/incubator/taverna/site/";>SVN repository
asf/incubator/taverna/site</a>, but should be edited using one of the methods
below:</p>
-<h1 id="github-pull-requests">Github pull requests</h1>
+<h1 id="github-pull-requests">Github pull requests<a class="headerlink"
href="#github-pull-requests" title="Permanent link">¶</a></h1>
<p>The source for the Apache Taverna website is mirrored to the GitHub project
<a
href="https://github.com/apache/incubator-taverna-site/tree/trunk/content";>incubator-taverna-site</a>,
where you can navigate to the source for the page you want to edit. <em>Anyone
with a GitHub account</em>
@@ -185,7 +197,7 @@ an Apache Taverna committer will review
on the Apache Taverna website.
Please sign up to <a
href="http://taverna.incubator.apache.org/community/lists#devtaverna";>dev@taverna</a>
to watch for to any follow-up comments about your changes.</p>
-<h1 id="apache-cms">Apache CMS</h1>
+<h1 id="apache-cms">Apache CMS<a class="headerlink" href="#apache-cms"
title="Permanent link">¶</a></h1>
<p>If you are an Apache Taverna <strong>committer</strong>, then use the
<a href="http://www.apache.org/dev/cmsref.html";>Apache CMS</a> directly from
<a href="https://cms.apache.org/taverna/";>https://cms.apache.org/taverna/</a>
using your <code>@apache.org</code> account as login.</p>
@@ -194,7 +206,7 @@ which you can click from any Apache Tave
<ul>
<li><a
href="javascript:void(location.href='https://cms.apache.org/redirect?uri='+escape(location.href))">Edit
in CMS</a></li>
</ul>
-<h2 id="non-taverna-committers">Non-Taverna committers</h2>
+<h2 id="non-taverna-committers">Non-Taverna committers<a class="headerlink"
href="#non-taverna-committers" title="Permanent link">¶</a></h2>
<p>If you are an existing
<a href="https://people.apache.org/committer-index.html";>Apache committer</a>,
but don't have write access to the pages
@@ -202,7 +214,7 @@ but don't have write access to the pages
an suggested patch to the
<a href="http://taverna.incubator.apache.org/community/lists";>dev@taverna</a>
mailing list,
which you should subscribe to in order to respond to any feedback.</p>
-<h2 id="anonymous-use-of-cms">Anonymous use of CMS</h2>
+<h2 id="anonymous-use-of-cms">Anonymous use of CMS<a class="headerlink"
href="#anonymous-use-of-cms" title="Permanent link">¶</a></h2>
<p>It is possible to log on to the
<a href="http://www.apache.org/dev/cmsref.html#faq";>CMS without an Apache
account</a>,
by using the username <code>anonymous</code> and an empty password.
@@ -212,7 +224,7 @@ involve renames, etc.</p>
<p>Note that in this case your suggested edit will be sent as an suggested
patch to the
<a href="http://taverna.incubator.apache.org/community/lists";>dev@taverna</a>
mailing list,
which you should subscribe to in order to respond to any feedback.</p>
-<h2 id="cms-usage-for-committers">CMS usage for committers</h2>
+<h2 id="cms-usage-for-committers">CMS usage for committers<a
class="headerlink" href="#cms-usage-for-committers" title="Permanent
link">¶</a></h2>
<p>For details, see the <a href="http://www.apache.org/dev/cmsref.html";>Apache
CMS reference</a>.</p>
<p>In short, follow this pattern:</p>
<ul>
@@ -234,7 +246,7 @@ which you should subscribe to in order t
<li>If you are happy, go back and click <code>[Publish]</code> followed by
<code>[Submit]</code>,
otherwise keep editing</li>
</ul>
-<h2 id="editing-tips">Editing tips</h2>
+<h2 id="editing-tips">Editing tips<a class="headerlink" href="#editing-tips"
title="Permanent link">¶</a></h2>
<p>Writing tips:</p>
<ul>
<li>Keep it simple. Use <a
href="https://en.wikipedia.org/wiki/Plain_English";>Plain English</a>.</li>
Modified: websites/staging/taverna/trunk/content/community/index.html
==============================================================================
--- websites/staging/taverna/trunk/content/community/index.html (original)
+++ websites/staging/taverna/trunk/content/community/index.html Mon Jul 13
14:55:40 2015
@@ -127,6 +127,7 @@
<li><a href="/community">Community
home</a></li>
<li><a
href="/community#mailinglists">Mailing Lists</a></li>
<li><a
href="/community#contribute">Contribute</a></li>
+ <li><a
href="/community/releasing">Release procedure</a></li>
<li><a
href="/community#reportbugs">Report a Bug</a></li>
<li><a
href="/community/news">News</a></li>
<li><a href="/community/irc">IRC
chat</a></li>
@@ -162,7 +163,18 @@
<div id="page" class="container">
<h1>About the Community</h1>
- <div id="content"><p>Apache Taverna is a <a
href="http://incubator.apache.org/";>incubator project</a> within the
+ <div id="content"><style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>Apache Taverna is a <a href="http://incubator.apache.org/";>incubator
project</a> within the
<a href="http://www.apache.org/";>The Apache Software Foundation (ASF)</a>.</p>
<p>Taverna is an open source community that's organized by its
<a
href="http://people.apache.org/committers-by-project.html#taverna";>members</a>,
including you!
@@ -171,12 +183,12 @@ Whether you're running or <a href="#cont
<a href="#contribute-code">hacking the core</a>, or just want to <a
href="#contribute-edit">edit</a> these pages
there are opportunities for you to <a href="#contact">get in touch and ask
questions</a>,
<a href="#contribute">contribute</a> or <a href="#reportbugs">report a
bug</a>. </p>
-<h2 id="incubator-status">Incubator status</h2>
+<h2 id="incubator-status">Incubator status<a class="headerlink"
href="#incubator-status" title="Permanent link">¶</a></h2>
<ul>
<li><a href="http://incubator.apache.org/projects/taverna.html";>Taverna
incubator status</a>.</li>
</ul>
<p><a name="mailinglists"></a></p>
-<h2 id="mailing-lists">Mailing Lists</h2>
+<h2 id="mailing-lists">Mailing Lists<a class="headerlink"
href="#mailing-lists" title="Permanent link">¶</a></h2>
<p>You are highly encouraged to participate on the Apache Taverna <a
href="/community/lists">mailing lists</a>:</p>
<table class="table table-condensed">
<tr>
@@ -221,41 +233,41 @@ there are opportunities for you to <a hr
</ul>
<p>Unsubscribing is done in the same way, using the <em>Unsubscribe</em>
address instead.</p>
<p>See the <a href="/community/lists">mailing list</a> page for more
details.</p>
-<h3 id="irc-chat">IRC chat</h3>
+<h3 id="irc-chat">IRC chat<a class="headerlink" href="#irc-chat"
title="Permanent link">¶</a></h3>
<p>Some of the Apache Taverna users and developers occassionally hang out on
the
<a href="/community/irc">IRC channel #taverna</a>. </p>
<p><a name="reportbugs"></a></p>
-<h3 id="report-or-track-a-bug">Report or track a bug</h3>
+<h3 id="report-or-track-a-bug">Report or track a bug<a class="headerlink"
href="#report-or-track-a-bug" title="Permanent link">¶</a></h3>
<p>Taverna's Apache Jira is still being setup.
In the mean time, the best place to report bugs is on the mailing lists.</p>
<p>The previous (non-Apache) Taverna Jira can be found at:
<a
href="http://dev.mygrid.org.uk/issues/browse/T3";>http://dev.mygrid.org.uk/issues/browse/T3</a></p>
-<h2 id="contribute">Contribute</h2>
+<h2 id="contribute">Contribute<a class="headerlink" href="#contribute"
title="Permanent link">¶</a></h2>
<p><a name="contribute-workflow"></a></p>
-<h3 id="contribute-a-workflow">Contribute a workflow</h3>
+<h3 id="contribute-a-workflow">Contribute a workflow<a class="headerlink"
href="#contribute-a-workflow" title="Permanent link">¶</a></h3>
<p>The best place to contribute Taverna workflows is on
<a href="http://www.myexperiment.org";>myExperiment</a>. </p>
<p><a name="contribute-server"></a></p>
-<h3 id="hosting-a-taverna-server">Hosting a Taverna Server</h3>
+<h3 id="hosting-a-taverna-server">Hosting a Taverna Server<a
class="headerlink" href="#hosting-a-taverna-server" title="Permanent
link">¶</a></h3>
<p>For information on hosting a Taverna Server to run Taverna workflows, see
the
<a href="/documentation/server">Server</a> Section.</p>
<p><a name="contribute-host"></a></p>
-<h3 id="hosting-a-service-for-taverna">Hosting a Service for Taverna</h3>
+<h3 id="hosting-a-service-for-taverna">Hosting a Service for Taverna<a
class="headerlink" href="#hosting-a-service-for-taverna" title="Permanent
link">¶</a></h3>
<p>For information on writing web services to be used in Taverna see our
<a href="/documentation/web-service-developers">Web Service Developers</a>
Section.</p>
<p>We recommend that your services are registered in Registries such as:
<a href="http://www.biocatalogue.org";>BioCatalogue</a></p>
<p><a name="contribute-code"></a></p>
-<h3 id="contributing-code">Contributing Code</h3>
+<h3 id="contributing-code">Contributing Code<a class="headerlink"
href="#contributing-code" title="Permanent link">¶</a></h3>
<p>We welcome any contributions for the <a href="/download/code/">source
code</a> of Apache Taverna. See how to
<a href="/download/code/#contribute-to-apache-taverna">contribute code</a>.</p>
<p><a name="contribute-plugin"></a></p>
-<h3 id="contribute-a-plugin">Contribute a plugin</h3>
+<h3 id="contribute-a-plugin">Contribute a plugin<a class="headerlink"
href="#contribute-a-plugin" title="Permanent link">¶</a></h3>
<p>The mechanisms for writing <strong>Apache Taverna 3 plugins</strong> is
still under development.
Please contact the <a href="/community/lists#devtaverna">dev@taverna</a>
mailing list for details.</p>
<p>For <strong>Taverna 2</strong> (non-Apache), see the <a
href="http://dev.mygrid.org.uk/wiki/display/developer/Creating+plugins+for+Taverna+2";>Creating
plugins for Taverna 2</a> tutorial.</p>
<p><a name="contribute-edit"></a></p>
-<h3 id="editing-the-website">Editing the website</h3>
+<h3 id="editing-the-website">Editing the website<a class="headerlink"
href="#editing-the-website" title="Permanent link">¶</a></h3>
<p>This website is always under development.
Please help make it better by <a href="/community/edit">editing</a> or adding
pages.</p></div>
Modified: websites/staging/taverna/trunk/content/community/irc.html
==============================================================================
--- websites/staging/taverna/trunk/content/community/irc.html (original)
+++ websites/staging/taverna/trunk/content/community/irc.html Mon Jul 13
14:55:40 2015
@@ -127,6 +127,7 @@
<li><a href="/community">Community
home</a></li>
<li><a
href="/community#mailinglists">Mailing Lists</a></li>
<li><a
href="/community#contribute">Contribute</a></li>
+ <li><a
href="/community/releasing">Release procedure</a></li>
<li><a
href="/community#reportbugs">Report a Bug</a></li>
<li><a
href="/community/news">News</a></li>
<li><a href="/community/irc">IRC
chat</a></li>
@@ -163,6 +164,17 @@
<div id="page" class="container">
<h1></h1>
<div id="content"><style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<style type="text/css">
<!--
#page {
margin-top: 0;
@@ -184,7 +196,7 @@ iframe {
-->
</style>
-<h1 id="irc-chat-for-apache-taverna">IRC chat for Apache Taverna</h1>
+<h1 id="irc-chat-for-apache-taverna">IRC chat for Apache Taverna<a
class="headerlink" href="#irc-chat-for-apache-taverna" title="Permanent
link">¶</a></h1>
<p>Some of the Apache Taverna developers and users hang out on the IRC chat
channel <a href="irc://irc.freenode.net/%23taverna">#taverna</a> on <a
href="http://freenode.net/";>irc.freenode.net</a>.</p>
<div id="content"><div class="alert alert-info alert-dismissible"
role="alert"><p><span class="glyphicon glyphicon-info-sign"
aria-hidden="true"></span><strong> Note:</strong>
The #taverna IRC channel is <a class="alert-link"
href="http://wilderness.apache.org/channels/#logs-#taverna";>logged publicly</a>.
Modified: websites/staging/taverna/trunk/content/community/lists.html
==============================================================================
--- websites/staging/taverna/trunk/content/community/lists.html (original)
+++ websites/staging/taverna/trunk/content/community/lists.html Mon Jul 13
14:55:40 2015
@@ -127,6 +127,7 @@
<li><a href="/community">Community
home</a></li>
<li><a
href="/community#mailinglists">Mailing Lists</a></li>
<li><a
href="/community#contribute">Contribute</a></li>
+ <li><a
href="/community/releasing">Release procedure</a></li>
<li><a
href="/community#reportbugs">Report a Bug</a></li>
<li><a
href="/community/news">News</a></li>
<li><a href="/community/irc">IRC
chat</a></li>
@@ -162,13 +163,24 @@
<div id="page" class="container">
<h1>Mailing lists</h1>
- <div id="content"><p>You can contact and participate in the Apache
Taverna community through the <strong>mailing lists</strong>.</p>
+ <div id="content"><style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>You can contact and participate in the Apache Taverna community through the
<strong>mailing lists</strong>.</p>
<p>The mailing lists are public. We suggest that all Taverna users join the
<em>users@taverna</em> list
â this allows us to notify you of any critical issues or upcoming changes
and allows you to have
a say in the future development of Taverna. Anyone using the Taverna APIs in
their own code
would be well advised to join both <em>dev@taverna</em> and
<em>users@taverna</em>.</p>
<p><a name="users"></a></p>
-<h3 id="userstaverna">users@taverna</h3>
+<h3 id="userstaverna">users@taverna<a class="headerlink" href="#userstaverna"
title="Permanent link">¶</a></h3>
<p><a class="btn btn-primary"
href="mailto:users-subscr...@taverna.incubator.apache.org";
role="button">Subscribe</a>
<a class="btn btn-default"
href="mailto:users-unsubscr...@taverna.incubator.apache.org";
role="button">Unsubscribe</a>
<a class="btn btn-default"
href="http://mail-archives.apache.org/mod_mbox/incubator-taverna-users/";
role="button">List info</a>
@@ -190,7 +202,7 @@ questions about how to do something in t
</li>
</ul>
<p><a name="dev"></a></p>
-<h3 id="devtaverna">dev@taverna</h3>
+<h3 id="devtaverna">dev@taverna<a class="headerlink" href="#devtaverna"
title="Permanent link">¶</a></h3>
<p><a class="btn btn-primary"
href="mailto:dev-subscr...@taverna.incubator.apache.org";
role="button">Subscribe</a>
<a class="btn btn-default"
href="mailto:dev-unsubscr...@taverna.incubator.apache.org";
role="button">Unsubscribe</a>
<a class="btn btn-default"
href="http://mail-archives.apache.org/mod_mbox/incubator-taverna-dev/";
role="button">List info</a>
@@ -214,7 +226,7 @@ are also welcome here. </p>
</li>
</ul>
<p><a name="commits"></a></p>
-<h3 id="commitstaverna">commits@taverna</h3>
+<h3 id="commitstaverna">commits@taverna<a class="headerlink"
href="#commitstaverna" title="Permanent link">¶</a></h3>
<p><a class="btn btn-primary"
href="mailto:commits-subscr...@taverna.incubator.apache.org";
role="button">Subscribe</a>
<a class="btn btn-default"
href="mailto:commits-unsubscr...@taverna.incubator.apache.org";
role="button">Unsubscribe</a>
<a class="btn btn-default"
href="http://mail-archives.apache.org/mod_mbox/incubator-taverna-dev/";
role="button">List info</a></p>
@@ -229,7 +241,7 @@ This list is high-traffic, from 100 to 1
<li><a
href="http://mail-archives.apache.org/mod_mbox/incubator-taverna-commits/";>List
information and archive for commits@taverna</a></li>
</ul>
<p><a name="private"></a></p>
-<h3 id="privatetaverna">private@taverna</h3>
+<h3 id="privatetaverna">private@taverna<a class="headerlink"
href="#privatetaverna" title="Permanent link">¶</a></h3>
<p><em>priv...@taverna.incubator.apache.org</em> can be used for sensitive
information that should not be made public
in mailing list archives. Only members of the <a href="/about/">Apache Taverna
PPMC</a> will receive the email. Only use this list
if the public lists cannot be used, for instance for business-sensitive
matters, grant proposals and collaborations,
Modified: websites/staging/taverna/trunk/content/community/news.html
==============================================================================
--- websites/staging/taverna/trunk/content/community/news.html (original)
+++ websites/staging/taverna/trunk/content/community/news.html Mon Jul 13
14:55:40 2015
@@ -128,6 +128,7 @@
<li><a href="/community">Community
home</a></li>
<li><a
href="/community#mailinglists">Mailing Lists</a></li>
<li><a
href="/community#contribute">Contribute</a></li>
+ <li><a
href="/community/releasing">Release procedure</a></li>
<li><a
href="/community#reportbugs">Report a Bug</a></li>
<li><a
href="/community/news">News</a></li>
<li><a href="/community/irc">IRC
chat</a></li>
@@ -167,7 +168,18 @@
</div>
<div class="row">
<div class="col-xs-12 col-sm-6 col-md-6 col-lg-6">
- <div id="content"><script type="text/javascript"
src="https://apis.google.com/js/plusone.js";></script>
+ <div id="content"><style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<script type="text/javascript"
src="https://apis.google.com/js/plusone.js";></script>
<div class="g-post"
data-href="https://plus.google.com/114650796366614174823/posts/JgfnJ9qfHor";></div>
Modified: websites/staging/taverna/trunk/content/community/releasing.html
==============================================================================
--- websites/staging/taverna/trunk/content/community/releasing.html (original)
+++ websites/staging/taverna/trunk/content/community/releasing.html Mon Jul 13
14:55:40 2015
@@ -127,6 +127,7 @@
<li><a href="/community">Community
home</a></li>
<li><a
href="/community#mailinglists">Mailing Lists</a></li>
<li><a
href="/community#contribute">Contribute</a></li>
+ <li><a
href="/community/releasing">Release procedure</a></li>
<li><a
href="/community#reportbugs">Report a Bug</a></li>
<li><a
href="/community/news">News</a></li>
<li><a href="/community/irc">IRC
chat</a></li>
@@ -162,7 +163,18 @@
<div id="page" class="container">
<h1>Releasing Apache Taverna</h1>
- <div id="content"><p>Anyone in the <a href="/community/">Apache Taverna
community</a>
+ <div id="content"><style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>Anyone in the <a href="/community/">Apache Taverna community</a>
can propose a release, although usually a release is
prepared by one of the <a href="/about/">committers</a>.
This page describes the procedure for preparing and voting
@@ -172,7 +184,7 @@ over a release.</p>
</blockquote>
<p><strong>Note</strong>: This page is still a <em>draft</em> under
development. See <a
href="https://issues.apache.org/jira/browse/TAVERNA-812";>TAVERNA-812</a>
for tasks required for a release.</p>
-<h2 id="preparations">Preparations</h2>
+<h2 id="preparations">Preparations<a class="headerlink" href="#preparations"
title="Permanent link">¶</a></h2>
<ul>
<li>Email dev@taverna to say a release is imminent. This gives the community a
chance
to finish up anything they want to get into the next release.</li>
@@ -180,7 +192,7 @@ to finish up anything they want to get i
<a
href="https://issues.apache.org/jira/browse/TAVERNA/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel";>components</a>.
If you find any that are blocking or in progress, consult with the dev@taverna
list first.</li>
</ul>
-<h3 id="prepare-your-build-machine">Prepare your build machine</h3>
+<h3 id="prepare-your-build-machine">Prepare your build machine<a
class="headerlink" href="#prepare-your-build-machine" title="Permanent
link">¶</a></h3>
<p>You need to build and release Apache Taverna from a machine you have control
over. Make sure you have a recent version of <code>java</code> and
<code>mvn</code>:</p>
<div class="codehilite"><pre><span class="n">stain</span><span
class="p">@</span><span class="n">biggie</span><span class="o">-</span><span
class="n">utopic</span><span class="p">:</span><span class="o">~/</span><span
class="n">src</span><span class="o">/</span><span class="n">taverna</span>$
<span class="n">java</span> <span class="o">-</span><span
class="n">version</span>
@@ -214,7 +226,7 @@ as the working directory.</p>
</pre></div>
-<h3 id="gpg-keys">GPG keys</h3>
+<h3 id="gpg-keys">GPG keys<a class="headerlink" href="#gpg-keys"
title="Permanent link">¶</a></h3>
<p>You need to have <code>gpg</code> and preferably a <em>GPG Agent</em>
installed on the machine
you will build the release on. This needs to be configured with your
<a href="https://www.apache.org/dev/release-signing.html";>GPG release
key</a>.</p>
@@ -256,7 +268,7 @@ file now includes the correct key finger
</pre></div>
-<h3 id="fresh-checkouts">Fresh checkouts</h3>
+<h3 id="fresh-checkouts">Fresh checkouts<a class="headerlink"
href="#fresh-checkouts" title="Permanent link">¶</a></h3>
<p>Then we'll clone the Taverna git repositories that we are going to release.
Be sure to clone using the <em>Apache Committer</em> URLs, as found on the
<a href="repositories">/download/code/</a> page:</p>
@@ -267,7 +279,7 @@ Be sure to clone using the <em>Apache Co
<p>Note that you do not need to clone the repositories which are already
released and which don't form part of this release.</p>
-<h2 id="git-config">Git config</h2>
+<h2 id="git-config">Git config<a class="headerlink" href="#git-config"
title="Permanent link">¶</a></h2>
<p>Make sure that each new checkout have the correct
user name information and your <code>@apache.org</code> email address:</p>
<div class="codehilite"><pre><span class="n">cd</span> <span
class="n">incubator</span><span class="o">-</span><span
class="n">taverna</span><span class="o">-</span><span
class="n">maven</span><span class="o">-</span><span class="n">parent</span>
@@ -280,7 +292,7 @@ user name information and your <code>@ap
</pre></div>
-<h3 id="verify-build">Verify build</h3>
+<h3 id="verify-build">Verify build<a class="headerlink" href="#verify-build"
title="Permanent link">¶</a></h3>
<p>Now we'll make sure they build normally, <em>pass all the tests</em> and
complete with <code>BUILD SUCCESS</code>:</p>
<div class="codehilite"><pre><span class="n">mvn</span> <span
class="n">clean</span> <span class="n">verify</span>
@@ -288,7 +300,7 @@ complete with <code>BUILD SUCCESS</code>
<p>Note that this would download all the <em>dependencies</em> from Maven
Central.</p>
-<h3 id="maven-repository-access">Maven repository access</h3>
+<h3 id="maven-repository-access">Maven repository access<a class="headerlink"
href="#maven-repository-access" title="Permanent link">¶</a></h3>
<p>When releasing a stable version, Maven will deploy to Apache's
<a href="https://repository.apache.org";>Maven repository</a>, a Nexus instance.
Here, a <em>staging repository</em> will be automatically created.</p>
@@ -328,20 +340,20 @@ deploy the current SNAPSHOT:</p>
<p>This is best tested with a small repository like
<code>taverna-maven-parent</code> as it
will perform a build.</p>
-<h3 id="closing-old-staging-repositories">Closing old staging repositories</h3>
+<h3 id="closing-old-staging-repositories">Closing old staging repositories<a
class="headerlink" href="#closing-old-staging-repositories" title="Permanent
link">¶</a></h3>
<p>Check the list of open
<a href="https://repository.apache.org/#stagingRepositories";>Staging
Repositories</a>
on the Nexus instance, and Close/Drop any old <code>orgapachetaverna-*</code>
repositories.
Do not touch the other repositories from other projects.</p>
-<h2 id="creating-release-candidate">Creating release candidate</h2>
-<h3 id="figure-out-release-order">Figure out release order</h3>
+<h2 id="creating-release-candidate">Creating release candidate<a
class="headerlink" href="#creating-release-candidate" title="Permanent
link">¶</a></h2>
+<h3 id="figure-out-release-order">Figure out release order<a
class="headerlink" href="#figure-out-release-order" title="Permanent
link">¶</a></h3>
<p>If more than one git repository needs to be released,
e.g. because the newer SNAPSHOT version is needed, then those
repositories needs to be released in incremental order. The
dependency order is generally from top to bottom of the list on
the <a href="/download/code">code download page</a>, e.g.
<code>taverna-language</code>
before <code>taverna-engine</code> before <code>taverna-workbench</code>.</p>
-<h3 id="fix-versions">Fix versions</h3>
+<h3 id="fix-versions">Fix versions<a class="headerlink" href="#fix-versions"
title="Permanent link">¶</a></h3>
<p>Edit the top-level <code>pom.xml</code> of each project to release,
ensuring there
are no <code>-SNAPSHOT</code> dependencies in its <code><parent></code>
and
<code><properties></code>.</p>
@@ -372,7 +384,7 @@ that this could change Maven build setti
</pre></div>
-<h3 id="prepare-release-candidate">Prepare release candidate</h3>
+<h3 id="prepare-release-candidate">Prepare release candidate<a
class="headerlink" href="#prepare-release-candidate" title="Permanent
link">¶</a></h3>
<p>We use the
<a href="https://maven.apache.org/maven-release/maven-release-plugin/";>Maven
release plugin</a>
to release candidates as it ensures a consistent release process:</p>
@@ -400,7 +412,7 @@ API backward compatibility)</p>
<p><strong>Note</strong>: Take care to use the correct version number if
preparing a
second release candidate, as Maven could suggest a higher version
number based on the bumped <code>-SNAPSHOT</code> version. </p>
-<h4 id="version-numbers">Version numbers</h4>
+<h4 id="version-numbers">Version numbers<a class="headerlink"
href="#version-numbers" title="Permanent link">¶</a></h4>
<ul>
<li>Has to end in <code>-incubating</code> (while Apache Taverna is
incubating)</li>
<li>taverna-maven-parent is versioned with just major version, e.g.
<code>4-incubating</code></li>
@@ -429,7 +441,7 @@ the REST API of the Taverna Server. </p
<p>Check with dev@taverna if you are not sure. Usually bumping minor
(e.g. from <code>1.5.2</code> to <code>1.6.0</code>) is the right option, as
we release all
modules in the git repository.</p>
-<h4 id="tagging-and-next-snapshot-version">Tagging and next SNAPSHOT
version</h4>
+<h4 id="tagging-and-next-snapshot-version">Tagging and next SNAPSHOT version<a
class="headerlink" href="#tagging-and-next-snapshot-version" title="Permanent
link">¶</a></h4>
<p>For the tag, use the proposed format (<code>0.15.0-incubating-RC1</code>),
but
modify <code>-RC1</code> for any subsequent release candidates.</p>
<div class="codehilite"><pre><span class="n">What</span> <span
class="n">is</span> <span class="n">SCM</span> <span class="n">release</span>
<span class="n">tag</span> <span class="n">or</span> <span
class="n">label</span> <span class="k">for</span> "<span
class="n">Apache</span> <span class="n">Taverna</span> <span
class="n">Language</span> <span class="n">APIs</span> <span
class="p">(</span><span class="n">Scufl2</span><span class="p">,</span> <span
class="n">Databundle</span><span class="p">)</span>"? <span
class="p">(</span><span class="n">org</span><span class="p">.</span><span
class="n">apache</span><span class="p">.</span><span
class="n">taverna</span><span class="p">.</span><span
class="n">language</span><span class="p">:</span><span
class="n">taverna</span><span class="o">-</span><span
class="n">language</span><span class="p">)</span> 0<span
class="p">.</span>15<span class="p">.</span>0<span class="o">-</span><span
class="n">incubating</span><span class="o">-</spa
n><span class="n">RC1</span><span class="p">:</span> <span class="p">:</span>
@@ -456,7 +468,7 @@ or for taverna-maven-parent simply the n
back to Apache's git repository.</p>
<p>If you abort, you can start the process again using <code>mvn
release:prepare</code>,
which will pick up your answers so far from the file
<code>release.profiles</code>.</p>
-<h4 id="rolling-back">Rolling back</h4>
+<h4 id="rolling-back">Rolling back<a class="headerlink" href="#rolling-back"
title="Permanent link">¶</a></h4>
<p>If anything goes wrong at this stage, you will need to undo,
edit and commit required changes, and start again:</p>
<div class="codehilite"><pre><span class="n">mvn</span> <span
class="n">release</span><span class="p">:</span><span class="n">rollback</span>
@@ -466,7 +478,7 @@ edit and commit required changes, and st
</pre></div>
-<h3 id="deploying-the-release-candidate">Deploying the release candidate</h3>
+<h3 id="deploying-the-release-candidate">Deploying the release candidate<a
class="headerlink" href="#deploying-the-release-candidate" title="Permanent
link">¶</a></h3>
<p>If the preparation was successful, then you should now be able to do:</p>
<div class="codehilite"><pre><span class="n">mvn</span> <span
class="n">release</span><span class="p">:</span><span class="n">perform</span>
</pre></div>
@@ -475,7 +487,7 @@ edit and commit required changes, and st
<p>This will check out the tag, build it, then sign and
deploy the packaged source code and compiled JARs
to <code>repository.apache.org</code>.</p>
-<h3 id="locate-the-staging-repository">Locate the staging repository</h3>
+<h3 id="locate-the-staging-repository">Locate the staging repository<a
class="headerlink" href="#locate-the-staging-repository" title="Permanent
link">¶</a></h3>
<p>On Apache's Nexus instance, locate the
<a href="https://repository.apache.org/#stagingRepositories";>Staging
Repository</a>
for the code you just released. It should be called something like
@@ -493,7 +505,7 @@ on both dev@taverna and general@incubato
<a href="https://repository.apache.org/content/repositories";>staging
repository</a>
which should be something like
<code>https://repository.apache.org/content/repositories/orgapachetaverna-1003/</code></p>
-<h3 id="uploading-to-distapacheorg">Uploading to dist.apache.org</h3>
+<h3 id="uploading-to-distapacheorg">Uploading to dist.apache.org<a
class="headerlink" href="#uploading-to-distapacheorg" title="Permanent
link">¶</a></h3>
<p>The release candidate source code, checksums and signatures
should be uploaded to
<a
href="https://dist.apache.org/repos/dist/dev/incubator/taverna/";>dist.apache.org</a>
@@ -562,7 +574,7 @@ candidate, and easier to promote the rel
<p>Now verify that the files are available on
<a
href="https://dist.apache.org/repos/dist/dev/incubator/taverna/";>https://dist.apache.org/repos/dist/dev/incubator/taverna/</a>
-
you might need a <em>Refresh</em> in the browser.</p>
-<h2 id="voting">Voting</h2>
+<h2 id="voting">Voting<a class="headerlink" href="#voting" title="Permanent
link">¶</a></h2>
<p>Any Apache release must be approved through a
<a href="http://www.apache.org/foundation/voting.html";>vote</a>
of the project's PMC. As Apache Taverna is an incubating project, a Taverna
release must be
@@ -582,7 +594,7 @@ a release candidate might be published a
<p>Anyone in the <a href="/community">community</a> can participate in the
review and vote, not just PMC members or committers. Only votes
from IPMC members are <strong>binding</strong>.</p>
-<h3 id="vote-email-to-devtaverna">Vote email to dev@taverna</h3>
+<h3 id="vote-email-to-devtaverna">Vote email to dev@taverna<a
class="headerlink" href="#vote-email-to-devtaverna" title="Permanent
link">¶</a></h3>
<p>To start the release vote, modify the below example and send to dev@taverna.
Remember <code>[VOTE]</code> in the subject line.</p>
<p>Subject: [VOTE] Release Apache Taverna Language 0.15.0-incubating RC2</p>
@@ -629,9 +641,9 @@ majority of at least three +1 Apache Tav
<p>Anyone can participate in testing and voting, not just
committers, please feel free to try out the release candidate
and provide your votes.</p>
-<h3 id="tallying-the-vote">Tallying the vote</h3>
-<h3 id="vote-email-to-generalincubator">Vote email to general@incubator</h3>
-<h2 id="dropping-a-release-candidate">Dropping a release candidate</h2>
+<h3 id="tallying-the-vote">Tallying the vote<a class="headerlink"
href="#tallying-the-vote" title="Permanent link">¶</a></h3>
+<h3 id="vote-email-to-generalincubator">Vote email to general@incubator<a
class="headerlink" href="#vote-email-to-generalincubator" title="Permanent
link">¶</a></h3>
+<h2 id="dropping-a-release-candidate">Dropping a release candidate<a
class="headerlink" href="#dropping-a-release-candidate" title="Permanent
link">¶</a></h2>
<p>If a release candidate is to be dropped, e.g. it fails the <em>[VOTE]</em>,
then:</p>
<p>In Nexus, tick the <a
href="https://repository.apache.org/#stagingRepositories";>staging
repository</a> and <em>Drop</em>.</p>
<p>Delete the old tag:</p>
@@ -649,13 +661,13 @@ and provide your votes.</p>
</pre></div>
-<h2 id="distributing">Distributing</h2>
+<h2 id="distributing">Distributing<a class="headerlink" href="#distributing"
title="Permanent link">¶</a></h2>
<p>Once a <em>[VOTE] [Results]</em> email has been agreed on general@incubator,
then:</p>
<ul>
<li>Promiote the release candidate to a release</li>
</ul>
-<h3 id="moving-to-release-area">Moving to release area</h3>
+<h3 id="moving-to-release-area">Moving to release area<a class="headerlink"
href="#moving-to-release-area" title="Permanent link">¶</a></h3>
<p>Use full URL <code>svn mv</code> to move the accepted release candidate
to the <code>release</code> folder structure on dist.apache.org,
e.g. at
@@ -666,12 +678,12 @@ but remember to remove the <code>-RC1</c
</pre></div>
-<h3 id="update-download-page">Update download page</h3>
+<h3 id="update-download-page">Update download page<a class="headerlink"
href="#update-download-page" title="Permanent link">¶</a></h3>
<p>Wait 24 hours for the download mirrors to pick up the new release from
<code>dist.apache.org</code>.</p>
<p>TODO.</p>
-<h3 id="removing-old-versions">Removing old versions</h3>
+<h3 id="removing-old-versions">Removing old versions<a class="headerlink"
href="#removing-old-versions" title="Permanent link">¶</a></h3>
<p>TODO</p>
-<h3 id="releasing-maven-repository">Releasing Maven repository</h3>
+<h3 id="releasing-maven-repository">Releasing Maven repository<a
class="headerlink" href="#releasing-maven-repository" title="Permanent
link">¶</a></h3>
<p>Tick the correct <a
href="https://repository.apache.org/#stagingRepositories";>staging
repository</a> (perhaps do a quick check of an SHA1 sum against the vote
email), then click <em>Release</em>.
It should then propagate to <a
href="https://repository.apache.org/content/repositories/releases/org/apache/taverna/";>Apache's
release Maven repository</a>
and eventually mirrored to <a
href="http://central.maven.org/maven2/org/apache/taverna/";>Maven
Central</a>.</p></div>
Modified: websites/staging/taverna/trunk/content/doc/edit.html
==============================================================================
--- websites/staging/taverna/trunk/content/doc/edit.html (original)
+++ websites/staging/taverna/trunk/content/doc/edit.html Mon Jul 13 14:55:40
2015
@@ -127,6 +127,7 @@
<li><a href="/community">Community
home</a></li>
<li><a
href="/community#mailinglists">Mailing Lists</a></li>
<li><a
href="/community#contribute">Contribute</a></li>
+ <li><a
href="/community/releasing">Release procedure</a></li>
<li><a
href="/community#reportbugs">Report a Bug</a></li>
<li><a
href="/community/news">News</a></li>
<li><a href="/community/irc">IRC
chat</a></li>
@@ -162,7 +163,18 @@
<div id="page" class="container">
<h1>Edit Instructions</h1>
- <div id="content"><h2 id="booklet">Booklet</h2>
+ <div id="content"><style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="booklet">Booklet<a class="headerlink" href="#booklet" title="Permanent
link">¶</a></h2>
<p><p>The easiest way to edit an Apache website is to use the edit javascript
booklet.</p></p>
<p><a
href="javascript:void(location.href='https://cms.apache.org/redirect?uri='+escape(location.href))">edit
of this page</a></p>
@@ -171,7 +183,7 @@ Add this booklet to you bookmark bar by
Alternatively add a bookmark manually which the location/target of the above
bookmark.
(Not the page you land on when you press the bookmark)</p>
-<h2 id="committing">Committing</h2>
+<h2 id="committing">Committing<a class="headerlink" href="#committing"
title="Permanent link">¶</a></h2>
<p>To be allowed to commit a change you must have an <code>@apache.org</code>
account.
You can log on as <code>anonymous</code> with no password but then your
changes will be emailed to the development list rather than committed.</p></div>
Modified: websites/staging/taverna/trunk/content/doc/index.html
==============================================================================
--- websites/staging/taverna/trunk/content/doc/index.html (original)
+++ websites/staging/taverna/trunk/content/doc/index.html Mon Jul 13 14:55:40
2015
@@ -127,6 +127,7 @@
<li><a href="/community">Community
home</a></li>
<li><a
href="/community#mailinglists">Mailing Lists</a></li>
<li><a
href="/community#contribute">Contribute</a></li>
+ <li><a
href="/community/releasing">Release procedure</a></li>
<li><a
href="/community#reportbugs">Report a Bug</a></li>
<li><a
href="/community/news">News</a></li>
<li><a href="/community/irc">IRC
chat</a></li>
@@ -162,7 +163,18 @@
<div id="page" class="container">
<h1>Documentation for Apache Taverna</h1>
- <div id="content"><div class="alert alert-warning"
role="alert"><strong>Warning:</strong>
+ <div id="content"><style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<div class="alert alert-warning" role="alert"><strong>Warning:</strong>
As of 2014-12-02, the Apache Taverna documentation
has not yet been migrated to the Apache wiki infrastructure. The links below
go to
the non-Apache taverna.org.uk website by University of Manchester.
Modified: websites/staging/taverna/trunk/content/documentation/404.html
==============================================================================
--- websites/staging/taverna/trunk/content/documentation/404.html (original)
+++ websites/staging/taverna/trunk/content/documentation/404.html Mon Jul 13
14:55:40 2015
@@ -128,6 +128,7 @@
<li><a href="/community">Community
home</a></li>
<li><a
href="/community#mailinglists">Mailing Lists</a></li>
<li><a
href="/community#contribute">Contribute</a></li>
+ <li><a
href="/community/releasing">Release procedure</a></li>
<li><a
href="/community#reportbugs">Report a Bug</a></li>
<li><a
href="/community/news">News</a></li>
<li><a href="/community/irc">IRC
chat</a></li>
@@ -171,7 +172,18 @@ Instead it shows <a class="alert-link" h
</div>
- <div id="content"><p>Thank you for your interest in Taverna.</p>
+ <div id="content"><style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>Thank you for your interest in Taverna.</p>
<p>The documentation page is currently under development.</p>
<p>You are seeing this message as the requested page has not yet been copied
from:
<a href="http://www.taverna.org.uk/documentation/taverna-2-x/";>the previous
Taverna website</a></p></div>
Modified:
websites/staging/taverna/trunk/content/documentation/api-consumer-tool/index.html
==============================================================================
---
websites/staging/taverna/trunk/content/documentation/api-consumer-tool/index.html
(original)
+++
websites/staging/taverna/trunk/content/documentation/api-consumer-tool/index.html
Mon Jul 13 14:55:40 2015
@@ -128,6 +128,7 @@
<li><a href="/community">Community
home</a></li>
<li><a
href="/community#mailinglists">Mailing Lists</a></li>
<li><a
href="/community#contribute">Contribute</a></li>
+ <li><a
href="/community/releasing">Release procedure</a></li>
<li><a
href="/community#reportbugs">Report a Bug</a></li>
<li><a
href="/community/news">News</a></li>
<li><a href="/community/irc">IRC
chat</a></li>
@@ -171,14 +172,25 @@ Instead it shows <a class="alert-link" h
</div>
- <div id="content"><p>This page contains information:</p>
+ <div id="content"><style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>This page contains information:</p>
<ul>
<li>for <a href="#api_developers">developers who want to use the API Consumer
Tool</a> to wrap their Java
API for the subsequent use in Taverna workflows, and</li>
<li>for <a href="#api_users">users who want to use the wrapped Java API</a>
inside their workflows.</li>
</ul>
<p><a name="api_developers"></a></p>
-<h2 id="api-consumer-tool">API Consumer Tool</h2>
+<h2 id="api-consumer-tool">API Consumer Tool<a class="headerlink"
href="#api-consumer-tool" title="Permanent link">¶</a></h2>
<p>Current version of the tool is 1.1.
You can get it from the old
<a
href="http://www.taverna.org.uk/download/associated-tools/api-consumer-tool";>download
pages</a>.
@@ -189,11 +201,11 @@ Please also refer to the
This tool is intended for API developers rather than end-users.
It produces an XML API definition file which Taverna imports - this is file
that you distribute
alongside your API to âTaverna enableâ it.</p>
-<h3 id="prerequisites">Prerequisites</h3>
+<h3 id="prerequisites">Prerequisites<a class="headerlink"
href="#prerequisites" title="Permanent link">¶</a></h3>
<p>The API Consumer Tool is a Java Doclet and uses Ant to launch; you must
therefore have Java and
Ant installed and available on the path.
The Tool has been tested on Java 1.6; use other versions at your own risk.</p>
-<h3 id="setup">Setup</h3>
+<h3 id="setup">Setup<a class="headerlink" href="#setup" title="Permanent
link">¶</a></h3>
<p>Before running the API Consumer Tool you need to place source files of your
API within the
âtargetâ directory and any supporting libraries (i.e. dependencies)
required in the
âlibâ directory.
@@ -206,7 +218,7 @@ As Taverna requires full classnames, thi
workflows.
You can normally trap these issues by watching for the standard JavaDoc
warning messages in the
console.</p>
-<h3 id="usage">Usage</h3>
+<h3 id="usage">Usage<a class="headerlink" href="#usage" title="Permanent
link">¶</a></h3>
<p>Once your source and any supporting files are present as described above,
from the API Consumer Tool directory you can either run the
ârunme.batâ/ârunme.sh script or call Ant directly (just type
âantâ on
@@ -225,32 +237,32 @@ Selecting a class from the tree produces
tree - enter a pattern to match and hit return in this text box and the
tree will be
expanded to show all matching nodes.
To return to the view with all nodes expanded clear the text in this box and
hit return.</p>
-<h3 id="adding-methods-to-the-api-definition">Adding methods to the API
definition</h3>
+<h3 id="adding-methods-to-the-api-definition">Adding methods to the API
definition<a class="headerlink" href="#adding-methods-to-the-api-definition"
title="Permanent link">¶</a></h3>
<p>The next step is to select methods to add to the API definition - these
methods
(static, instance or constructors) will appear as services within Taverna
Workbench's
<a href="/documentation/glossary#service_panel">Service Panel</a> when the
definition file is imported.</p>
-<h4 id="using-graphical-interface">Using graphical interface</h4>
+<h4 id="using-graphical-interface">Using graphical interface<a
class="headerlink" href="#using-graphical-interface" title="Permanent
link">¶</a></h4>
<p>Methods can be manually added by choosing the class, opening the
âMethodsâ tab and either
selecting individual methods or using the âSelect allâ and âClear
allâ boxes:</p>
<p><img alt="API Consumer - methods" src="/img/APIConsumer-Methods.png" /></p>
-<h4 id="using-javadoc-tags">Using JavaDoc tags</h4>
+<h4 id="using-javadoc-tags">Using JavaDoc tags<a class="headerlink"
href="#using-javadoc-tags" title="Permanent link">¶</a></h4>
<p>For APIs under your direct control there is an alternative based on JavaDoc
tags.
By adding the tag â@taverna.consumeâ to either classes or individual
methods you can
automatically have these methods selected in the API consumer when it first
scans the source
files.
In the case of the tag at a class or interface level all constructors and
methods will be
selected.</p>
-<h3 id="api-level-metadata">API level metadata</h3>
+<h3 id="api-level-metadata">API level metadata<a class="headerlink"
href="#api-level-metadata" title="Permanent link">¶</a></h3>
<p>To aid use of your exported API you can select the âAPI Descriptionâ
tab and use it to provide
a name and description for the entire API subset:</p>
<p><img alt="API Consumer - description"
src="/img/APIConsumer-Description.png" /></p>
-<h3 id="saving-the-api-definition-file">Saving the API definition file</h3>
+<h3 id="saving-the-api-definition-file">Saving the API definition file<a
class="headerlink" href="#saving-the-api-definition-file" title="Permanent
link">¶</a></h3>
<p>To save the API definition select the &âFileâ -> âSave as
XMLâ.
This should bring up a standard save dialogue, choose a filename and save.
This is the file that is then imported into Taverna Workbench's Service Panel
by selecting
âImport new servicesâ -> âAPI Consumer servicesâ¦â.</p>
<p><a name="api_users"></a></p>
-<h2 id="using-api-consumer-services-in-workflows">Using API Consumer Services
in Workflows</h2>
+<h2 id="using-api-consumer-services-in-workflows">Using API Consumer Services
in Workflows<a class="headerlink"
href="#using-api-consumer-services-in-workflows" title="Permanent
link">¶</a></h2>
<p>Please also refer to
<a
href="http://www.mygrid.org.uk/dev/wiki/display/taverna/API+Consumer";>the API
Consumer section of the User Manual</a>.</p>
<p>In order to use the API Consumer services in Taverna workflows, you need
the XML API Consumer
@@ -309,7 +321,7 @@ services in the User Manual. In particul
System classloader sharing for all your services and modify the
Taverna startup scripts.</p>
</blockquote>
-<h3 id="a-word-of-advice">A word of advice</h3>
+<h3 id="a-word-of-advice">A word of advice<a class="headerlink"
href="#a-word-of-advice" title="Permanent link">¶</a></h3>
<p>Depending on the complexity of your API, building workflows in this way can
turn out to be
very a cumbersome way to do graphical Java programming in a workflow.
In many cases, writing a <a
href="/documentation/glossary#beanshell">Beanshell</a> script using the same
Modified:
websites/staging/taverna/trunk/content/documentation/command-line-tool/index.html
==============================================================================
---
websites/staging/taverna/trunk/content/documentation/command-line-tool/index.html
(original)
+++
websites/staging/taverna/trunk/content/documentation/command-line-tool/index.html
Mon Jul 13 14:55:40 2015
@@ -128,6 +128,7 @@
<li><a href="/community">Community
home</a></li>
<li><a
href="/community#mailinglists">Mailing Lists</a></li>
<li><a
href="/community#contribute">Contribute</a></li>
+ <li><a
href="/community/releasing">Release procedure</a></li>
<li><a
href="/community#reportbugs">Report a Bug</a></li>
<li><a
href="/community/news">News</a></li>
<li><a href="/community/irc">IRC
chat</a></li>
@@ -171,14 +172,25 @@ Instead it shows <a class="alert-link" h
</div>
- <div id="content"><p>Taverna 2 Command Line Tool is a script
that runs Taverna 2.x workflows from a terminal.
+ <div id="content"><style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>Taverna 2 Command Line Tool is a script that runs Taverna 2.x workflows
from a terminal.
It comes in a form of a command line script <em>executeworkflow</em>
(<em>executeworkflow.bat</em> on
Windows and <em>executeworkflow.sh</em> on Linux/UNIX).</p>
-<h2 id="latest-none-apache-release">Latest None Apache Release</h2>
+<h2 id="latest-none-apache-release">Latest None Apache Release<a
class="headerlink" href="#latest-none-apache-release" title="Permanent
link">¶</a></h2>
<ul>
<li>Documentation for the <a
href="http://dev.mygrid.org.uk/wiki/display/taverna/Command+Line+Tool";>Taverna
Command Line Tool 2.5</a></li>
</ul>
-<h2 id="previous-releases">Previous Releases</h2>
+<h2 id="previous-releases">Previous Releases<a class="headerlink"
href="#previous-releases" title="Permanent link">¶</a></h2>
<ul>
<li>Documentation for the <a
href="http://dev.mygrid.org.uk/wiki/display/taverna24/Command+Line+Tool";>Taverna
Command Line Tool 2.4</a></li>
<li>Documentation for the <a
href="http://dev.mygrid.org.uk/wiki/display/taverna23/Command+Line+Tool";>Taverna
Command Line Tool 2.3</a></li>
Modified:
websites/staging/taverna/trunk/content/documentation/command-line/index.html
==============================================================================
---
websites/staging/taverna/trunk/content/documentation/command-line/index.html
(original)
+++
websites/staging/taverna/trunk/content/documentation/command-line/index.html
Mon Jul 13 14:55:40 2015
@@ -128,6 +128,7 @@
<li><a href="/community">Community
home</a></li>
<li><a
href="/community#mailinglists">Mailing Lists</a></li>
<li><a
href="/community#contribute">Contribute</a></li>
+ <li><a
href="/community/releasing">Release procedure</a></li>
<li><a
href="/community#reportbugs">Report a Bug</a></li>
<li><a
href="/community/news">News</a></li>
<li><a href="/community/irc">IRC
chat</a></li>
@@ -171,7 +172,18 @@ Instead it shows <a class="alert-link" h
</div>
- <div id="content"><p>Command Line Tool is a script that runs
Taverna workflows from a terminal.
+ <div id="content"><style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>Command Line Tool is a script that runs Taverna workflows from a terminal.
It comes in a form of a command line script called <em>executeworkflow</em>
(<em>executeworkflow.bat</em> on Windows and <em>executeworkflow.sh</em> on
Linux/UNIX).</p>
<p>You can <a href="/download/command-line-tool">download the Command Line
Tool</a> from the Taverna Web site
@@ -180,7 +192,7 @@ It comes in a form of a command line scr
<ul>
<li><a
href="http://dev.mygrid.org.uk/wiki/display/tav250/Extended+version";>Extended
version</a></li>
</ul>
-<h2
id="what-is-the-difference-between-the-bundled-and-standalone-executeworkflow"><img
alt="" src="/img/information.png" />What is the difference between the bundled
and standalone executeworkflow?</h2>
+<h2
id="what-is-the-difference-between-the-bundled-and-standalone-executeworkflow"><img
alt="" src="/img/information.png" />What is the difference between the bundled
and standalone executeworkflow?<a class="headerlink"
href="#what-is-the-difference-between-the-bundled-and-standalone-executeworkflow"
title="Permanent link">¶</a></h2>
<ul>
<li>
<p>The standalone command line tool has a <strong>separate
configuration</strong>
@@ -234,7 +246,7 @@ It comes in a form of a command line scr
</li>
</ul>
<p><a name="CommandLineTool-ExecuteworkflowScript"></a></p>
-<h2 id="executeworkflow-script">Executeworkflow Script</h2>
+<h2 id="executeworkflow-script">Executeworkflow Script<a class="headerlink"
href="#executeworkflow-script" title="Permanent link">¶</a></h2>
<p>To get help and a full set of options for the executeworkflow script type
the following in the
command prompt:</p>
<blockquote>
@@ -347,7 +359,7 @@ However, if you provide an input of lowe
wrapped in one or more lists up to the required depth.
Providing an input of greater depth than that required will result in an
error. </p>
<p><a name"CommandLineTool-Runningthescriptwithdatabase"></a></p>
-<h3 id="running-the-script-with-database">Running the script with database</h3>
+<h3 id="running-the-script-with-database">Running the script with database<a
class="headerlink" href="#running-the-script-with-database" title="Permanent
link">¶</a></h3>
<p>If a workflow has a high memory requirement, then it may be better to run
it using a database
to store data rather than storing it in memory, which is the default
option.
There are three options for using a database: </p>
@@ -412,7 +424,7 @@ port=<port>
options, the other options take precedence.</p>
</blockquote>
<p><a name=CommandLineTool-Examples"></a></p>
-<h2 id="examples">Examples</h2>
+<h2 id="examples">Examples<a class="headerlink" href="#examples"
title="Permanent link">¶</a></h2>
<p>Some examples on how the script can be invoked are shown below. </p>
<blockquote>
<p>$ sh executeworkflow.sh "/Users/alex/Taverna
Modified:
websites/staging/taverna/trunk/content/documentation/components/component-profile-editor.html
==============================================================================
---
websites/staging/taverna/trunk/content/documentation/components/component-profile-editor.html
(original)
+++
websites/staging/taverna/trunk/content/documentation/components/component-profile-editor.html
Mon Jul 13 14:55:40 2015
@@ -128,6 +128,7 @@
<li><a href="/community">Community
home</a></li>
<li><a
href="/community#mailinglists">Mailing Lists</a></li>
<li><a
href="/community#contribute">Contribute</a></li>
+ <li><a
href="/community/releasing">Release procedure</a></li>
<li><a
href="/community#reportbugs">Report a Bug</a></li>
<li><a
href="/community/news">News</a></li>
<li><a href="/community/irc">IRC
chat</a></li>
@@ -171,7 +172,18 @@ Instead it shows <a class="alert-link" h
</div>
- <div id="content"><p>The Taverna Component Profile Editor is a
simple tool for editing and creating profiles for
+ <div id="content"><style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>The Taverna Component Profile Editor is a simple tool for editing and
creating profiles for
[Taverna Components[(/documentation/components).
Component profiles define the required and supported interface of components;
they are not intended to be easily edited by normal users.
Modified:
websites/staging/taverna/trunk/content/documentation/components/component-validator.html
==============================================================================
---
websites/staging/taverna/trunk/content/documentation/components/component-validator.html
(original)
+++
websites/staging/taverna/trunk/content/documentation/components/component-validator.html
Mon Jul 13 14:55:40 2015
@@ -128,6 +128,7 @@
<li><a href="/community">Community
home</a></li>
<li><a
href="/community#mailinglists">Mailing Lists</a></li>
<li><a
href="/community#contribute">Contribute</a></li>
+ <li><a
href="/community/releasing">Release procedure</a></li>
<li><a
href="/community#reportbugs">Report a Bug</a></li>
<li><a
href="/community/news">News</a></li>
<li><a href="/community/irc">IRC
chat</a></li>
@@ -171,7 +172,18 @@ Instead it shows <a class="alert-link" h
</div>
- <div id="content"><p>The Taverna Component Validator is a tool
and library for checking whether a
+ <div id="content"><style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>The Taverna Component Validator is a tool and library for checking whether
a
<a href="/documentation/components">Taverna Component</a> satisfies the
component profile defined by the family of which it is a member.
It applies a number of checks to the component such that when they are all
satisfied,
the component can be considered to be a high-quality member of the
component family,
Modified:
websites/staging/taverna/trunk/content/documentation/components/index.html
==============================================================================
--- websites/staging/taverna/trunk/content/documentation/components/index.html
(original)
+++ websites/staging/taverna/trunk/content/documentation/components/index.html
Mon Jul 13 14:55:40 2015
@@ -128,6 +128,7 @@
<li><a href="/community">Community
home</a></li>
<li><a
href="/community#mailinglists">Mailing Lists</a></li>
<li><a
href="/community#contribute">Contribute</a></li>
+ <li><a
href="/community/releasing">Release procedure</a></li>
<li><a
href="/community#reportbugs">Report a Bug</a></li>
<li><a
href="/community/news">News</a></li>
<li><a href="/community/irc">IRC
chat</a></li>
@@ -171,7 +172,18 @@ Instead it shows <a class="alert-link" h
</div>
- <div id="content"><p>Taverna Workflow Components are a system
for creating shareable, reusable,
+ <div id="content"><style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>Taverna Workflow Components are a system for creating shareable, reusable,
encapsulated sub-workflows that perform clearly defined tasks while
abstracting away from
the details of how those tasks are performed.
They are an integrated feature of Taverna Since Workbench 2.5.0 and Server
2.5.4.</p>
@@ -198,13 +210,13 @@ Workflow components within a given compo
</ul>
<p><img class="aligncenter" title="The Model of Components"
src="/img/registry.png" alt=""
width="433" height="251" /></p>
-<h2 id="example">Example</h2>
+<h2 id="example">Example<a class="headerlink" href="#example" title="Permanent
link">¶</a></h2>
<p>This is an example workflow that includes components, with internal ports
hidden for simplicity:</p>
<p><img class="alignnone" title="Componentized Workflow"
src="/img/component_b_1.png" alt=""
width="679" height="294" /></p>
<p>Without components, using the same view, it would instead look like
this:</p>
<p><a
href="http://www.taverna.org.uk/pages/wp-content/uploads/2013/05/component_c.png";><img
class="aligncenter" title="Un-componentized Workflow"
src="/img/component_c.png" alt="" width="245" height="526" /></a></p>
-<h2 id="including-a-component-in-a-workflow">Including a component in a
workflow</h2>
+<h2 id="including-a-component-in-a-workflow">Including a component in a
workflow<a class="headerlink" href="#including-a-component-in-a-workflow"
title="Permanent link">¶</a></h2>
<p>A component can be added into a Taverna workflow in the same way as an
ordinary service,
by dragging it from the service panel of the workbench into the workflow
design view.
Note that although it may be realized internally as a workflow,
@@ -213,7 +225,7 @@ Workflow components within a given compo
<p>It is intended that there will be consistency checks to ensure that
components are only plugged
together in a sensible manner, and for the discovery of and connection to
suitable components
based upon existing workflow structure.</p>
-<h2 id="executing-a-component-in-a-workflow-run">Executing a component in a
workflow run</h2>
+<h2 id="executing-a-component-in-a-workflow-run">Executing a component in a
workflow run<a class="headerlink"
href="#executing-a-component-in-a-workflow-run" title="Permanent
link">¶</a></h2>
<p>When a component is invoked during a workflow run, the underlying workflow
is called with the
corresponding data.
The results of the workflow are used as the output data for the component
invocation.
@@ -222,13 +234,13 @@ Note that the user sees the component in
<p>Note that if you publish a workflow containing a component, you
<em>need</em> to make sure that the
component is publicly readable in a globally-accessible component registry;
myExperiment is such a suitable registry.</p>
-<h2 id="component-creation">Component creation</h2>
+<h2 id="component-creation">Component creation<a class="headerlink"
href="#component-creation" title="Permanent link">¶</a></h2>
<p>It was decided that the majority of the information necessary for a
component will be specified
as a Taverna workflow.
This allows complex internal component functionality and removes the need for
extensive new
software to design components.</p>
<p><img class="aligncenter" src="/img/arch1.png" alt="" width="340"
height="433" /></p>
-<h2 id="component-profile">Component profile</h2>
+<h2 id="component-profile">Component profile<a class="headerlink"
href="#component-profile" title="Permanent link">¶</a></h2>
<p>A specification of the format for the component profile has been agreed.
The format is in XML and an XML schema (xsd) has been created.
An example <a
href="http://www.myexperiment.org/files/905/versions/1/download/Characterisation%20Component.xml";>component
profile</a>
@@ -243,7 +255,7 @@ A <a href="/documentation/components/com
<p>The SCAPE project has an
<a href="https://github.com/openpreserve/scape-component-profiles";>extended
discussion of component profiles</a>
available.</p>
-<h2 id="component-creation-against-a-profile">Component creation against a
profile</h2>
+<h2 id="component-creation-against-a-profile">Component creation against a
profile<a class="headerlink" href="#component-creation-against-a-profile"
title="Permanent link">¶</a></h2>
<p>In order to conform to a component profile, it can be necessary to make
semantic annotations
parts of the corresponding workflow.
For example, the annotation of the type of format in which data is output by a
port or
@@ -251,7 +263,7 @@ For example, the annotation of the type
<p>The component profile specifies the ontologies that will be used for the
components within the
family, the correspondence between object classes within a workflow
(input port, service etc.) and the concepts within the ontologies.</p>
-<h2 id="checking-a-component-against-a-profile">Checking a component against a
profile</h2>
+<h2 id="checking-a-component-against-a-profile">Checking a component against a
profile<a class="headerlink" href="#checking-a-component-against-a-profile"
title="Permanent link">¶</a></h2>
<p>Although the components will be modified using a chosen profile,
it is unlikely that the components can be assured as being âcorrect by
constructionâ.
For this reason, a separate
@@ -259,7 +271,7 @@ For this reason, a separate
is being implemented.
The component validator is included within
<a href="http://www.myexperiment.org";>myExperiment</a>.</p>
-<h2 id="publishing-a-component">Publishing a component</h2>
+<h2 id="publishing-a-component">Publishing a component<a class="headerlink"
href="#publishing-a-component" title="Permanent link">¶</a></h2>
<p>Since components are realized as âextensionsâ to Taverna workflows,
it was decided that rather than using a separate component repository,
the extensive capabilities of myExperiment would be used.
@@ -270,7 +282,7 @@ The components themselves are items with
machine.</p>
<p>When a user publishes a component either to myExperiment or to their local
file system,
their service panel is updated to reflect the new component.</p>
-<h2 id="discovering-a-component">Discovering a component</h2>
+<h2 id="discovering-a-component">Discovering a component<a class="headerlink"
href="#discovering-a-component" title="Permanent link">¶</a></h2>
<p>Since component families are realized as packs on myExperiment
(or by analogous structures in the userâs file system),
we use the existing Taverna code to talk to the myExperiment REST interface
to give users
Modified:
websites/staging/taverna/trunk/content/documentation/dataviewer-tool/index.html
==============================================================================
---
websites/staging/taverna/trunk/content/documentation/dataviewer-tool/index.html
(original)
+++
websites/staging/taverna/trunk/content/documentation/dataviewer-tool/index.html
Mon Jul 13 14:55:40 2015
@@ -128,6 +128,7 @@
<li><a href="/community">Community
home</a></li>
<li><a
href="/community#mailinglists">Mailing Lists</a></li>
<li><a
href="/community#contribute">Contribute</a></li>
+ <li><a
href="/community/releasing">Release procedure</a></li>
<li><a
href="/community#reportbugs">Report a Bug</a></li>
<li><a
href="/community/news">News</a></li>
<li><a href="/community/irc">IRC
chat</a></li>
@@ -171,7 +172,18 @@ Instead it shows <a class="alert-link" h
</div>
- <div id="content"><p>DataViewer Tool is a utility for viewing
Baclava data files.
+ <div id="content"><style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>DataViewer Tool is a utility for viewing Baclava data files.
Baclava is an XML format used to save workflow inputs and/or outputs from the
<a href="/documentation">Workbench</a> or <a
href="/documentation/command-line-tool">Command Line Tool</a> for later
re-use or inspection.
@@ -185,7 +197,7 @@ The functionality of the tool remained (
Check out the a
<a
href="http://www.taverna.org.uk/download/associated-tools/dataviewer-tool/release-notes/";>release
notes</a>
for the minor changes in the latest version.</p>
-<h2 id="creating-baclava-files">Creating Baclava files</h2>
+<h2 id="creating-baclava-files">Creating Baclava files<a class="headerlink"
href="#creating-baclava-files" title="Permanent link">¶</a></h2>
<p>From the Workbench, you can save the inputs you have specified for a
workflow to a Baclava file
from the <em>Run Dialog</em> (which is used to launch a workflow).
From the same dialog you can also load inputs from a previously saved Baclava
file so you do
Modified:
websites/staging/taverna/trunk/content/documentation/example-workflows/index.html
==============================================================================
---
websites/staging/taverna/trunk/content/documentation/example-workflows/index.html
(original)
+++
websites/staging/taverna/trunk/content/documentation/example-workflows/index.html
Mon Jul 13 14:55:40 2015
@@ -128,6 +128,7 @@
<li><a href="/community">Community
home</a></li>
<li><a
href="/community#mailinglists">Mailing Lists</a></li>
<li><a
href="/community#contribute">Contribute</a></li>
+ <li><a
href="/community/releasing">Release procedure</a></li>
<li><a
href="/community#reportbugs">Report a Bug</a></li>
<li><a
href="/community/news">News</a></li>
<li><a href="/community/irc">IRC
chat</a></li>
@@ -171,7 +172,18 @@ Instead it shows <a class="alert-link" h
</div>
- <div id="content"><p>Example workflows to get you started with
Taverna are available from the
+ <div id="content"><style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>Example workflows to get you started with Taverna are available from the
<em>myExperiment Perspective</em> in the Taverna Workbench, by selecting
the âStarter Packâ tab.</p>
<p>They can also be downloaded from <a
href="http://myexperiment.org/";>myExperiment</a>.
Additional workflows from other users can be found by browsing
myExperiment.</p>
Modified:
websites/staging/taverna/trunk/content/documentation/glossary/index.html
==============================================================================
Binary files - no diff available.
![http://www.taverna.org.uk/pages/wp-content/uploads/2013/05/component_c.png"](http://www.taverna.org.uk/pages/wp-content/uploads/2013/05/component_c.png"){kind=link}