Note: Before we get started, anyone interested in signing up for Maven training should do so soon. We’ve got a class in Mountain View, CA on May 12-13, and a class in Chicago on May 19-20. Sign up today. It’ll be great, and we’ve got some new material from John Smart, author of “Java Power Tools”.
Alright, we’ve put the infrastructure in place for more participation in the development of Maven: The Definitive Guide. We’ve already had two forks of the Definitive Guide on GitHub. People are interested in helping out, and we encourage anyone to either submit a patch or fork and start innovating. Read on for some more details, how to sign up for our author mailing list, register for an account in the issue tracker, and get started with the code:
The Nexus 1.3.3 Pro release includes enhancements to allow validation of PGP signed artifacts, and block access based on the results of that check. This release also adds an enhanced set of capabilities and rules in the procurement suite. Download your free Nexus Professional Evaluation or Learn more about Nexus Professional today. Continue reading this post for more information about these new procurement features.
At Sonatype we are trying very much to bring the Maven, OSGi and Eclipse worlds together and Tycho is a big part of this strategy for us. Tycho is a set of sophisticated plugins for Maven that makes OSGi bundles first class citizens in the Maven world. We use OSGi metadata, we use MANIFEST.MF files for dependency information, and we use OSGi resolving strategies.
We are earnestly trying to bridge the Maven and Eclipse worlds and today’s dev build of Tycho is another step in that direction. Today we have our first publicly available version of Tycho with implicit build target platform support. In a nutshell we deal with target platforms in much the same way we deal with dependencies in Maven. We figure out what you need, and we’ll go get it from a set of remote repositories for you.
So let’s take a look at a simple demo application which illustrates how Tycho and the new build target platform support works.
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:
Ok, it will take you longer than 5 minutes, but 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.
Once upon a time, I was tasked with converting an existing, monolithic Ant / CVS based build to Maven 2 and Svn. This was back in the 2.0-beta-1 days (2005) so many of the tools have changed to make life easier, but I think the general process I used is still applicable to users migrating today. I’ll try to focus on the generic approach and leave specific details to the best practices documented elsewhere on this blog or in the Maven book.
Migrating from Ant to Maven requires a few basic steps: