Sonatype is going through the archives and digging up articles that we think would be useful to developers using our tools. If you use Maven, keep reading the post below from Sonatype Vice President of Engineering Brian Fox on Maven best practices and how-tos.
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. Learn more about Maven by checking out the following blogs:
How to properly manage repository definitions and why you shouldn't declare them in your poms.
How to most effectively create your own internal release of a snapshot dependency.
Multiple techniques for running Maven builds from a CI system.
See the code that Maven uses to detect a snapshot version. This is helpful if you have non-standard release versions to make sure they won't be detected by Maven as a snapshot.
Tips on how to configure plugins in a way that makes it easier to understand what is happening in your pom.
How to use the buildhelper plugin to add additional source folders to your build. This is common if you have tools that generate sources that don't have a Maven plugin to add the source folder automatically.
Find out about several terms that are often misquoted. This post also specifically discusses classifiers and attached artifacts.
How to override a plugin dependency in your own pom...for example if you want to use a newer version of a tool wrapped by a plugin (pmd, checkstyle, cobertura are common examples)
How to share resources in a repeatable way without using relative paths in your poms. It also shows a technique for sharing checkstyle and pmd configurations across all your modules.
Learn about how Maven determines which version of a plugin to use, and why you should use PluginManagement to control the versions yourself.
Okay so it might take longer than 5 minutes to convert from Ant to Maven, but this post will show you that it is possible to work the migration in parallel so that most of your team sees the conversion happen very quickly when the time is right.
Step-by-step instructions on how to make a standalone JAR (i.e. one with no dependencies) executable.
Note: If you have suggestions for further topics, please leave a comment with your ideas.