Note that as running this build currently fails due to the wsdl OSGi bug
https://issues.apache.org/jira/browse/TAVERNA-883
You can work around this by commenting out these lines from
ApplicationProfile.xml
<bundle
symbolicName="org.apache.taverna.commonactivities.taverna-wsdl-activity"
version="2.1.0.incubating-SNAPSHOT">
<fileName>org.apache.taverna.commonactivities/taverna-wsdl-activity-2.1.0-incubating-SNAPSHOT.jar</fileName>
</bundle>
<bundle
symbolicName="org.apache.taverna.commonactivities.taverna-wsdl-generic"
version="2.1.0.incubating-SNAPSHOT">
<fileName>org.apache.taverna.commonactivities/taverna-wsdl-generic-2.1.0-incubating-SNAPSHOT.jar</fileName>
</bundle>
On 18 January 2016 at 17:24, Stian Soiland-Reyes <[email protected]> wrote:
> Hi,
>
> We already have Jenkins building+deploying on commit (or at least 7
> minutes after) - but all they do is provide nightly snapshots to
> http://repository.apache.org/snapshots
>
> See http://s.apache.org/taverna-builds
>
> (This is what makes it possible for you to check out and work with
> incubator-taverna-common-activities even if it relies on an unreleased
> -SNAPSHOT version of incubator-taverna-engine. )
>
>
> However now that we are moving towards preparing our first Apache
> Taverna command line release, and we still have quite a few
> intra-SNAPSHOT dependencies, I think it's also important to ensure
> that we have a downloadable nightly snapshot build.
>
>
> but I've also added a separate job:
>
> http://s.apache.org/taverna-nightly
>
>
> This builds incubator-taverna-commandline/taverna-commandline-product
> with -Pnightly - so it produces a downloadable
> taverna-command-line-product-3.1.0-incubating-SNAPSHOT-nightly.zip
>
> This should in theory contain all the needed dependencies (see lib/)
> and an executeworkflow.sh / executeworkflow.bat and can run Taverna 3
> workflows.
>
>
>
> We should use these nightly builds for testing the command line as we
> move towards release.
>
> It's important to note that as this does not actually compile any
> code, only assembles the product, it relies on previous builds being
> built successfully (and thus have their SNAPSHOTs deployed to the
> Snapshot Maven repository).
>
>
> NOTE: These nightly builds should not be propagated beyond this list -
> as they are just for our testing and debugging purposes and do not
> constitute an Apache release. For instance, the downloaded ZIP do not
> yet contain a full list of LICENSE/NOTICE entries for all the bundled
> dependency JARs.
>
> The Apache Release rules: http://www.apache.org/dev/release-distribution.html
>
>
> You can see the status of all the Jenkins builds at
> http://s.apache.org/taverna-builds
>
> If you need access to modify the Jenkins build setting, see
> http://wiki.apache.org/general/Jenkins
> ..basically our "PMC chair" must give access - I think our mentors
> would be the able to execute such commands.
>
>
>
> BTW - I am not sure how much of the above we can put on our website
> http://taverna.incubator.apache.org/download/code/#snapshot-builds
> as we should not link normal users to the nightly builds, so I've just
> added it to the command-line README here:
>
> https://github.com/apache/incubator-taverna-commandline/#nightly-builds
>
>
>
> --
> Stian Soiland-Reyes
> Apache Taverna (incubating), Apache Commons RDF (incubating)
> http://orcid.org/0000-0001-9842-9718
--
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons RDF (incubating)
http://orcid.org/0000-0001-9842-9718
