It's what we've done so far.. I didn't mean we won't publish to Maven Central - but that we won't try to release the build taverna-commandline-product zip file on dist.apache.org, as that would include lib/*.jar for all of our dependencies. (we would need to propagate their licenses)
On 21 April 2016 at 13:21, Ian Dunlop <[email protected]> wrote: > Hello, > > Is there a different procedure for a source only release? Do we need to > document that? > > Cheers, > > Ian > > On 21/04/16 07:39, Stian Soiland-Reyes wrote: >> Hi, >> >> Shall we try to get out a release of Taverna Command Line? >> >> That would mean the repositories: >> >> taverna-engine >> taverna-common-activities >> taverna-commandline >> >> I think they are in a good state now, although we ideally should have a bit >> more example workflows. >> >> I suggest we do a source only release of cmd line this time to avoid >> overloading mentors in reviewing the binary distribution (which would mean >> propagating NOTICE and LICENSE from all external JARs) >> >> Are there any remaining work we should finish first? >> > > -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/0000-0001-9842-9718
