Hello It is absolutely possible for you to acquire this information and such license and risk evaluation is done frequently.
For a proper license/risk evaluation it will be important to perform detailed analysis of both the source and the binaries. For the source, and the Hive example you showed, this means we copied the specified code into the Apache NiFi codebase and with or without modification are using it. For binary dependencies it means at the time of executing an actual build we pull in the necessary jars/artifacts that are used to make up an actual java/executable application. You listed a small subset of them in the table. For a finding of all the binary dependencies we have you could run 'mvn -o dependency:list' and extract the necessary values from there. Please keep in mind that our LICENSE and NOTICE information provided for the source itself is covered in the top level LICENSE and NOTICE files in our github repository. Take care to do this for an actual release that you might be evaluating such as the most recent 1.3.0 release [1]. The LICENSE and NOTICE found within the nifi-assembly module and within all NARs and WARs cover the binary representation of the artifacts that are built. To better understand our practices and procedures you can take a look here [2]. Our LICENSE and NOTICE only describes items which are necessary to list for L&N reasons as per Apache license requirements and Apache Software Foundation guidelines. So for certain types of scans/analysis that you'll be doing you might need/want to go beyond what it is listed in our L&N. Thanks Joe [1] https://github.com/apache/nifi/tree/rel/nifi-1.3.0 [2] https://nifi.apache.org/licensing-guide.html On Wed, Jun 21, 2017 at 11:24 AM, Heinz Dreinhoff <[email protected]> wrote: > Dear Apache Team, > > we need a detailed overview of all (sub) components of your product NIFI with > version number for a license (risk) evaluation, > > Nifi uses the WriterImpl component of Apache HIVE. This component is written > with version 1.2.1 in the Nifi-Notice. However this information is missing > for HiveWriter and HiveOptions. Likewise for the processors nifi-kafka-nar > (0.10). JavaMail API is specified with versionsnr 1.4.7. This value is > missing for Yammer Metrics > > Please give me the version numbers for the following components: > > Apache NiFi > > Apache NiFi > > 1..2.0 > > Apache NiFi > > python-evtx > > > > Apache NiFi > > HiveWriter > > > > Apache NiFi > > HiveOptions > > > > Apache NiFi > > WriterImpl > > 1.2.1 > > > > > Apache NiFi > > nifi-kafka-nar (0.10) > > 0.10 > > Apache NiFi > > Apache Commons Lang > > > > Apache NiFi > > Apache Kafka > > > > Apache NiFi > > Yammer Metrics > > > > Apache NiFi > > Snappy Java > > > > Apache NiFi > > Apache ZooKeeper > > > > Apache NiFi > > JavaMail API > > 1.4.7 > > Apache NiFi > > JavaBeans Activation Framework (JAF) > > 1.1 > > Apache NiFi > > nifi-transform-json-ui > > > > Apache NiFi > > Apache Commons Lang > > > > Apache NiFi > > Jolt > > > > Apache NiFi > > Jettison > > > > Apache NiFi > > jersey-core > > 1.18.3 > > Apache NiFi > > jersey-server > > 1.18.3 > > Apache NiFi > > jersey-json > > 1.18.3 > > Apache NiFi > > jersey-servlet > > 1.18.3 > > Apache NiFi > > Old JAXB Runtime > > 2.2.3-1 > > Apache NiFi > > Java Architecture For XML Binding > > 2.2.2 > > Apache NiFi > > Streaming API For XML > > 1.0-2 > > Apache NiFi > > JavaBeans Activation Framework > > 1.1 > > > > Apache NiFi > > nifi-web-docs > > > > Apache NiFi > > Apache Commons Lang > > > > Apache NiFi > > Apache Avro > > > > Apache NiFi > > Snappy Java > > > > > > Apache NiFi > > nifi-standard-nar > > > > Apache NiFi > > Apache Hadoop > > > > Apache NiFi > > Jolt > > > > Apache NiFi > > Apache Calcite > > > > Apache NiFi > > Apache Commons IO > > > > Apache NiFi > > Apache Commons Lang > > > > Apache NiFi > > Apache Commons Net > > > > Apache NiFi > > Apache Commons Compress > > > > Apache NiFi > > Apache HttpComponents > > > > Apache NiFi > > Apache HttpComponents > > > > Apache NiFi > > Apache Commons Logging > > > > Apache NiFi > > Joda Time > > > > Apache NiFi > > Apache ActiveMQ > > > > Apache NiFi > > Apache Geronimo > > > > Apache NiFi > > Yammer Metrics > > > > Apache NiFi > > JSON-SMART > > > > Apache NiFi > > JsonPath > > > > Apache NiFi > > Jolt > > > > Apache NiFi > > Apache Commons Codec > > > > Apache NiFi > > Apache Tika > > > > Apache NiFi > > Jackson JSON processor > > > > Apache NiFi > > Apache Avro > > > > Apache NiFi > > Snappy Java > > > > Apache NiFi > > ParCEFone > > > > Apache NiFi > > Grok > > > > Apache NiFi > > Apache Calcite > > > > Apache NiFi > > jersey-core > > 1.19 > > Apache NiFi > > jersey-client > > 1.19 > > Apache NiFi > > jersey-server > > 1.19 > > Apache NiFi > > JavaMail API > > 1.4.7 > > Apache NiFi > > Javax JMS Api > > 2.0.1 > > Apache NiFi > > Expression Language 3.0 API > > 3.0.0 > > Apache NiFi > > JavaBeans Activation Framework (JAF) > > 1.1 > > Apache NiFi > > JSR311 API > > 1.1.1 > > Apache NiFi > > Saxon HE > > 9.6.0-5 > > Apache NiFi > > XZ for Java > > 1.5 > > > > Is it possible to get this information? > > Best Heinz > > > > Mit freundlichen Grüßen / With best regards > > Heinz Dreinhoff > Manager > > MHP - Excellence in Management- and IT-Consulting for Automotive. > > > MHP > Management- und IT-Beratung GmbH > > Office Wolfsburg > Major-Hirst-Straße 3 > Autovision ICW Gebäude 8 > 38442 Wolfsburg > > Mobile: +49 152 3314 5221 > eMail: [email protected] > Web: www.mhp.com > > MHP > Management- und IT-Beratung GmbH > Sitz der Gesellschaft: Ludwigsburg > Registergericht: Amtsgericht Stuttgart HRB-Nr. 205571 > Geschäftsführung: > Dr.-Ing. Ralf Hofmann (Vorsitzender der Geschäftsführung) > Marc Zimmermann > > Die vorgenannten Angaben werden jeder E-Mail automatisch > hinzugefügt. Dies ist kein Anerkenntnis, dass es sich beim > Inhalt dieser E-Mail um eine rechtsverbindliche Erklärung von > MHP Management- und IT-Beratung GmbH handelt. > Erklärungen, die die MHP Management- und IT-Beratung > GmbH verpflichten, bedürfen jeweils der Unterschrift > durch zwei zeichnungsberechtigte Personen der GmbH. >
