DOCSLIB.ORG

Advanced Programming with Java Why a Build Tool for Java? Apache Ant Enter Apache Maven

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Advanced Programming with Java Why a Build Tool for Java? Apache Ant Enter Apache Maven Advanced Programming with Java Why a build tool for Java? As an application scales in size, its build process must be Apache Maven provides developers with a automated standard set of tools and conventions for building and deploying Java applications. Maven manages the integration of third-party libraries in The UNIX make utility has been around for years a project and provides a plug-in architecture that User specifies the dependencies among various allows new tools and reports to be easily • integrated into a project’s build system. application components in a “makefile” The make program analyzes those dependencies and • Building Java applications with Maven rebuilds components as necessary Don’t have to rebuild the entire product when you • A history of building Java projects only change one source file • Make doesn’t fit well with Java Maven: building, testing, and reporting • Dependencies among Java files are complex • Make is rarely platform independent • Syntax of makefiles is wiggy • Copyright ©2008-2021 by David M. Whitlock. Permission to make digital or hard copies of part or all of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and full citation on the first page. To copy otherwise, to republish, to post on servers, or to redistribute to lists, requires prior specific permission and/or fee. Request permission to publish from [email protected]. Last updated March 14, 2021. 1 2 Apache Ant Enter Apache Maven The Apache Foundation developed Ant in 2000 to build Developers noticed common patterns in the projects that their Java projects they built Ant provides the building blocks for compiling, Running unit tests as part of every build • assembling, and testing a Java project • Generating reports and documentation about the Ant has tasks that invoke tools like javac, javac, and • project • javadoc Versioning the software and deploying it to a central Tasks are grouped together into build targets that are • location so it can be shared • configured in an XML file that specifies source file locations and class paths Apache Maven was developed to provide a standard build environment that could be used by many projects Ant worked very well, but... Each project produces some artifact (jar file, web Each project had its own build procedure with • application, etc.) from source code • different directory layouts and naming conventions Unit tests are fully integrated into the project – Ramp-up time for new developers • Third-party libraries are automatically downloaded Dependencies on third-party libraries had to be • • managed by individual projects and placed on the classpath – Jar files were often checked into CVS along with Artifacts and supporting information (documentation source code • and reports) can be published to a centralized repository for consumption by others – Often difficult to determine which version of the library was used 3 4 Getting started with Maven Layout of a Maven project Maven can be downloaded from Maven defines a standard layout the project’s source files*. http://maven.apache.org +- proj1/ +- pom.xml The mvn command line tool executes Maven +- src/ +- main/ A new Java project can be created using a Maven +- java/ (Base dir for source code) “archetype” +- edu/pdx/cs410J/whitlock/ +- resources/ (Files on classpath) +- META-INF/MANIFEST.MF $ mvn archetype:create \ +- test/ -DgroupId=edu.pdx.cs410J.whitlock \ +- java/ (Base dir for test code) -DartifactId=proj1 +- edu/pdx/cs410J/whitlock/ +- resources/ (Files on test classpath) This generates a very simple Java project that can be +- site/ (Files for web site) built with Maven +- site.xml (Describes site) +- apt/ (Supplementary site files) $ find proj1 -type f +- resources/ proj1/pom.xml +- css/ proj1/src/main/java/edu/pdx/cs410J/whitlock/App.java +- site.css proj1/src/test/java/edu/pdx/cs410J/whitlock/AppTest.java +- images/ +- target/ +- proj1-1.0.jar (Project artifact) pom.xml is the Maven ”Project Object Model” +- surefire-reports/ (Unit test output) configuration file that specifies how the project is built +- site/ (Generated web site) *The layout can be configured, if necessary. 5 6 What can you do with Maven? Looking at pom.xml Maven defines several build “phases” that perform <project xmlns=’’http://maven.apache.org/POM/4.0.0’’ common tasks xmlns:xsi=’’http://www.w3.org/2001/XMLSchema-instance’’ xsi:schemaLocation=’’http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd’’> mvn compile Compiles Java source code in <modelVersion>4.0.0</modelVersion> <groupId>edu.pdx.cs410J.whitlock</groupId> src/main/java <artifactId>proj1</artifactId> mvn test Recompiles necessary source <packaging>jar</packaging> code and runs unit tests <version>1.0-SNAPSHOT</version> mvn package After running unit tests, builds a <name>proj1</name> <url>http://maven.apache.org</url> jar file with the compiled source <dependencies> code <dependency> mvn site Generates a web site for the <groupId>junit</groupId> <artifactId>junit</artifactId> project with information gleaned <version>3.8.1</version> from pom.xml <scope>test</scope> mvn clean Deletes all build artifacts </dependency> mvn eclipse:eclipse Generates an Eclipse project </dependencies> based on the Maven project </project> This POM configures version 1.0-SNAPSHOT of proj1 Build artifacts are placed in the target directory released by the edu.pdx.cs410J.whitlock organization. The project builds a jar file and its tests depend on version 3.8.1 of junit. 7 8 Information about the project Managing dependencies The POM can contain several pieces of information about A project often requires third-party libraries to do its work. the project that Maven uses for various purposes* A POM specifies what libraries the project depends on and Maven downloads them as needed. name The name of the project (often a code <dependency> name such as “Guatemala”) <groupId>junit</groupId> description General description of project <artifactId>junit</artifactId> url URL where users can learn more <version>3.8.1</version> <scope>test</scope> about project </dependency> inceptionYear When project was started The scope element determine which build phase the You can also include information about the project dependency applies to compile (default): library and all of its dependencies Organization that develops the project (name, url) • • are available to all build phases Developers and contributes (id, name, email, role, a • runtime not required for compilation; only needed to picture URL) • execute tests and run project License under which it is distributed provided: only needed at compile time; someone • • else provides it at runtime Bug tracking system, Mailing lists • test: only needed to compile and run tests • Source code repository, Automated build server • system: library is not available in repository • *These are XML elements that are children of the top-level project – Location is provided by the systemPath POM element. element 9 10 Repositories Local Repository Maven specifies a layout for repositories of deployed Maven downloads project dependencies to a local artifacts repository that resides in your home directory: The layout of the repository is based on the artifact’s ${user.home}/.m2/repository • group id, version, and id The JUnit 3.8.1 artifact is located at When resolving a project dependency, Maven will search • junit/junit/3.8.1/junit-3.8.1.jar the local repository before searching other repositories. Running mvn with -o or --offline will prevent it from The repository also contains a copy of the artifact’s • • POM so that artifacts that it depends on can be accessing remote repositories resolved By default, Maven will search for an artifact in a public repository: http://repo1.maven.org/maven2/ A POM can also specify repositories to search: <repositories> <repository> <id>CS410J</id> <name>CS410J Maven Repository</name> <url>http://web.cecs.pdx.edu/~whitlock/repository/maven2</url> </repository> </repositories> 11 12 Build phases Build Goals A Maven build consists of a number of phases (each Each build phase consists of goals that perform some phase depends on the previous) build task like compiling source code, running tests, or building a jar file validate Validates pom.xml and downloads necessary dependencies Each phase has a default goal that depends on the projects packaging (jar, war, etc.) compile Compiles the source code test Tests the source code (can’t require compile compile:compile that code be packaged) test-compile compiler:testCompile package Builds the project artifact (jar file) test surefire:test integration-test Deploys the artifact (e.g. to a web package jar:jar server) for integration testing verify Makes sure that artifact meets quality Maven plugins are artifacts that provide goals to a Maven criteria (coding standards, etc.) build install Copies artifacts to the local Maven repository for use in other local The plugin for compiling Java source has two goals: • main compiler:compile projects one for the code ( ) and other for test code (compiler:testCompile) deploy Publishes artifacts to remote Maven repository for use by others Plugins are configured in the POM and must be • associated with a build phase Each build phase is dependent on the previous Information about the standard Maven plugins can be Running mvn package will invoke validate, found at: • compile, and test http://maven.apache.org/plugins/index.html 13 14 Compiling Source Code Running Tests Running mvn
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]
  • 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]
  • 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]
  • 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]
  • 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]
  • Maven Vs Gradle
    Maven vs Gradle This is a working document on the topic of converting from gradle to maven. If you add items / questions / etc, please tag and maybe color it (e.g., <dl>...) to make it easier to track things. Open questions / issues are in red. At a high level the motivations are: improve consumability of Edgent by users add publishing of signed Edgent binary release artifacts (JAR, WAR) in maven repos ultimately cease creating signed binary release bundles (tgz) simplify the build tooling the gradle scripting has some non-standard / complicated processing either out of ignorance or to achieve certain things TODO add the "why the complications" note here. (manifest classpath, binary bundle tgz with transitive deps, ...) Suspect that to simplify maven based tooling we'd need to eliminate some of those things (which would also simplify gradle stuff) Chris Dutz created PR-309 for working on a maven based system. PR-309 now includes a maven wrapper (mvnw). Set JAVA_HOME and then use "mvnw" instead of "mvn" below and you don't have to manually install maven. Or, to manually install maven https://maven.apache.org/download.cgi https://maven.apache.org/install.html Maven concepts: lifecycles, phases, goals, plugins High level building and testing mvn clean install # builds and tests add -DskipTests to omit testing, --fail-at-end for "continue"-like mvn clean package # a bit fewer phases than install mvn clean compile # even fewer/faster mvn site:site site:staging # see target/stagingindex.html mvn dependency:copy-dependencies # copies all dep
    [Show full text]
  • Apache Maven Cookbook I
    Apache Maven Cookbook i Apache Maven Cookbook Apache Maven Cookbook ii Contents 1 Maven Tutorial for Beginners 1 1.1 Introduction......................................................1 1.2 Prerequisites......................................................1 1.3 Installing maven....................................................1 1.4 Creating an example project.............................................2 1.5 Importing generated project into eclipse.......................................2 1.6 Maven config files. POM file.............................................5 1.7 Building the project..................................................6 1.8 Conclusions......................................................9 2 How to Use Maven For Dependency Management 10 2.1 Environment...................................................... 10 2.2 Maven for Dependency Management......................................... 10 2.3 Transitive Dependency................................................ 10 2.4 Dependency Scope.................................................. 11 2.5 Dependency Management.............................................. 11 2.6 System Dependencies................................................. 14 2.7 Conclusion...................................................... 14 2.8 Related Articles.................................................... 14 3 Difference Between ANT and Maven 15 3.1 Introduction...................................................... 15 3.2 High level comparision................................................ 15 3.2.1
    [Show full text]
  • Maven Quick Guide
    MMAAVVEENN -- QQUUIICCKK GGUUIIDDEE http://www.tutorialspoint.com/maven/maven_quick_guide.htm Copyright © tutorialspoint.com MMAAVVEENN -- OOVVEERRVVIIEEWW What is Maven? Maven is a project management and comprehension tool. Maven provides developers a complete build lifecycle framework. Development team can automate the project's build infrastructure in almost no time as Maven uses a standard directory layout and a default build lifecycle. In case of multiple development teams environment, Maven can set-up the way to work as per standards in a very short time. As most of the project setups are simple and reusable, Maven makes life of developer easy while creating reports, checks, build and testing automation setups. Maven provides developers ways to manage following: Builds Documentation Reporting Dependencies SCMs Releases Distribution mailing list To summarize, Maven simplifies and standardizes the project build process. It handles compilation, distribution, documentation, team collaboration and other tasks seamlessly. Maven increases reusability and takes care of most of build related tasks. Maven History Maven was originally designed to simplify building processes in Jakarta Turbine project. There were several projects and each project contained slightly different ANT build files. JARs were checked into CVS. Apache group then developed Maven which can build multiple projects together, publish projects information, deploy projects, share JARs across several projects and help in collaboration of teams. Maven Objective Maven primary goal is to provide developer A comprehensive model for projects which is reusable, maintainable, and easier to comprehend. plugins or tools that interact with this declarative model. Maven project structure and contents are declared in an xml file, pom.xml referred as Project Object Model POM, which is the fundamental unit of the entire Maven system.
    [Show full text]
  • Log4j User Guide
    ...................................................................................................................................... Apache Log4j 2 v. 2.14.1 User's Guide ...................................................................................................................................... The Apache Software Foundation 2021-03-06 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 . 17 6. Configuration . 20 7. Web Applications and JSPs . 62 8. Plugins . 71 9. Lookups . 75 10. Appenders . 87 11. Layouts . 183 12. Filters . 222 13. Async Loggers . 238 14. Garbage-free Logging . 253 15. JMX . 262 16. Logging Separation . 269 17. Extending Log4j . 271 18. Programmatic Log4j Configuration . 282 19. Custom Log Levels . 290 © 2 0 2 1 , 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 2 1 , 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]
  • Licensing Information User Manual
    Oracle® Hospitality Payment Interface License Information User Manual Release 20.3 F35686-01 December 2020 Oracle Hospitality Payment Interface License Information User Manual Release 20.3 F35686-01 Copyright © 2020, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • Apache Maven Current Version User Guide
    ...................................................................................................................................... Apache Maven Current version User Guide ...................................................................................................................................... The Apache Software Foundation 2009-10-16 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 What is Maven? . 1 3 Features . 3 4 FAQ . 4 5 Community Overview . 11 5.1 How to Contribute . 13 5.2 Getting Help . 15 5.3 Issue Tracking . 17 5.4 Source Repository . 18 5.5 Continuous Integration . 20 6 Running Maven . 21 7 Maven Plugins . 23 8 User Centre . 30 8.1 Maven in 5 Minutes . 31 8.2 Getting Started Guide . 35 8.3 POM Reference . 57 8.4 Settings Reference . 91 8.5 Guides . 100 8.5.1 The Build Lifecycle . 103 8.5.2 The POM . 111 8.5.3 Profiles . 123 8.5.4 Repositories . 133 8.5.5 Standard Directory Layout . 136 8.5.6 The Dependency Mechanism . 137 8.5.7 Plugin Development . 153 8.5.8 Configuring Plug-ins . 156 8.5.9 The Plugin Registry . 169 8.5.10 Plugin Prefix Resolution . 172 8.5.11 Developing Ant Plugins . 174 8.5.12 Developing Java Plugins . 188 8.5.13 Creating a Site . 198 8.5.14 Snippet Macro . 203 8.5.15 What is an Archetype . 205 8.5.16 Creating Archetypes . 207 8.5.17 From Maven 1.x to Maven 2.x . 210 8.5.18 Using Maven 1.x repositories with Maven 2.x . 213 8.5.19 Relocation of Artifacts . 214 8.5.20 Installing 3rd party JARs to Local Repository .
    [Show full text]