I am not sure what is the relation to the release.. you mean taverna-language? That can do these things:
https://github.com/apache/incubator-taverna-language/blob/master/README.md e.g. a Java API for dealing with Taverna workflow definitions and RO bundles. It can't run workflows - that is as you found the taverna-commandline. the taverna-commandline-product does not build an executable *.jar (that is an unfortunate side-effect), but a ZIP/tar.gz distribution that includes the command line and all required jars. Some of the README content from the 2.5.0 release might help, and the relevant bits probably could be added to the README.md of incubator-taverna-commandline https://github.com/apache/incubator-taverna-commandline/tree/old/taverna-commandline-product-core-2.5.0.1 although the talk about 'editions' no longer apply, as we agreed not to do so for 3.0. After building taverna-commandline-product you should find a folder like target/apache-taverna-commandline-3.1.0-incubating-SNAPSHOT-dev You can make the archives by using -Pnightly or -Prelease This didn't run though.. stain@biggie:~/src/taverna/incubator-taverna-commandline/taverna-commandline-product/target/apache-taverna-commandline-3.1.0-incubating-SNAPSHOT-dev/apache-taverna-commandline-3.1.0-incubating-SNAPSHOT$ sh executeworkflow.sh Error: Unable to access jarfile /home/stain/src/taverna/incubator-taverna-commandline/taverna-commandline-product/target/apache-taverna-commandline-3.1.0-incubating-SNAPSHOT-dev/apache-taverna-commandline-3.1.0-incubating-SNAPSHOT/lib/org.apache.taverna.commandline/taverna-commandline-launcher-3.1.0.incubating-SNAPSHOT.jar It was because 3.1.0.incubating should be 3.1.0-incubating - and this was hardcoded in src/main/etc/executeworkflow.sh and executeworkflow.bat - which will be tricky when we are doing a release. Also the launcher tried to run uk.org.taverna.commandline.TavernaCommandLine as its mainClass, so I fixed the pom.xml Now: stain@biggie:~/src/taverna/incubator-taverna-commandline/taverna-commandline-product/target/apache-taverna-commandline-3.1.0-incubating-SNAPSHOT-dev/apache-taverna-commandline-3.1.0-incubating-SNAPSHOT$ sh executeworkflow.sh OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=400m; support was removed in 8.0 usage: executeworkflow [options] [workflow] On 15 September 2015 at 12:10, Ian Dunlop <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Hello, > > What exactly can you do with the software we released? Are there any > examples. I'm trying to get to the stage where I can run a workflow > using the commandline tool. I guess you have to download the > commandline code from > https://github.com/apache/incubator-taverna-commandline and install it > and then you can run the executeworkflow script which is in > taverna-commandline-product\src\main\etc\ > The script looks for java %ARGS% -jar > "/lib/org.apache.taverna.commandline/taverna-commandline-launcher-3.1.0. > incubating-SNAPSHOT.jar" > > I can find that JAR file inside taverna-commandline-product\target\ > but cannot run it since it seems to have no manifest file "no main > manifest attribute" > > So, why is the manifest file missing and what mvn goal is needed to > generate the lib directory that the script expects? > > Cheers, > > Ian > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iQEcBAEBCAAGBQJV9/y2AAoJEPK45GBX+Cy58fsIAJwzBjSXE78oCZg1scXH50+1 > yCVkeWgknoyKOR/GW6qw/SccevZqZ/W8OrxiXvTE8jnSMGFmHyQ2ucEmEKFF17Rm > VBP+cJmcRMmMnwjO1IaTcj0+S+ObP4BIcBGX4BdMxQUKNcOE7cojL0TuFal61dtw > o5P3oSSiN3vqY7AeogVn7J2h8CoiBkrlzBGjEBDGIohRsHa/L6mPENzEhpAOep3T > 0sDdy1+hpG0sTiCu/oUHiF8fXGl2n/a04ctXUzEzsk5z9VgLEQBbSNCy0aAlDDjD > yoUJBREopkLwCxRj0nL1ts1lM497MU9HRkX+I0/Ix7iVFrovdQJXDVn9+FoH8DI= > =sZ98 > -----END PGP SIGNATURE----- -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/0000-0001-9842-9718
