You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@buildr.apache.org by Alex Boisvert <al...@gmail.com> on 2009/11/10 23:04:19 UTC
Bundled Buildr + JRuby distribution
Hi,
I've created an experimental distribution of Buildr 1.3.5 and JRuby 1.4.0
and made it available at:
http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip
The distro is 15M -- not too bad. I've trimmed the packaged JRuby of
everything I could that didn't affect functionality, such as documentation
and Ruby 1.9 support.
To use it, simply
1) unzip in a directory,
2) set your PATH to point to the "bin" directory, and
3) run "buildr" as usual.
Looking for feedback on how it works as a quick way to get yourself/other
people started. If there's enough interest, it could become part of our
supported distros.
thanks,
alex
Re: Bundled Buildr + JRuby distribution
Posted by Antoine Toulme <an...@lunar-ocean.com>.
I filed JRUBY-4383 for this. Any help is much welcome!
Antoine
On Wed, Dec 23, 2009 at 21:56, Antoine Toulme <an...@lunar-ocean.com>wrote:
> I just tried installing the package on build.eclipse.org, and it's a
> rather odd machine running with a PPC arch on 64 bit, with IBM sdks lying
> around.
>
> Trying to run with IBM SDKs, I get this error:
>
> buildr -v
> /shared/common/buildr-1.4.0-jruby-1.4.0/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `require': Could not load FFI Provider: FFI not available: Could not locate
> stub library (/jni/ppc-Linux/libjffi-0.6.so) in jar file (LoadError)
>
> uname -a gives:
> Linux build 2.6.16.60-0.42.7-ppc64 #1 SMP Tue Nov 3 11:20:42 UTC 2009 ppc64
> ppc64 ppc64 GNU/Linux
>
> Should I attempt installing a sun jdk there ? And/or require FFI to come up
> with a PPC port ?
>
> Extra karma points for anybody giving me a nice solution on Xmas morning.
>
> Cheers,
>
> Antoine
>
> On Mon, Nov 16, 2009 at 07:19, Greg Lucas <gr...@gmail.com> wrote:
>
>> Thanks for putting this together Alex.
>>
>> I've been trying it out with our continuous integration system in order to
>> build on multiple Linux machines. I'm getting:
>>
>> /opt/tools/buildr-1.3.5-jruby-1.4.0/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
>> `require': Could not load FFI Provider: FFI not available:
>> /tmp/jffi60799.tmp: Can't load AMD 64-bit .so on a AMD 64-bit platform
>> (LoadError)
>>
>> Has anyone seen this?
>>
>> --
>> Greg Lucas
>>
>
>
Re: Bundled Buildr + JRuby distribution
Posted by Antoine Toulme <an...@lunar-ocean.com>.
I filed JRUBY-4383 for this. Any help is much welcome!
Antoine
On Wed, Dec 23, 2009 at 21:56, Antoine Toulme <an...@lunar-ocean.com>wrote:
> I just tried installing the package on build.eclipse.org, and it's a
> rather odd machine running with a PPC arch on 64 bit, with IBM sdks lying
> around.
>
> Trying to run with IBM SDKs, I get this error:
>
> buildr -v
> /shared/common/buildr-1.4.0-jruby-1.4.0/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `require': Could not load FFI Provider: FFI not available: Could not locate
> stub library (/jni/ppc-Linux/libjffi-0.6.so) in jar file (LoadError)
>
> uname -a gives:
> Linux build 2.6.16.60-0.42.7-ppc64 #1 SMP Tue Nov 3 11:20:42 UTC 2009 ppc64
> ppc64 ppc64 GNU/Linux
>
> Should I attempt installing a sun jdk there ? And/or require FFI to come up
> with a PPC port ?
>
> Extra karma points for anybody giving me a nice solution on Xmas morning.
>
> Cheers,
>
> Antoine
>
> On Mon, Nov 16, 2009 at 07:19, Greg Lucas <gr...@gmail.com> wrote:
>
>> Thanks for putting this together Alex.
>>
>> I've been trying it out with our continuous integration system in order to
>> build on multiple Linux machines. I'm getting:
>>
>> /opt/tools/buildr-1.3.5-jruby-1.4.0/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
>> `require': Could not load FFI Provider: FFI not available:
>> /tmp/jffi60799.tmp: Can't load AMD 64-bit .so on a AMD 64-bit platform
>> (LoadError)
>>
>> Has anyone seen this?
>>
>> --
>> Greg Lucas
>>
>
>
Re: Bundled Buildr + JRuby distribution
Posted by Antoine Toulme <an...@lunar-ocean.com>.
I just tried installing the package on build.eclipse.org, and it's a rather
odd machine running with a PPC arch on 64 bit, with IBM sdks lying around.
Trying to run with IBM SDKs, I get this error:
buildr -v
/shared/common/buildr-1.4.0-jruby-1.4.0/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require': Could not load FFI Provider: FFI not available: Could not locate
stub library (/jni/ppc-Linux/libjffi-0.6.so) in jar file (LoadError)
uname -a gives:
Linux build 2.6.16.60-0.42.7-ppc64 #1 SMP Tue Nov 3 11:20:42 UTC 2009 ppc64
ppc64 ppc64 GNU/Linux
Should I attempt installing a sun jdk there ? And/or require FFI to come up
with a PPC port ?
Extra karma points for anybody giving me a nice solution on Xmas morning.
Cheers,
Antoine
On Mon, Nov 16, 2009 at 07:19, Greg Lucas <gr...@gmail.com> wrote:
> Thanks for putting this together Alex.
>
> I've been trying it out with our continuous integration system in order to
> build on multiple Linux machines. I'm getting:
>
> /opt/tools/buildr-1.3.5-jruby-1.4.0/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `require': Could not load FFI Provider: FFI not available:
> /tmp/jffi60799.tmp: Can't load AMD 64-bit .so on a AMD 64-bit platform
> (LoadError)
>
> Has anyone seen this?
>
> --
> Greg Lucas
>
Re: Bundled Buildr + JRuby distribution
Posted by Alex Boisvert <al...@gmail.com>.
On Mon, Nov 16, 2009 at 7:21 AM, Daniel Spiewak <dj...@gmail.com> wrote:
> I forgot about that. Our JRuby code does require jruby-ffi. Is it
> possible
> to bundle the appropriate native libs within a JRuby distribution?
>
Actually, the libs are already there.
boisvert@boog:/opt/boisvert/buildr-1.3.5-jruby-1.4.0/lib/native$ find . |
grep ffi
./x86_64-FreeBSD/libjffi-0.6.so
./i386-SunOS/libjffi-0.6.so
./i386-Windows/jffi-0.6.dll
./i386-Linux/libjffi-0.6.so
./s390x-Linux/libjffi-0.6.so
./darwin/libjffi-0.6.jnilib
./x86_64-SunOS/libjffi-0.6.so
./x86_64-Linux/libjffi-0.6.so
./i386-FreeBSD/libjffi-0.6.so
./sparc-SunOS/libjffi-0.6.so
./sparcv9-SunOS/libjffi-0.6.so
I can't make sense of the error message "Can't load AMD 64-bit .so on a AMD
64-bit platform", though.
Another thing to consider is that JRuby does have a jar-complete
> distribution which is a little easier to manage. We would have to write a
> separate buildr script just for that distribution, but it might be an
> overall win in terms of manageability.
>
Yes, I think that's a logical second step. I'd like to get things polished
with the current distro first.
alex
Re: Bundled Buildr + JRuby distribution
Posted by Alex Boisvert <al...@gmail.com>.
On Mon, Nov 16, 2009 at 7:21 AM, Daniel Spiewak <dj...@gmail.com> wrote:
> I forgot about that. Our JRuby code does require jruby-ffi. Is it
> possible
> to bundle the appropriate native libs within a JRuby distribution?
>
Actually, the libs are already there.
boisvert@boog:/opt/boisvert/buildr-1.3.5-jruby-1.4.0/lib/native$ find . |
grep ffi
./x86_64-FreeBSD/libjffi-0.6.so
./i386-SunOS/libjffi-0.6.so
./i386-Windows/jffi-0.6.dll
./i386-Linux/libjffi-0.6.so
./s390x-Linux/libjffi-0.6.so
./darwin/libjffi-0.6.jnilib
./x86_64-SunOS/libjffi-0.6.so
./x86_64-Linux/libjffi-0.6.so
./i386-FreeBSD/libjffi-0.6.so
./sparc-SunOS/libjffi-0.6.so
./sparcv9-SunOS/libjffi-0.6.so
I can't make sense of the error message "Can't load AMD 64-bit .so on a AMD
64-bit platform", though.
Another thing to consider is that JRuby does have a jar-complete
> distribution which is a little easier to manage. We would have to write a
> separate buildr script just for that distribution, but it might be an
> overall win in terms of manageability.
>
Yes, I think that's a logical second step. I'd like to get things polished
with the current distro first.
alex
Re: Bundled Buildr + JRuby distribution
Posted by Daniel Spiewak <dj...@gmail.com>.
I forgot about that. Our JRuby code does require jruby-ffi. Is it possible
to bundle the appropriate native libs within a JRuby distribution?
Another thing to consider is that JRuby does have a jar-complete
distribution which is a little easier to manage. We would have to write a
separate buildr script just for that distribution, but it might be an
overall win in terms of manageability.
Daniel
On Mon, Nov 16, 2009 at 9:19 AM, Greg Lucas <gr...@gmail.com> wrote:
> Thanks for putting this together Alex.
>
> I've been trying it out with our continuous integration system in order to
> build on multiple Linux machines. I'm getting:
>
> /opt/tools/buildr-1.3.5-jruby-1.4.0/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `require': Could not load FFI Provider: FFI not available:
> /tmp/jffi60799.tmp: Can't load AMD 64-bit .so on a AMD 64-bit platform
> (LoadError)
>
> Has anyone seen this?
>
> --
> Greg Lucas
>
Re: Bundled Buildr + JRuby distribution
Posted by Daniel Spiewak <dj...@gmail.com>.
I forgot about that. Our JRuby code does require jruby-ffi. Is it possible
to bundle the appropriate native libs within a JRuby distribution?
Another thing to consider is that JRuby does have a jar-complete
distribution which is a little easier to manage. We would have to write a
separate buildr script just for that distribution, but it might be an
overall win in terms of manageability.
Daniel
On Mon, Nov 16, 2009 at 9:19 AM, Greg Lucas <gr...@gmail.com> wrote:
> Thanks for putting this together Alex.
>
> I've been trying it out with our continuous integration system in order to
> build on multiple Linux machines. I'm getting:
>
> /opt/tools/buildr-1.3.5-jruby-1.4.0/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `require': Could not load FFI Provider: FFI not available:
> /tmp/jffi60799.tmp: Can't load AMD 64-bit .so on a AMD 64-bit platform
> (LoadError)
>
> Has anyone seen this?
>
> --
> Greg Lucas
>
Re: Bundled Buildr + JRuby distribution
Posted by Antoine Toulme <an...@lunar-ocean.com>.
I just tried installing the package on build.eclipse.org, and it's a rather
odd machine running with a PPC arch on 64 bit, with IBM sdks lying around.
Trying to run with IBM SDKs, I get this error:
buildr -v
/shared/common/buildr-1.4.0-jruby-1.4.0/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require': Could not load FFI Provider: FFI not available: Could not locate
stub library (/jni/ppc-Linux/libjffi-0.6.so) in jar file (LoadError)
uname -a gives:
Linux build 2.6.16.60-0.42.7-ppc64 #1 SMP Tue Nov 3 11:20:42 UTC 2009 ppc64
ppc64 ppc64 GNU/Linux
Should I attempt installing a sun jdk there ? And/or require FFI to come up
with a PPC port ?
Extra karma points for anybody giving me a nice solution on Xmas morning.
Cheers,
Antoine
On Mon, Nov 16, 2009 at 07:19, Greg Lucas <gr...@gmail.com> wrote:
> Thanks for putting this together Alex.
>
> I've been trying it out with our continuous integration system in order to
> build on multiple Linux machines. I'm getting:
>
> /opt/tools/buildr-1.3.5-jruby-1.4.0/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `require': Could not load FFI Provider: FFI not available:
> /tmp/jffi60799.tmp: Can't load AMD 64-bit .so on a AMD 64-bit platform
> (LoadError)
>
> Has anyone seen this?
>
> --
> Greg Lucas
>
Re: Bundled Buildr + JRuby distribution
Posted by Greg Lucas <gr...@gmail.com>.
Thanks Alex. I think I was wrong before about the workaround, but I just
tried your patch and that does solve the issue.
On Tue, 17 Nov 2009 14:03:43 -0500, Alex Boisvert
<al...@gmail.com> wrote:
> On Tue, Nov 17, 2009 at 9:49 AM, Greg Lucas <gr...@gmail.com> wrote:
>
>> Alex,
>>
>> I was seeing this with the ODE 1.x project, which just moved from Buildr
>> 1.2.10 to 1.3.5. It turns out that if I explicitly add the test task on
>> the
>> command line it does work as expected:
>>
>> buildr test=all test package
>>>
>>
>> Otherwise, the test=all is ignored and the build aborts on the first
>> test
>> failure:
>>
>> buildr test=all package
>>>
>>
>>
>> Not sure if that is expected behavior, but it was a change from buildr
>> 1.2.10.
>
>
> Ok, I just fixed this in trunk. Will be in 1.4.0.
>
> alex
--
Greg Lucas
Re: Bundled Buildr + JRuby distribution
Posted by Alex Boisvert <al...@gmail.com>.
On Tue, Nov 17, 2009 at 9:49 AM, Greg Lucas <gr...@gmail.com> wrote:
> Alex,
>
> I was seeing this with the ODE 1.x project, which just moved from Buildr
> 1.2.10 to 1.3.5. It turns out that if I explicitly add the test task on the
> command line it does work as expected:
>
> buildr test=all test package
>>
>
> Otherwise, the test=all is ignored and the build aborts on the first test
> failure:
>
> buildr test=all package
>>
>
>
> Not sure if that is expected behavior, but it was a change from buildr
> 1.2.10.
Ok, I just fixed this in trunk. Will be in 1.4.0.
alex
Re: Bundled Buildr + JRuby distribution
Posted by Greg Lucas <gr...@gmail.com>.
Alex,
I was seeing this with the ODE 1.x project, which just moved from Buildr
1.2.10 to 1.3.5. It turns out that if I explicitly add the test task on
the command line it does work as expected:
> buildr test=all test package
Otherwise, the test=all is ignored and the build aborts on the first test
failure:
> buildr test=all package
Not sure if that is expected behavior, but it was a change from buildr
1.2.10.
On Mon, 16 Nov 2009 16:33:07 -0500, Alex Boisvert
<al...@gmail.com> wrote:
> On Mon, Nov 16, 2009 at 1:19 PM, Greg Lucas <gr...@gmail.com> wrote:
>
>> Hm - switched to JDK 1.6 and it seems to be running fine now.
>>
>> TEST=all doesn't seem to work, the build stops on the first test
>> failure.
>> But otherwise it is running.
>>
>
> If you can reproduce this in a small project, please open an issue and
> I'll
> look into it.
>
> alex
--
Greg Lucas
Re: Bundled Buildr + JRuby distribution
Posted by Alex Boisvert <al...@gmail.com>.
On Mon, Nov 16, 2009 at 1:19 PM, Greg Lucas <gr...@gmail.com> wrote:
> Hm - switched to JDK 1.6 and it seems to be running fine now.
>
> TEST=all doesn't seem to work, the build stops on the first test failure.
> But otherwise it is running.
>
If you can reproduce this in a small project, please open an issue and I'll
look into it.
alex
Re: Bundled Buildr + JRuby distribution
Posted by Greg Lucas <gr...@gmail.com>.
Hm - switched to JDK 1.6 and it seems to be running fine now.
TEST=all doesn't seem to work, the build stops on the first test failure.
But otherwise it is running.
~Greg
On Mon, 16 Nov 2009 11:00:33 -0500, Alex Boisvert
<al...@gmail.com> wrote:
> On Mon, Nov 16, 2009 at 7:19 AM, Greg Lucas <gr...@gmail.com> wrote:
>
>> Thanks for putting this together Alex.
>>
>> I've been trying it out with our continuous integration system in order
>> to
>> build on multiple Linux machines. I'm getting:
>>
>> /opt/tools/buildr-1.3.5-jruby-1.4.0/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
>> `require': Could not load FFI Provider: FFI not available:
>> /tmp/jffi60799.tmp: Can't load AMD 64-bit .so on a AMD 64-bit platform
>> (LoadError)
>>
>> Has anyone seen this?
>>
>
> If you're running on JDK 1.5, you may want to try with JDK 1.6 to get a
> better error message.
>
> alex
Re: Bundled Buildr + JRuby distribution
Posted by Alex Boisvert <al...@gmail.com>.
On Mon, Nov 16, 2009 at 7:19 AM, Greg Lucas <gr...@gmail.com> wrote:
> Thanks for putting this together Alex.
>
> I've been trying it out with our continuous integration system in order to
> build on multiple Linux machines. I'm getting:
>
> /opt/tools/buildr-1.3.5-jruby-1.4.0/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `require': Could not load FFI Provider: FFI not available:
> /tmp/jffi60799.tmp: Can't load AMD 64-bit .so on a AMD 64-bit platform
> (LoadError)
>
> Has anyone seen this?
>
If you're running on JDK 1.5, you may want to try with JDK 1.6 to get a
better error message.
alex
Re: Bundled Buildr + JRuby distribution
Posted by Greg Lucas <gr...@gmail.com>.
Thanks for putting this together Alex.
I've been trying it out with our continuous integration system in order to
build on multiple Linux machines. I'm getting:
/opt/tools/buildr-1.3.5-jruby-1.4.0/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require': Could not load FFI Provider: FFI not available:
/tmp/jffi60799.tmp: Can't load AMD 64-bit .so on a AMD 64-bit platform
(LoadError)
Has anyone seen this?
--
Greg Lucas
Re: Bundled Buildr + JRuby distribution
Posted by Greg Lucas <gr...@gmail.com>.
Thanks for putting this together Alex.
I've been trying it out with our continuous integration system in order to
build on multiple Linux machines. I'm getting:
/opt/tools/buildr-1.3.5-jruby-1.4.0/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require': Could not load FFI Provider: FFI not available:
/tmp/jffi60799.tmp: Can't load AMD 64-bit .so on a AMD 64-bit platform
(LoadError)
Has anyone seen this?
--
Greg Lucas
Re: Bundled Buildr + JRuby distribution
Posted by Alexis Midon <al...@gmail.com>.
On Windows, it worked out of the box.
On Mac I had to make the ./bin/buildr file executable.
Thanks Alex!
On Tue, Nov 10, 2009 at 4:16 PM, Alex Boisvert <al...@gmail.com>wrote:
> Ok, updated the distro at
> http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip<http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip>
>
> Tested on both Linux and Windows.
>
> Let me know if you have any luck using it.
>
> alex
>
> On Tue, Nov 10, 2009 at 2:59 PM, Alex Boisvert <alex.boisvert@gmail.com
> >wrote:
>
> > Thanks, yes, I think I have solutions for both platforms now. Just need
> > to start VirtualBox to test the Windows part (which I should have done
> the
> > first time around).
> >
> > And I've now removed all other scripts (jirb, jrubyc, ...) so they don't
> > conflict with other JRuby installs.
> >
> > alex
> >
> >
> >
> > On Tue, Nov 10, 2009 at 2:53 PM, Nick Sieger <ni...@gmail.com>
> wrote:
> >
> >> Alex,
> >>
> >> For Windows, you can piggy back off our new native launcher in JRuby 1.4
> >> by copying jruby.exe to buildr.exe. This effectively does the same as
> "jruby
> >> -S buildr" would do. The PATH issue is trickier admittedly. You really
> need
> >> the shebang in the "buildr" script to point to the copy of JRuby that
> was
> >> bundled, instead of "#!/usr/bin/env jruby".
> >>
> >> /Nick
> >>
> >>
> >> On Nov 10, 2009, at 16:42 , Alex Boisvert wrote:
> >>
> >> Hmmmm.... for a start there's two big issues with this distro. First,
> if
> >>> you already have jruby in your PATH, things get confused and basically
> >>> nothing works. Second, there's no buildr.bat so it's pretty useless
> for
> >>> Windows users. (Unless they are willing to run "jruby -S buildr")
> >>>
> >>> I'll do another take later. Thanks for listening ;)
> >>>
> >>> alex
> >>>
> >>>
> >>> On Tue, Nov 10, 2009 at 2:04 PM, Alex Boisvert <
> alex.boisvert@gmail.com
> >>> >wrote:
> >>>
> >>> Hi,
> >>>>
> >>>> I've created an experimental distribution of Buildr 1.3.5 and JRuby
> >>>> 1.4.0
> >>>> and made it available at:
> >>>> http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip<http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip>
> <http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip>
> >>>> <http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip>
> >>>>
> >>>>
> >>>> The distro is 15M -- not too bad. I've trimmed the packaged JRuby of
> >>>> everything I could that didn't affect functionality, such as
> >>>> documentation
> >>>> and Ruby 1.9 support.
> >>>>
> >>>> To use it, simply
> >>>> 1) unzip in a directory,
> >>>> 2) set your PATH to point to the "bin" directory, and
> >>>> 3) run "buildr" as usual.
> >>>>
> >>>> Looking for feedback on how it works as a quick way to get
> >>>> yourself/other
> >>>> people started. If there's enough interest, it could become part of
> our
> >>>> supported distros.
> >>>>
> >>>> thanks,
> >>>> alex
> >>>>
> >>>>
> >>>>
> >>
> >
>
Re: Bundled Buildr + JRuby distribution
Posted by Alexis Midon <al...@gmail.com>.
On Windows, it worked out of the box.
On Mac I had to make the ./bin/buildr file executable.
Thanks Alex!
On Tue, Nov 10, 2009 at 4:16 PM, Alex Boisvert <al...@gmail.com>wrote:
> Ok, updated the distro at
> http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip<http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip>
>
> Tested on both Linux and Windows.
>
> Let me know if you have any luck using it.
>
> alex
>
> On Tue, Nov 10, 2009 at 2:59 PM, Alex Boisvert <alex.boisvert@gmail.com
> >wrote:
>
> > Thanks, yes, I think I have solutions for both platforms now. Just need
> > to start VirtualBox to test the Windows part (which I should have done
> the
> > first time around).
> >
> > And I've now removed all other scripts (jirb, jrubyc, ...) so they don't
> > conflict with other JRuby installs.
> >
> > alex
> >
> >
> >
> > On Tue, Nov 10, 2009 at 2:53 PM, Nick Sieger <ni...@gmail.com>
> wrote:
> >
> >> Alex,
> >>
> >> For Windows, you can piggy back off our new native launcher in JRuby 1.4
> >> by copying jruby.exe to buildr.exe. This effectively does the same as
> "jruby
> >> -S buildr" would do. The PATH issue is trickier admittedly. You really
> need
> >> the shebang in the "buildr" script to point to the copy of JRuby that
> was
> >> bundled, instead of "#!/usr/bin/env jruby".
> >>
> >> /Nick
> >>
> >>
> >> On Nov 10, 2009, at 16:42 , Alex Boisvert wrote:
> >>
> >> Hmmmm.... for a start there's two big issues with this distro. First,
> if
> >>> you already have jruby in your PATH, things get confused and basically
> >>> nothing works. Second, there's no buildr.bat so it's pretty useless
> for
> >>> Windows users. (Unless they are willing to run "jruby -S buildr")
> >>>
> >>> I'll do another take later. Thanks for listening ;)
> >>>
> >>> alex
> >>>
> >>>
> >>> On Tue, Nov 10, 2009 at 2:04 PM, Alex Boisvert <
> alex.boisvert@gmail.com
> >>> >wrote:
> >>>
> >>> Hi,
> >>>>
> >>>> I've created an experimental distribution of Buildr 1.3.5 and JRuby
> >>>> 1.4.0
> >>>> and made it available at:
> >>>> http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip<http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip>
> <http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip>
> >>>> <http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip>
> >>>>
> >>>>
> >>>> The distro is 15M -- not too bad. I've trimmed the packaged JRuby of
> >>>> everything I could that didn't affect functionality, such as
> >>>> documentation
> >>>> and Ruby 1.9 support.
> >>>>
> >>>> To use it, simply
> >>>> 1) unzip in a directory,
> >>>> 2) set your PATH to point to the "bin" directory, and
> >>>> 3) run "buildr" as usual.
> >>>>
> >>>> Looking for feedback on how it works as a quick way to get
> >>>> yourself/other
> >>>> people started. If there's enough interest, it could become part of
> our
> >>>> supported distros.
> >>>>
> >>>> thanks,
> >>>> alex
> >>>>
> >>>>
> >>>>
> >>
> >
>
Re: Bundled Buildr + JRuby distribution
Posted by Alex Boisvert <al...@gmail.com>.
Ok, updated the distro at
http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip
Tested on both Linux and Windows.
Let me know if you have any luck using it.
alex
On Tue, Nov 10, 2009 at 2:59 PM, Alex Boisvert <al...@gmail.com>wrote:
> Thanks, yes, I think I have solutions for both platforms now. Just need
> to start VirtualBox to test the Windows part (which I should have done the
> first time around).
>
> And I've now removed all other scripts (jirb, jrubyc, ...) so they don't
> conflict with other JRuby installs.
>
> alex
>
>
>
> On Tue, Nov 10, 2009 at 2:53 PM, Nick Sieger <ni...@gmail.com> wrote:
>
>> Alex,
>>
>> For Windows, you can piggy back off our new native launcher in JRuby 1.4
>> by copying jruby.exe to buildr.exe. This effectively does the same as "jruby
>> -S buildr" would do. The PATH issue is trickier admittedly. You really need
>> the shebang in the "buildr" script to point to the copy of JRuby that was
>> bundled, instead of "#!/usr/bin/env jruby".
>>
>> /Nick
>>
>>
>> On Nov 10, 2009, at 16:42 , Alex Boisvert wrote:
>>
>> Hmmmm.... for a start there's two big issues with this distro. First, if
>>> you already have jruby in your PATH, things get confused and basically
>>> nothing works. Second, there's no buildr.bat so it's pretty useless for
>>> Windows users. (Unless they are willing to run "jruby -S buildr")
>>>
>>> I'll do another take later. Thanks for listening ;)
>>>
>>> alex
>>>
>>>
>>> On Tue, Nov 10, 2009 at 2:04 PM, Alex Boisvert <alex.boisvert@gmail.com
>>> >wrote:
>>>
>>> Hi,
>>>>
>>>> I've created an experimental distribution of Buildr 1.3.5 and JRuby
>>>> 1.4.0
>>>> and made it available at:
>>>> http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip<http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip>
>>>> <http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip>
>>>>
>>>>
>>>> The distro is 15M -- not too bad. I've trimmed the packaged JRuby of
>>>> everything I could that didn't affect functionality, such as
>>>> documentation
>>>> and Ruby 1.9 support.
>>>>
>>>> To use it, simply
>>>> 1) unzip in a directory,
>>>> 2) set your PATH to point to the "bin" directory, and
>>>> 3) run "buildr" as usual.
>>>>
>>>> Looking for feedback on how it works as a quick way to get
>>>> yourself/other
>>>> people started. If there's enough interest, it could become part of our
>>>> supported distros.
>>>>
>>>> thanks,
>>>> alex
>>>>
>>>>
>>>>
>>
>
Re: Bundled Buildr + JRuby distribution
Posted by Alex Boisvert <al...@gmail.com>.
Ok, updated the distro at
http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip
Tested on both Linux and Windows.
Let me know if you have any luck using it.
alex
On Tue, Nov 10, 2009 at 2:59 PM, Alex Boisvert <al...@gmail.com>wrote:
> Thanks, yes, I think I have solutions for both platforms now. Just need
> to start VirtualBox to test the Windows part (which I should have done the
> first time around).
>
> And I've now removed all other scripts (jirb, jrubyc, ...) so they don't
> conflict with other JRuby installs.
>
> alex
>
>
>
> On Tue, Nov 10, 2009 at 2:53 PM, Nick Sieger <ni...@gmail.com> wrote:
>
>> Alex,
>>
>> For Windows, you can piggy back off our new native launcher in JRuby 1.4
>> by copying jruby.exe to buildr.exe. This effectively does the same as "jruby
>> -S buildr" would do. The PATH issue is trickier admittedly. You really need
>> the shebang in the "buildr" script to point to the copy of JRuby that was
>> bundled, instead of "#!/usr/bin/env jruby".
>>
>> /Nick
>>
>>
>> On Nov 10, 2009, at 16:42 , Alex Boisvert wrote:
>>
>> Hmmmm.... for a start there's two big issues with this distro. First, if
>>> you already have jruby in your PATH, things get confused and basically
>>> nothing works. Second, there's no buildr.bat so it's pretty useless for
>>> Windows users. (Unless they are willing to run "jruby -S buildr")
>>>
>>> I'll do another take later. Thanks for listening ;)
>>>
>>> alex
>>>
>>>
>>> On Tue, Nov 10, 2009 at 2:04 PM, Alex Boisvert <alex.boisvert@gmail.com
>>> >wrote:
>>>
>>> Hi,
>>>>
>>>> I've created an experimental distribution of Buildr 1.3.5 and JRuby
>>>> 1.4.0
>>>> and made it available at:
>>>> http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip<http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip>
>>>> <http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip>
>>>>
>>>>
>>>> The distro is 15M -- not too bad. I've trimmed the packaged JRuby of
>>>> everything I could that didn't affect functionality, such as
>>>> documentation
>>>> and Ruby 1.9 support.
>>>>
>>>> To use it, simply
>>>> 1) unzip in a directory,
>>>> 2) set your PATH to point to the "bin" directory, and
>>>> 3) run "buildr" as usual.
>>>>
>>>> Looking for feedback on how it works as a quick way to get
>>>> yourself/other
>>>> people started. If there's enough interest, it could become part of our
>>>> supported distros.
>>>>
>>>> thanks,
>>>> alex
>>>>
>>>>
>>>>
>>
>
Re: Bundled Buildr + JRuby distribution
Posted by Alex Boisvert <al...@gmail.com>.
Thanks, yes, I think I have solutions for both platforms now. Just need to
start VirtualBox to test the Windows part (which I should have done the
first time around).
And I've now removed all other scripts (jirb, jrubyc, ...) so they don't
conflict with other JRuby installs.
alex
On Tue, Nov 10, 2009 at 2:53 PM, Nick Sieger <ni...@gmail.com> wrote:
> Alex,
>
> For Windows, you can piggy back off our new native launcher in JRuby 1.4 by
> copying jruby.exe to buildr.exe. This effectively does the same as "jruby -S
> buildr" would do. The PATH issue is trickier admittedly. You really need the
> shebang in the "buildr" script to point to the copy of JRuby that was
> bundled, instead of "#!/usr/bin/env jruby".
>
> /Nick
>
>
> On Nov 10, 2009, at 16:42 , Alex Boisvert wrote:
>
> Hmmmm.... for a start there's two big issues with this distro. First, if
>> you already have jruby in your PATH, things get confused and basically
>> nothing works. Second, there's no buildr.bat so it's pretty useless for
>> Windows users. (Unless they are willing to run "jruby -S buildr")
>>
>> I'll do another take later. Thanks for listening ;)
>>
>> alex
>>
>>
>> On Tue, Nov 10, 2009 at 2:04 PM, Alex Boisvert <alex.boisvert@gmail.com
>> >wrote:
>>
>> Hi,
>>>
>>> I've created an experimental distribution of Buildr 1.3.5 and JRuby 1.4.0
>>> and made it available at:
>>> http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip<http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip>
>>> <http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip>
>>>
>>>
>>> The distro is 15M -- not too bad. I've trimmed the packaged JRuby of
>>> everything I could that didn't affect functionality, such as
>>> documentation
>>> and Ruby 1.9 support.
>>>
>>> To use it, simply
>>> 1) unzip in a directory,
>>> 2) set your PATH to point to the "bin" directory, and
>>> 3) run "buildr" as usual.
>>>
>>> Looking for feedback on how it works as a quick way to get yourself/other
>>> people started. If there's enough interest, it could become part of our
>>> supported distros.
>>>
>>> thanks,
>>> alex
>>>
>>>
>>>
>
Re: Bundled Buildr + JRuby distribution
Posted by Alex Boisvert <al...@gmail.com>.
Thanks, yes, I think I have solutions for both platforms now. Just need to
start VirtualBox to test the Windows part (which I should have done the
first time around).
And I've now removed all other scripts (jirb, jrubyc, ...) so they don't
conflict with other JRuby installs.
alex
On Tue, Nov 10, 2009 at 2:53 PM, Nick Sieger <ni...@gmail.com> wrote:
> Alex,
>
> For Windows, you can piggy back off our new native launcher in JRuby 1.4 by
> copying jruby.exe to buildr.exe. This effectively does the same as "jruby -S
> buildr" would do. The PATH issue is trickier admittedly. You really need the
> shebang in the "buildr" script to point to the copy of JRuby that was
> bundled, instead of "#!/usr/bin/env jruby".
>
> /Nick
>
>
> On Nov 10, 2009, at 16:42 , Alex Boisvert wrote:
>
> Hmmmm.... for a start there's two big issues with this distro. First, if
>> you already have jruby in your PATH, things get confused and basically
>> nothing works. Second, there's no buildr.bat so it's pretty useless for
>> Windows users. (Unless they are willing to run "jruby -S buildr")
>>
>> I'll do another take later. Thanks for listening ;)
>>
>> alex
>>
>>
>> On Tue, Nov 10, 2009 at 2:04 PM, Alex Boisvert <alex.boisvert@gmail.com
>> >wrote:
>>
>> Hi,
>>>
>>> I've created an experimental distribution of Buildr 1.3.5 and JRuby 1.4.0
>>> and made it available at:
>>> http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip<http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip>
>>> <http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip>
>>>
>>>
>>> The distro is 15M -- not too bad. I've trimmed the packaged JRuby of
>>> everything I could that didn't affect functionality, such as
>>> documentation
>>> and Ruby 1.9 support.
>>>
>>> To use it, simply
>>> 1) unzip in a directory,
>>> 2) set your PATH to point to the "bin" directory, and
>>> 3) run "buildr" as usual.
>>>
>>> Looking for feedback on how it works as a quick way to get yourself/other
>>> people started. If there's enough interest, it could become part of our
>>> supported distros.
>>>
>>> thanks,
>>> alex
>>>
>>>
>>>
>
Re: Bundled Buildr + JRuby distribution
Posted by Nick Sieger <ni...@gmail.com>.
Alex,
For Windows, you can piggy back off our new native launcher in JRuby
1.4 by copying jruby.exe to buildr.exe. This effectively does the same
as "jruby -S buildr" would do. The PATH issue is trickier admittedly.
You really need the shebang in the "buildr" script to point to the
copy of JRuby that was bundled, instead of "#!/usr/bin/env jruby".
/Nick
On Nov 10, 2009, at 16:42 , Alex Boisvert wrote:
> Hmmmm.... for a start there's two big issues with this distro.
> First, if
> you already have jruby in your PATH, things get confused and basically
> nothing works. Second, there's no buildr.bat so it's pretty useless
> for
> Windows users. (Unless they are willing to run "jruby -S buildr")
>
> I'll do another take later. Thanks for listening ;)
>
> alex
>
>
> On Tue, Nov 10, 2009 at 2:04 PM, Alex Boisvert <alex.boisvert@gmail.com
> >wrote:
>
>> Hi,
>>
>> I've created an experimental distribution of Buildr 1.3.5 and JRuby
>> 1.4.0
>> and made it available at:
>> http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip<http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip
>> >
>>
>> The distro is 15M -- not too bad. I've trimmed the packaged JRuby of
>> everything I could that didn't affect functionality, such as
>> documentation
>> and Ruby 1.9 support.
>>
>> To use it, simply
>> 1) unzip in a directory,
>> 2) set your PATH to point to the "bin" directory, and
>> 3) run "buildr" as usual.
>>
>> Looking for feedback on how it works as a quick way to get yourself/
>> other
>> people started. If there's enough interest, it could become part
>> of our
>> supported distros.
>>
>> thanks,
>> alex
>>
>>
Re: Bundled Buildr + JRuby distribution
Posted by Nick Sieger <ni...@gmail.com>.
Alex,
For Windows, you can piggy back off our new native launcher in JRuby
1.4 by copying jruby.exe to buildr.exe. This effectively does the same
as "jruby -S buildr" would do. The PATH issue is trickier admittedly.
You really need the shebang in the "buildr" script to point to the
copy of JRuby that was bundled, instead of "#!/usr/bin/env jruby".
/Nick
On Nov 10, 2009, at 16:42 , Alex Boisvert wrote:
> Hmmmm.... for a start there's two big issues with this distro.
> First, if
> you already have jruby in your PATH, things get confused and basically
> nothing works. Second, there's no buildr.bat so it's pretty useless
> for
> Windows users. (Unless they are willing to run "jruby -S buildr")
>
> I'll do another take later. Thanks for listening ;)
>
> alex
>
>
> On Tue, Nov 10, 2009 at 2:04 PM, Alex Boisvert <alex.boisvert@gmail.com
> >wrote:
>
>> Hi,
>>
>> I've created an experimental distribution of Buildr 1.3.5 and JRuby
>> 1.4.0
>> and made it available at:
>> http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip<http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip
>> >
>>
>> The distro is 15M -- not too bad. I've trimmed the packaged JRuby of
>> everything I could that didn't affect functionality, such as
>> documentation
>> and Ruby 1.9 support.
>>
>> To use it, simply
>> 1) unzip in a directory,
>> 2) set your PATH to point to the "bin" directory, and
>> 3) run "buildr" as usual.
>>
>> Looking for feedback on how it works as a quick way to get yourself/
>> other
>> people started. If there's enough interest, it could become part
>> of our
>> supported distros.
>>
>> thanks,
>> alex
>>
>>
Re: Bundled Buildr + JRuby distribution
Posted by Alex Boisvert <al...@gmail.com>.
Hmmmm.... for a start there's two big issues with this distro. First, if
you already have jruby in your PATH, things get confused and basically
nothing works. Second, there's no buildr.bat so it's pretty useless for
Windows users. (Unless they are willing to run "jruby -S buildr")
I'll do another take later. Thanks for listening ;)
alex
On Tue, Nov 10, 2009 at 2:04 PM, Alex Boisvert <al...@gmail.com>wrote:
> Hi,
>
> I've created an experimental distribution of Buildr 1.3.5 and JRuby 1.4.0
> and made it available at:
> http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip<http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip>
>
> The distro is 15M -- not too bad. I've trimmed the packaged JRuby of
> everything I could that didn't affect functionality, such as documentation
> and Ruby 1.9 support.
>
> To use it, simply
> 1) unzip in a directory,
> 2) set your PATH to point to the "bin" directory, and
> 3) run "buildr" as usual.
>
> Looking for feedback on how it works as a quick way to get yourself/other
> people started. If there's enough interest, it could become part of our
> supported distros.
>
> thanks,
> alex
>
>
Re: Bundled Buildr + JRuby distribution
Posted by Assaf Arkin <as...@labnotes.org>.
On Thu, Dec 17, 2009 at 7:27 AM, Alex Boisvert <al...@gmail.com>wrote:
> Hi Ittay,
>
> I'm unclear as to whether we'll be able to distribute it on the Apache
> site. We'll need to review the license on all packaged software against
> Apache policies.
>
Official Apache releases are source code and have to be clear of any
licensing issues.
There's more flexibility with convenience binary downloads (that are not
official releases), as long as they don't cause any licensing violations and
people won't get them confused with official releases.
Assaf
>
> My intention is definitely to synchronize the release of the all-in-one
> JRuby distribution with the official Apache Buildr release and worse case,
> distribute it via separate channels and link to it from our site -- not
> unlike what we do with RubyForge/GemCutter.
>
> If you have suggestions, I'm all ears.
>
> alex
>
> On Thu, Dec 17, 2009 at 12:37 AM, Ittay Dror <it...@gmail.com> wrote:
>
> > Any plans on making the distribution available in the site? Maybe using
> > --fast to run jruby and jrubyc to precompile all ruby files?
> >
> > Thanks
> > Ittay
> >
> >
> > Alex Boisvert wrote:
> >
> >> Hi,
> >>
> >> I've created an experimental distribution of Buildr 1.3.5 and JRuby
> 1.4.0
> >> and made it available at:
> >> http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip<
> http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip>
> >>
> >> The distro is 15M -- not too bad. I've trimmed the packaged JRuby of
> >> everything I could that didn't affect functionality, such as
> documentation
> >> and Ruby 1.9 support.
> >>
> >> To use it, simply
> >> 1) unzip in a directory,
> >> 2) set your PATH to point to the "bin" directory, and
> >> 3) run "buildr" as usual.
> >>
> >> Looking for feedback on how it works as a quick way to get
> yourself/other
> >> people started. If there's enough interest, it could become part of our
> >> supported distros.
> >>
> >> thanks,
> >> alex
> >>
> >>
> >>
> >
>
Re: Bundled Buildr + JRuby distribution
Posted by Alex Boisvert <al...@gmail.com>.
Hi Ittay,
I'm unclear as to whether we'll be able to distribute it on the Apache
site. We'll need to review the license on all packaged software against
Apache policies.
My intention is definitely to synchronize the release of the all-in-one
JRuby distribution with the official Apache Buildr release and worse case,
distribute it via separate channels and link to it from our site -- not
unlike what we do with RubyForge/GemCutter.
If you have suggestions, I'm all ears.
alex
On Thu, Dec 17, 2009 at 12:37 AM, Ittay Dror <it...@gmail.com> wrote:
> Any plans on making the distribution available in the site? Maybe using
> --fast to run jruby and jrubyc to precompile all ruby files?
>
> Thanks
> Ittay
>
>
> Alex Boisvert wrote:
>
>> Hi,
>>
>> I've created an experimental distribution of Buildr 1.3.5 and JRuby 1.4.0
>> and made it available at:
>> http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip<http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip>
>>
>> The distro is 15M -- not too bad. I've trimmed the packaged JRuby of
>> everything I could that didn't affect functionality, such as documentation
>> and Ruby 1.9 support.
>>
>> To use it, simply
>> 1) unzip in a directory,
>> 2) set your PATH to point to the "bin" directory, and
>> 3) run "buildr" as usual.
>>
>> Looking for feedback on how it works as a quick way to get yourself/other
>> people started. If there's enough interest, it could become part of our
>> supported distros.
>>
>> thanks,
>> alex
>>
>>
>>
>
Re: Bundled Buildr + JRuby distribution
Posted by Daniel Spiewak <dj...@gmail.com>.
Precompiling all of the .rb scripts is a really good idea. That would
certainly help improve performance of the all-in-one bundle, especially on
JRuby 1.4 and later.
Daniel
On Thu, Dec 17, 2009 at 2:37 AM, Ittay Dror <it...@gmail.com> wrote:
> Any plans on making the distribution available in the site? Maybe using
> --fast to run jruby and jrubyc to precompile all ruby files?
>
> Thanks
> Ittay
>
>
> Alex Boisvert wrote:
>
>> Hi,
>>
>> I've created an experimental distribution of Buildr 1.3.5 and JRuby 1.4.0
>> and made it available at:
>> http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip<http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip>
>>
>> The distro is 15M -- not too bad. I've trimmed the packaged JRuby of
>> everything I could that didn't affect functionality, such as documentation
>> and Ruby 1.9 support.
>>
>> To use it, simply
>> 1) unzip in a directory,
>> 2) set your PATH to point to the "bin" directory, and
>> 3) run "buildr" as usual.
>>
>> Looking for feedback on how it works as a quick way to get yourself/other
>> people started. If there's enough interest, it could become part of our
>> supported distros.
>>
>> thanks,
>> alex
>>
>>
>>
>
Re: Bundled Buildr + JRuby distribution
Posted by Ittay Dror <it...@gmail.com>.
Any plans on making the distribution available in the site? Maybe using
--fast to run jruby and jrubyc to precompile all ruby files?
Thanks
Ittay
Alex Boisvert wrote:
> Hi,
>
> I've created an experimental distribution of Buildr 1.3.5 and JRuby 1.4.0
> and made it available at:
> http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip
>
> The distro is 15M -- not too bad. I've trimmed the packaged JRuby of
> everything I could that didn't affect functionality, such as documentation
> and Ruby 1.9 support.
>
> To use it, simply
> 1) unzip in a directory,
> 2) set your PATH to point to the "bin" directory, and
> 3) run "buildr" as usual.
>
> Looking for feedback on how it works as a quick way to get yourself/other
> people started. If there's enough interest, it could become part of our
> supported distros.
>
> thanks,
> alex
>
>
Re: Bundled Buildr + JRuby distribution
Posted by Alex Boisvert <al...@gmail.com>.
Hmmmm.... for a start there's two big issues with this distro. First, if
you already have jruby in your PATH, things get confused and basically
nothing works. Second, there's no buildr.bat so it's pretty useless for
Windows users. (Unless they are willing to run "jruby -S buildr")
I'll do another take later. Thanks for listening ;)
alex
On Tue, Nov 10, 2009 at 2:04 PM, Alex Boisvert <al...@gmail.com>wrote:
> Hi,
>
> I've created an experimental distribution of Buildr 1.3.5 and JRuby 1.4.0
> and made it available at:
> http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip<http://people.apache.org/%7Eboisvert/buildr-1.3.5-jruby-1.4.0.zip>
>
> The distro is 15M -- not too bad. I've trimmed the packaged JRuby of
> everything I could that didn't affect functionality, such as documentation
> and Ruby 1.9 support.
>
> To use it, simply
> 1) unzip in a directory,
> 2) set your PATH to point to the "bin" directory, and
> 3) run "buildr" as usual.
>
> Looking for feedback on how it works as a quick way to get yourself/other
> people started. If there's enough interest, it could become part of our
> supported distros.
>
> thanks,
> alex
>
>