DOCSLIB.ORG

HYCU for Google Cloud Open Source Licenses

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
HYCU for Google Cloud Open Source Licenses OPEN SOURCE LICENSES HYCU Data Protection as a Service for Google Cloud Service update date: January 2021 Document release date: January 2021 OPEN SOURCE LICENSES Legal notices Copyright notice © 2021 HYCU. All rights reserved. This document contains proprietary information, which is protected by copyright. No part of this document may be photocopied, reproduced, distributed, transmitted, stored in a retrieval system, modified or translated to another language in any form by any means, without the prior written consent of HYCU. Trademarks HYCU logos, names, trademarks and/or service marks and combinations thereof are the property of HYCU or its affiliates. Other product names are the property of their respective trademark or service mark holders and are hereby acknowledged. GCP™, Google Chrome™, Google Cloud™, Google Cloud Platform™, Google Cloud Storage™, and Google Compute Engine™ are trademarks of Google LLC. Internet Explorer®, Microsoft®, Microsoft Edge™, and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries. Mozilla and Firefox are trademarks of the Mozilla Foundation in the U.S. and other countries. SAP HANA® is the trademark or registered trademark of SAP SE or its affiliates in Germany and in several other countries. HYCU Data Protection as a Service for Google Cloud is not affiliated with Debian. Debian is a registered trademark owned by Software in the Public Interest, Inc. Disclaimer The details and descriptions contained in this document are believed to have been accurate and up to date at the time the document was written. The information contained in this document is subject to change without notice. HYCU provides this material "as is" and makes no warranty of any kind, expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. HYCU shall not be liable for errors and omissions contained herein. In no event shall HYCU be liable for any direct, indirect, consequential, punitive, special or incidental damages, including, without limitation, damages for loss and profits, loss of anticipated savings, business interruption, or loss of information arising out of the 2 www.hycu.com OPEN SOURCE LICENSES use or inability to use this document, or any action taken based on the information contained herein, even if it has been advised of the possibility of such damages, whether based on warranty, contract, or any other legal theory. The only warranties for HYCU products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Notice This document is provided in connection with HYCU products. HYCU may have copyright, patents, patent applications, trademark, or other intellectual property rights covering the subject matter of this document. Except as expressly provided in any written license agreement from HYCU, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property on HYCU products. Use of underlying HYCU product(s) is governed by their respective Software License and Support Terms. Important: Please read Software License and Support Terms before using the accompanying software product(s). HYCU www.hycu.com 3 www.hycu.com OPEN SOURCE LICENSES Contents Software component list 16 Base operating system 16 Components licensed under Apache License 2.0 (Apache-2.0) 16 Components licensed under Apache License 2.0 (Apache-2.0) and The MIT License (MIT) 23 Components licensed under Common Development and Distribution License 1.0 (CDDL-1.0) 23 Components licensed under Common Development and Distribution License 1.1 (CDDL-1.1) 24 Components licensed under Common Public License 1.0 (CPL-1.0) 24 Components licensed under Creative Commons Zero v1.0 Universal 24 Components licensed under curl License 24 Components licensed under WTFPL 24 Components licensed under Eclipse Distribution License 1.0 (EDL-1.0) and Eclipse Public License 1.0 (EPL-1.0) 24 Components licensed under Eclipse Public License 1.0 (EPL-1.0) 25 Components licensed under Eclipse Public License 2.0 (EPL-2.0) 25 Components licensed under GNU General Public License version 2 (GPL-2.0) 26 Components licensed under GNU General Public License version 2 w/Classpath exception (GPL-2.0-with-classpath-exception) 27 Components licensed under GNU General Public License version 3 (GPL-3.0) 27 Components licensed under GNU Lesser General Public License version 2.1 (LGPL-2.1) 27 Components licensed under ISC License (ISC) 27 Components licensed under SIL Open Font License (OFL-1.1) 27 Components licensed under The 2-Clause BSD License (BSD-2-Clause) 27 Components licensed under The 3-Clause BSD License (BSD-3-Clause) 28 Components licensed under The MIT License (MIT) 29 Components licensed under The MIT +no-false-attribs License (MITNFA) 31 Components licensed under The PostgreSQL License (PostgreSQL) 31 4 www.hycu.com OPEN SOURCE LICENSES Components licensed under custom license 31 Components in the public domain 31 License attribution texts 32 Ace (Ajax.org Cloud9 Editor): The 3-Clause BSD License 32 Angular-UI.Ace: The MIT License 32 Angular IVH Treeview: The MIT License 33 angular-busy2: The MIT License 33 angular-drag-and-drop-lists: The MIT License 34 angular-gridster: The MIT License 34 angular-modal-service: The MIT License 35 AngularJS: The MIT License 35 AngularJS-Toaster: The MIT License 35 AngularUI Router: The MIT License 36 Animal Sniffer Annotations: The MIT License 36 Animate.css: The MIT License 37 AntLR Parser Generator: The 3-Clause BSD License 37 AOP Alliance: public domain 38 Aopalliance Version 1.0 Repackaged AS A Module: Eclipse Public License 2.0 38 Apache Commons BeanUtils: Apache License 2.0 38 Apache Commons CLI: Apache License 2.0 39 Apache Commons Codec: Apache License 2.0 39 Apache Commons Collections: Apache License 2.0 40 Apache Commons Collections 4: Apache License 2.0 41 Apache Commons IO: Apache License 2.0 41 Apache Commons Lang: Apache License 2.0 42 Apache Commons Logging: Apache License 2.0 42 Apache Commons Text: Apache License 2.0 43 Apache CXF Core, Apache CXF Runtime Core For WSDL, Apache CXF Runtime HTTP Async Transport: Apache License 2.0 43 Apache CXF Runtime HTTP Transport: Apache License 2.0 44 Apache CXF Runtime JAX WS Frontend: Apache License 2.0 44 5 www.hycu.com OPEN SOURCE LICENSES Apache CXF Runtime JAXB DataBinding, Apache CXF Runtime Simple Frontend, Apache CXF Runtime SOAP Binding, Apache CXF Runtime WS Addressing: Apache License 2.0 45 Apache CXF Runtime WS Policy: Apache License 2.0 45 Apache CXF Runtime XML Binding: Apache License 2.0 46 Apache HttpAsyncClient: Apache License 2.0 46 Apache HttpClient: Apache License 2.0 47 Apache HttpCore 4.4.4: Apache License 2.0 47 Apache HttpCore 4.4.9: Apache License 2.0 48 Apache HttpCore NIO: Apache License 2.0 48 Apache Log4j JUL Adapter: Apache License 2.0 49 Apache Neethi: Apache License 2.0 49 API Common: The 3-Clause BSD License 50 ASM: The 3-Clause BSD License 50 ASM Based Accessors Helper Used By JSON Smart: Apache License 2.0 51 AssertJ Fluent Assertions: Apache License 2.0 51 Asynchronous Http Client, Asynchronous Http Client Netty Utils: Apache License 2.0 52 Babel compiler core: The MIT License 52 Babel Loader: The MIT License 53 babel/plugin-transform-runtime, babel-preset-es2015, babel-preset-es2016, babel-preset-es2017: The MIT License 53 Bean: The MIT +no-false-attribs License 54 Bean Validation API 1.1.0.Final: Apache License 2.0 54 Bean Validation API 2.0.1.Final: Apache License 2.0 55 Bootstrap: The MIT License 55 Bootstrap 3 Date/Time Picker: The MIT License 55 bootstrap-progressbar: The MIT License 56 Bouncy Castle Provider: The MIT License 56 Byte Buddy (without Dependencies): Apache License 2.0 57 C3P0: Eclipse Public License 1.0 57 C3p0:JDBC DataSources/Resource Pools: GNU Lesser General Public License 58 6 www.hycu.com OPEN SOURCE LICENSES version 2.1 Chalk: The MIT License 58 Chart.js: The MIT License 58 ClassMate: Apache License 2.0 59 Cloud Billing API, Cloud Resource Manager API: Apache License 2.0 59 Cloud Storage JSON API: Apache License 2.0 59 Commons CA Certificates: GNU General Public License version 2 60 Commons CA Certificates (JKS keystore): GNU General Public License version 3 60 Commons IP Math: The MIT License 60 Compute Engine API: Apache License 2.0 61 containerd: Apache License 2.0 61 copy-webpack-plugin: The MIT License 62 css-loader: The MIT License 62 cURL, cURL GnuTLS library, cURL library: curl License 63 D3: Data-Driven Documents: The 3-Clause BSD License 63 dateformat: The MIT License 64 del: The MIT License 64 Docker: the open-source application container engine: Apache License 2.0 65 Docker CLI: the open-source application container engine: Apache License 2.0 65 Dom4J: custom license 65 Eclipse Collections API, Eclipse Collections Fork Join Utilities, Eclipse Collections Main Library: Eclipse Distribution License 1.0, Eclipse Public License 1.0 66 Elsa Serialization: Apache License 2.0 66 Error Prone Annotations: Apache License 2.0 67 EventSource polyfill: The MIT License 67 Expression Language 3.0, Expression Language 3.0 API: Eclipse Public License 2.0 67 Extended StAX API: Common Development and Distribution License 1.1 68 Extract Text Plugin: The MIT License 68 Failsafe: Apache License 2.0 69 FastInfoset:
Load more

