DOCSLIB.ORG

Design and Development of a Service for Software Interrelationships

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Design and Development of a Service for Software Interrelationships Die approbierte Originalversion dieser Diplom-/ Masterarbeit ist in der Hauptbibliothek der Tech- nischen Universität Wien aufgestellt und zugänglich. http://www.ub.tuwien.ac.at The approved original version of this diploma or master thesis is available at the main library of the Vienna University of Technology. http://www.ub.tuwien.ac.at/eng Design and Development of a Service for Software Interrelationships Diplomarbeit zur Erlangung des akademischen Grades Diplom-Ingenieur im Rahmen des Studiums Software Engineering & Internet Computing eingereicht von Nikola Ilo Matrikelnummer 0925955 an der Fakultät für Informatik der Technischen Universität Wien Betreuung: Thomas Grechenig Mitwirkung: Mario Bernhart Wien, 6. Oktober 2014 (Unterschrift Verfasser/In) (Unterschrift Betreuung) Technische Universität Wien A-1040 Wien Karlsplatz 13 Tel. +43-1-58801-0 www.tuwien.ac.at Design and Development of a Service for Software Interrelationships Master’s Thesis submitted in partial fulfillment of the requirements for the degree of Diplom-Ingenieur in Software Engineering & Internet Computing by Nikola Ilo Registration Number 0925955 to the Faculty of Informatics at the Vienna University of Technology Advisor: Thomas Grechenig Assistance: Mario Bernhart Vienna, October 6, 2014 (Signature of Author) (Signature of Advisor) Technische Universität Wien A-1040 Wien Karlsplatz 13 Tel. +43-1-58801-0 www.tuwien.ac.at Statement by Author Nikola Ilo Pfalzauerstraße 60, 3021 Pressbaum Hiermit erkläre ich, dass ich diese Arbeit selbständig verfasst habe, dass ich die verwendeten Quellen und Hilfsmittel vollständig angegeben habe und dass ich die Stellen der Arbeit – einschließlich Tabellen, Karten und Abbildungen –, die anderen Werken oder dem Internet im Wortlaut oder dem Sinn nach entnommen sind, auf jeden Fall unter Angabe der Quelle als Entlehnung kenntlich gemacht habe. I hereby declare that I am the sole author of this thesis, that I have completely indicated all sources and help used, and that all parts of this work – including tables, maps and figures – if taken from other works or from the internet, whether copied literally or by sense, have been labelled including a citation of the source. (Place, Date) (Signature of Author) i This thesis is dedicated to the memory of my beloved father. Dipl.-Ing. Dr. Sotiraq Ilo 1958–2014 iii Acknowledgements First of all I want to thank my advisers Prof. Dr. Thomas Grechenig and Mario Bernhart for their support. They allowed me to explore my topic freely and therefore walk the path to which the research led me, from Software Engineering into the interesting field of the Semantic Web. Such open mindedness is not to be taken for granted. I also like to thank Brigitte Brem, who helped with the formalities of handing in the thesis. I want to thank my two employers I had during my master’s studies, Christoph Leithner and Manfred Gronalt. They made it possible to finish my degree and work at the same time. Special thanks is due to my friends and supporters Michael Geyer, who helped to convert my hand drawn sketches into beautiful graphics, Wilfried Mayer, who always was there to speak to when I encountered a problem, and Florian Hassanen, who significantly helped me to refine the nomenclature of the concepts which were created as part of this thesis. Further I want to thank my mother, Albana Ilo. Besides caring like all mothers do, she proofread my thesis and provided most valuable feedback. For this she made a great effort to read into a new subject. Most I want to thank my significant other, Anna Mach, for the steady support and for enduring the countless days where the keyboard noise did not stop until late at night. She cheered me up whenever I hit a wall and managed everything I could not while I was writing. Last but not least I want to thank all my family, friends, and colleagues, who supported me throughout the difficult last two years. v Kurzfassung Inter-Software-Beziehungen, wie z.B. Software-Abhängigkeiten, haben Auswirkung auf die Qualität und Entwicklung von Software und Software-Projekten und sind daher von essentieller Bedeutung für die Software-Entwicklung und Wartung. Aus diesem Grund gibt es bereits ausgeklügelte Systeme, um Software-Beziehungen zu deklarieren, zu verwalten und nutzbringend für Softwarebetriebs- und Entwicklungsprozesse einzusetzen. Nennenswerte Beispiele hierfür sind Packet-Management-Systeme von Linux-Distributionen und Build-Management-Systeme wie Apache Maven. Die Software-Netzwerke, auf denen diese Systeme agieren, bilden in sich interoperable, aber jeweils abgeschlossene Software- Ökosysteme, die sich in Syntax und Semantik voneinander unterscheiden, obwohl es Überlappungen in der Menge der enthaltenen Software gibt. Derzeit gibt es kein anwendbares System, welches Software- Ökosystem übergreifende Abfragen und Auswertungen zulässt. Diese Arbeit greift die Problemstellung auf, die semantischen und syntaktischen Grenzen von Software-Ökosystemen zu überwinden und dadurch die praktische Nutzung von Informationen über Inter-Software-Beziehungen für die Software Entwicklung und Wartung zu ermöglichen. Im Rahmen dieser Arbeit wurde ein Software-Prototyp entwickelt, der es ermöglicht, verschiedene Software-Ökosysteme zu integrieren und dadurch systemübergreifende Abfragen durchzuführen. Ein besonderes Augenmerk wurde auf Erweiterbarkeit und Skalierbarkeit gelegt, damit möglichst einfach neue, aber auch zahlreiche Software-Ökosysteme integriert werden können. Während der Entwicklung zeigte sich, dass Semantic Web-Technologien einen guten Rahmen für die Bearbeitung der Problem- stellung bieten. Mehrere Software-Ökosysteme wurden, z.B. aus den Debian/Ubuntu-Quellen oder den Common Vulnerability Enumeration (CVE)- und Common Platform Enumeration (CPE)-Verzeichnissen des National Institute of Standards and Technology (NIST), für die Evaluierung der Datenintegrati- on eingebunden. Weiters wurden Applikationen, wie ein Sicherheitslücken-Benachrichtigungssystem oder ein Lizenz-Einhaltungs-Überprüfungsprogramm, beispielhaft implementiert, um das Potential von Software-Ökosystem übergreifenden Abfragen aufzuzeigen und das Ergebnis zu evaluieren. Die wissenschaftlichen Beiträge dieser Arbeit gliedern sich wie folgt: eine verteilte Architektur für das Abgreifen, Parsen, Umlegen, Nachbearbeiten und Abrufen von generischen Datenquellen in ein semantisches RDF Datenmodel; eine abstrakte OWL-Ontologie für die semantische Modellierung von Inter-Software-Beziehungen; sowie ein System für die Verarbeitung von temporalen Resource Description Framework (RDF)-Aussagen mit SPARQL Protocol and RDF Query Language (SPARQL). Hierbei werden die Anfragen unter Beachtung der zeitlichen Gültigkeit, jedoch ohne vorheriger zeitlichen Normalisierung von Beobachtungszeitpunkten in Gültigkeitszeiträume, evaluiert. Schlüsselwörter Software Beziehungen, Software Abhängigkeiten, Semantic Web, Ontologie, Temporales SPARQL, metaservice, Mining Software Repositories vii Abstract Software interrelationships, like software dependencies, have impact on the quality and evolution of software projects and are therefore important to software development and maintenance. Sophisticated systems have been created in the past to define, manage, and utilize relationships in software processes. Mentionable examples for this are package management systems of Linux distributions and build systems like Apache Maven. These systems are clustered in software-ecosystems, which most of the times are syntactically and semantically incompatible to each other, although the described software can overlap. Currently there are no viable systems for querying information across different ecosystems. This thesis is about how to overcome semantic and syntactic borders of software ecosystems and thereby enable practical usage of information about software interrelationships in software development and maintenance. An iterative approach was used to develop a prototype, which enables integration of - and therefore queries across - different software ecosystems. Particular emphasis was placed on the extendibility and the scalability, i.e., to be able to easily integrate new and many ecosystems. During development, Semantic Web technologies showed to provide a suitable framework to approach this task. Several ecosystems, like Debian/Ubuntu repositories, and CVEs and CPEs defined by the NIST, were used to evaluate data integration. Additionally small applications, like a vulnerability notification system and license violation detector were used to show the usefulness of aggregated cross-ecosystem-interrelationships. Contributions of this thesis consist of: a distributed architecture for data retrieval, parsing, mapping, post-processing and querying of generic data into semantic RDF data model; an abstract owl-ontology for semantic modeling of inter-software relationships; and a model for processing temporally scoped RDF statements using SPARQL without previous normalization of observation times to time periods. Keywords Software Relationships, Software Dependencies, Semantic Web, Ontology, Temporal SPARQL, metaser- vice, Mining Software Repositories ix Contents 1 Introduction 1 1.1 Problem Statement . 1 1.2 Motivation . 2 1.3 Methodology . 3 1.4 Contributions . 3 1.5 Related Work . 3 1.5.1 Software Interrelationships . 3 1.5.2 Mining Software Repositories . 4 1.5.3 Semantic Web . 4 1.6 Thesis Structure . 5 2 Fundamentals 7 2.1 Software Repositories and Ecosystems . 7 2.1.1 Debian Ecosystem . 8 2.1.2 Apache Maven Repositories . 8 2.1.3 Joinup . 9 2.1.4
Load more

