Mailing-List: contact buildr-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: buildr-user@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of djspiewak@gmail.com designates
 209.85.219.20 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:references;
        b=rx9iIFkK4ovH/LLSTl4wEBDwAFY7LGJn5sCmtIGDIKoaw/V0n3s8sTaFb2qQ3Q8IIw
         j769gKX7kXjgKUobMKIoWMLADW7vjqbkmgakxnll3iRLLB45fq/LKkP5Dx5QmspnKK40
         E0yc42J4H4EyJWnWTvzeNRyh8/ieU2Q1Yxd5Q=
Message-ID: <5c99d0330901061142h6881570brb956dd4692ac9ad8@mail.gmail.com>
Date: Tue, 6 Jan 2009 13:42:50 -0600
From: "Daniel Spiewak" <djspiewak@gmail.com>
To: buildr-user@incubator.apache.org
Subject: Re: Interactive Shell Support
In-Reply-To: <5582dd3b0901061140k3e79f69ak483aa17b2b3a8540@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_196719_14125000.1231270970099"
References: <5c99d0330901032203pbc6a3fdq645782c8921d9a1a@mail.gmail.com>
	 <3de5d7d20901051708g677bf2axd173e35822f11505@mail.gmail.com>
	 <5c99d0330901051735t72d8008bo158d46692e5f9d2@mail.gmail.com>
	 <3de5d7d20901051851p19df3163y3d696cc8423685bf@mail.gmail.com>
	 <5c99d0330901051906p68de504bq72d7fba81be00e9a@mail.gmail.com>
	 <3de5d7d20901061024o1933c056wa9a88d561bf0c294@mail.gmail.com>
	 <5c99d0330901061050n3cdfebaeyae6b56d4a600500e@mail.gmail.com>
	 <5582dd3b0901061107i33285b03kffcc2c17b8e09dd6@mail.gmail.com>
	 <5c99d0330901061134i2c7a1349x1bde171a815fab0d@mail.gmail.com>
	 <5582dd3b0901061140k3e79f69ak483aa17b2b3a8540@mail.gmail.com>

------=_Part_196719_14125000.1231270970099
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Right, that's what I understood you to mean.  I guess I just didn't echo it
back correctly.  :-)

Daniel

On Tue, Jan 6, 2009 at 1:40 PM, Alex Boisvert <boisvert@intalio.com> wrote:

> Sorry, I wasn't clear.
>
> In my example, I was defining a top-level task "shell" that would be linked
> to a project's specific shell task.
>
> That way, you could do "buildr shell" instead of "buildr myproject:shell"
> or
> "buildr myproject:shell:jirb"
>
> alex
>
>
> On Tue, Jan 6, 2009 at 11:34 AM, Daniel Spiewak <djspiewak@gmail.com>
> wrote:
>
> > Oh I see, allow the task to be project local, just don't define the
> > local_task alias.  That would work, but again it's not as magical.
> >
> > Daniel
> >
> > On Tue, Jan 6, 2009 at 1:07 PM, Alex Boisvert <boisvert@intalio.com>
> > wrote:
> >
> > > On Tue, Jan 6, 2009 at 10:50 AM, Daniel Spiewak <djspiewak@gmail.com>
> > > wrote:
> > >
> > > > > Yes, but I only have to do it once when I write the buildfile. All
> > the
> > > > > times I run the shell, I don't have to cd into a specific
> directory,
> > > > > or remember the qualified task name. So if you don't need different
> > > > > shells for different projects (in the same build), overall there's
> > > > > much less effort setting it up this way.
> > > >
> > >
> > > The same could be said for the other approach.  You could easily have,
> > >
> > > task 'shell' => 'myproject:shell:jirb'
> > >
> > > in your project and be done with it.
> > >
> > >
> > > > Oh, on a syntactic note, Lispers would know the "shell" much better
> as
> > a
> > > > REPL.  What's the preferred terminology?  I like shell because it's
> > short
> > > > and relatively easy to understand, but maybe I'm the minority.  If
> > > someone
> > > > is expecting the interactive language shell to be called a "REPL",
> then
> > > > they
> > > > would probably expect `buildr shell` to be some sort of interactive
> > > command
> > > > interface to Buildr itself (allowing you to run tasks).  Does this
> seem
> > > > like
> > > > a potential problem or should we not fret over it?
> > >
> > >
> > > I think "shell" is the more common and broader name.   And as shown
> > above,
> > > it's easy to create an alias if you insist on a specific name.
> > >
> > > alex
> > >
> >
>

------=_Part_196719_14125000.1231270970099--