You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@buildr.apache.org by Matei Zaharia <ma...@apache.org> on 2010/11/13 01:47:21 UTC
Packaging buildr with a project
I've taken a quick look at Buildr and would like to use it in my Scala project, but I'd prefer not to ask users to install it separately (i.e. install ruby and then gem install buildr). Is it at all common to include Buildr and JRuby within a project so that users only need a JVM on their system to build the project? This is one of the things I liked about SBT.
I'm asking this partly due to my own experience trying to install Buildr on OS X: the version in rubygems didn't build because Java update 3 removed the include directory from JAVA_HOME, installing the Java developer package mentioned on http://buildr.apache.org/installing.html didn't help, and even the install-jruby.sh script mentioned at the top of the page was out of date (it downloads JRuby 1.1.6, but Buildr now requires JRuby 1.5). I eventually ended up installing JRuby manually and then using its gem to install Buildr. I could certainly tell users to do this, but since I just ended up downloading some Java code, I figured it might be easier to just ship that code with my project like SBT does.
Matei
Re: Packaging buildr with a project
Posted by Alex Boisvert <al...@gmail.com>.
Hi Matei,
I'll update the install script for JRuby -- you're right that it's out of
date.
In the past, we've also created an "all-in-one" JRuby distrition with the
buildr gem (and dependencies) all pre-installed in a single zip. It helps
make the first-time experience better. I'll create a new one for buildr
1.4.3. Give me a few days ...
alex
On Fri, Nov 12, 2010 at 4:47 PM, Matei Zaharia <ma...@apache.org> wrote:
> I've taken a quick look at Buildr and would like to use it in my Scala
> project, but I'd prefer not to ask users to install it separately (i.e.
> install ruby and then gem install buildr). Is it at all common to include
> Buildr and JRuby within a project so that users only need a JVM on their
> system to build the project? This is one of the things I liked about SBT.
>
> I'm asking this partly due to my own experience trying to install Buildr on
> OS X: the version in rubygems didn't build because Java update 3 removed the
> include directory from JAVA_HOME, installing the Java developer package
> mentioned on http://buildr.apache.org/installing.html didn't help, and
> even the install-jruby.sh script mentioned at the top of the page was out of
> date (it downloads JRuby 1.1.6, but Buildr now requires JRuby 1.5). I
> eventually ended up installing JRuby manually and then using its gem to
> install Buildr. I could certainly tell users to do this, but since I just
> ended up downloading some Java code, I figured it might be easier to just
> ship that code with my project like SBT does.
>
> Matei