Recommended publications
  • Return of Organization Exempt from Income
    OMB No. 1545-0047 Return of Organization Exempt From Income Tax Form 990 Under section 501(c), 527, or 4947(a)(1) of the Internal Revenue Code (except black lung benefit trust or private foundation) Open to Public Department of the Treasury Internal Revenue Service The organization may have to use a copy of this return to satisfy state reporting requirements. Inspection A For the 2011 calendar year, or tax year beginning 5/1/2011 , and ending 4/30/2012 B Check if applicable: C Name of organization The Apache Software Foundation D Employer identification number Address change Doing Business As 47-0825376 Name change Number and street (or P.O. box if mail is not delivered to street address) Room/suite E Telephone number Initial return 1901 Munsey Drive (909) 374-9776 Terminated City or town, state or country, and ZIP + 4 Amended return Forest Hill MD 21050-2747 G Gross receipts $ 554,439 Application pending F Name and address of principal officer: H(a) Is this a group return for affiliates? Yes X No Jim Jagielski 1901 Munsey Drive, Forest Hill, MD 21050-2747 H(b) Are all affiliates included? Yes No I Tax-exempt status: X 501(c)(3) 501(c) ( ) (insert no.) 4947(a)(1) or 527 If "No," attach a list. (see instructions) J Website: http://www.apache.org/ H(c) Group exemption number K Form of organization: X Corporation Trust Association Other L Year of formation: 1999 M State of legal domicile: MD Part I Summary 1 Briefly describe the organization's mission or most significant activities: to provide open source software to the public that we sponsor free of charge 2 Check this box if the organization discontinued its operations or disposed of more than 25% of its net assets.
    [Show full text]
  • Maven by Example I
    Maven by Example i Maven by Example Ed. 0.7 Maven by Example ii Contents 1 Introducing Apache Maven1 1.1 Maven. What is it?....................................1 1.2 Convention Over Configuration...............................2 1.3 A Common Interface....................................3 1.4 Universal Reuse through Maven Plugins..........................3 1.5 Conceptual Model of a “Project”..............................4 1.6 Is Maven an alternative to XYZ?..............................5 1.7 Comparing Maven with Ant................................6 2 Installing Maven 10 2.1 Verify your Java Installation................................ 10 2.2 Downloading Maven.................................... 11 2.3 Installing Maven...................................... 11 Maven by Example iii 2.3.1 Installing Maven on Linux, BSD and Mac OS X................. 11 2.3.2 Installing Maven on Microsoft Windows...................... 12 2.3.2.1 Setting Environment Variables..................... 12 2.4 Testing a Maven Installation................................ 13 2.5 Maven Installation Details................................. 13 2.5.1 User-Specific Configuration and Repository.................... 14 2.5.2 Upgrading a Maven Installation.......................... 15 2.6 Uninstalling Maven..................................... 15 2.7 Getting Help with Maven.................................. 15 2.8 About the Apache Software License............................ 16 3 A Simple Maven Project 17 3.1 Introduction......................................... 17 3.1.1 Downloading
    [Show full text]
  • Op E N So U R C E Yea R B O O K 2 0
    OPEN SOURCE YEARBOOK 2016 ..... ........ .... ... .. .... .. .. ... .. OPENSOURCE.COM Opensource.com publishes stories about creating, adopting, and sharing open source solutions. Visit Opensource.com to learn more about how the open source way is improving technologies, education, business, government, health, law, entertainment, humanitarian efforts, and more. Submit a story idea: https://opensource.com/story Email us: [email protected] Chat with us in Freenode IRC: #opensource.com . OPEN SOURCE YEARBOOK 2016 . OPENSOURCE.COM 3 ...... ........ .. .. .. ... .... AUTOGRAPHS . ... .. .... .. .. ... .. ........ ...... ........ .. .. .. ... .... AUTOGRAPHS . ... .. .... .. .. ... .. ........ OPENSOURCE.COM...... ........ .. .. .. ... .... ........ WRITE FOR US ..... .. .. .. ... .... 7 big reasons to contribute to Opensource.com: Career benefits: “I probably would not have gotten my most recent job if it had not been for my articles on 1 Opensource.com.” Raise awareness: “The platform and publicity that is available through Opensource.com is extremely 2 valuable.” Grow your network: “I met a lot of interesting people after that, boosted my blog stats immediately, and 3 even got some business offers!” Contribute back to open source communities: “Writing for Opensource.com has allowed me to give 4 back to a community of users and developers from whom I have truly benefited for many years.” Receive free, professional editing services: “The team helps me, through feedback, on improving my 5 writing skills.” We’re loveable: “I love the Opensource.com team. I have known some of them for years and they are 6 good people.” 7 Writing for us is easy: “I couldn't have been more pleased with my writing experience.” Email us to learn more or to share your feedback about writing for us: https://opensource.com/story Visit our Participate page to more about joining in the Opensource.com community: https://opensource.com/participate Find our editorial team, moderators, authors, and readers on Freenode IRC at #opensource.com: https://opensource.com/irc .
    [Show full text]
  • Apache Buildr in Action a Short Intro
    Apache Buildr in Action A short intro BED 2012 Dr. Halil-Cem Gürsoy, adesso AG 29.03.12 About me ► Round about 12 Years in the IT, Development and Consulting ► Before that development in research (RNA secondary structures) ► Software Architect @ adesso AG, Dortmund ► Main focus on Java Enterprise (Spring, JEE) and integration projects > Build Management > Cloud > NoSQL / BigData ► Speaker and Author 29.03.12 2 Scala für Enterprise-Applikationen Agenda ► Why another Build System? ► A bit history ► Buildr catchwords ► Tasks ► Dependency management ► Testing ► Other languages ► Extending 3 Apache Buildr in Action – BED-Con 2012 Any aggressive Maven fanboys here? http://www.flickr.com/photos/bombardier/19428000/4 Apache Buildr in Action – BED-Con 2012 Collected quotes about Maven “Maven is such a pain in the ass” http://appwriter.com/what-if-maven-was-measured-cost-first-maven-project 5 Apache Buildr in Action – BED-Con 2012 Maven sucks... ► Convention over configuration > Inconsistent application of convention rules > High effort needed to configure ► Documentation > Which documentation? (ok, gets better) ► “Latest and greatest” plugins > Maven @now != Maven @yesterday > Not reproducible builds! ► Which Bugs are fixed in Maven 3? 6 Apache Buildr in Action – BED-Con 2012 Other buildsystems ► Ant > Still good and useful, can do everything... but XML ► Gradle > Groovy based > Easy extensible > Many plugins, supported by CI-Tools ► Simple Build Tool > In Scala for Scala (but does it for Java, too) 7 Apache Buildr in Action – BED-Con 2012 Apache
    [Show full text]
  • The Maven Definitive Guide
    Tim O'Brien (Sonatype, Inc.), John Casey (Sonatype, Inc.), Brian Fox (Sonatype, Inc.), Bruce Snyder (Sonatype, Inc.), Jason Van Zyl (Sonatype, Inc.), Eric Redmond () Copyright © 2006-2008 Copyright ......................................................................................................xiii 1. Creative Commons BY-ND-NC ........................................................xiii Foreword: Beta 0.13 ....................................................................................... xv Preface ........................................................................................................... xvi 1. How to Use this Book ........................................................................ xvi 2. Your Feedback ..................................................................................xvii 3. Font Conventions .............................................................................xviii 4. Maven Writing Conventions ............................................................xviii 5. Acknowledgements ............................................................................ xix 1. Introducing Apache Maven .......................................................................... 1 1.1. Maven... What is it? ........................................................................... 1 1.2. Convention Over Configuration ......................................................... 2 1.3. A Common Interface .......................................................................... 3 1.4. Universal Reuse through
    [Show full text]
  • Free and Open Source Software Across the EU 153
    Free and Open Source Software Across the EU 153 Free and Open Source Software Across the EU Gijs Hillenius(a) (a) Journalist, contributor to Joinup DOI: 10.5033/ifosslr.v5i2.90 Abstract Across the EU, there is a groundswe of pu& ic ad'inistrations that use open source for their I() so utions. E!idence of its benefits as we as practica e*a'p es are steadi y pi ing up at the European Co''ission's Open Source O&ser!atory. The areas where this t+pe of so ution can be found most inc ude, in rando' order$ content mana%e'ent ((.S/, document mana%e'ent (D.S/, data&ase app ications, a kinds of on ine e1%o!ernment ser!ices, geo-infor'ation s+ste's (2IS/ and in 'ost if not a pu& ic y pro!ided app ications bui t to use open data. Keywords 3u& ic ad'inistrations; European Union; Joinup; Free and Open Source Software Po icies; i'p e'entations. 6hen it co'es to free and open source software -FOSS/$ 'an+ pu& ic ad'inistrations wi ha!e stu'& ed across it. )hese da+s, their I) dea er te s the' that their proprietar+ s+ste' for 'ana%in% citi7en records wi function 8ust as we with the open source data&ase 'ana%e'ent s+ste' 3ost%res9 $ +et the su&scription fee is 'uch ower than when co'&ined with the pre!ious + re9uired proprietary a ternati!e.1 For others, switchin% to free and open source is increasin% + a conscious decision.
    [Show full text]
  • Client-Server Web Apps with Javascript and Java
    Client-Server Web Apps with JavaScript and Java Casimir Saternos Client-Server Web Apps with JavaScript and Java by Casimir Saternos Copyright © 2014 EzGraphs, LLC. 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. Online editions are also available for most titles (http://my.safaribooksonline.com). For more information, contact our corporate/ institutional sales department: 800-998-9938 or [email protected]. Editors: Simon St. Laurent and Allyson MacDonald Indexer: Judith McConville Production Editor: Kristen Brown Cover Designer: Karen Montgomery Copyeditor: Gillian McGarvey Interior Designer: David Futato Proofreader: Amanda Kersey Illustrator: Rebecca Demarest April 2014: First Edition Revision History for the First Edition: 2014-03-27: First release See http://oreilly.com/catalog/errata.csp?isbn=9781449369330 for release details. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. Client-Server Web Apps with JavaScript and Java, the image of a large Indian civet, and related trade dress are trademarks of O’Reilly Media, Inc. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O’Reilly Media, Inc. was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this book, the publisher and author assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.
    [Show full text]
  • EIRA Overview
    Delivered in the context of ABC-IV-66 An introduction to the European Interoperability Reference Architecture (EIRA©) v3.0.0 EIRA EUROPEAN INTEROPERABILITY REFERENCE ARCHITECTURE European Interoperability Reference Architecture (EIRA©) v3.0.0 Change Control Modification Details Version 3.0.0 ABBs definition update All the ABBs definitions have been reviewed and a section referring to the interoperability saliency have been introduced, in order to highlight the ABB’s interoperability relevance for EU integrated public services. EIF is the framework against which interoperability saliency has been assessed, per each ABB. EIRA viewpoints New viewpoints have been added in order to align the model to the New introduction and update European Interoperability Framework. Existing viewpoints have been reviewed. Examples ABB examples have been reviewed. In particular, obsolete examples have been replaced with up-to-date ones. Version 2.1.0 Introduction of a new A new viewpoint has been added to match the “Conceptual Model for viewpoint: Conceptual Integrated Service Provisioning” as it is provided in the New European Model for Integrated Interoperability Framework. Service Provisioning Examples Architecture Building Blocks have received examples to guide the user in the type of implementation that can be imagined for these building blocks. Synonyms Added synonyms to selected Architecture Building Blocks Version 2.0.0 ArchiMate® 3 upgrade EIRA© v1.2.2 was aligned with ArchiMate® 2.1, EIRA© v2.0.0 is aligned with ArchiMate® 3.0 Introduction to the
    [Show full text]
  • Brian Fox (Sonatype, Inc.), Bruce Snyder (Sonatype, Inc.), Jason Van Zyl (Sonatype, Inc.), Eric Redmond ()
    Tim O'Brien (Sonatype, Inc.), John Casey (Sonatype, Inc.), Brian Fox (Sonatype, Inc.), Bruce Snyder (Sonatype, Inc.), Jason Van Zyl (Sonatype, Inc.), Eric Redmond () Copyright © 2006-2008 Copyright .......................................................................................................xii 1. Creative Commons BY-ND-NC .........................................................xii Foreword: 0.3 ................................................................................................ xiv Preface ........................................................................................................... xvi 1. How to Use this Book ........................................................................ xvi 2. Your Feedback ..................................................................................xvii 3. Font Conventions .............................................................................xviii 4. Maven Writing Conventions ............................................................xviii 5. Acknowledgements ............................................................................ xix 1. Introducing Apache Maven .......................................................................... 1 1.1. Maven... What is it? ........................................................................... 1 1.2. Convention Over Configuration ......................................................... 2 1.3. A Common Interface .......................................................................... 3 1.4. Universal Reuse through
    [Show full text]
  • Buildr by Apache
    Quick Start ......................................................................................................................................4 Installing and Running................................................................................................................14 Projects...........................................................................................................................................25 Building .........................................................................................................................................38 Artifacts .........................................................................................................................................49 Packaging ......................................................................................................................................57 Testing ...........................................................................................................................................79 Settings & Profiles........................................................................................................................89 Languages .....................................................................................................................................99 More Stuff....................................................................................................................................119 Extending Buildr ........................................................................................................................160
    [Show full text]
  • O2/A5 Final Release All Content
    Project title: Free Open Source Software for SMEs Project activity: O2/A5 Final Release All content The European Commission’s support for the production of this publication does not constitute an endorse- ment of the contents which reflects the views only of the authors, and the Commission cannot be held re- sponsible for any use which may be made of the information contained therein. CONTEXT Grant agreement 2017-1-EL01-KA202-036112 Programme Erasmus+ Key action Cooperation for innovation and the exchange of good practices Action Strategic Partnerships Project acronym FOSS4SMEs Project title Free Open Source Software for SMEs Project starting date 01/10/2017 Project duration 24 months Project end date 30/09/2019 Project Activity (A) Intellectual Output (IO) Multiplier Event (E) O2/A5 Final Release Short-term joint staff training events (C) Document title O2/A5 Final Release Nature of document Service Dissemination level PUBLIC Due date of document M21 Produced All partners . 2 TABLE OF CONTENTS Unit 1: INTRODUCING FOSS ....................................................................................................... 5 . Lesson 1.1: Defining FOSS and the difference with proprietary software ......................... 7 . U1.L1. Part 1 - A historical background .......................................................................... 8 . U1.L1. Part 2 - Guiding principles: The four freedoms ................................................... 9 . U1.L1. Part 3 - The definition of FOSS .........................................................................
    [Show full text]
  • Securegateway Server
    Open Source Used In Secure Gateway 2.26 Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. Text Part Number: 78EE117C99-135850904 Open Source Used In Secure Gateway 2.26 1 This document contains licenses and notices for open source software used in this product. With respect to the free/open source software listed in this document, if you have any questions or wish to receive a copy of any source code to which you may be entitled under the applicable free/open source license(s) (such as the GNU Lesser/General Public License), please contact us at [email protected]. In your requests please include the following reference number 78EE117C99-135850904 Contents 1.1 Apache Commons Codec 1.3. 1.1.1 Available under license 1.2 Apache Commons Configuration 1.6 1.2.1 Available under license 1.3 Apache Commons Lib Apache 2.0 1.3.1 Available under license 1.4 Apache HTTP Server 2.2.9 1.4.1 Available under license 1.5 Apache Jakarta Commons HttpClient 3.1 1.5.1 Available under license 1.6 Apache Jakarta Commons HttpClient 3.1 1.6.1 Available under license 1.7 Apache Log4j 1.2.16 1.7.1 Available under license 1.8 apache-log4j 1.2.15 :DUPLICATE 1.8.1 Available under license 1.9 apache-log4j 1.2.15 1.9.1 Available under license 1.10 bcprov-jdk16 1.36 1.10.1 Available under license 1.11 BouncyCastle 1.46 :ICS 1.11.1 Available under license 1.12 c3p0 0.9.1.2 1.12.1 Available under license 1.13 Codec 1.2 1.13.1
    [Show full text]