Recommended publications
  • XML Document Parsing: Operational and Performance Characteristics
    COMPUTING PRACTICES XML Document Parsing: Operational and Performance Characteristics Parsing is an expensive operation that can degrade XML processing performance. A survey of four representative XML parsing models—DOM, SAX, StAX, and VTD—reveals their suitability for different types of applications. Tak Cheung Lam roadly used in database and networking applications, the and Jianxun Jason Ding Extensible Markup Language is the de facto standard for the Cisco Systems interoperable document format. As XML becomes widespread, it is critical for application developers to understand the opera- Jyh-Charn Liu tional and performance characteristics of XML processing. Texas A&M University BAs Figure 1 shows, XML processing occurs in four stages: parsing, access, modification, and serialization. Although parsing is the most expensive operation,1 there are no detailed studies that compare • the processing steps and associated overhead costs of different parsing models, • tradeoffs in accessing and modifying parsed data, and • XML-based applications’ access and modification requirements. Figure 1 also illustrates the three-step parsing process. The first two steps, character conversion and lexical analysis, are usually invariant among dif- ferent parsing models, while the third step, syntactic analysis, creates data representations based on the parsing model used. To help developers make sensible choices for their target applications, we compared the data representations of four representative parsing models: document object model (DOM; www.w3.org/DOM), simple API for XML (SAX; www.saxproject.org), streaming API for XML (StAX; http://jcp.org/ en/jsr/detail?id=173), and virtual token descriptor (VTD; http://vtd-xml. sourceforge.net). These data representations result in different operational and performance characteristics.
    [Show full text]
  • Security in Cloud Computing a Security Assessment of Cloud Computing Providers for an Online Receipt Storage
    Security in Cloud Computing A Security Assessment of Cloud Computing Providers for an Online Receipt Storage Mats Andreassen Kåre Marius Blakstad Master of Science in Computer Science Submission date: June 2010 Supervisor: Lillian Røstad, IDI Norwegian University of Science and Technology Department of Computer and Information Science Problem Description We will survey some current cloud computing vendors and compare them to find patterns in how their feature sets are evolving. The start-up firm dSafe intends to exploit the promises of cloud computing in order to launch their business idea with only marginal hardware and licensing costs. We must define the criteria for how dSafe's application can be sufficiently secure in the cloud as well as how dSafe can get there. Assignment given: 14. January 2010 Supervisor: Lillian Røstad, IDI Abstract Considerations with regards to security issues and demands must be addressed before migrating an application into a cloud computing environment. Different vendors, Microsoft Azure, Amazon Web Services and Google AppEngine, provide different capabilities and solutions to the individual areas of concern presented by each application. Through a case study of an online receipt storage application from the company dSafe, a basis is formed for the evaluation. The three cloud computing vendors are assessed with regards to a security assessment framework provided by the Cloud Security Alliance and the application of this on the case study. Finally, the study is concluded with a set of general recommendations and the recommendation of a cloud vendor. This is based on a number of security as- pects related to the case study’s existence in the cloud.
    [Show full text]
  • O'reilly- Collaborating in Devops Culture
    Compliments of Collaborating in DevOps Culture Better Software Through Better Relationships Jennifer Davis & Ryn Daniels REPORT Teamwork powers DevOps GitHub powers teams GitHub helps more than two million organizations build better software together by centralizing discussions, automating tasks, and integrating with thousands of apps. Embraced by 31 million developers and counting, GitHub is where high-performing DevOps starts. Get started with a free trial at enterprise.github.com/contact Our on-premises and cloud solutions help enterprise teams: Collaborate Innovate Integrate Work across internal and Bring the power of Build on GitHub and external teams securely. the world’s largest open integrate with everything GitHub Enterprise includes source community to from legacy tools to access to on-premises developers at work, while cutting-edge apps, unifying Enterprise Server as well keeping your most critical your DevOps toolchain as Enterprise Cloud—now code behind the firewall so you can keep things with SOC 1, SOC 2, and ISAE with GitHub Connect. simple as you grow. 3000/3402 compliance. Work fast. Work secure. Work together. Start a free trial To find out more about GitHub Enterprise visit github.com/enterprise or email us at [email protected] Collaborating in DevOps Culture Better Software Through Better Relationships Jennifer Davis and Ryn Daniels Beijing Boston Farnham Sebastopol Tokyo Collaborating in DevOps Culture by Jennifer Davis and Ryn Daniels Copyright © 2019 Jennifer Davis and Ryn Daniels. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use.
    [Show full text]
  • Open Cloud Computing with the Simple Cloud API and Apache Libcloud Doug Tidwell Cloud Computing Evangelist, IBM [email protected]
    Open Cloud Computing with the Simple Cloud API and Apache libcloud Doug Tidwell Cloud Computing Evangelist, IBM [email protected] Session 7665 Agenda • Portability and interoperability • A few words about APIs • The Simple Cloud API • Storage • Queues • Documents • Controlling VMs with Apache libcloud • Resources / Next steps The problem Vendor lock-in • If there’s a new technology, any talented programmer will want to use it. • Maybe the shiny new thing is appropriate for what we’re doing. • Maybe not. • We’re probably going to use it anyway. • The challenge is to walk the line between using the newest, coolest thing and avoiding vendor lock-in. Portability and Interoperability • In writing flexible code for the cloud, there are two key concepts: • Portability is the ability to run components or systems written for one cloud provider in another cloud provider’s environment. • Interoperability is the ability to write one piece of code that works with multiple cloud providers, regardless of the differences between them. How standards work • For a standards effort to work, three things have to happen: • The standard has to solve a common problem in an elegant way. • The standard has to be implemented consistently by vendors. • Users have to insist that the products they use implement the standard. How standards work • All three things have to happen. • If the standard doesn't solve a common problem, or if it solves it in an awkward way, the standard fails. • If the standard isn't implemented by anyone, the standard fails. • If customers buy and use products even though they don't implement the standard, the standard fails.
    [Show full text]
  • Mobile Phones and Cloud Computing
    Mobile phones and cloud computing A quantitative research paper on mobile phone application offloading by cloud computing utilization Oskar Hamrén Department of informatics Human Computer Interaction Master’s programme Master thesis 2-year level, 30 credits SPM 2012.07 Abstract The development of the mobile phone has been rapid. From being a device mainly used for phone calls and writing text messages the mobile phone of today, or commonly referred to as the smartphone, has become a multi-purpose device. Because of its size and thermal constraints there are certain limitations in areas of battery life and computational capabilities. Some say that cloud computing is just another buzzword, a way to sell already existing technology. Others claim that it has the potential to transform the whole IT-industry. This thesis is covering the intersection of these two fields by investigating if it is possible to increase the speed of mobile phones by offloading computational heavy mobile phone application functions by using cloud computing. A mobile phone application was developed that conducts three computational heavy tests. The tests were run twice, by not using cloud computing offloading and by using it. The time taken to carry out the tests were saved and later compared to see if it is faster to use cloud computing in comparison to not use it. The results showed that it is not beneficial to use cloud computing to carry out these types of tasks; it is faster to use the mobile phone. 1 Table of Contents Abstract ..................................................................................................................................... 1 Table of Contents ..................................................................................................................... 2 1. Introduction .......................................................................................................................... 5 1.1 Previous research ........................................................................................................................
    [Show full text]
  • Software As a Service
    Software as a Service Haojie Hang Ogheneovo Dibie Executive Summary • In this presentation, we go through the Software as a Service Methodology, examine its benefits and drawbacks and talk about two state-of-art SaaS systems– Amazon Web Service and Google App Engine • We also look into Service Oriented Architecture powering SaaS applications and its impact on modern web 2.0 applications • Finally, we examine hybrids of traditional and SaaS applications Overview • What is Software as a Service (SaaS) • Background o Brief history o Concept o Big picture o Related terms • Computing Today o SasS is everywhere o The SaaS Market • Benefits of SaaS • Drawbacks of SaaS o Robustness o Privacy o Security o Reliability • Service Oriented Architectures (SOA) o Guiding principles of SOA • Case studies o Amazon Web Services (AWS) o Google App Engine • Influence of SOA on Web 2.0 development o Zend Framework • Hybrids of Traditional and SaaS applications o Dropbox o Microsoft Office • Summary • References What is SaaS? • Definition: Software as a Service (SaaS), a.k.a. on- demand software, is a software delivery model in which software and its associated data are hosted centrally and accessed using a thin-client, usually a web browser over the internet. – Wikipedia • Simply put, SaaS is a method for delivering software that provides remote access to software as a web- based service. The software service can be purchased with a monthly fee and pay as you go. What is SaaS? • Where does the term SaaS come from? o The SAAS acronym allegedly first appeared
    [Show full text]
  • Poly Videoos Offer of Source for Open Source Software 3.6.0
    OFFER OF SOURCE FOR 3.6.0 | 2021 | 3725-85857-010A OPEN SOURCE SOFTWARE August Poly VideoOS Software Contents Offer of Source for Open Source Software .............................................................................. 1 Open Source Software ............................................................................................................. 2 Qualcomm Platform Licenses ............................................................................................................. 2 List of Open Source Software .................................................................................................. 2 Poly G7500, Poly Studio X50, and Poly Studio X30 .......................................................................... 2 Poly Microphone IP Adapter ............................................................................................................. 13 Poly IP Table Microphone and Poly IP Ceiling Microphone ............................................................. 18 Poly TC8 and Poly Control Application ............................................................................................. 21 Get Help ..................................................................................................................................... 22 Related Poly and Partner Resources ..................................................................................... 22 Privacy Policy ...........................................................................................................................
    [Show full text]
  • A Comprehensive Study of Bloated Dependencies in the Maven Ecosystem
    Noname manuscript No. (will be inserted by the editor) A Comprehensive Study of Bloated Dependencies in the Maven Ecosystem César Soto-Valero · Nicolas Harrand · Martin Monperrus · Benoit Baudry Received: date / Accepted: date Abstract Build automation tools and package managers have a profound influence on software development. They facilitate the reuse of third-party libraries, support a clear separation between the application’s code and its ex- ternal dependencies, and automate several software development tasks. How- ever, the wide adoption of these tools introduces new challenges related to dependency management. In this paper, we propose an original study of one such challenge: the emergence of bloated dependencies. Bloated dependencies are libraries that the build tool packages with the application’s compiled code but that are actually not necessary to build and run the application. This phenomenon artificially grows the size of the built binary and increases maintenance effort. We propose a tool, called DepClean, to analyze the presence of bloated dependencies in Maven artifacts. We ana- lyze 9; 639 Java artifacts hosted on Maven Central, which include a total of 723; 444 dependency relationships. Our key result is that 75:1% of the analyzed dependency relationships are bloated. In other words, it is feasible to reduce the number of dependencies of Maven artifacts up to 1=4 of its current count. We also perform a qualitative study with 30 notable open-source projects. Our results indicate that developers pay attention to their dependencies and are willing to remove bloated dependencies: 18/21 answered pull requests were accepted and merged by developers, removing 131 dependencies in total.
    [Show full text]
  • Gateway Licensing Information User Manual Version 19
    Gateway Licensing Information User Manual Version 19 December 2019 Contents Introduction ...................................................................................................................................... 5 Licensed Products, Restricted Use Licenses, and Prerequisite Products ........................................ 5 Primavera Gateway ................................................................................................................................ 5 Third Party Notices and/or Licenses ................................................................................................ 6 Bootstrap ................................................................................................................................................ 6 Commons Codec .................................................................................................................................... 6 Commons Compress .............................................................................................................................. 6 Commons IO ........................................................................................................................................... 7 Commons Net ......................................................................................................................................... 7 commons-vfs .......................................................................................................................................... 7 HttpComponents HttpClient ..................................................................................................................
    [Show full text]
  • Licensing Information User Manual Release 21C (21.1) F37966-01 March 2021
    Oracle® Zero Downtime Migration Licensing Information User Manual Release 21c (21.1) F37966-01 March 2021 Introduction This Licensing Information document is a part of the product or program documentation under the terms of your Oracle license agreement and is intended to help you understand the program editions, entitlements, restrictions, prerequisites, special license rights, and/or separately licensed third party technology terms associated with the Oracle software program(s) covered by this document (the "Program(s)"). Entitled or restricted use products or components identified in this document that are not provided with the particular Program may be obtained from the Oracle Software Delivery Cloud website (https://edelivery.oracle.com) or from media Oracle may provide. If you have a question about your license rights and obligations, please contact your Oracle sales representative, review the information provided in Oracle’s Software Investment Guide (http://www.oracle.com/us/ corporate/pricing/software-investment-guide/index.html), and/or contact the applicable Oracle License Management Services representative listed on http:// www.oracle.com/us/corporate/license-management-services/index.html. Licensing Information Third-Party Notices and/or Licenses About the Third-Party Licenses The third party licensing information in Oracle Database Licensing Information User Manual, Third-Party Notices and/or Licenses and Open Source Software License Text, applies to Oracle Zero Downtime Migration. The third party licensing information included in the license notices provided with Oracle Linux applies to Oracle Zero Downtime Migration. Open Source or Other Separately Licensed Software Required notices for open source or other separately licensed software products or components distributed in Oracle Zero Downtime Migration are identified in the following table along with the applicable licensing information.
    [Show full text]
  • Skalierbare Echtzeitverarbeitung Mit Spark Streaming: Realisierung Und Konzeption Eines Car Information Systems
    Bachelorarbeit Philipp Grulich Skalierbare Echtzeitverarbeitung mit Spark Streaming: Realisierung und Konzeption eines Car Information Systems Fakultät Technik und Informatik Faculty of Engineering and Computer Science Department Informatik Department of Computer Science Philipp Grulich Skalierbare Echtzeitverarbeitung mit Spark Streaming: Realisierung und Konzeption eines Car Information Systems Bachelorarbeit eingereicht im Rahmen Bachelorprüfung im Studiengang Angewandte Informatik am Department Informatik der Fakultät Technik und Informatik der Hochschule für Angewandte Wissenschaften Hamburg Betreuender Prüfer: Prof. Dr.-Ing. Olaf Zukunft Zweitgutachter: Prof. Dr. Stefan Sarstedt Abgegeben am 1.3.2016 Philipp Grulich Thema der Arbeit Skalierbare Echtzeitverarbeitung mit Spark Streaming: Realisierung und Konzeption eines Car Information Systems Stichworte Echtzeitverarbeitung, Spark, Spark Streaming, Car Information System, Event Processing, Skalierbarkeit, Fehlertoleranz Kurzzusammenfassung Stream Verarbeitung ist mittlerweile eines der relevantesten Bereiche im Rahmen der Big Data Analyse, da es die Verarbeitung einer Vielzahl an Events innerhalb einer kurzen Latenz erlaubt. Eines der momentan am häufigsten genutzten Stream Verarbeitungssysteme ist Spark Streaming. Dieses wird im Rahmen dieser Arbeit anhand der Konzeption und Realisie- rung eines Car Information Systems demonstriert und diskutiert, wobei viel Wert auf das Er- zeugen einer möglichst generischen Anwendungsarchitektur gelegt wird. Abschließend wird sowohl das CIS als
    [Show full text]
  • Unravel Data Systems Version 4.5
    UNRAVEL DATA SYSTEMS VERSION 4.5 Component name Component version name License names jQuery 1.8.2 MIT License Apache Tomcat 5.5.23 Apache License 2.0 Tachyon Project POM 0.8.2 Apache License 2.0 Apache Directory LDAP API Model 1.0.0-M20 Apache License 2.0 apache/incubator-heron 0.16.5.1 Apache License 2.0 Maven Plugin API 3.0.4 Apache License 2.0 ApacheDS Authentication Interceptor 2.0.0-M15 Apache License 2.0 Apache Directory LDAP API Extras ACI 1.0.0-M20 Apache License 2.0 Apache HttpComponents Core 4.3.3 Apache License 2.0 Spark Project Tags 2.0.0-preview Apache License 2.0 Curator Testing 3.3.0 Apache License 2.0 Apache HttpComponents Core 4.4.5 Apache License 2.0 Apache Commons Daemon 1.0.15 Apache License 2.0 classworlds 2.4 Apache License 2.0 abego TreeLayout Core 1.0.1 BSD 3-clause "New" or "Revised" License jackson-core 2.8.6 Apache License 2.0 Lucene Join 6.6.1 Apache License 2.0 Apache Commons CLI 1.3-cloudera-pre-r1439998 Apache License 2.0 hive-apache 0.5 Apache License 2.0 scala-parser-combinators 1.0.4 BSD 3-clause "New" or "Revised" License com.springsource.javax.xml.bind 2.1.7 Common Development and Distribution License 1.0 SnakeYAML 1.15 Apache License 2.0 JUnit 4.12 Common Public License 1.0 ApacheDS Protocol Kerberos 2.0.0-M12 Apache License 2.0 Apache Groovy 2.4.6 Apache License 2.0 JGraphT - Core 1.2.0 (GNU Lesser General Public License v2.1 or later AND Eclipse Public License 1.0) chill-java 0.5.0 Apache License 2.0 Apache Commons Logging 1.2 Apache License 2.0 OpenCensus 0.12.3 Apache License 2.0 ApacheDS Protocol
    [Show full text]