The goal of this blog is to show an updated and more involved example then what is currently located on the plexus site. This will cover creating a couple of components and explain the different ways to inject your dependencies. This example assumes you are using maven 2 to make your life easier.
We have a handful of Maven best practice and How-Tos documented in the blogs. Over time they get buried by newer posts, but the content is still just as relevant. Here is a summary of what exists: Continue reading
I get this question frequently so it is time to write down my thoughts on the answer so I can stop repeating myself. Here’s the question:
Should I put the urls to my repositories in my poms or in my settings?
The short answer is: settings.
The long answer is: it depends.
There are two scenarios to consider here. Enterprise software (generally not published externally) and public software. Lets take Enterprise software first. Continue reading this post for a full explanation of both scenarios. Continue reading
The Maven Release plugin enforces best practices for releasing Maven artifacts. In summary, the release plugin performs the following steps:
Dealing with failures on Step #2 is where I want to focus today. Continue reading
Continuous Integration is a development best practice that you need to be using in your process; it is an essential part of an efficient Software Development Lifecycle (SLDC). If you aren’t using it already, then you should start, now. The main benefit of Continuous Integration is the ability to flag errors as they are introduced into a system instead of waiting multiple days for test failures and critical errors to be identified during the QA cycle. This post isn’t about the virtues of using CI, it’s about how to setup an optimal environment in a Maven shop. Here are seven tips for running Maven builds in a CI system such as Hudson. Continue reading
