Welcome to the weekly roundup of blog posts that mention Nexus, Maven, and other projects that Sonatype developers contribute to.
Getting Agile: HOWTO: Maven + StoryTestIQ + Selenium RC “StoryTestIQ is an automated acceptance testing tool, which was originally a mashup of 2 existing open source projects, Selenium and FitNesse. StoryTestIQ is many times shortened to STIQ (pronounced “stick”) so it rolls off the tongue more easily. STIQ takes the idea of testing inside the browser a la Selenium and enables editing, tagging, and multi-table execution through a modified FitNesse underneath the covers.” By Sterling Barton, on November 23rd, 2009
Simplericity: Make your war file executable with the Jetty Console Maven plugin “A while back I made a little Maven plugin that takes a war file and makes it executable. With executable I mean that it embeds a Jetty servlet container. Running java -jar myapp.war will deploy your war with the embedded Jetty instance. This provides a very convenient distribution method for Java web applications. It lets you distribute your application as a single artifact. Your users are no longer forced to install a big and ugly app server just to run your app.” By Eirik Bjørsnøs, on November 10, 2009
Karsten’s Blog: How to register a custom Maven repository layout “Maven repositories have a defined directory layout. In the standard installation Maven comes with 2 implementations, the default layout for Maven 2 and legacy layout for Maven 1.x. The layout is configured in the repository setting either in POMs or settings.xml file.” By Karsten Thoms, on October 13, 2009
Ham and Eggs: Creating A Simple Maven Plugin “I’ve been a big admirer of Maven for a long time. For some reason I have never made a plugin of my own. Today I did it, and I have to say it was a great learning experience. I will introduce all the neat things I figured out during the development. So let the story begin.” Published on August 30, 2009
Un expresso sans sucre: Créer un packaging maven2 “Maven 2 propose d’origine les types de packaging des différents composants java / j2ee : jar, war, ejb et ear. Cependant, il faut parfois utiliser des types de packaging moins conventionnels qui nécessitent la création d’un packaging maven dédié.” By Thomas Recloux, on July 07, 2008