DOCSLIB.ORG

The Eclipse Cloud Devtools Ecosystem: Defining the Future of Cloud Native Software Development

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The Eclipse Cloud Devtools Ecosystem: Defining the Future of Cloud Native Software Development The Eclipse Cloud DevTools Ecosystem: Defining the Future of Cloud Native Software Development White Paper 2 Eclipse Foundation White Paper The Eclipse Cloud DevTools Working Group offers a vendor-neutral ecosystem of open source projects focused on defining, implementing, and promoting best-in-class web and cloud-based development tools. COPYRIGHT (C) 2021, ECLIPSE FOUNDATION, INC. | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0) 3 Eclipse Foundation White Paper Open Source Software Accelerates Migration of Developer Tools to the Cloud ver the past two decades, most relevant business applications have been migrated to the cloud. More recently, there’s growing awareness that the cloud is also an innovation O platform that accelerates software development.1,2 It’s now well understood that with cloud-based IDEs and For many enterprises, using proprietary cloud tools, developers can more efficiently migrate and build development tools doesn’t make sense because the applications than they can with desktop tools. Cloud tools don’t provide adequate flexibility or control over native tools also enable large and diverse developer the development ecosystem. The flexibility to adapt teams to share the same configuration and runtime tools to domain-specific requirements increases environments, increasing productivity and reducing, developer efficiency. And control over the development if not eliminating, setup times. ecosystem mitigates critical risks associated with developer tools that are often the backbone of business So why has adoption of cloud-based developer tools models and the resulting intellectual property. lagged behind other types of cloud migration? A number of commercial businesses certainly recognized For these and other reasons, open source software the potential early on. The problem was those early- is key for cloud native software development. stage cloud development tools were mostly proprietary Recognizing this fact, several leading organizations solutions that came with restrictions and limitations joined forces in the Eclipse Cloud DevTools Working that didn’t meet market needs and expectations. Group to create open source alternatives, and to build and support the ecosystem. 1 Cloud’s trillion-dollar prize is up for grabs, McKinsey Quarterly, February 26, 2021. 2 The Cloud as an Innovation Platform for Software Development, Communications of the ACM, October 2019. COPYRIGHT (C) 2021, ECLIPSE FOUNDATION, INC. | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0) 4 Eclipse Foundation White Paper Industry Leaders Collaborate to Build an Open Cloud Development Ecosystem he Eclipse Cloud DevTools Working Group is a diverse group of members that includes globally recognized technology leaders as well as smaller organizations — all focused T on open source developer tools and software innovation. Founding members include Broadcom, EclipseSource, Ericsson, IBM, Intel, Red Hat, SAP, and TypeFox, among others. Initially, the working group’s primary focus was to the speed of collaboration and development in order identify common issues and how these issues might to out-flank their competitors. However, the hybrid be resolved, with the ultimate goal of making life cloud operating environment can be complex, with easier for developers through more efficient cloud Kubernetes, containers, microservices, and service development options. When the working group was meshes adding a host of new considerations to formally announced in October of 2019, Brad Micklea, application design and implementation. Red Hat is then VP of Developer Tools and Advocacy at Red Hat, working with the Eclipse Cloud DevTools Working confirmed the need to leverage open source software Group to provide new open source alternatives to these to streamline and accelerate cloud development. technology stacks while giving developers the tools they need to get their software to market faster.” “Developers today are building applications for the hybrid cloud,” said Micklea. “They are focused on COPYRIGHT (C) 2021, ECLIPSE FOUNDATION, INC. | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0) 5 Eclipse Foundation White Paper History Is Repeating Itself in the Best Possible Way “The breadth, depth, and According to Dr. Jonas Helming, principal software diversity in the Eclipse cloud architect and general manager of EclipseSource, the development ecosystem Eclipse Foundation was the logical place to create an make it the place to be for ecosystem around cloud development tools. any person or organization “For almost 20 years, the Eclipse Foundation ecosystem with a vested interest in around the Eclipse IDE has been the biggest alternative next-generation cloud native to closed developer tools,” he says. “There is currently development.” no comparable ecosystem for cloud development tools — Tim deBoer, Senior Principal and I foresee the Eclipse Cloud DevTools ecosystem Software Engineer at Red Hat making a similar impact as we move more development tools and concepts to the cloud.” Tim deBoer, a senior principal software engineer at Red Hat, was the cloud developer experience lead architect at IBM when the working group was first created. He also draws a parallel to the success of the Eclipse IDE ecosystem by pointing out that the vendor neutral governance at the Eclipse Foundation enables success. Organizations in any market, even competitors, can freely collaborate on new technology development, with each company providing a different piece of the overall solution. “By pooling our resources, everyone in the ecosystem can achieve more,” says deBoer. “The breadth, depth, and diversity in the Eclipse cloud development ecosystem make it the place to be for any person or organization with a vested interest in next-generation cloud native development.” COPYRIGHT (C) 2021, ECLIPSE FOUNDATION, INC. | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0) 6 Eclipse Foundation White Paper Flexible, Open Source Technologies Streamline and Accelerate Cloud Development rojects hosted and nurtured by the Eclipse Cloud DevTools Working Group provide open source technologies that are the basis for building enterprise cloud development P products. Each of the project technologies can be used individually or together. And they can be adapted to suit the adopter organization’s environment and developer requirements. This flexibility allows adopter organizations to go well beyond the potential they can achieve with proprietary, single-vendor cloud development tools. Eclipse Cloud DevTools Landscape Here’s a brief overview of the current projects in the Extension Marketplace Cloud DevTools ecosystem, Web IDE their relationships to one another, along with use Dev Tools cases and commercial adoption examples. Sprotty Figure 1 loosely illustrates Che4z working group projects and the high-level GLSP IDE Technologies functional focus areas of Container Deployment Tools Function Specific Tools each project. Figure 1: Projects in the Eclipse Cloud DevTools Ecosystem COPYRIGHT (C) 2021, ECLIPSE FOUNDATION, INC. | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0) 7 Eclipse Foundation White Paper Eclipse Theia: The Open Source Alternative to Visual Studio Code Eclipse Theia is an extensible platform that allows companies to develop their own multi-language cloud and desktop IDEs using a single, open source technology stack. The software combines many of the great user interface features in Visual Studio (VS) Code with a more modular architecture that enables far more customizations than VS Code. Eclipse Theia is the basis for well-known industry offerings, including: • ARM Mbed Studio • Arduino Pro IDE • Google Cloud Shell Eclipse Che eliminates • SAP Business Application Studio the workspace Eclipse Che: A Kubernetes-Native configuration complexities IDE for Cloud Native and challenges with Application Development Kubernetes-native Eclipse Che eliminates the workspace configuration development so it’s faster complexities and challenges with Kubernetes-native and easier for developer development so it’s faster and easier for developer teams to build cloud native teams to build cloud native applications. Che also applications. leverages Theia software to provide an in-browser VS Code experience, and is the basis for well-known industry offerings, including: Eclipse Che4z, is a lightweight, hosted IDE based on Eclipse Che. With Che4z, it’s faster and easier for • IBM Cloud Pak for Applications the new generation of developers to get involved in • Red Hat OpenShift + CodeReady Workspaces mainframe application development. Che4z is the basis for Broadcom’s CA Brightside, a DevOps solution • SAP Hana Cloud that enables development teams to control, script, and develop cloud-based apps for mainframes. COPYRIGHT (C) 2021, ECLIPSE FOUNDATION, INC. | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0) 8 Eclipse Foundation White Paper Eclipse Open VSX: A Vendor It can be easily defined as the default extension registry Neutral Marketplace for for any technology or tool that supports VS Code Visual Studio Code Extensions extensions. Eclipse Open VSX provides a free marketplace for VS For more insight into why industry leaders are moving Code extensions that can be used with any technology beyond walled gardens to embrace Open VSX,
Load more

