High Quality
Open the downloaded document, and select print from the file menu (PDF reader required).
Better Builds with Maven
The How-to Guide for Maven 2.0
John Casey Vincent MassolBrett PorterCarlos SanchezJason van Zyl
Better Builds with Maven. The How-to Guide for Maven 2.0
© 2006 Mergere, Inc.The contents of this publication are protected by U.S. copyright law and international treaties.Unauthorized reproduction of this publication or any portion of it is strictly prohibited.While every precaution has been taken in the preparation of this book, the publisher and theauthors assume no responsibility for errors or omissions, or for damages resulting from the use ofinformation contained in this book or from the use of programs and source code that mayaccompany it. In no event shall the publisher and the authors be liable for any loss of profit or anyother commercial damage caused or alleged to have been caused directly or indirectly by thisbook.Printed: October 2006 in the USAVersion 1.0.2
Sections
« prev | next »- Preface
- 1. Introducing Maven
- Introducing Maven
- 1.1. Maven Overview
- 1.1.1. What is Maven?
- 1.1.2. Maven's Origins
- 1.1.3. What Does Maven Provide?
- 1.2. Maven’s Principles
- 1.2.1. Convention Over Configuration
- Standard Directory Layout for Projects
- One Primary Output Per Project
- Standard Naming Conventions
- 1.2.2. Reuse of Build Logic
- Maven's project object model (POM)
- 1.2.3. Coherent Organization of Dependencies
- Local Maven repository
- Locating dependency artifacts
- 1.3. Maven's Benefits
- 2. Getting Started with Maven
- Getting Started with Maven
- 2.1. Preparing to Use Maven
- 2.2. Creating Your First Maven Project
- 2.3. Compiling Application Sources
- 2.4. Compiling Test Sources and Running Unit Tests
- 2.5. Packaging and Installation to Your Local Repository
- 2.6. Handling Classpath Resources
- 2.6.1. Handling Test Classpath Resources
- 2.6.2. Filtering Classpath Resources
- 2.6.3. Preventing Filtering of Binary Resources
- 2.7. Using Maven Plugins
- 2.8. Summary
- 3. Creating Applications with Maven
- Creating Applications with Maven
- 3.1. Introduction
- 3.2. Setting Up an Application Directory Structure
- Table 3-1: Module packaging types
- 3.3. Using Project Inheritance
- 3.4. Managing Dependencies
- 3.5. Using Snapshots
- 3.6. Resolving Dependency Conflicts and Using Version Ranges
- Table 3-2: Examples of Version Ranges
- 3.7. Utilizing the Build Life Cycle
- 3.8. Using Profiles
- 3.9. Deploying your Application
- 3.9.1. Deploying to the File System
- 3.9.2. Deploying with SSH2
- 3.9.3. Deploying with SFTP
- 3.9.4. Deploying with an External SSH
- 3.9.5. Deploying with FTP
- 3.10. Creating a Web Site for your Application
- Table 3-3: Site descriptor
- 3.11. Summary
- 4. Building J2EE Applications
- Building J2EE Applications
- 4.1. Introduction
- 4.2. Introducing the DayTrader Application
- 4.3. Organizing the DayTrader Directory Structure
- 4.4. Building a Web Services Client Project
- Table 4-1: Axis generated classes
- 4.5. Building an EJB Project
- 4.6. Building an EJB Module With Xdoclet
- 4.7. Deploying EJBs
- 4.8. Building a Web Application Project
- Table 4-2: WAR plugin configuration properties
- 4.9. Improving Web Development Productivity
- 4.10. Deploying Web Applications
- 4.11. Building an EAR Project
- 4.12. Deploying a J2EE Application
- 4.13. Testing J2EE Application
- 4.14. Summary
- 5. Developing Custom Maven Plugins
- Developing Custom Maven Plugins
- 5.1. Introduction
- 5.2. A Review of Plugin Terminology
- 5.3. Bootstrapping into Plugin Development
- 5.3.1. The Plugin Framework
- Participation in the build life cycle
- Table 5-1: Life-cycle bindings for jar packaging
- Accessing build information
- The plugin descriptor
- 5.3.2. Plugin Development Tools
- Choose your mojo implementation language
- 5.3.3. A Note on the Examples in this Chapter
- 5.4. Developing Your First Mojo
- 5.4.1. BuildInfo Example: Capturing Information with a Java Mojo
- Prerequisite: Building the buildinfo generator project
- Using the archetype plugin to generate a stub plugin project
- The mojo
- The plugin POM
- Binding to the life cycle
- The output
- 5.4.2. BuildInfo Example: Notifying Other Developers with an Ant Mojo
- The Ant target
- The mojo metadata file
- Modifying the plugin POM for Ant mojos
- Binding the notify mojo to the life cycle
- 5.5. Advanced Mojo Development
- 5.5.1. Gaining Access to Maven APIs
- 5.5.2. Accessing Project Dependencies
- Injecting the project dependency set
- Requiring dependency resolution
- BuildInfo example: logging dependency versions
- 5.5.3. Accessing Project Sources and Resources
- Adding a source directory to the build
- Adding a resource to the build
- Accessing the source-root list
- Accessing the resource list
- Note on testing source-roots and resources
- Table 5-2: Key differences between compile-time and test-time mojo activities
- 5.5.4. Attaching Artifacts for Installation and Deployment
- 5.6. Summary
- 6. Assessing Project Health with Maven
- Assessing Project Health with Maven
- 6.1. What Does Maven Have to do With Project Health?
- 6.2. Adding Reports to the Project Web site
- 6.3. Configuration of Reports
- 6.4. Separating Developer Reports From User Documentation
- Table 6-1: Project Web site content types
- 6.5. Choosing Which Reports to Include
- Table 6-2: Report highlights
- 6.6. Creating Reference Material
- 6.7. Monitoring and Improving the Health of Your Source Code
- Table 6-3: Built-in Checkstyle configurations
- 6.8. Monitoring and Improving the Health of Your Tests
- 6.9. Monitoring and Improving the Health of Your Dependencies
- 6.10. Monitoring and Improving the Health of Your Releases
- 6.11. Viewing Overall Project Health
- 6.12. Summary
- 7. Team Collaboration with Maven
- Team Collaboration with Maven
- 7.1. The Issues Facing Teams
- 7.2. How to Set up a Consistent Developer Environment
- 7.3. Creating a Shared Repository
- 7.4. Creating an Organization POM
- 7.5. Continuous Integration with Continuum
- 7.6. Team Dependency Management Using Snapshots
- 7.7. Creating a Standard Project Archetype
- 7.8. Cutting a Release
- 7.9. Summary
- 8. Migrating to Maven
- Migrating to Maven
- 8.1. Introduction
- 8.1.1. Introducing the Spring Framework
- 8.2. Where to Begin?
- 8.3. Creating POM files
- 8.4. Compiling
- 8.5. Testing
- 8.5.1. Compiling Tests
- 8.5.2. Running Tests
- 8.6. Other Modules
- 8.6.1. Avoiding Duplication
- 8.6.2. Referring to Test Classes from Other Modules
- 8.6.3. Building Java 5 Classes
- 8.6.4. Using Ant Tasks From Inside Maven
- 8.6.5. Non-redistributable Jars
- 8.6.6. Some Special Cases
- 8.7. Restructuring the Code
- 8.8. Summary
- Appendix A: Resources for Plugin Developers
- Appendix A: Resources for Plugin Developers
- A.1. Maven's Life Cycles
- A.1.1. The default Life Cycle
- Life-cycle phases
- Bindings for the jar packaging
- Table A-1: The default life-cycle bindings for the jar packaging
- Bindings for the maven-plugin packaging
- Table A-2: A summary of the additional mojo bindings
- A.1.2. The clean Life Cycle
- Default life-cycle bindings
- Table A-3: The clean life-cycle bindings for the jar packaging
- A.1.3. The site Life Cycle
- Default Life Cycle Bindings
- Table A-4: The site life-cycle bindings for the jar packaging
- A.2. Mojo Parameter Expressions
- A.2.1. Simple Expressions
- Table A-5: Primitive expressions supported by Maven's plugin parameter
- A.2.2. Complex Expression Roots
- Table A-6: A summary of the valid root objects for plugin parameter expressions
- A.2.3. The Expression Resolution Algorithm
- Plugin metadata
- Plugin descriptor syntax
- A.2.4. Java Mojo Metadata: Supported Javadoc Annotations
- Class-level annotations
- Table A-7: A summary of class-level javadoc annotations
- Field-level annotations
- Table A-8: Field-level annotations
- A.2.5. Ant Metadata Syntax
- Appendix B: Standard Conventions
- B.1. Standard Directory Structure
- Table B-1: Standard directory layout for maven project content
- B.2. Maven’s Super POM
- B.3. Maven’s Default Build Life Cycle
- Table B-2: Phases in Maven's life cycle
- Bibliography
- Index
Add a Comment
chaitzzleft a comment