DOCSLIB.ORG

HCP - CS Product Manager HCP-CS V 2

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
HCP - CS Product Manager HCP-CS V 2 HITACHI Inspire the Next 2535 Augustine Drive Santa Clara, CA 95054 USA Contact Information : HCP - CS Product Manager HCP-CS v 2 . 1 . 0 Hitachi Vantara LLC 2535 Augustine Dr. Santa Clara CA 95054 Component Version License Modified 18F/domain-scan 20181130-snapshot-988de72b Public Domain activesupport 5.2.1 MIT License Activiti - BPMN Converter 6.0.0 Apache License 2.0 Activiti - BPMN Model 6.0.0 Apache License 2.0 Activiti - DMN API 6.0.0 Apache License 2.0 Activiti - DMN Model 6.0.0 Apache License 2.0 Activiti - Engine 6.0.0 Apache License 2.0 Activiti - Form API 6.0.0 Apache License 2.0 Activiti - Form Model 6.0.0 Apache License 2.0 Activiti - Image Generator 6.0.0 Apache License 2.0 Activiti - Process Validation 6.0.0 Apache License 2.0 Addressable URI parser 2.5.2 Apache License 2.0 Advanced Linux Sound Architecture GNU Lesser General Public License 1.1.8 (ALSA) v2.1 only adzap/timeliness 0.3.8 MIT License aggs-matrix-stats 5.5.1 Apache License 2.0 aggs-matrix-stats 7.6.2 Apache License 2.0 agronholm/pythonfutures 3.3.0 3Delight License ahoward's lockfile 2.1.3 Ruby License ahoward's systemu 2.6.5 Ruby License GNU Lesser General Public License ai's r18n 3.1.2 v3.0 only airbnb/streamalert v3.3.0 Apache License 2.0 BSD 3-clause "New" or "Revised" ANTLR 2.7.7 License BSD 3-clause "New" or "Revised" ANTLR 4.5.1-1 License BSD 3-clause "New" or "Revised" antlr-python-runtime 4.7.2 License antw's iniparse 1.4.4 MIT License AOP Alliance (Java/J2EE AOP 1 Public Domain standard) HITACHI Inspire the Next 2535 Augustine Drive Santa Clara, CA 95054 USA Component Version License Modified Apache Commons BeanUtils 1.8.3 Apache License 2.0 Apache Commons BeanUtils 1.9.2 Apache License 2.0 Apache Commons BeanUtils 1.9.3 Apache License 2.0 Apache Commons CLI 1.3.1 Apache License 2.0 Apache Commons Codec 1.1 Apache License 2.0 Apache Commons Codec 1.11 Apache License 2.0 Apache Commons Codec 1.13 Apache License 2.0 Apache Commons Codec 1.9 Apache License 2.0 Apache Commons Collections 3.2.1 Apache License 2.0 Apache Commons Collections 3.2.2 Apache License 2.0 Apache Commons Collections 4 Apache License 2.0 Apache Commons Collections 4.1 Apache License 2.0 Apache Commons Compress 1.5 Apache License 2.0 Apache Commons Configuration 1.8 Apache License 2.0 Apache Commons Daemon 1.0.13 Apache License 2.0 Apache Commons DBCP 1.4 Apache License 2.0 Apache Commons Digester 1.8.1 Apache License 2.0 Apache Commons Digester 2.1 Apache License 2.0 Apache Commons Email 1.4 Apache License 2.0 Apache Commons Lang 2.5.0 Apache License 2.0 Apache Commons Lang 2.6 Apache License 2.0 Apache Commons Lang 3.7 Apache License 2.0 Apache Commons Lang 3.9 Apache License 2.0 Apache Commons Lang 62 Apache License 2.0 Apache Commons Logging 1.1.1 Apache License 2.0 Apache Commons Logging 1.1.2 Apache License 2.0 Apache Commons Logging 1.1.3 Apache License 2.0 Apache Commons Logging 1.2 Apache License 2.0 Apache Commons Math 2.2 Apache License 2.0 Apache Commons Pool 1.6 Apache License 2.0 Apache Commons Text 1.3 Apache License 2.0 Apache Commons Validator 1.6 Apache License 2.0 HITACHI Inspire the Next 2535 Augustine Drive Santa Clara, CA 95054 USA Component Version License Modified Apache Extras Companion for log4j 1.2.17 Apache License 2.0 1.2. Apache Geronimo 1.1.1 Apache License 2.0 Apache Geronimo Annotation Spec 1.3 Apache License 2.0 1.3 Apache Groovy 2.4.12 Apache License 2.0 Apache Groovy 2.4.15 Apache License 2.0 Apache Groovy 2.4.6 Apache License 2.0 Apache Groovy GROOVY_2_5_9 Apache License 2.0 Apache HttpClient 4.4.1 Apache License 2.0 Apache HttpClient 4.5.2 Apache License 2.0 Apache HttpClient 4.5.3 Apache License 2.0 Apache HttpClient 4.5.5 Apache License 2.0 Apache HttpClient 4.5.8 Apache License 2.0 Apache HttpClient 4.5.9 Apache License 2.0 Apache HttpClient rel/v4.5.11 Apache License 2.0 Apache HttpComponents AsyncClient 4.1.2 Apache License 2.0 Apache HttpComponents AsyncClient 4.1.3 Apache License 2.0 Apache HttpComponents AsyncClient 4.1.4 Apache License 2.0 Apache HttpComponents Core 4.4.11 Apache License 2.0 Apache HttpComponents Core 4.4.12 Apache License 2.0 Apache HttpComponents Core 4.4.13 Apache License 2.0 Apache HttpComponents Core 4.4.5 Apache License 2.0 Apache HttpComponents Core 4.4.6 Apache License 2.0 Apache HttpComponents Core 4.4.9 Apache License 2.0 Apache log4j 1.2.14 Apache License 2.0 Apache log4j 1.2.17 Apache License 2.0 Apache log4j 2.10.0 Apache License 2.0 Apache log4j 2.11.0 Apache License 2.0 Apache log4j 2.11.1 Apache License 2.0 Apache log4j 2.8.2 Apache License 2.0 Apache Log4j to SLF4J Adapter 2.12.1 Apache License 2.0 Apache Lucene 5.5.4 Apache License 2.0 HITACHI Inspire the Next 2535 Augustine Drive Santa Clara, CA 95054 USA Component Version License Modified Apache Lucene 6.6.0 Apache License 2.0 Apache Lucene 6.6.1 Apache License 2.0 Apache Lucene 8.4.0 Apache License 2.0 Apache POI 3.17 Apache License 2.0 Apache POI: OOXML 3.17 Apache License 2.0 Apache POI: OOXML-schemas 3.17 Apache License 2.0 Apache Tomcat 7.0.53 Apache License 2.0 Apache Tomcat 7.0.76 Apache License 2.0 Apache Tomcat 7.0.81 Apache License 2.0 Apache Tomcat 8.5.16 Apache License 2.0 Apache Tomcat 8.5.31 Apache License 2.0 Apache Tomcat 9.0.1237-atlassian-hosted Apache License 2.0 Apache Tomcat 9.0.31 Apache License 2.0 Apache Tomcat Embed 8.5.16 Apache License 2.0 Apache Tomcat Embed 8.5.31 Apache License 2.0 Apache Tomcat Embed 9.0.31 Apache License 2.0 Apache Tomcat Embed 9.0.37 Apache License 2.0 Apache Tomcat for precompile 1.0.3 Apache License 2.0 JSP/JSTL for A-Jetty. Apache Velocity 1.7 Apache License 2.0 Apache Velocity - Engine 2 Apache License 2.0 Apache Velocity - JSR 223 Scripting 2 Apache License 2.0 Apache Xalan (Java) 2.7.1 Apache License 2.0 Apache Xerces2 J 2.11.0 Apache License 2.0 Apache Xerces2 J 2.11.0-22 Apache License 2.0 Apache XML Commons 1.0.b2 Apache License 2.0 Apache XML Commons 1.2 Apache License 2.0 Apache XML Commons 1.4.01 Apache License 2.0 app_conf 0.4.2 MIT License appbundler 0.11.6 Apache License 2.0 applicationinsights 0.11.2 MIT License apt - Advanced Package Tool 1.8.2 GNU General Public License v2.0 only archaius-core 0.7.4 Apache License 2.0 HITACHI Inspire the Next 2535 Augustine Drive Santa Clara, CA 95054 USA Component Version License Modified artifactory-java-client 2.6.2 Apache License 2.0 Asciidoctor 0.1.2 MIT License BSD 3-clause "New" or "Revised" ASM 3.1 License BSD 3-clause "New" or "Revised" ASM 5.0.3 License BSD 3-clause "New" or "Revised" ASM 5.0.4 License ASM based accessors helper used by 1.1 Apache License 2.0 json-smart BSD 3-clause "New" or "Revised" ASM Commons 5.0.4 License BSD 3-clause "New" or "Revised" ASM Debug All 5.1 License BSD 3-clause "New" or "Revised" ASM Tree 5.0.4 License ASN.1 library for Python 0.2.1 BSD 2-clause "Simplified" License ASN.1 library for Python 0.4.2 BSD 2-clause "Simplified" License BSD 3-clause "New" or "Revised" ASN.1 library for Python v0.4.7 License asn1crypto 0.22.0 MIT License AspectJ Runtime 1.9.3 Eclipse Public License 1.0 AspectJ Runtime 1.9.4 Eclipse Public License 1.0 AspectJ weaver 1.8.10 Eclipse Public License 1.0 AspectJ weaver 1.8.13 Eclipse Public License 1.0 AspectJ weaver 1.9.5 Eclipse Public License 1.0 AspectJ weaver 1.9.6 Eclipse Public License 1.0 GNU Library General Public License audit-libs 2.8.5 v2 only BSD 3-clause "New" or "Revised" Automaton 1.11-8 License Avalon Framework API 4.3 Apache License 2.0 avalon-framework 4.3 Apache License 2.0 avalon-logkit 2.1 Apache License 2.0 AWS CLI 2.0.45 Apache License 2.0 AWS Java SDK for Alexa For 1.11.524 Apache License 2.0 Business HITACHI Inspire the Next 2535 Augustine Drive Santa Clara, CA 95054 USA Component Version License Modified AWS Java SDK for Alexa For 1.11.627 Apache License 2.0 Business AWS Java SDK for Amazon API 1.11.524 Apache License 2.0 Gateway AWS Java SDK for Amazon API 1.11.627 Apache License 2.0 Gateway AWS Java SDK for Amazon 1.11.524 Apache License 2.0 AppStream AWS Java SDK for Amazon 1.11.627 Apache License 2.0 AppStream AWS Java SDK for Amazon Athena 1.11.524 Apache License 2.0 AWS Java SDK for Amazon Athena 1.11.627 Apache License 2.0 AWS Java SDK for Amazon Chime 1.11.524 Apache License 2.0 AWS Java SDK for Amazon Chime 1.11.627 Apache License 2.0 AWS Java SDK for Amazon 1.11.524 Apache License 2.0 CloudDirectory AWS Java SDK for Amazon 1.11.627 Apache License 2.0 CloudDirectory AWS Java SDK for Amazon 1.11.524 Apache License 2.0 CloudFront AWS Java SDK for Amazon 1.11.627 Apache License 2.0 CloudFront AWS Java SDK for Amazon 1.11.524 Apache License 2.0 CloudSearch AWS Java SDK for Amazon 1.11.627 Apache License 2.0 CloudSearch AWS Java SDK for Amazon 1.11.524 Apache License 2.0 CloudWatch AWS Java SDK for Amazon 1.11.627 Apache License 2.0 CloudWatch AWS Java SDK for Amazon 1.11.627 Apache License 2.0 CloudWatch Application Insights AWS Java SDK for Amazon 1.11.524 Apache License 2.0 CloudWatch Events AWS Java SDK for Amazon 1.11.627 Apache License 2.0 CloudWatch Events AWS Java SDK for Amazon 1.11.524 Apache License 2.0 CloudWatch Logs AWS Java SDK for Amazon 1.11.627 Apache License 2.0 CloudWatch Logs AWS Java SDK for Amazon Cognito 1.11.524 Apache License 2.0 Identity HITACHI Inspire the Next 2535 Augustine Drive Santa Clara, CA 95054 USA Component Version License Modified AWS Java SDK for Amazon Cognito 1.11.627 Apache License 2.0 Identity AWS Java SDK for Amazon Cognito 1.11.524 Apache License 2.0 Identity Provider Service AWS Java SDK for Amazon Cognito 1.11.627 Apache License 2.0 Identity Provider Service AWS Java SDK for Amazon Cognito
Load more

