Managed to get it working. I'm keeping the version for the packages static, so they can always find themselves in the maven repo, while allowing "release" to update a different version counter, so I still get those nice tags in git.
Thanks for the help! On Mon, Jan 9, 2012 at 9:35 PM, Alex Boisvert <alex.boisv...@gmail.com>wrote: > The common practice (in Maven + Buildr world) is to name the version with > -SNAPSHOT postfix. This way you don't have to change version numbers until > you do a proper release. The -SNAPSHOT postfix is automatically trimmed > during release (and the version number is incremented). > > Some more details here: http://buildr.apache.org/releasing.html > > alex > > > On Mon, Jan 9, 2012 at 10:22 AM, Paul Goldbaum <p...@cyberfonica.com> > wrote: > > > I currently have a group of separate projects, each with their own > > buildfile. Some of these depend on others in the group, so I'm running > > 'buildr install' after every compilation to get the others to see the > > changes. The problem with this solution is the need to specify the exact > > version of the dependency in the buildfile. Is there a better solution > than > > going into each buildfile and update the version for each build, > something > > like maven's LATEST keyword for the version? > > > > Thanks > > >
