You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@taverna.apache.org by bu...@apache.org on 2015/01/29 11:51:23 UTC
svn commit: r938172 - in /websites/staging/taverna/trunk: cgi-bin/ content/
content/code/index.html
Author: buildbot
Date: Thu Jan 29 10:51:23 2015
New Revision: 938172
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/code/index.html
Propchange: websites/staging/taverna/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Jan 29 10:51:23 2015
@@ -1 +1 @@
-1655583
+1655584
Propchange: websites/staging/taverna/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Jan 29 10:51:23 2015
@@ -1 +1 @@
-1655583
+1655584
Modified: websites/staging/taverna/trunk/content/code/index.html
==============================================================================
--- websites/staging/taverna/trunk/content/code/index.html (original)
+++ websites/staging/taverna/trunk/content/code/index.html Thu Jan 29 10:51:23 2015
@@ -115,41 +115,90 @@
<div id="page" class="container">
<h1>Apache Taverna source code and APIs</h1>
<div id="content"><p>Apache Taverna's source code is hosted at <a href="http://git.apache.org/">git.apache.org</a>, with read-only mirroring to
-<a href="https://github.com/apache/">Github</a>.</p>
-<div class="alert alert-warning" role="alert"><p><strong>Warning:</strong> As of 2014-12-19, the Taverna source code
+<a href="https://github.com/apache/">GitHub</a>.</p>
+<div class="alert alert-warning" role="alert"><p><strong>Warning:</strong> As of 2015-01-29, the Taverna source code
has not yet been migrated to the Apache Incubator infrastructure.</p>
-<p>The current source code is still maintained at the
+<p>The actively maintaned source code is still maintained at the
<a href="https://github.com/taverna/" class="alert-link">taverna GitHub repositories</a>.
-</p></p>
-The links below are to the temporary STAGING repository
-<a href="https://github.com/taverna-incubator" class="alert-link">taverna-incubator</a> at Github. The repositories called <code>incubator-*</code> should build, and are ready to be migrated to git.apache.org. The remaining <code>taverna-*</code> repositories are <strong>drafts</strong> of proposed git restructure and probably <em>won't build</em> correctly..
+For now, the links below are to the temporary <strong>staging repository</strong>
+<a href="https://github.com/taverna-incubator" class="alert-link">taverna-incubator</a> at GitHub.
+</p><p>
+The repositories called <code>incubator-*</code> should build,
+are ready to be migrated to <code>git.apache.org</code>, and use
+groupId and Java package names on the form <code>org.apache.taverna.*</code>
+</p><p>
+The remaining <code>taverna-*</code> repositories are <strong>drafts</strong> of
+the proposed git restructure and probably <em>won't build</em> correctly.
+Unlike the <code>incubator-*</code> repositories, these drafts don't correctly
+preserve git history from pre-Apache.
Note that the structure of the staging repositories might change significantly
before the code has been migrated.
</div>
-<p>The Apache Taverna source code is organized into multiple repositories:</p>
+<h2 id="source-code-repositories">Source code repositories</h2>
+<p>The Apache Taverna source code is organized into multiple <a href="http://www.git-scm.com/">git</a> repositories:</p>
<ul>
<li><a href="https://github.com/taverna-incubator/incubator-taverna-maven-parent">incubator-taverna-maven-parent</a> - Common Maven parent for the below</li>
<li><a href="https://github.com/taverna-incubator/incubator-taverna-language">incubator-taverna-language</a> - Taverna Language APIs for workflow definitions (SCUFL2)
and workflow inputs/outputs/run (DataBundle). </li>
<li><a href="https://github.com/taverna-incubator/incubator-taverna-osgi">incubator-taverna-osgi</a> - Generic OSGi extensions</li>
<li><a href="https://github.com/taverna-incubator/incubator-taverna-engine">incubator-taverna-engine</a> - Taverna workflow engine</li>
-<li><a href="https://github.com/taverna-incubator/taverna-engine-common-activities">taverna-common-activities</a> - Common activity implementation for engine (e.g. WSDL, REST, Tool, Interaction)</li>
+<li><a href="https://github.com/taverna-incubator/incubator-taverna-common-activities">incubator-taverna-common-activities</a> - Common activity implementation for engine (e.g. WSDL, REST, Tool, Interaction)</li>
<li><a href="https://github.com/taverna-incubator/incubator-taverna-commandline">incubator-taverna-commandline</a> - Command line for running Taverna workflows</li>
+<li><a href="https://github.com/taverna-incubator/taverna-server">taverna-server</a> - A REST and WSDL interface for running Taverna workflows</li>
<li><a href="https://github.com/taverna-incubator/taverna-workbench">taverna-workbench</a> - Graphical workbench for editing Taverna workflows</li>
<li><a href="https://github.com/taverna-incubator/taverna-workbench-common-activities">taverna-workbench-common-activities</a> - Common activities UI (discovery+configuration for Workbench</li>
-<li><a href="https://github.com/taverna-incubator/taverna-server">taverna-server</a> - A REST and WSDL interface for running Taverna workflows</li>
+<li><a href="https://github.com/taverna-incubator/taverna-workbench-product">taverna-workbench-product</a> - Distribution of Taverna Workbench</li>
+<li><a href="https://github.com/taverna-incubator/taverna-plugin-component">taverna-plugin-component</a> Component plugin</li>
+<li><a href="https://github.com/taverna-incubator/taverna-plugin-bioinformatics">taverna-plugin-bioinformatics</a></li>
</ul>
-<p>The build order is roughly the order of the above list, but as <a href="#snapshot-builds">snapshots</a> are picked up from the snapshot repository, you do not need to build them all.</p>
-<p>For any questions about the Taverna source code, please subscribe to and contact the
-<a href="http://mail-archives.apache.org/mod_mbox/taverna-dev/">dev@taverna</a> mailing list.</p>
+<h2 id="building-apache-taverna">Building Apache Taverna</h2>
+<p>You need <a href="https://maven.apache.org/download.html">Apache Maven 3.2</a> or newer to build Taverna.
+To build a checked out repository:</p>
+<div class="codehilite"><pre><span class="n">mvn</span> <span class="n">clean</span> <span class="n">install</span>
+</pre></div>
+
+
+<p>If you want to skip tests (these can be time-consuming):</p>
+<div class="codehilite"><pre><span class="n">mvn</span> <span class="n">clean</span> <span class="n">install</span> <span class="o">-</span><span class="n">PskipTests</span>
+</pre></div>
+
+
+<p>If you get license header warnings from the
+<a href="https://creadur.apache.org/rat/apache-rat-plugin/">Apache RAT plugin</a>,
+and you are not a committer (who should fix those :) ),
+you can skip these checks with:</p>
+<div class="codehilite"><pre><span class="n">mvn</span> <span class="n">clean</span> <span class="n">install</span> <span class="o">-</span><span class="n">Drat</span><span class="p">.</span><span class="n">skip</span><span class="p">=</span><span class="n">true</span>
+</pre></div>
+
+
+<p>The build order is roughly the order of the above list, but as regular
+<a href="#snapshot-builds">snapshots</a> are picked up from the snapshot repository,
+usually you only need to build the modules you have changed. </p>
+<p>Note that a repository might depend on a released version of an upstream Taverna
+repository, so if you want to be sure that a build picks up the <code>SNAPSHOT</code> version
+you built instead, check the <code><properties></code> section within the <code>pom.xml</code>.</p>
+<h2 id="contribute-to-apache-taverna">Contribute to Apache Taverna</h2>
+<p><strong>Patches welcome!</strong> Apache Taverna is a volunteer project, and we rely on the community to help
+improve the code base. Anyone can suggest a change to Apache Taverna, not just the existing <a href="/about/">committers</a>.</p>
+<p>For many developers the easiest is to <em>Fork</em> the repository on <em>GitHub</em>, and submit your suggested
+changes as a <em>Pull request</em>. The pull request is automatically forwarded to the
+<a href="http://mail-archives.apache.org/mod_mbox/taverna-dev/">dev@taverna</a> mailing list, which you
+should subscribe to in order to receive feedback for your patch.</p>
+<p>Alternatively you may checkout directly from the repositories above,
+use <a href="https://www.kernel.org/pub/software/scm/git/docs/git-format-patch.html">git format-patch</a>
+and send your patches to the <a href="http://mail-archives.apache.org/mod_mbox/taverna-dev/">dev@taverna</a>
+mailing list after subscribing. Note that large patch files might not be accepted by
+the mailing list software.</p>
+<p>For any questions about using or modifying the Apache Taverna source code and APIs,
+please subscribe to and contact the <a href="http://mail-archives.apache.org/mod_mbox/taverna-dev/">dev@taverna</a> mailing list.</p>
<h2 id="snapshot-builds">Snapshot builds</h2>
<p>A corresponding set of <a href="http://build.mygrid.org.uk/ci/view/incubator-taverna/">automatic Jenkins builds for Apache Taverna</a> deploy to the
-<a href="http://repository.mygrid.org.uk/artifactory/incubator-snapshot-local/">Apache Taverna Maven snapshot repository</a>.
+<a href="http://repository.mygrid.org.uk/artifactory/incubator-snapshot-local/"><del>Apache</del> Taverna Maven snapshot repository</a>.
Note that these builds and repository are currently hosted outside of Apache, but will soon move to Apache.org infrastructure.</p>
<p>This means that as a developer, you only need to build the repositories you are modifying, as the remaining modules will be retrieved from the Maven repository.
-You will however always need to build the product (command line or workbench) to incorporate your changes.</p>
+You will however always need to build the distribution product (command line or workbench) to incorporate your changes. (Make sure that references your <code>SNAPSHOT</code> version!)</p>
<h2 id="taverna-extras">Taverna Extras</h2>
<p>The separate GitHub group <a href="https://github.com/taverna-extras">taverna-extras</a> host independent community-submitted plugins for Apache Taverna.
Unlike Apache Taverna, the taverna-extras include plugins covered by the licenses <a href="https://www.gnu.org/licenses/;gpl.html">LGPL</a> and <a href="https://www.gnu.org/licenses/gpl.html">GPL</a>.
@@ -157,7 +206,6 @@ Note that the taverna-extras are not aff
<p>Some plugins that were previously part of Taverna 2 have or will migrate to taverna-extras due to <a href="http://dev.mygrid.org.uk/wiki/display/developer/Third-party+licenses">licensing incompatibility</a>. This includes:</p>
<ul>
<li>RShell activity</li>
-<li>Beanshell activity</li>
<li><a href="https://github.com/taverna-extras/table-activity">Table activity</a></li>
</ul></div>