The Taverna Language Command Line tool would also include transitively the dependencies of the rest of Taverna Language, so their NOTICE should also be taken into consideration, and the NOTICE of their dependencies again.
Luckily most of those dependencies don't have a NOTICE and even the general one for Taverna Language we managed to shrink down to just: Apache Taverna Language Copyright 2010-2014 University of Manchester, UK Copyright 2014-2015 The Apache Software Foundation This product includes software developed at The Apache Software Foundation (http://www.apache.org/). So for now I think that is the best NOTICE.. just copy NOTICE from the top-level of taverna-language to cmndline/src/main/resources/META-INF/NOTICE - and then as we go through all the dependencies we can see if they have other NOTICEs that needs to go in? I know I know.. copy pasting is bad and this will be out of sync in just 4 months time. But unfortunately that is where the "state of the art" is with regards to NOTICE files :( On 19 August 2015 at 10:38, Menaka Madushanka <[email protected]> wrote: > Hello, > As it is an essential factor that to include the information about 3rd > party software and resources used in the project. > For the Taverna Language Command line tool, I have used the Alirlift > airline commandline parser library. > > I also found a example notice file for ASF. > Should I make the NOTICE file for the commandline tool according to that > structure or more simpler? > > Where should it be stored when deployment? > > Cheers > Menaka > > -- > Menaka Madushanka Jayawardena > Faculty of Engineering, <http://www.pdn.ac.lk/eng> > University of Peradeniyaya. > LinkedIn <http://lk.linkedin.com/in/menakajayawardena> -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/0000-0001-9842-9718
