DOCSLIB.ORG

Maven: the Complete Reference I

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Maven: the Complete Reference I Maven: The Complete Reference i Maven: The Complete Reference Ed. 1.0 Maven: The Complete Reference 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: The Complete Reference iii 2.3.1 Installing Maven on Linux, BSD or Mac OSX................... 12 2.3.2 Installing Maven on Microsoft Windows...................... 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 The Project Object Model 18 3.1 Introduction......................................... 18 3.2 The POM.......................................... 18 3.2.1 The Super POM.................................. 21 3.2.2 The Simplest POM................................. 25 3.2.3 The Effective POM................................. 26 3.2.4 Real POMs..................................... 26 3.3 POM Syntax......................................... 26 3.3.1 Project Versions.................................. 27 Maven: The Complete Reference iv 3.3.1.1 Version Build Numbers......................... 27 3.3.1.2 SNAPSHOT Versions.......................... 28 3.3.2 Property References................................ 28 3.4 Project Dependencies.................................... 30 3.4.1 Dependency Scope................................. 31 3.4.2 Optional Dependencies............................... 32 3.4.3 Dependency Version Ranges............................ 34 3.4.4 Transitive Dependencies.............................. 35 3.4.4.1 Transitive Dependencies and Scope................... 35 3.4.5 Conflict Resolution................................. 36 3.5 Project Relationships.................................... 40 3.5.1 More on Coordinates................................ 40 3.5.2 Project Inheritance................................. 42 3.6 POM Best Practices..................................... 44 3.6.1 Grouping Dependencies.............................. 45 3.6.2 Multi-module vs. Inheritance........................... 47 3.6.2.1 Simple Project.............................. 47 3.6.2.2 Multi-module Enterprise Project.................... 49 Maven: The Complete Reference v 4 The Build Lifecycle 52 4.1 Introduction......................................... 52 4.1.1 Clean Lifecycle (clean)............................... 53 4.1.2 Default Lifecycle (default)............................. 56 4.1.3 Site Lifecycle (site)................................. 57 4.2 Package-specific Lifecycles................................. 58 4.2.1 JAR......................................... 59 4.2.2 POM........................................ 59 4.2.3 Maven Plugin.................................... 60 4.2.4 EJB......................................... 60 4.2.5 WAR........................................ 61 4.2.6 EAR........................................ 61 4.2.7 Other Packaging Types............................... 62 4.3 Common Lifecycle Goals.................................. 63 4.3.1 Process Resources................................. 63 4.3.2 Compile....................................... 67 4.3.3 Process Test Resources............................... 68 4.3.4 Test Compile.................................... 68 Maven: The Complete Reference vi 4.3.5 Test......................................... 69 4.3.6 Install........................................ 70 4.3.7 Deploy....................................... 70 5 Build Profiles 71 5.1 What Are They For?.................................... 71 5.1.1 What is Build Portability.............................. 71 5.1.1.1 Non-Portable Builds........................... 72 5.1.1.2 Environment Portability......................... 72 5.1.1.3 Organizational (In-House) Portability.................. 72 5.1.1.4 Wide (Universal) Portability....................... 73 5.1.2 Selecting an Appropriate Level of Portability................... 73 5.2 Portability through Maven Profiles............................. 74 5.2.1 Overriding a Project Object Model......................... 76 5.3 Profile Activation...................................... 77 5.3.1 Activation Configuration.............................. 79 5.3.2 Activation by the Absence of a Property...................... 80 5.4 Listing Active Profiles................................... 81 5.5 Tips and Tricks....................................... 81 Maven: The Complete Reference vii 5.5.1 Common Environments.............................. 82 5.5.2 Protecting Secrets.................................. 84 5.5.3 Platform Classifiers................................. 85 5.6 Summary.......................................... 87 6 Running Maven 88 6.1 Maven Command Line Options............................... 88 6.1.1 Defining Properties................................. 88 6.1.2 Getting Help.................................... 89 6.1.3 Using Build Profiles................................ 90 6.1.4 Displaying Version Information.......................... 90 6.1.5 Running in Offline Mode.............................. 91 6.1.6 Using a Custom POM or Custom Settings File.................. 91 6.1.7 Encrypting Passwords............................... 91 6.1.8 Dealing with Failure................................ 92 6.1.9 Controlling Maven’s Verbosity........................... 92 6.1.10 Running Maven in Batch Mode.......................... 93 6.1.11 Downloading and Verifying Dependencies..................... 93 6.1.12 Non-recursive Builds................................ 94 Maven: The Complete Reference viii 6.2 Using Advanced Reactor Options.............................. 94 6.2.1 Advanced Reactor Options Example Project.................... 95 6.2.2 Resuming Builds.................................. 97 6.2.3 Specifying a Subset of Projects........................... 97 6.2.4 Making a Subset of Projects............................ 98 6.2.5 Making Project Dependents............................ 98 6.2.6 Resuming a "make" build............................. 99 6.3 Using the Maven Help Plugin................................ 99 6.3.1 Describing a Maven Plugin............................. 100 7 Maven Configuration 103 7.1 Configuring Maven Plugins................................. 103 7.1.1 Plugin Configuration Parameters.......................... 103 7.1.2 Adding Plugin Dependencies............................ 107 7.1.3 Setting Global Plugin Parameters......................... 108 7.1.4 Setting Execution Specific Parameters....................... 108 7.1.5 Setting Default Command Line Execution Parameters.............. 109 7.1.6 Setting Parameters for Goals Bound to Default Lifecycle............. 110 8 Maven Assemblies 112 Maven: The Complete Reference ix 8.1 Introduction......................................... 112 8.2 Assembly Basics...................................... 113 8.2.1 Predefined Assembly Descriptors......................... 114 8.2.2 Building an Assembly............................... 114 8.2.3 Assemblies as Dependencies............................ 117 8.2.4 Assembling Assemblies via Assembly Dependencies............... 118 8.3 Overview of the Assembly Descriptor........................... 122 8.4 The Assembly Descriptor.................................. 123 8.4.1 Property References in Assembly Descriptors................... 123 8.4.2 Required Assembly Information.......................... 123 8.5 Controlling the Contents of an Assembly.......................... 125 8.5.1 Files Section................................... 125 8.5.2 FileSets Section................................ 126 8.5.3 Default Exclusion Patterns for........................... 128 8.5.4 dependencySets Section............................ 129 8.5.4.1 Customizing Dependency Output Location............... 131 8.5.4.2 Interpolation of Properties in Dependency Output........... 132 8.5.4.3 Including and Excluding Dependencies by Scope........... 133 Maven: The Complete Reference x 8.5.4.4 Fine Tuning: Dependency Includes and Excludes........... 135 8.5.4.5 Transitive Dependencies, Project Attachments, and Project...... 137 8.5.4.6 Advanced Unpacking Options...................... 138 8.5.4.7 Summarizing Dependency Sets..................... 140 8.5.5 moduleSets Sections.............................. 140 8.5.5.1 Module Selection............................ 141 8.5.5.2 Sources Section............................. 141 8.5.5.3 Interpolation of outputDirectoryMapping in.......... 143 8.5.5.4 Binaries section............................. 144 8.5.5.5 moduleSets, Parent POMs...................... 146 8.5.6 Repositories Section................................ 146 8.5.7 Managing the Assembly’s Root Directory..................... 147 8.5.8 componentDescriptors
Load more