Recommended publications
  • Developer Survey
    Developer Survey Questions requiring a response are in r ed . Questions in which a response is NOT required are in blue. This survey is a critical element of the developers workshop. We are using it to capture nuts and bolts information about codes within the community so that we can assess the landscape before the workshop and use this information to drive the discussions. Please collaborate to provide only one submission per code and submit your response using the online survey: h ttps://ucdavis.co1.qualtrics.com/jfe/form/SV_57wtv4gpuaowTsh Basic Information Code identification 1. What is the name of the code? [small text box] 2. Who are the primary authors/maintainers? [medium text box] 3. URL of webpage for the code (if different than the version control repository) [small text box] 4. URL of version control repository (if public) [small text box] Software 1. Which license(s) do you use? Select all that apply. a. Apache license b. BSD license c. GNU General Public License d. GNU Lesser General Public License e. MIT license f. Mozilla Public License g. Common Development and Distribution License h. Eclipse Public License i. Other. Please specify [small text box] j. No license 2. What programming language(s) is your code currently written in? Select all that apply a. Fortran 77 b. Fortran 90 or later c. C d. C++ e. Go f. Python g. Julia h. Matlab i. Other. Please specify. [small text box] 3. List the primary (high-level) code dependencies (e.g., PETSc, deal.ii, FEniCS) [medium text box] 4. List any additional (low-level) code dependencies (e.g., MPI, NetCDF, HDF5) [medium text box] 5.
    [Show full text]
  • Installation of Portal Applications
    TIBCO Foresight® Transaction Insight® Installation of Portal Applications Software Release 5.2 September 2017 Two-Second Advantage® Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCHEM BEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE. USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME. This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc. TIBCO, Two-Second Advantage, TIBCO BusinessConnect Insight, TIBCO Foresight Archive and Retrieval System, TIBCO Foresight BI Bridge – BAM, TIBCO Foresight EDISIM, TIBCO Foresight Instream, TIBCO Foresight Operational Monitor, TIBCO Foresight Studio, TIBCO Foresight Test Asset Management Suite, and TIBCO Foresight Transaction Insight are either registered trademarks or trademarks of TIBCO Software Inc.
    [Show full text]
  • CADET: Computer Assisted Discovery Extraction and Translation
    CADET: Computer Assisted Discovery Extraction and Translation Benjamin Van Durme, Tom Lippincott, Kevin Duh, Deana Burchfield, Adam Poliak, Cash Costello, Tim Finin, Scott Miller, James Mayfield Philipp Koehn, Craig Harman, Dawn Lawrie, Chandler May, Max Thomas Annabelle Carrell, Julianne Chaloux, Tongfei Chen, Alex Comerford Mark Dredze, Benjamin Glass, Shudong Hao, Patrick Martin, Pushpendre Rastogi Rashmi Sankepally, Travis Wolfe, Ying-Ying Tran, Ted Zhang Human Language Technology Center of Excellence, Johns Hopkins University Abstract Computer Assisted Discovery Extraction and Translation (CADET) is a workbench for helping knowledge workers find, la- bel, and translate documents of interest. It combines a multitude of analytics together with a flexible environment for customiz- Figure 1: CADET concept ing the workflow for different users. This open-source framework allows for easy development of new research prototypes using a micro-service architecture based atop Docker and Apache Thrift.1 1 Introduction CADET is an integrated workbench for helping knowledge workers discover, extract, and translate Figure 2: Discovery user interface useful information. The user interface (Figure1) is based on a domain expert starting with a large information in structured form. To do so, she ex- collection of data, wishing to discover the subset ports the search results to our Extraction interface, that is most salient to their goals, and exporting where she can provide annotations to help train an the results to tools for either extraction of specific information extraction system. The Extraction in- information of interest or interactive translation. terface allows the user to label any text span using For example, imagine a humanitarian aid any schema, and also incorporates active learning worker with a large collection of social media to complement the discovery process in selecting messages obtained in the aftermath of a natural data to annotate.
    [Show full text]
  • Eclipse IP Management Modernization Sharon Corbett MODERNIZATION
    Eclipse IP Management Modernization Sharon Corbett MODERNIZATION ● Eclipse IP - About ● Issue Statement WELCOME ● Objectives/Benefits ● License Compliance ● Self Service ● New Process Overview ● Futures ● Best Practices ● OSCM ● Wrap Up Eclipse Intellectual Property Management > Eclipse IP Policy (Board Approved) ○ Defines mechanism for accepting and licensing the intellectual property developed and leveraged by Eclipse projects > Legal Agreements ○ Formal - ECA, Committer Agreements, Working Group Participation Agreements > Due Diligence Review Process ○ Provenance, License Compatibility, Scanning for Anomalies ○ IP Ticket (CQ) > Commercial Adoption (Confidence/Safe) > High Bar, Rigorous, Well Respected COPYRIGHT (C) 2019, ECLIPSE FOUNDATION, INC. | MADE AVAILABLE UNDER THE ECLIPSE PUBLIC LICENSE 2.0 (EPL-2.0) What’s at Issue? > Eclipse IP Policy and Procedures (2004) > Significant changes over time > Cannot support agile development nor continuous delivery > Impossible to scale to modern day technology (Node.JS, Electron, NPM, etc.) > Burdensome - Lack of Automation COPYRIGHT (C) 2019, ECLIPSE FOUNDATION, INC. | MADE AVAILABLE UNDER THE ECLIPSE PUBLIC LICENSE 2.0 (EPL-2.0) The Time has Arrived ... > Bring Eclipse IP Policy and Process in line with contemporary expectations! COPYRIGHT (C) 2019, ECLIPSE FOUNDATION, INC. | MADE AVAILABLE UNDER THE ECLIPSE PUBLIC LICENSE 2.0 (EPL-2.0) Eclipse IP Governance Approach (Redefined) > Revise the IP Review requirements for third party content > Update IP Policy ○ Change due diligence approach for
    [Show full text]
  • A Strategy for Addressing the Needs of Advanced Scientific Computing Using Eclipse As a Parallel Tools Platform
    A Strategy for Addressing the Needs of Advanced Scientific Computing Using Eclipse as a Parallel Tools Platform Gregory R. Watson Craig E. Rasmussen Los Alamos National Laboratory P.O. Box 1663, MS B287 Los Alamos, NM 87545 December 2005 LA-UR-05-9114 ABSTRACT If parallel computer systems are to achieve the kinds of productivity improvements necessary to meet the needs of high productivity computing systems (HPCS), then a radical change will be required in how tools are developed for programmers and users of these systems. The number and complexity of tools is making it difficult for developers to access and use the tools effectively, and the lack of a common tool infrastructure significantly complicates tool development efforts. The rapid pace of change means that developing and maintaining the kinds of tools that will be needed to effectively utilize the capacity of future advanced computer systems is an increasingly onerous task. This paper proposes a strategy that will lead directly to productivity and quality improvements in the development and use of parallel applications, and that will provide a framework to guide and foster future tool development. This strategy is based on using the Eclipse platform to form the foundation of an integrated environment for parallel application development. The intention is not just to produce another set of tools, however, but rather to use Eclipse as both a focal point for tool development, and as a platform for producing highly integrated tools that are needed to meet the future needs of the HPC community. A Strategy for Addressing the Needs of Advanced Scientific Computing Using Eclipse as a Parallel Tools Platform 1 1 INTRODUCTION As high productivity computing systems (HPCS) are developed to meet the demands and computational challenges facing advanced scientific research, it is becoming increasingly apparent that existing software infrastructure and tools will need to be substantially improved in order to achieve the goal of sustained performance on terascale machines [17].
    [Show full text]
  • The Dzone Guide to Volume Ii
    THE D ZONE GUIDE TO MODERN JAVA VOLUME II BROUGHT TO YOU IN PARTNERSHIP WITH DZONE.COM/GUIDES DZONE’S 2016 GUIDE TO MODERN JAVA Dear Reader, TABLE OF CONTENTS 3 EXECUTIVE SUMMARY Why isn’t Java dead after more than two decades? A few guesses: Java is (still) uniquely portable, readable to 4 KEY RESEARCH FINDINGS fresh eyes, constantly improving its automatic memory management, provides good full-stack support for high- 10 THE JAVA 8 API DESIGN PRINCIPLES load web services, and enjoys a diverse and enthusiastic BY PER MINBORG community, mature toolchain, and vigorous dependency 13 PROJECT JIGSAW IS COMING ecosystem. BY NICOLAI PARLOG Java is growing with us, and we’re growing with Java. Java 18 REACTIVE MICROSERVICES: DRIVING APPLICATION 8 just expanded our programming paradigm horizons (add MODERNIZATION EFFORTS Church and Curry to Kay and Gosling) and we’re still learning BY MARKUS EISELE how to mix functional and object-oriented code. Early next 21 CHECKLIST: 7 HABITS OF SUPER PRODUCTIVE JAVA DEVELOPERS year Java 9 will add a wealth of bigger-picture upgrades. 22 THE ELEMENTS OF MODERN JAVA STYLE But Java remains vibrant for many more reasons than the BY MICHAEL TOFINETTI robustness of the language and the comprehensiveness of the platform. JVM languages keep multiplying (Kotlin went 28 12 FACTORS AND BEYOND IN JAVA GA this year!), Android keeps increasing market share, and BY PIETER HUMPHREY AND MARK HECKLER demand for Java developers (measuring by both new job 31 DIVING DEEPER INTO JAVA DEVELOPMENT posting frequency and average salary) remains high. The key to the modernization of Java is not a laundry-list of JSRs, but 34 INFOGRAPHIC: JAVA'S IMPACT ON THE MODERN WORLD rather the energy of the Java developer community at large.
    [Show full text]
  • Openjdk – the Future of Open Source Java on GNU/Linux
    OpenJDK – The Future of Open Source Java on GNU/Linux Dalibor Topić Java F/OSS Ambassador Blog aggregated on http://planetjdk.org Java Implementations Become Open Source Java ME, Java SE, and Java EE 2 Why now? Maturity Java is everywhere Adoption F/OSS growing globally Innovation Faster progress through participation 3 Why GNU/Linux? Values Freedom as a core value Stack Free Software above and below the JVM Demand Increasing demand for Java integration 4 Who profits? Developers New markets, new possibilities Customers More innovations, reduced risk Sun Mindshare, anchoring Java in GNU/Linux 5 License + Classpath GPL v2 Exception • No proprietary forks (for SE, EE) • Popular & trusted • Programs can have license any license • Compatible with • Improvements GNU/Linux remain in the community • Fostering adoption • FSFs license for GNU Classpath 6 A Little Bit Of History Jun 1996: Work on gcj starts Nov 1996: Work on Kaffe starts Feb 1998: First GNU Classpath Release Mar 2000: GNU Classpath and libgcj merge Dec 2002: Eclipse runs on gcj/Classpath Oct 2003: Kaffe switches to GNU Classpath Feb 2004: First FOSDEM Java Libre track Apr 2004: Richard Stallman on the 'Java Trap' Jan 2005: OpenOffice.org runs on gcj Mai 2005: Work on Harmony starts 7 Sun & Open Source Java RIs Juni 2005: Java EE RI Glassfish goes Open Source Mai 2006: First Glassfish release Mai 2006: Java announced to go Open Source November 2006: Java ME RI PhoneME goes Open Source November 2006: Java SE RI Hotspot und Javac go Open Source Mai 2007: The rest of Java SE follows suit 8 Status: JavaOne, Mai 2007 OpenJDK can be fully built from source, 'mostly' Open Source 25,169 Source code files 894 (4%) Binary files (“plugs”) 1,885 (8%) Open Source, though not GPLv2 The rest is GPLv2 (+ CP exception) Sun couldn't release the 4% back then as free software.
    [Show full text]
  • Eclipse (Software) 1 Eclipse (Software)
    Eclipse (software) 1 Eclipse (software) Eclipse Screenshot of Eclipse 3.6 Developer(s) Free and open source software community Stable release 3.6.2 Helios / 25 February 2011 Preview release 3.7M6 / 10 March 2011 Development status Active Written in Java Operating system Cross-platform: Linux, Mac OS X, Solaris, Windows Platform Java SE, Standard Widget Toolkit Available in Multilingual Type Software development License Eclipse Public License Website [1] Eclipse is a multi-language software development environment comprising an integrated development environment (IDE) and an extensible plug-in system. It is written mostly in Java and can be used to develop applications in Java and, by means of various plug-ins, other programming languages including Ada, C, C++, COBOL, Perl, PHP, Python, Ruby (including Ruby on Rails framework), Scala, Clojure, and Scheme. The IDE is often called Eclipse ADT for Ada, Eclipse CDT for C/C++, Eclipse JDT for Java, and Eclipse PDT for PHP. The initial codebase originated from VisualAge.[2] In its default form it is meant for Java developers, consisting of the Java Development Tools (JDT). Users can extend its abilities by installing plug-ins written for the Eclipse software framework, such as development toolkits for other programming languages, and can write and contribute their own plug-in modules. Released under the terms of the Eclipse Public License, Eclipse is free and open source software. It was one of the first IDEs to run under GNU Classpath and it runs without issues under IcedTea. Eclipse (software) 2 Architecture Eclipse employs plug-ins in order to provide all of its functionality on top of (and including) the runtime system, in contrast to some other applications where functionality is typically hard coded.
    [Show full text]
  • Rakuten Card Smoothly Transition to Cloud-Native Architecture With
    Case Study RakutenCase Study Card Smoothly Transition to Cloud-Native Architecture with Payara Server About Rakuten Card Established as its own credit card Enterprise brand in 2005, Rakuten Card Co. Ltd. is a Japanese credit card company formerly known as Rakuten Credit Inc. It has been recognised for In late 2017, Rakuten Card needed a reliable application server for its customer fac- achieving the number one credit card ing web applications. It found its best solution in Payara Server Enterprise: migrating shopping gross transaction value in Japan and hit the milestone of 20 in October 2017 for regular updates, improved support and services helping them in million credit card members in June achieving 99.9999% middleware availability. Two years later, Rakuten Card moved 2020. to a cloud-native architecture. It found Payara’s low maintenance technology and cloud-orientated features ensured a smooth transition with a stable version and flawless successful deployment. Industry: • Financial Challenges: The Initial Move to Payara Server • Banking Service Rakuten Card faced difficulties with its previous application server’s critical pending CVE bugs, memory leaks and sporadic errors without proper explanation in a stack Location: Tokyo, Japan trace. The expensive commercial support was too slow, and patches released intro- duced worsened security holes. Rakuten Card were looking for a support team who Software & Services: were well versed in Java based frameworks and could communicate in technical ter- • Payara Server Enterprise minology while resolving issues. • Java EE/Jakarta EE Moving to Payara Server Enterprise solved these issues, by providing monthly releases, bug fixes and patches, security improvements, and support directly from engineers within the Jakarta EE (Java EE) community.
    [Show full text]
  • Coleman-Coding-Freedom.Pdf
    Coding Freedom !" Coding Freedom THE ETHICS AND AESTHETICS OF HACKING !" E. GABRIELLA COLEMAN PRINCETON UNIVERSITY PRESS PRINCETON AND OXFORD Copyright © 2013 by Princeton University Press Creative Commons Attribution- NonCommercial- NoDerivs CC BY- NC- ND Requests for permission to modify material from this work should be sent to Permissions, Princeton University Press Published by Princeton University Press, 41 William Street, Princeton, New Jersey 08540 In the United Kingdom: Princeton University Press, 6 Oxford Street, Woodstock, Oxfordshire OX20 1TW press.princeton.edu All Rights Reserved At the time of writing of this book, the references to Internet Web sites (URLs) were accurate. Neither the author nor Princeton University Press is responsible for URLs that may have expired or changed since the manuscript was prepared. Library of Congress Cataloging-in-Publication Data Coleman, E. Gabriella, 1973– Coding freedom : the ethics and aesthetics of hacking / E. Gabriella Coleman. p. cm. Includes bibliographical references and index. ISBN 978-0-691-14460-3 (hbk. : alk. paper)—ISBN 978-0-691-14461-0 (pbk. : alk. paper) 1. Computer hackers. 2. Computer programmers. 3. Computer programming—Moral and ethical aspects. 4. Computer programming—Social aspects. 5. Intellectual freedom. I. Title. HD8039.D37C65 2012 174’.90051--dc23 2012031422 British Library Cataloging- in- Publication Data is available This book has been composed in Sabon Printed on acid- free paper. ∞ Printed in the United States of America 1 3 5 7 9 10 8 6 4 2 This book is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE !" We must be free not because we claim freedom, but because we practice it.
    [Show full text]
  • Fedora Core, Java™ and You
    Fedora Core, Java™ and You Gary Benson Software Engineer What is Java? The word ªJavaº is used to describe three things: The Java programming language The Java virtual machine The Java platform To support Java applications Fedora needs all three. What Fedora uses: GCJ and ECJ GCJ is the core of Fedora©s Java support: GCJ includes gcj, a compiler for the Java programming language. GCJ also has a runtime and class library, collectively called libgcj. The class library is separately known as GNU Classpath. ECJ is the Eclipse Compiler for Java: GCJ©s compiler gcj is not used for ªtraditionalº Java compilation. More on that later... Why libgcj? There are many free Java Virtual machines: Cacao, IKVM, JamVM, Jikes RVM, Kaffe, libgcj, Sable VM, ... There are two main reasons Fedora uses libgcj: Availability on many platforms. Ability to use precompiled native code. GNU Classpath Free core class library for Java virtual machines and compilers. The JPackage Project A collection of some 1,600 Java software packages for Linux: Distribution-agnostic RPM packages. Both runtimes/development kits and applications. Segregation between free and non-free packages. All free packages built entirely from source. Multiple runtimes/development kits may be installed. Fedora includes: JPackage-compatible runtime and development kit packages. A whole bunch of applications. JPackage JOnAS Fedora©s Java Compilers gcj can operate in several modes: Java source (.java) to Java bytecode (.class) Java source (.java) to native machine code (.o) Java bytecode (.class, .jar) to native machine code (.o) In Fedora: ECJ compiles Java source to bytecode. gcj compiles that bytecode to native machine code.
    [Show full text]
  • ATLAS Operational Monitoring Data Archival and Visualization
    EPJ Web of Conferences 245, 01020 (2020) https://doi.org/10.1051/epjconf/202024501020 CHEP 2019 ATLAS Operational Monitoring Data Archival and Visualiza- tion Igor Soloviev1;∗, Giuseppe Avolio2, Andrei Kazymov3, and Matei Vasile4 1University of California, Irvine, CA 92697-4575, US 2European Laboratory for Particle Physics, CERN, Geneva 23, CH-1211, Switzerland 3Joint Institute for Nuclear Research, JINR, Dubna, Russian Federation 4Horia Hulubei National Institute of Physics and Nuclear Engineering, Bucharest, Romania Abstract. The Information Service (IS) is an integral part of the Trigger and Data Acquisition (TDAQ) system of the ATLAS experiment at the Large Hadron Collider (LHC) at CERN. The IS allows online publication of opera- tional monitoring data, and it is used by all sub-systems and sub-detectors of the experiment to constantly monitor their hardware and software components including more than 25000 applications running on more than 3000 comput- ers. The Persistent Back-End for the ATLAS Information System (PBEAST) service stores all raw operational monitoring data for the lifetime of the ex- periment and provides programming and graphical interfaces to access them including Grafana dashboards and notebooks based on the CERN SWAN plat- form. During the ATLAS data taking sessions (for the full LHC Run 2 period) PBEAST acquired data at an average information update rate of 200 kHz and stored 20 TB of highly compacted and compressed data per year. This paper reports how over six years PBEAST became an essential piece of the experi- ment operations including details of the challenging requirements, the failures and successes of the various attempted implementations, the new types of mon- itoring data and the results of the time-series database technology evaluations for the improvements towards LHC Run 3.
    [Show full text]