Beyond the basics and the core principles, it's difficult to write down the exact instructions for a large scale deployment and use of Maven because the situations are vastly different. Even if one would document the best practices for some particular situations, the issue for the novice is identifying the right case for your situation. Between the company's SCM of choice, preferred branching patterns (release / feature branches), development velocity, maturity of the codebase, the type of software (libraries, service, pre-packaged apps) and programming languages used (plain Java, native libs w/ OS-specific languages, scripting), development methodology etc. there are too many variations to be able to confidently arrive at an optimal solution just by reading about it. For somebody with experience though, it's typically simple to re-organize even larger builds to follow best practices in a matter of few days. However, you often end up spending much much longer in real time, because first, you want to go at it alone and second, you always discount the level of resistance to change.
Kalle On Fri, Dec 10, 2010 at 2:19 PM, Peter Schuller <[email protected]> wrote: >> I very much second Kalle here. >> Stay away from profiles as much as possible - most often they are used in >> the wrong way. Also, if you're migrating a large system I would very much >> recommend that you get someone with good Maven knowledge to help you get >> things right. I very often come to projects where some senior developer has >> created a Maven build setup which is just completely wrong. Having to >> refactor that costs possibly two-three times more than doing it right from >> the beginning. It often also upsets the developers as they often have to >> change the way they work. > > So on that topic, is there good material that covers doing it right? > I've read the sonatype maven book and while it's good as far as it > goes, it doesn't really cover the intended workflows in various > situations and the intent of various abstractions. Googling is kind of > problematic because there is a lot of cargo cult information floating > around. > > Is there a book of other material that truly goes through the intended > way to deploy Maven in an organization, including not just stuff like > "here's how you install nexus", but things like release management, > the relationship between maven release management and VCS tagging, > what to do about multiple branches of development, etc, etc. > > Suppose you want to build an eco-system of tens or hundreds of > projects in an organization and deploy/build them scalably (in terms > of administration/build costs) using maven in a clean and maintainable > fashion without hacks or non-idiomatic mistakes. What material does > one preferably read? > > -- > / Peter Schuller > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