Recommended publications
  • Log4j-Users-Guide.Pdf
    ...................................................................................................................................... Apache Log4j 2 v. 2.2 User's Guide ...................................................................................................................................... The Apache Software Foundation 2015-02-22 T a b l e o f C o n t e n t s i Table of Contents ....................................................................................................................................... 1. Table of Contents . i 2. Introduction . 1 3. Architecture . 3 4. Log4j 1.x Migration . 10 5. API . 16 6. Configuration . 18 7. Web Applications and JSPs . 48 8. Plugins . 56 9. Lookups . 60 10. Appenders . 66 11. Layouts . 120 12. Filters . 140 13. Async Loggers . 153 14. JMX . 167 15. Logging Separation . 174 16. Extending Log4j . 176 17. Extending Log4j Configuration . 184 18. Custom Log Levels . 187 © 2 0 1 5 , T h e A p a c h e S o f t w a r e F o u n d a t i o n • A L L R I G H T S R E S E R V E D . T a b l e o f C o n t e n t s ii © 2 0 1 5 , T h e A p a c h e S o f t w a r e F o u n d a t i o n • A L L R I G H T S R E S E R V E D . 1 I n t r o d u c t i o n 1 1 Introduction ....................................................................................................................................... 1.1 Welcome to Log4j 2! 1.1.1 Introduction Almost every large application includes its own logging or tracing API. In conformance with this rule, the E.U.
    [Show full text]
  • NASA's Lunar Atmosphere and Dust Environment Explorer (LADEE)
    Geophysical Research Abstracts Vol. 13, EGU2011-5107-2, 2011 EGU General Assembly 2011 © Author(s) 2011 NASA’s Lunar Atmosphere and Dust Environment Explorer (LADEE) Richard Elphic (1), Gregory Delory (1,2), Anthony Colaprete (1), Mihaly Horanyi (3), Paul Mahaffy (4), Butler Hine (1), Steven McClard (5), Joan Salute (6), Edwin Grayzeck (6), and Don Boroson (7) (1) NASA Ames Research Center, Moffett Field, CA USA ([email protected]), (2) Space Sciences Laboratory, University of California, Berkeley, CA USA, (3) Laboratory for Atmospheric and Space Physics, University of Colorado, Boulder, CO USA, (4) NASA Goddard Space Flight Center, Greenbelt, MD USA, (5) LunarQuest Program Office, NASA Marshall Space Flight Center, Huntsville, AL USA, (6) Planetary Science Division, Science Mission Directorate, NASA, Washington, DC USA, (7) Lincoln Laboratory, Massachusetts Institute of Technology, Lexington MA USA Nearly 40 years have passed since the last Apollo missions investigated the mysteries of the lunar atmosphere and the question of levitated lunar dust. The most important questions remain: what is the composition, structure and variability of the tenuous lunar exosphere? What are its origins, transport mechanisms, and loss processes? Is lofted lunar dust the cause of the horizon glow observed by the Surveyor missions and Apollo astronauts? How does such levitated dust arise and move, what is its density, and what is its ultimate fate? The US National Academy of Sciences/National Research Council decadal surveys and the recent “Scientific Context for Exploration of the Moon” (SCEM) reports have identified studies of the pristine state of the lunar atmosphere and dust environment as among the leading priorities for future lunar science missions.
    [Show full text]
  • Introduction to Apache Maven 2 Skill Level: Intermediate
    Introduction to Apache Maven 2 Skill Level: Intermediate Sing Li ([email protected]) Author Wrox Press 19 Dec 2006 Modern software projects are no longer solely monolithic creations of single local project teams. With the increased availability of robust, enterprise-grade open source components, today's software projects require dynamic collaboration among project teams and often depend on a mix of globally created and maintained components. Now in its second generation, the Apache Maven build system -- unlike legacy build tools created before the Internet-enabled era of global software development -- was designed from the ground up to take on these modern challenges. This tutorial gets you started with Maven 2. Section 1. Before you start Modern software development based on robust, enterprise-grade open source technologies requires a new breed of build and project collaboration tool. The engine at the core of Apache Maven 2 works to simplify building and managing large and often complex collaborative software projects. Yet Maven 2's design aims to be friendly even to developers unfamiliar with the challenges of working in large project team environments. Focusing initially on the beginner single developer, this tutorial gradually introduces some of the collaborative concepts and features that are available with Maven 2. You are encouraged to build on the introduction this tutorial provides by exploring the advanced features of Maven 2 that are beyond its scope. About this tutorial This tutorial guides you step-by-step through the fundamental concepts and hands-on exercises with Maven 2: • Overview of Maven 2 Introduction to Apache Maven 2 © Copyright IBM Corporation 1994, 2008.
    [Show full text]
  • Apache Ant Best Practices
    08_Lee_ch05.qxd 5/3/06 5:12 PM Page 81 C HAPTER 5 Apache Ant Best Practices This chapter looks in more detail at some best practices for using Ant on real projects. First I describe the use of property files to enable configuration of the build process depending on a user’s role and requirements. I then describe how best to integrate Ant with IBM Rational ClearCase. Finally, I look at some general best practices for supporting the build process on large projects. Aims of This Chapter Apache Ant is a powerful build tool with significant built-in capabilities. However, a few capabil- ities and best practices stand out; they are described here. After reading this chapter, you will be able to • Understand what Ant property files are and how they can be used to make build scripts more maintainable. • Understand how to use Ant’s capabilities to better integrate with IBM Rational ClearCase. • Implement Ant build files that support reuse and maintainability on large projects. This chapter assumes that you are familiar with the basic concepts of Apache Ant that were discussed in Chapter 4, “Defining Your Build and Release Scripts.” Property Files From the perspective of Chapter 4, an Ant build.xml file is a single centralized build file that defines a repeatable process for bringing together an application, usually producing some form of 81 08_Lee_ch05.qxd 5/3/06 5:12 PM Page 82 82 Chapter 5 Apache Ant Best Practices executable output. Although a single build.xml file can be enough to drive the build process, in practice it can quickly become large and unwieldy.
    [Show full text]
  • Hippo Consolidates Its Leadership Status in the Open Source Software Community Submitted By: Prompt Communications Ltd Wednesday, 25 March 2009
    Hippo consolidates its leadership status in the open source software community Submitted by: Prompt Communications Ltd Wednesday, 25 March 2009 – Global software developer comes of age with more than 150 enterprise organisations using its open source CMS & portal software, ten Hippo developers accepted as ‘committers' to Apache projects; and three 'members' of The Apache Software Foundation – San Francisco, CA and Amsterdam, The Netherlands –25 March, 2009 – Hippo (http://www.onehippo.com), a leading vendor of open source Enterprise Content Management and Portal technology, today further demonstrated its leadership in the open source community with the announcement that the tenth member of its Technology Expertise Team has joined with the prestigious status of ‘committer’ to projects of The Apache Software Foundation. Out of its team of over 50 employees, nine others have attained this status, of which three have since received recognition for their technical excellence and contribution by achieving 'member' level. Developers are accepted as committers by the ASF based on the quality and quantity of their contributions to Apache open source development projects. Led by Hippo’s CTO, Arje Cahn, the Hippo Technology Expertise Team includes ASF members and committers to a broad range of Apache projects including Cocoon, Jetspeed, Portals, Wicket, and Jackrabbit. The number of Hippo developers accepted as Apache committers is indicative both of the high levels of technical expertise within the company, and of its commitment to contributing to open source development projects and enriching the world’s store of open source software. The ASF process is meritocratic: to attain committer status, developers have to be voted on by other committers.
    [Show full text]
  • First Year of Coordinated Science Observations by Mars Express and Exomars 2016 Trace Gas Orbiter
    MANUSCRIPT PRE-PRINT Icarus Special Issue “From Mars Express to ExoMars” https://doi.org/10.1016/j.icarus.2020.113707 First year of coordinated science observations by Mars Express and ExoMars 2016 Trace Gas Orbiter A. Cardesín-Moinelo1, B. Geiger1, G. Lacombe2, B. Ristic3, M. Costa1, D. Titov4, H. Svedhem4, J. Marín-Yaseli1, D. Merritt1, P. Martin1, M.A. López-Valverde5, P. Wolkenberg6, B. Gondet7 and Mars Express and ExoMars 2016 Science Ground Segment teams 1 European Space Astronomy Centre, Madrid, Spain 2 Laboratoire Atmosphères, Milieux, Observations Spatiales, Guyancourt, France 3 Royal Belgian Institute for Space Aeronomy, Brussels, Belgium 4 European Space Research and Technology Centre, Noordwijk, The Netherlands 5 Instituto de Astrofísica de Andalucía, Granada, Spain 6 Istituto Nazionale Astrofisica, Roma, Italy 7 Institut d'Astrophysique Spatiale, Orsay, Paris, France Abstract Two spacecraft launched and operated by the European Space Agency are currently performing observations in Mars orbit. For more than 15 years Mars Express has been conducting global surveys of the surface, the atmosphere and the plasma environment of the Red Planet. The Trace Gas Orbiter, the first element of the ExoMars programme, began its science phase in 2018 focusing on investigations of the atmospheric composition with unprecedented sensitivity as well as surface and subsurface studies. The coordination of observation programmes of both spacecraft aims at cross calibration of the instruments and exploitation of new opportunities provided by the presence of two spacecraft whose science operations are performed by two closely collaborating teams at the European Space Astronomy Centre (ESAC). In this paper we describe the first combined observations executed by the Mars Express and Trace Gas Orbiter missions since the start of the TGO operational phase in April 2018 until June 2019.
    [Show full text]
  • Insight Spacecraft Launch for Mission to Interior of Mars
    InSight Spacecraft Launch for Mission to Interior of Mars InSight is a robotic scientific explorer to investigate the deep interior of Mars set to launch May 5, 2018. It is scheduled to land on Mars November 26, 2018. It will allow us to better understand the origin of Mars. First Launch of Project Orion Project Orion took its first unmanned mission Exploration flight Test-1 (EFT-1) on December 5, 2014. It made two orbits in four hours before splashing down in the Pacific. The flight tested many subsystems, including its heat shield, electronics and parachutes. Orion will play an important role in NASA's journey to Mars. Orion will eventually carry astronauts to an asteroid and to Mars on the Space Launch System. Mars Rover Curiosity Lands After a nine month trip, Curiosity landed on August 6, 2012. The rover carries the biggest, most advanced suite of instruments for scientific studies ever sent to the martian surface. Curiosity analyzes samples scooped from the soil and drilled from rocks to record of the planet's climate and geology. Mars Reconnaissance Orbiter Begins Mission at Mars NASA's Mars Reconnaissance Orbiter launched from Cape Canaveral August 12. 2005, to find evidence that water persisted on the surface of Mars. The instruments zoom in for photography of the Martian surface, analyze minerals, look for subsurface water, trace how much dust and water are distributed in the atmosphere, and monitor daily global weather. Spirit and Opportunity Land on Mars January 2004, NASA landed two Mars Exploration Rovers, Spirit and Opportunity, on opposite sides of Mars.
    [Show full text]
  • Building, Deploying and Testing DPES Application
    1 Building, Deploying and Testing DPES application This chapter provides updated instructions for accessing the sources code, developing, building and deploying the DPES application in the user environment. DPES development environment is split into two part 1. Backend DPES webserver – Maven Java Project and 2. DPES Frontend Adobe Flash UI project using flex 3 SDK. The following instruction covers both development environments. 1.1 Development Environment This section is useful for developers who wants to develop the DPES tools by extending some features which are already exists in the project or create some additional new features based users need. Source codes are freely available to the developer community at TIMBUS open source repository i. It is assumed that the developer would have sufficient knowledge on Java, Maven, Eclipse, Version controls such as Git and eGit and flex development. Hence the scope of this document is restricted to detailing DPES application only rather than providing information for setting up the above said technologies. 1.1.1 DPES Webserver System Requirements · Java Development Kit (JDK) (version 1.7_17 or above) ii · Apache Maven plugin for Eclipse (version – 3.2.3) iii · Eclipse IDE for Java EE Developers (version – Juno or later) iv · Tomcat Web Servlet Container ( version – 7 or above) v · EGit plugin for eclipse vi · H2 data base for DPES registry (version – 1.3.173) vii 1.1.2 DPES UI application System Requirements Adobe Flex Development Tools · Flex builder 3 standalone or plugin to eclipse · Flex SDK
    [Show full text]
  • Develop a Simple Web Application with Apache Wicket and Apache
    Develop a simple Web application with Apache Wicket and Apache Geronimo Combine Wicket, Geronimo, and Apache Derby to form an open source Java Web development platform Skill Level: Intermediate Robi Sen ([email protected]) Vice President Department 13 LLC 10 Jul 2007 Apache Wicket is an innovative Java™ Web application framework that was introduced a couple of years ago. It helps simplify Web application development by clearly separating the roles of developers and designers. It lets you remove logical code from the view layer, eliminating the need for JavaServer Pages (JSP), providing a simple plain old Java object (POJO)-centric mode of development, and removing much of the need for XML and other configuration file formats. In this tutorial, learn how to set up your system to develop a simple Web application with Wicket, using Apache Geronimo as your application server and Apache Derby as the embedded database. Section 1. Before you start This tutorial is designed for developers who have found Java frameworks, such as Struts, lacking in needed functionality. If you're interested in developing Web applications in a more object-oriented manner, where the view is clearly separated from logic and there's minimal configuration and mapping, then Wicket is for you! This tutorial walks you through the basics of how Wicket works, while using Apache Geronimo to set up a Java Platform, Enterprise Edition (Java EE) server, Web server, and embedded database in just minutes. Combining Wicket with Geronimo lets you develop data-driven, scalable Web applications using software that's all open source. Develop a simple Web application with Apache Wicket and Apache Geronimo © Copyright IBM Corporation 1994, 2008.
    [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]
  • Explore Digital.Pdf
    EXPLORE “sic itur ad astra” ~ thus you shall go to the stars EXPERTISE FOR THE MISSION We’ve built more interplanetary spacecraft than all other U.S. companies combined. We’re ready for humanity’s next step, for Earth, the Sun, our planets … and beyond. We do this for the New capability explorers. And for us for a new space era Achieving in space takes tenacity. Lockheed Martin brings more We’ve never missed a tight (and finite) capability to the table than ever planetary mission launch window. before, creating better data, new Yet, despite how far we go, the most images and groundbreaking ways to important technologies we develop work. And we’re doing it with smarter improve life now, closer to home. factories and common products, Here on Earth. making our systems increasingly affordable and faster to produce. HALF A CENTURY AT MARS Getting to space is hard. Each step past that is increasingly harder. We’ve been a part of every NASA mission to Mars, and we know what it takes to arrive on another planet and explore. Our proven work includes aeroshells, autonomous deep space operations or building orbiters and landers, like InSight. AEROSHELLS VIKING 1 VIKING 2 PATHFINDER MARS POLAR SPIRIT OPPORTUNITY PHOENIX CURIOSITY INSIGHT MARS 2020 1976 1976 1996 LANDER 2004 2018 2008 2012 2018 2020 1999 ORBITERS MARS OBSERVER MARS GLOBAL MARS CLIMATE MARS ODYSSEY MARS RECONNAISSANCE MAVEN 1993 SURVEYOR ORBITER 2001 ORBITER 2014 1997 1999 2006 LANDERS VIKING 1 VIKING 2 MARS POLAR PHOENIX INSIGHT 1976 1976 LANDER 2008 2018 1999 Taking humans back to the Moon – We bring solutions for our customers that include looking outside our organization to deliver the best science through our spacecraft and operations expertise.
    [Show full text]
  • Open Source and Third Party Documentation
    Open Source and Third Party Documentation Verint.com Twitter.com/verint Facebook.com/verint Blog.verint.com Content Introduction.....................2 Licenses..........................3 Page 1 Open Source Attribution Certain components of this Software or software contained in this Product (collectively, "Software") may be covered by so-called "free or open source" software licenses ("Open Source Components"), which includes any software licenses approved as open source licenses by the Open Source Initiative or any similar licenses, including without limitation any license that, as a condition of distribution of the Open Source Components licensed, requires that the distributor make the Open Source Components available in source code format. A license in each Open Source Component is provided to you in accordance with the specific license terms specified in their respective license terms. EXCEPT WITH REGARD TO ANY WARRANTIES OR OTHER RIGHTS AND OBLIGATIONS EXPRESSLY PROVIDED DIRECTLY TO YOU FROM VERINT, ALL OPEN SOURCE COMPONENTS ARE PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. Any third party technology that may be appropriate or necessary for use with the Verint Product is licensed to you only for use with the Verint Product under the terms of the third party license agreement specified in the Documentation, the Software or as provided online at http://verint.com/thirdpartylicense. You may not take any action that would separate the third party technology from the Verint Product. Unless otherwise permitted under the terms of the third party license agreement, you agree to only use the third party technology in conjunction with the Verint Product.
    [Show full text]