Refactoring Maven Projects
65d12002-6474-4d67-a934-f84f36f0ca0a
 |
Presentation |
Introductory
Birds of a Feather (BOF)
Room:
BoF
Timeslot:
18.09.08 14:15
Speaker: Ole-Martin Mørk
Abstract
This experience report will cover how our maven project moved from one single line of code in one webapp module to five webapplications and fourteen modules. There are very few best practises regarding how to organize a maven project over time. After talking to several peers and reading all available material I have not found any good solutions to this. This presentation is my effort to give something back to the java community and hopefully start a discussionon how you should organize your maven projects.
Keypoints:
- What is the best way to keep buildtime down to a absolute minimum?
- Should the modules be organized in vertical or horizontal modules?
- How should you use a maven repository?
- How do you handle releases
- When should you create a new module?
- What is the downsize of creating a new module?
Outline
- Introduction
- How it all got started
- What was the result of our first refactoring?
- How did we use CI-servers?
- How did we use the maven:release-plugin?
- What other useful plugins did we use?
- Where did we end up and what did we learn?
- Q&A
-
Ole-Martin MørkOle-Martin Mørk jobber som Manager i Bekk Consulting og er leder for faggruppen Systemutvikling. Han har jobbet med Java og Java EE utvikling i åtte år. Den siste tiden har han økt sitt fokus på andre programmeringsspråk som Ruby og Scala.