Chris, Not sure if you're familiar with the Ruby debugger, but the gem ruby-debug is helpful tool for debugging your Buildr script. Of course there's nothing quite like doc or help pages, but this writeup serves as a good guide on getting started with it:
http://pivotallabs.com/users/chad/blog/articles/366-ruby-debug-in-30-seconds-we-don-t-need-no-stinkin-gui- This will allow you to set breakpoints and inspect the environment. On Thu, Jul 21, 2011 at 10:32 AM, Chris Adams <[email protected]> wrote: > >> task("outside-project:build").clear.enhance > >> ["outside-project:webapp-1:build"] > > That's a neat little hack :) I'm slowly learning buildr and Ruby... One of > these days I'll get it. > Thanks all for your help; for now, I'm probably going to just setup some > shortcut tasks and call it good enough. Although if enough people complain > on our project about the lack of a true "default" project, I may opt for > Stephen's solution. > > Thanks again. > > - Chris > > On Thu, Jul 21, 2011 at 9:31 AM, Stephen Haberman > <[email protected]>wrote: > > > > > > PS: If you really want to override the default, you can do something > > > along the lines of, > > > > This will change the behavior of "build" even when buildr is invokved > > within a subproject, correctly? E.g. "cd webapp2", "buildr" would end > > up invoking outside-project:webapp1:build, right? If so, you're right, > > that would be fairly unintuitive. > > > > Maybe something like: > > > > task("outside-project:build").clear.enhance > > ["outside-project:webapp-1:build"] > > > > Would accomplish getting webapp-1 to be the "default" project built, > > but only if you're in the outside-project root directory when buildr > > is invoked? > > > > - Stephen > > > > >
