You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@buildr.apache.org by Antoine Toulme <an...@lunar-ocean.com> on 2009/12/09 00:14:01 UTC
Package Buildr plugins with Buildr standalone distributions
Hi guys,
I have been working a bit with the standalone distrib of Buildr mounted on
JRuby and I liked it so far, I think it offers a very simple way to have
buildr around.
I had the need to install gems on that jruby installation and my quick fix
was to edit the buildr executable, remove the mention of _buildr, run:
buildr gem install mygem
Two questions:
1. Can we have a way to install Buildr gems as part of Buildr in an easy way
?
2. Can we prepackage Buildr with one or more plugins and distribute it that
way ? Either on apache.org or at the plugin website ? If yes, what would be
the instructions to do that ?
Thanks,
Antoine
Re: Package Buildr plugins with Buildr standalone distributions
Posted by Antoine Toulme <an...@lunar-ocean.com>.
Opened https://issues.apache.org/jira/browse/BUILDR-355 to follow up on
this.
Thanks!
On Wed, Dec 16, 2009 at 12:02, Alex Boisvert <al...@gmail.com>wrote:
> On Wed, Dec 16, 2009 at 11:31 AM, Antoine Toulme <an...@lunar-ocean.com>wrote:
>
>> Alex,
>>
>> rather than using lambdas, could you use tasks ? I think there would be a
>> lost of interest in using rake here, in particular when downloading jruby.
>>
>
> Absolutely. I just didn't have time to polish it the first time.
>
>>
>> Would it also be possible to use Maven to download JRuby rather than using
>> an explicit URL ?
>>
>> Maven Central should have JRuby around.
>>
>
> Yep, http://repo1.maven.org/maven2/org/jruby/jruby-complete/1.4.0/
>
> When I come back to it, I'll fix these things.
> (BTW, I don't think the currently generated distro works on Windows)
>
> alex
>
Re: Package Buildr plugins with Buildr standalone distributions
Posted by Alex Boisvert <al...@gmail.com>.
On Wed, Dec 16, 2009 at 11:31 AM, Antoine Toulme <an...@lunar-ocean.com>wrote:
> Alex,
>
> rather than using lambdas, could you use tasks ? I think there would be a
> lost of interest in using rake here, in particular when downloading jruby.
>
Absolutely. I just didn't have time to polish it the first time.
>
> Would it also be possible to use Maven to download JRuby rather than using
> an explicit URL ?
>
> Maven Central should have JRuby around.
>
Yep, http://repo1.maven.org/maven2/org/jruby/jruby-complete/1.4.0/
When I come back to it, I'll fix these things.
(BTW, I don't think the currently generated distro works on Windows)
alex
Re: Package Buildr plugins with Buildr standalone distributions
Posted by Antoine Toulme <an...@lunar-ocean.com>.
Alex,
rather than using lambdas, could you use tasks ? I think there would be a
lost of interest in using rake here, in particular when downloading jruby.
Would it also be possible to use Maven to download JRuby rather than using
an explicit URL ?
Maven Central should have JRuby around.
Thanks,
Antoine
On Thu, Dec 10, 2009 at 14:32, Antoine Toulme <an...@lunar-ocean.com>wrote:
>
>
> On Tue, Dec 8, 2009 at 15:43, Alex Boisvert <al...@gmail.com>wrote:
>
>> On Tue, Dec 8, 2009 at 3:14 PM, Antoine Toulme <an...@lunar-ocean.com>wrote:
>>
>>> I have been working a bit with the standalone distrib of Buildr mounted
>>> on
>>> JRuby and I liked it so far, I think it offers a very simple way to have
>>> buildr around.
>>>
>>
>> Good to hear.
>>
>> I had the need to install gems on that jruby installation and my quick fix
>>> was to edit the buildr executable, remove the mention of _buildr, run:
>>> buildr gem install mygem
>>>
>>
>> That's the kind of feedback I was hoping for :)
>>
>>
>>> Two questions:
>>> 1. Can we have a way to install Buildr gems as part of Buildr in an easy
>>> way?
>>>
>>
>> Yes, we could leave the original jruby executable/scripts in the distro
>> for that purpose.
>>
> The more I think about it, the less I like having a jruby script in my
> path. It is likely to be an issue or maybe not clear to me that it relates
> to buildr.
> Could we use that -S parameter ? buildr -S gem install stuff.
>
> This way I know for certain I am installing something in my buildr tool.
>
> It's really more work for you, I would feel better with it though. You be
> the judge.
>
>>
>>
>>> 2. Can we prepackage Buildr with one or more plugins and distribute it
>>> that
>>> way ? Either on apache.org or at the plugin website ? If yes, what would
>>> be
>>> the instructions to do that ?
>>>
>>
>> Possible but I'd personally rather do #1. Sooner or later you want to
>> add another plugin and I'd rather avoid the combinational explosion of
>> distros.
>>
>> alex
>>
>
>
Re: Package Buildr plugins with Buildr standalone distributions
Posted by Antoine Toulme <an...@lunar-ocean.com>.
On Tue, Dec 8, 2009 at 15:43, Alex Boisvert <al...@gmail.com> wrote:
> On Tue, Dec 8, 2009 at 3:14 PM, Antoine Toulme <an...@lunar-ocean.com>wrote:
>
>> I have been working a bit with the standalone distrib of Buildr mounted on
>> JRuby and I liked it so far, I think it offers a very simple way to have
>> buildr around.
>>
>
> Good to hear.
>
> I had the need to install gems on that jruby installation and my quick fix
>> was to edit the buildr executable, remove the mention of _buildr, run:
>> buildr gem install mygem
>>
>
> That's the kind of feedback I was hoping for :)
>
>
>> Two questions:
>> 1. Can we have a way to install Buildr gems as part of Buildr in an easy
>> way?
>>
>
> Yes, we could leave the original jruby executable/scripts in the distro for
> that purpose.
>
The more I think about it, the less I like having a jruby script in my path.
It is likely to be an issue or maybe not clear to me that it relates to
buildr.
Could we use that -S parameter ? buildr -S gem install stuff.
This way I know for certain I am installing something in my buildr tool.
It's really more work for you, I would feel better with it though. You be
the judge.
>
>
>> 2. Can we prepackage Buildr with one or more plugins and distribute it
>> that
>> way ? Either on apache.org or at the plugin website ? If yes, what would
>> be
>> the instructions to do that ?
>>
>
> Possible but I'd personally rather do #1. Sooner or later you want to add
> another plugin and I'd rather avoid the combinational explosion of distros.
>
> alex
>
Re: Package Buildr plugins with Buildr standalone distributions
Posted by Alex Boisvert <al...@gmail.com>.
On Tue, Dec 8, 2009 at 5:55 PM, Antoine Toulme <an...@lunar-ocean.com>wrote:
> OK I just tried, it worked for me.
>
Cool!
> For some reason rake -T doesn't return all-in-one ?
>
Fixed.
alex
Re: Package Buildr plugins with Buildr standalone distributions
Posted by Antoine Toulme <an...@lunar-ocean.com>.
OK I just tried, it worked for me.
For some reason rake -T doesn't return all-in-one ?
Cheers,
Antoine
On Tue, Dec 8, 2009 at 17:40, Alex Boisvert <al...@gmail.com> wrote:
> On Tue, Dec 8, 2009 at 4:12 PM, Antoine Toulme <an...@lunar-ocean.com>wrote:
>
>>
>> Do you mind sharing how you bundled jruby with buildr ? Do you have a
>>>> script for that ?
>>>>
>>>
>>> I don't have a script yet; I just whipped it out manually.
>>>
>>> I'll add it to Buildr's rakefile now(ish).
>>>
>>
> Ok, committed a first shot. Try "rake all-in-one". I'm curious to know if
> it runs on MacOS. And there's probably more cleanup to do... far from
> ready for a release but good enough to get the ball rolling.
>
> alex
>
>
Re: Package Buildr plugins with Buildr standalone distributions
Posted by Alex Boisvert <al...@gmail.com>.
On Tue, Dec 8, 2009 at 4:12 PM, Antoine Toulme <an...@lunar-ocean.com>wrote:
>
> Do you mind sharing how you bundled jruby with buildr ? Do you have a
>>> script for that ?
>>>
>>
>> I don't have a script yet; I just whipped it out manually.
>>
>> I'll add it to Buildr's rakefile now(ish).
>>
>
Ok, committed a first shot. Try "rake all-in-one". I'm curious to know if
it runs on MacOS. And there's probably more cleanup to do... far from
ready for a release but good enough to get the ball rolling.
alex
Re: Package Buildr plugins with Buildr standalone distributions
Posted by Antoine Toulme <an...@lunar-ocean.com>.
On Tue, Dec 8, 2009 at 16:11, Alex Boisvert <al...@gmail.com> wrote:
> On Tue, Dec 8, 2009 at 3:51 PM, Antoine Toulme <an...@lunar-ocean.com>wrote:
>
>>
>>
>> On Tue, Dec 8, 2009 at 15:43, Alex Boisvert <al...@gmail.com>wrote:
>>
>>> On Tue, Dec 8, 2009 at 3:14 PM, Antoine Toulme <an...@lunar-ocean.com>wrote:
>>>
>>>> I have been working a bit with the standalone distrib of Buildr mounted
>>>> on
>>>> JRuby and I liked it so far, I think it offers a very simple way to have
>>>> buildr around.
>>>>
>>>
>>> Good to hear.
>>>
>>> I had the need to install gems on that jruby installation and my quick
>>>> fix
>>>> was to edit the buildr executable, remove the mention of _buildr, run:
>>>> buildr gem install mygem
>>>>
>>>
>>> That's the kind of feedback I was hoping for :)
>>>
>>>
>>>> Two questions:
>>>> 1. Can we have a way to install Buildr gems as part of Buildr in an easy
>>>> way?
>>>>
>>>
>>> Yes, we could leave the original jruby executable/scripts in the distro
>>> for that purpose.
>>>
>> Indeed.
>>
>>>
>>>
>>>> 2. Can we prepackage Buildr with one or more plugins and distribute it
>>>> that
>>>> way ? Either on apache.org or at the plugin website ? If yes, what
>>>> would be
>>>> the instructions to do that ?
>>>>
>>>
>>> Possible but I'd personally rather do #1. Sooner or later you want to
>>> add another plugin and I'd rather avoid the combinational explosion of
>>> distros.
>>>
>> After giving it some more thought, I think in that case, such a distro
>> would not be buildr anymore. Buildr would be bundled in there, but the
>> distro would be something else.
>> Do you mind sharing how you bundled jruby with buildr ? Do you have a
>> script for that ?
>>
>
> I don't have a script yet; I just whipped it out manually.
>
> I'll add it to Buildr's rakefile now(ish).
>
ok(ish)
Thanks!
>
> alex
>
Re: Package Buildr plugins with Buildr standalone distributions
Posted by Alex Boisvert <al...@gmail.com>.
On Tue, Dec 8, 2009 at 3:51 PM, Antoine Toulme <an...@lunar-ocean.com>wrote:
>
>
> On Tue, Dec 8, 2009 at 15:43, Alex Boisvert <al...@gmail.com>wrote:
>
>> On Tue, Dec 8, 2009 at 3:14 PM, Antoine Toulme <an...@lunar-ocean.com>wrote:
>>
>>> I have been working a bit with the standalone distrib of Buildr mounted
>>> on
>>> JRuby and I liked it so far, I think it offers a very simple way to have
>>> buildr around.
>>>
>>
>> Good to hear.
>>
>> I had the need to install gems on that jruby installation and my quick fix
>>> was to edit the buildr executable, remove the mention of _buildr, run:
>>> buildr gem install mygem
>>>
>>
>> That's the kind of feedback I was hoping for :)
>>
>>
>>> Two questions:
>>> 1. Can we have a way to install Buildr gems as part of Buildr in an easy
>>> way?
>>>
>>
>> Yes, we could leave the original jruby executable/scripts in the distro
>> for that purpose.
>>
> Indeed.
>
>>
>>
>>> 2. Can we prepackage Buildr with one or more plugins and distribute it
>>> that
>>> way ? Either on apache.org or at the plugin website ? If yes, what would
>>> be
>>> the instructions to do that ?
>>>
>>
>> Possible but I'd personally rather do #1. Sooner or later you want to
>> add another plugin and I'd rather avoid the combinational explosion of
>> distros.
>>
> After giving it some more thought, I think in that case, such a distro
> would not be buildr anymore. Buildr would be bundled in there, but the
> distro would be something else.
> Do you mind sharing how you bundled jruby with buildr ? Do you have a
> script for that ?
>
I don't have a script yet; I just whipped it out manually.
I'll add it to Buildr's rakefile now(ish).
alex
Re: Package Buildr plugins with Buildr standalone distributions
Posted by Antoine Toulme <an...@lunar-ocean.com>.
On Tue, Dec 8, 2009 at 15:43, Alex Boisvert <al...@gmail.com> wrote:
> On Tue, Dec 8, 2009 at 3:14 PM, Antoine Toulme <an...@lunar-ocean.com>wrote:
>
>> I have been working a bit with the standalone distrib of Buildr mounted on
>> JRuby and I liked it so far, I think it offers a very simple way to have
>> buildr around.
>>
>
> Good to hear.
>
> I had the need to install gems on that jruby installation and my quick fix
>> was to edit the buildr executable, remove the mention of _buildr, run:
>> buildr gem install mygem
>>
>
> That's the kind of feedback I was hoping for :)
>
>
>> Two questions:
>> 1. Can we have a way to install Buildr gems as part of Buildr in an easy
>> way?
>>
>
> Yes, we could leave the original jruby executable/scripts in the distro for
> that purpose.
>
Indeed.
>
>
>> 2. Can we prepackage Buildr with one or more plugins and distribute it
>> that
>> way ? Either on apache.org or at the plugin website ? If yes, what would
>> be
>> the instructions to do that ?
>>
>
> Possible but I'd personally rather do #1. Sooner or later you want to add
> another plugin and I'd rather avoid the combinational explosion of distros.
>
After giving it some more thought, I think in that case, such a distro would
not be buildr anymore. Buildr would be bundled in there, but the distro
would be something else.
Do you mind sharing how you bundled jruby with buildr ? Do you have a script
for that ?
Thanks,
Antoine
Re: Package Buildr plugins with Buildr standalone distributions
Posted by Alex Boisvert <al...@gmail.com>.
On Tue, Dec 8, 2009 at 3:14 PM, Antoine Toulme <an...@lunar-ocean.com>wrote:
> I have been working a bit with the standalone distrib of Buildr mounted on
> JRuby and I liked it so far, I think it offers a very simple way to have
> buildr around.
>
Good to hear.
I had the need to install gems on that jruby installation and my quick fix
> was to edit the buildr executable, remove the mention of _buildr, run:
> buildr gem install mygem
>
That's the kind of feedback I was hoping for :)
> Two questions:
> 1. Can we have a way to install Buildr gems as part of Buildr in an easy
> way?
>
Yes, we could leave the original jruby executable/scripts in the distro for
that purpose.
> 2. Can we prepackage Buildr with one or more plugins and distribute it that
> way ? Either on apache.org or at the plugin website ? If yes, what would
> be
> the instructions to do that ?
>
Possible but I'd personally rather do #1. Sooner or later you want to add
another plugin and I'd rather avoid the combinational explosion of distros.
alex