Maven from Scratch to Production (.odp)
•Download as ODP, PDF•
2 likes•1,554 views
My presentation on Maven for the Durban Java User Group meeting, held at Thumbtribe's offices. As I'm not happy with everything as-is, my aim is to improve the presentation with an accompanying project which I need to set up in a proper environment so that it can serve as a fully functional example. To follow progress, keep an eye on the following blog post: http://johanmynhardt.blogspot.com/2011/05/maven-from-scratch-to-production.html
![by: Johan Mynhardt | Durban JUG Meeting | 12 May 2011| ,[object Object]](https://image.slidesharecdn.com/maven-scratch-to-production-110513133851-phpapp02/85/Maven-from-Scratch-to-Production-odp-1-320.jpg)
![[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Similar to Maven from Scratch to Production (.odp)
Similar to Maven from Scratch to Production (.odp) (20)
Recently uploaded
Recently uploaded (20)
Maven from Scratch to Production (.odp)
- 4. Y is better than X.
- 7. Set up the CI environment with Apache Continuum
- 13. Providing a uniform build system
- 14. Providing quality project information
- 22. Contributors
- 23. Reporting
- 24. Licenses
- 25. Organisation
- 31. ANT
- 33. Scheduled
- 35. Parallel Builds
Editor's Notes
- Welcome note Introduce yourself Why maven as a topic?
- Avoid conflict and flame-wars :P
- Quick overview of the entire presentation's objective
- Quick word on technologies used in the skeleton project which took some time to set up
- 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
- Just covering the most parts needed for enabling the project to a production environment
- 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)
- SCM support : CVS, Subversion, Clearcase, Perforce, Starteam, Visual Source Safe, CM Synergy, Bazaar, Mercurial
- 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.