This appears to be a bug. I was under the impression the _1.3.4_ convention to select a version was universal across platforms but apparently it's not. (I didn't find any documentation on this... if anybody has pointers, I'd very grateful)
I've created https://issues.apache.org/jira/browse/BUILDR-303 to track this. The workaround using -V doesn't actually fix the issue; it happens to work but does not ensure the same buildr version is used for releasing. alex On Tue, Aug 18, 2009 at 4:37 PM, Joel Muzzerall <muzzer...@intalio.com>wrote: > I am trying to run > > buildr release > > but it produces this error: > > /usr/bin/ruby1.8 -S buildr _1.3.4_ --buildfile *snip* --environment > development clean upload DEBUG=no > (in *snip*, development) > Buildr aborted! > Don't know how to build task '_1.3.4_' > > I believe that this syntax should work. Any idea why it doesn't? > > I can work around this issue by changing lib/buildr/core/build.rb:270 from > > args = '-S', 'buildr', "_#{Buildr::VERSION}_", '--buildfile', > release_candidate_buildfile > > to > > args = '-S', 'buildr', "-V#{Buildr::VERSION}", '--buildfile', > release_candidate_buildfile > > -- > Joel Muzzerall > Computer Systems Analyst > Intalio > > 415-519-6747 >
