Thanks for updating!  I think this could be helpful - specially as it
will help the GSOC students in participating.


I think #10 is still relevant - sorry for the confusion about "binary
distro" - we will still do the binaries distributed to Maven Central
(e.g. populating http://central.maven.org/maven2/org/apache/taverna/)
- otherwise we will struggle later to do the Taverna Server or
Workbench release.  Perhaps we shall call this "Maven artifacts"?


But we won't yet make a binary release ZIP to upload to
https://dist.apache.org/repos/dist/dev/incubator/taverna/binaries/ (we
haven't done any so yet),  as that means we have to reflect the
LICENSE and NOTICE of the bundled JARs.

That is - while the old Taverna Command Line 2.5 could be downloaded
as a thing you could just run - even with installers for different
operating systems - see
https://taverna.incubator.apache.org/download/command-line-tool/

Now we won't do those for this very first Apache Taverna command line
3.1.0.  Early adopters would have to compile the taverna-command-line
- which is rather fast as (unless you have already compiled them
locally) it would still get the binary JARs from Maven Central for
taverna-language, taverna-osgi, taverna-engine and
taverna-common-activities.


Note that the build actually DO make a binary Command Line
distribution ZIP as part of the Maven artifacts - see for instance
https://repository.apache.org/content/repositories/snapshots/org/apache/taverna/commandline/taverna-commandline-product/3.1.0-incubating-SNAPSHOT/taverna-commandline-product-3.1.0-incubating-20160506.180359-36-nightly.zip
.. this is retrieved by taverna-server

(although it seems some paths are not quite what it expects due to  it
being SNAPSHOT - see
https://builds.apache.org/user/stain/my-views/view/taverna/job/incubator-taverna-server/136/console
>
Error: Unable to access jarfile
/home/jenkins/jenkins-slave/workspace/incubator-taverna-server/taverna-server-webapp/target/TavernaServer.3.1.0-incubating-SNAPSHOT/WEB-INF/classes/util/taverna-command-line-3.1.0-incubating-SNAPSHOT/lib/taverna-command-line-0.1.1.jar

Looking in the ZIP I think this should be
lib/org.apache.taverna.commandline.taverna-commandline-api-3.1.0-incubating-SNAPSHOT.jar

I'll make a new Jira issue for this - it has something to do with
https://github.com/apache/incubator-taverna-server/blob/master/taverna-server-webapp/src/main/replacementscripts/executeworkflow.sh

which I'm not sure we need anymore - or perhaps we need to fix
whatever it adds into the Command Line executeworkflow.sh? Donal?


On 6 May 2016 at 19:31, Gale Naylor <[email protected]> wrote:
> In preparation for the release, I cleaned up the "How to Review a Release"
> wiki.(
> https://cwiki.apache.org/confluence/display/TAVERNADEV/2016-03+Apache+Taverna%3A+How+to+Review+a+Release+and+Vote
> ).
>
> I'm wondering what changes in a source-only release. For example, is #10
> ignored?
>
> Right now, the items to check are:
>
> 1) checksums and PGP signatures
> 2) commit ID
> 3) disclaimer and incubator- file names
> 4) top-level license and notice
> 5) source files have license headers
> 6) clear provenance (I'm still not sure how to check this, other than
> what's part of #4 and #5)
> 7) dependency licenses
> 8) no compiled binaries in release
> 9) successful build, including automated tests
> 10) source produces correct binaries.
>
> Are these all still relevant?
>
> Thanks,
>
> Gale
>
> On Fri, May 6, 2016 at 4:14 AM Stian Soiland-Reyes <[email protected]> wrote:
>
>> Thanks for checking Ian!
>>
>> I think I updated all the READMEs to say we need Java 8 now.  We
>> agreed to that update in
>> https://issues.apache.org/jira/browse/TAVERNA-869
>>
>>
>> I'm going to do a pre-flight test in Windows 10 as well so we don't
>> need to do the dance on the RCs again..
>>
>> I'll be brave and even have a go inside the new Ubuntu in Windows
>> subsystem... if it works there, then we have nothing to worry about :)
>>
>>
>> Perhaps Alan can have a go in his temperamental Windows 8?
>>
>> Anyone with a recent Mac OS X who could have a go? Always a risky ride
>> with Apple and Java..
>>
>> To install JDK 8 on a Mac - see
>>
>> http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
>>
>>
>>
>> To remind you, we will be releasing
>>
>> https://git-wip-us.apache.org/repos/asf/incubator-taverna-engine.git
>>
>> https://git-wip-us.apache.org/repos/asf/incubator-taverna-common-activities.git
>> https://git-wip-us.apache.org/repos/asf/incubator-taverna-commandline.git
>>
>> (built in that order with Java 8)
>>
>>
>> On 6 May 2016 at 11:49, alaninmcr <[email protected]> wrote:
>> > On 06/05/2016 10:19, Ian Dunlop wrote:
>> >>
>> >> Hello,
>> >>
>> >> JAVA_HOME set to 1.8 and everything builds successfully :)
>> >
>> >
>> > Good to know.
>> >
>> >> Cheers,
>> >>
>> >> Ian
>> >
>> >
>> > Alan
>>
>>
>>
>> --
>> 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

Reply via email to