Downloaded 16 times
Uploaded byJohan Mynhardt
Maven from Scratch to Production (.odp)
The document discusses setting up a Maven project with a focus on continuous integration using Apache Continuum and Java EE technologies. It outlines the process of creating a multi-module project, configuring documentation and source code management, and highlights the benefits of Maven in simplifying the build process. Additionally, it provides links to resources and tools for further exploration and learning.
More Related Content
![[English][Test Girls] Zero to Hero: Start Test automation with Cypress](https://cdn.slidesharecdn.com/ss_thumbnails/entestgirlstestingwithcypress-191024022807-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Maven from Scratch to Production (.odp)
Maven from Scratch to Production (.odp)
- 1. by: Johan Mynhardt| Durban JUG Meeting | 12 May 2011| Maven From Scratch to Production
- 2. Ripe ground forflame-war
- 3. Argumenting that: Xis better than Y.
- 4. Y is betterthan X.
- 5. I can dothis with X by making use of Z. A session to convince you What this is *not*
- 6. Set up aMaven project
- 7. Set up theCI environment with Apache Continuum
- 8. See everything inaction! Objectives
- 9. Java EE 6 Glassfish Application Server EJB 3.1
- 10. JSF 2.0 PrimeFacesContinuous Integration and Project Management (from development perspective) Apache Continuum
- 11. Apache Maven ProjectTechnologies
- 12. Making the buildprocess easy
- 13. Providing a uniformbuild system
Editor's Notes
- #2 Welcome note Introduce yourself Why maven as a topic?
- #3 Avoid conflict and flame-wars :P
- #4 Quick overview of the entire presentation's objective
- #5 Quick word on technologies used in the skeleton project which took some time to set up
- #7 The first steps in creating a maven project. Creating the child Modules are excluded. Child modules can be created using different project templates, war, ejb, ear, portlet etc. Steps excluded from setup: version control (subversion) ssh keys web config for project documentation
- #8 Just covering the most parts needed for enabling the project to a production environment
- #9 The standalone option is the easiest Setup in Glassfish requires JNDI resources being set up mail database logging config (working though) Depending on the project the default build flow is sufficient (for using the root POM and produce artifacts)
- #10 SCM support : CVS, Subversion, Clearcase, Perforce, Starteam, Visual Source Safe, CM Synergy, Bazaar, Mercurial
- #11 Release preparation sees to it that most of the build issues are sorted out before a release. (issues not discovered in a normal build) Once preparation succeeds the build is ready for release. After the release build all the documentation and relevant information will be available in a web format which can be published, using the site plugin. The site plugin enhances the developer experience in that for example, a new developer joins the team, he/she can be pointed to the project site which has all the required documentation.