Recommended publications
  • Alnao Debian Handbook
    AlNao Debian HandBook Nao Alberto (www.alnao.it) December 5, 2020 AlNao Debian 10 HandBook Autore Nao Alberto ([email protected]) Disponibile su www.alnao.it Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Docu- mentation License, Version 1.2 or any later version published by the Free Software Foundation. E` garantito il permesso di copiare, distribuire e/o modificare questo documento in base ai termini della GNU Free Documentation License, Versione 1.2 o ogni versione successiva pubblicata dalla Free Software Foundation. Scritto da Nao Alberto (www.alnao.it - [email protected]) con LATEX con l'editor Kile Forse un giorno riuscir`oa finire questa maledetta cosa che chiamo manuale Prima edizione (solo appunti, versione Debian 3.1 Sarge): 2006 Seconda edizione (versione Debian 4 Etch): 2008 Terza edizione (in inglese, incompleta, Debian 5): 2011/2012 Quarta edizione (versione Debian 8): 2015/2016 Quinta edizione (versione Debian 9): 2018 Sesta edizione (versione Debian 10): 2020 Contents 1 Introduzione 7 1.1 Perch`equesto manuale? . 7 1.2 Perch´eLinux? . 7 1.3 Note e Convenzioni . 8 1.4 Correttezza di questo manuale . 9 2 Installazione di Debian 10 2.1 Come e dove trovare Debian . 10 2.1.1 Le versioni di Debian . 11 2.2 Avvio dell'installazione . 11 2.3 Configurazioni del sistema (rete, partizioni ed utenti) . 12 2.4 Copia del sistema base e impostazioni finali . 12 2.5 Il primo avvio . 13 2.6 Installazione dalla versione live . 13 3 Configurazioni base 15 3.1 Gestione di cartelle e file .
    [Show full text]
  • 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]
  • An Overview of Platforms for Cloud Based Development G
    Fylaktopoulos et al. SpringerPlus (2016) 5:38 DOI 10.1186/s40064-016-1688-5 REVIEW Open Access An overview of platforms for cloud based development G. Fylaktopoulos1, G. Goumas2, M. Skolarikis1, A. Sotiropoulos3 and I. Maglogiannis4* Abstract This paper provides an overview of the state of the art technologies for software development in cloud environments. The surveyed systems cover the whole spectrum of cloud-based development including integrated programming environments, code repositories, software modeling, composition and documentation tools, and application man- agement and orchestration. In this work we evaluate the existing cloud development ecosystem based on a wide number of characteristics like applicability (e.g. programming and database technologies supported), productiv- ity enhancement (e.g. editor capabilities, debugging tools), support for collaboration (e.g. repository functionality, version control) and post-development application hosting and we compare the surveyed systems. The conducted survey proves that software engineering in the cloud era has made its initial steps showing potential to provide con- crete implementation and execution environments for cloud-based applications. However, a number of important challenges need to be addressed for this approach to be viable. These challenges are discussed in the article, while a conclusion is drawn that although several steps have been made, a compact and reliable solution does not yet exist. Keywords: Cloud computing, Integrated Development Environment (IDE), Code repositories, Software modeling, Orchestration tools Background application side, large families of applications including Within the past few years, cloud computing has emerged desktop, business, entertainment (Simmhan et al. 2010; as a dominant computing model in IT infrastructures, Schmidt 2012; Hobfeld et al.
    [Show full text]
  • Eclipse Theia Vs Che Vs VS Code.Pdf
    Eclipse Theia vs Che vs VS Code Jonas Helming EclipseSource © 2020 EclipseSource | https://eclipsesource.com | Dr. Jonas Helming | Eclipse Theia vs Che vs VS Code 1 Agenda ● VS Code vs. Eclipse Theia ● VS Codespaces vs. Eclipse Che ● Conclusion © 2020 EclipseSource | https://eclipsesource.com | Dr. Jonas Helming | Eclipse Theia vs Che vs VS Code 2 Eclipse Theia vs. VS Code (online, project) © 2020 EclipseSource | https://eclipsesource.com | Dr. Jonas Helming | Eclipse Theia vs Che vs VS Code 3 What is VS Code? ● An extensible Code Editor / IDE ○ Free of charge / built on open source ○ Thousands of extensions available ○ Downloadable desktop tool © 2020 EclipseSource | https://eclipsesource.com | Dr. Jonas Helming | Eclipse Theia vs Che vs VS Code 4 What is the VS Code project? ● The open source project, which is the base of VS Code ○ Very active development and innovation ○ Driven by Microsoft + contributors ○ Use by other tools such as: ■ VS Codium ■ Eclipse Theia © 2020 EclipseSource | https://eclipsesource.com | Dr. Jonas Helming | Eclipse Theia vs Che vs VS Code 5 What is “VS Code Online”? ● Online version of VS Code hosted in VS Codespaces ○ Runs in the browser ○ Bound to Azure ○ Currently not open source © 2020 EclipseSource | https://eclipsesource.com | Dr. Jonas Helming | Eclipse Theia vs Che vs VS Code 6 What is Eclipse Theia? ● An open source platform for building web-based tools and IDEs ○ Supports local and cloud/online deployment ○ A modular and flexible architecture ○ Project fully open source and hosted at the Eclipse Foundation © 2020 EclipseSource | https://eclipsesource.com | Dr. Jonas Helming | Eclipse Theia vs Che vs VS Code 7 Product vs.
    [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]
  • 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]
  • An Intro to Eclipse Che Next-Generation Eclipse IDE & Open Source Alternative to Intellij
    An Intro to Eclipse Che Next-Generation Eclipse IDE & Open Source Alternative to IntelliJ January 2016 Tyler Jewell, Eclipse Che Project Lead @TylerJewell The Application Trinity Develop Apps Deliver Apps Host Apps check out & issue mgmt source code repo unit test quality control test build code pre-production agile ide package & integration deploy to test production archiving testing environment deploy to pre- acceptance deploy to production testing production continuous packaging & code quality integration build tools analysis testing artifact release mgmt workspace frameworks repository 100 firms including Atlassian, JetBrains, Puppet, Chef, Ansible, ZeroTurnaround, IBM, Electric Cloud, Coverity, Sonatype, JFrog, and so on... Big Hairy Audacious Goal Let anyone contribute to any project anywhere at any time. no pre-installation required ready to participate in any branch flow always compiles and runs How http://someurl/factory?id=a_project 1. Create new, or load existing, workspace 2. Populate workspace with projects 3. Fetch source 4. Inject tools (compiler, ssh, intellisense) 5. Create runtime 6. Onboard developer into workspace A New Workspace Is Needed Eclipse Che - Next Generation Eclipse IDE Che: IDE + Workspace Server + Plug-Ins Cloud IDE Collaborative WS Server Plug-In Framework A no-installation browser IDE and Host Eclipse Che as a workspace Che includes a growing set of plug- IOE accessible from any local or server. Share tools, runtime and ins. You can also create and remote device. Thin, fast, and programming services across
    [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]
  • Don't Build and Push, Move Your Inner Loop to Your Cluster!
    Don't build and push, move your inner loop to your cluster! RAMIRO BERRELLEZA | @RBERRELLEZA Hey everyone! • Co-founder of Okteto. • Former architect @ Atlassian, Software Engineer @ Azure. • @rberrelleza in most places. Application architecture has evolved a lot in the past few years... Challenges Challenges We solved production*, but at the expense of the development experience. Building Cloud Native Applications is hard. An inner loop full of friction makes it harder to develop even the simpler features. https://twitter.com/ellenkorbes/status/1143451907492 655105 Community Automate the inner loop • Skaffold • Draft • Garden • Tilt Community Dev environments on demand • Visual Studio Code Online • Code Ready workspaces (Eclipse Che) • Jenkins X But we're still waiting on builds and deploys. … and dev, stage and prod are completely different We started Okteto to give us a better developer experience in Kubernetes Demo time! • https://github.com/rberrelleza/movies-demo How does it work? With okteto you get • A manifest + container development environment • Automatic file synchronization between local and remote env • A remote terminal into your development environment • Forward and Reverse port-forwarding • Integration JetBrain and VSCode's remote development modes • Single binary, works on linux, macos and windows Developing in the same environment as your applications are going to run lets you go way faster. You are not waiting on builds and deploys. And you’re fully integrated from the very beginning. You can leverage the entire platform as well as your stack’s toolkit. Incremental builds. Hot reloaders. Debuggers! Okteto works with anything that speaks Kubernetes • Local clusters: Minikube, k3s, kind • Remote clusters: EKS, GKE, AKS, Digital Ocean, Civo • Kubernetes Manifests • Helm • Serverless functions • ….
    [Show full text]
  • Introducing the Eclipse Foundation Specification Process
    Introducing the Eclipse Foundation Specification Process 1 Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0) Agenda • Background • Creating the EFSP • What is a Specification? • Eclipse Foundation Specification Process • EFSP and the JCP • Certification 2 Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0) Background 3 Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0) Why are we doing this? • Opportunity meets necessity • Java EE migration to Eclipse Foundation requires a spec process to replace the JCP • We expect that this process will be used elsewhere 4 Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0) What’s the Big Deal? Specifications • Guides you to implement collectively developed idea • Support multiple implementations • Allow for interoperability 5 Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0) Guiding Principles • “Code First” • No more “Spec Lead” • Specifications run as open source projects • “Compatible” implementations, rather than one “Reference” implementation • Self-certification • Branding for compatible implementations of Profiles 6 Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0) Jakarta EE Spec Process: 2018 Key deliverables • Establish spec process for existing (JCP) and new specs • Compatibility process • Brand licensing 7 Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0) Creating the EFSP 8 Copyright (c) 2018, Eclipse Foundation, Inc.
    [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]
  • IP Issues in Open Source
    IP Issues in Open Source Eclipse Banking Day Janet Campbell Jeffrey D. Neuburger Eclipse Foundation Inc. PROSKAUER ROSE LLP Legal Counsel & Manager, IP Partner Key Areas of Focus 2 (c) Eclipse Foundation Inc. 11/18/2008 Open Source Software Software that is distributed with its source code (or an offer for it) under a license agreement that allows for its use and modification. 1. “Permissive” or “Attribution” Open Source License Agreements E.g, BSD License 2. “Copyleft” Open Source License Agreements E.g., EPL, MPL Distribution is not a requirement; licensees can use internally without obligations. 3 (c) Eclipse Foundation Inc. 11/18/2008 Open Source Initiative Determined by 1. Free Redistribution the License No fees or royalties Characteristics. 2. Source Code Included and Redistributable Defined by the 3. Derived Works Open Source Allowed and redistributable under same Initiative terms. 4. Integrity of The Author's Source Code The license must permit distribution of http://www.open software built from modified source code. source.org/docs/ osd 5. No Discrimination Against Persons or Groups The license must not discriminate against any person or group of persons. 4 (c) Eclipse Foundation Inc. 11/18/2008 Open Source Initiative Cont… 6. No Discrimination Against Fields of Determined by Endeavor the License Can’t restrict commercial use for example. Characteristics. 7. Distribution of License Must be self standing and not require a Defined by the non-disclosure or other agreement Open Source 8. License Must Not Be Specific to a Initiative Product The rights attached to the program must not depend on the program's being part of a particular software distribution.
    [Show full text]