http://www.anthillpro.com/blogs/anthillpro-blog/ News and Info about AnthillPro. en The AnthillPro Team Sun, 28 Feb 2010 13:02:22 GMT Pebble (http://pebble.sourceforge.net) http://backend.userland.com/rss http://www.anthillpro.com/blogs/anthillpro-blog/2010/02/26/mavens_strengths_and_weaknesses_as_a_dependency_management_system.html#comment1267362142130 There is a way to depend on status. You would tackle this via setting up a Staging repository. This is fully supported by the maven release plugin and even has a goal: mvn release:prepare release:stage -DautoVersionSubmodules=true This publishes the artifact to a 'staging' repository. You point your build at your release repository, and set the version to RELEASE, or [1.3, , etc. <dependency> <artifactId>artifactId</artifactId> <groupId>groupId</groupId> <version>RELEASE</version> </dependency> In this circumstance you'll always get your release from your release policy which is your safe, test pasted usable release. For your unsafe / non-qa'd artifact, simply add your staging repository in under a profile activation (in your parent pom, define the repository under a profile): mvn install -P staging When you have test passed, simply finish the release: mvn release:perform This will make it into your release policy Jacob Briggs http://www.anthillpro.com/blogs/anthillpro-blog/2010/02/26/mavens_strengths_and_weaknesses_as_a_dependency_management_system.html#comments http://www.anthillpro.com/blogs/anthillpro-blog/2010/02/26/mavens_strengths_and_weaknesses_as_a_dependency_management_system.html#comment1267362142130 Sun, 28 Feb 2010 13:02:22 GMT http://www.anthillpro.com/blogs/anthillpro-blog/2010/02/15/configure_a_multiplatform_build_in_anthillpro.html#comment1266315331946 Oh yes. Creating some best practices / patterns / refactorings kind of guide is a project that we need to tackle - I think it is on my plate to get done this year. Hopefully sooner rather than later. Eric Minick http://www.anthillpro.com/blogs/anthillpro-blog/2010/02/15/configure_a_multiplatform_build_in_anthillpro.html#comments http://www.anthillpro.com/blogs/anthillpro-blog/2010/02/15/configure_a_multiplatform_build_in_anthillpro.html#comment1266315331946 Tue, 16 Feb 2010 10:15:31 GMT http://www.anthillpro.com/blogs/anthillpro-blog/2010/02/15/configure_a_multiplatform_build_in_anthillpro.html#comment1266276212277 Thanks, Eric. Although we don't have a need for multi-platform builds yet, this is a good introduction on how to use iteration properties. Also, the idea of separating out the platform-agnostic setup and wrap up jobs is a nice strategy to avoid duplication. Both features make me wonder if there's a catalog of AntHill Pro Refactorings waiting to be made. :-) Brian Kelly http://www.anthillpro.com/blogs/anthillpro-blog/2010/02/15/configure_a_multiplatform_build_in_anthillpro.html#comments http://www.anthillpro.com/blogs/anthillpro-blog/2010/02/15/configure_a_multiplatform_build_in_anthillpro.html#comment1266276212277 Mon, 15 Feb 2010 23:23:32 GMT