Re: Bundled Buildr + JRuby distribution

2009-12-17 Thread Ittay Dror
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

2009-12-17 Thread Alex Boisvert
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 ittay.d...@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.ziphttp://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






rjb-1.1.9 does not build on Windows with JDK in default location

2009-12-17 Thread Will Rogers
I just went through an unpleasant two hours trying to get buildr to install
on Windows. May I make two suggestions to improve your Installing on
Windows section at http://buildr.apache.org/installing.html ?

1. Installing the Ruby one-click installer is not enough, you also need the
devkit so you have a compiler and make. The devkit is a 7zip file available
on the same page as the one-click installer. You just extract it to your
Ruby directory and make sure the paths in devkit/msys/1.0.11/etc/fstab are
accurate.

2. The version rjb-1.1.9 required by buildr-1.3.5 does not build when your
JAVA_HOME has spaces in the path. The default install location is in
C:/Program Files, which means rjb will not build. rjb-1.2.0 works, so
please either release an updated buildr gem that works with this fixed
version of rjb or suggest a work-around of installing the JDK to a
non-default location with no spaces in the path.


Thanks,

-- Will


Re: rjb-1.1.9 does not build on Windows with JDK in default location

2009-12-17 Thread Alex Boisvert
Hi Will,

Thanks for sharing your experience.  I'm sure it will be useful to others.

On Thu, Dec 17, 2009 at 7:48 AM, Will Rogers wjrog...@gmail.com wrote:

 I just went through an unpleasant two hours trying to get buildr to install
 on Windows. May I make two suggestions to improve your Installing on
 Windows section at http://buildr.apache.org/installing.html ?

 1. Installing the Ruby one-click installer is not enough, you also need the
 devkit so you have a compiler and make. The devkit is a 7zip file available
 on the same page as the one-click installer. You just extract it to your
 Ruby directory and make sure the paths in devkit/msys/1.0.11/etc/fstab are
 accurate.


Ok, added a mention of the devkit under the Windows section.   (Website not
yet updated)


 2. The version rjb-1.1.9 required by buildr-1.3.5 does not build when your
 JAVA_HOME has spaces in the path. The default install location is in
 C:/Program Files, which means rjb will not build. rjb-1.2.0 works, so
 please either release an updated buildr gem that works with this fixed
 version of rjb or suggest a work-around of installing the JDK to a
 non-default location with no spaces in the path.


Ok, we'll upgrade to rjb-1.2.0 for Buildr 1.4.0 so this shouldn't be an
issue in the future.

http://issues.apache.org/jira/browse/BUILDR-356

alex


Re: rjb-1.1.9 does not build on Windows with JDK in default location

2009-12-17 Thread Will Rogers
On Thu, Dec 17, 2009 at 1:23 PM, Assaf Arkin as...@labnotes.org wrote:
  2. The version rjb-1.1.9 required by buildr-1.3.5 does not build when your
  JAVA_HOME has spaces in the path

 I'm not sure why you're getting the all-platforms gem with RJB 1.1.9
 dependency, but you shouldn't.   Could be one of the gems was in the
 switchover from Rubyforge to Gemcutter?

The latest versions of the Ruby one click installer are compiled with
mingw, not msvc6, and I believe that means they are not binary
compatible with -mswin32 gems. Rubygems selects the basic
all-platforms gems with this build of Ruby.


Re: Bundled Buildr + JRuby distribution

2009-12-17 Thread Assaf Arkin
On Thu, Dec 17, 2009 at 7:27 AM, Alex Boisvert alex.boisv...@gmail.comwrote:

 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 ittay.d...@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: rjb-1.1.9 does not build on Windows with JDK in default location

2009-12-17 Thread Assaf Arkin
On Thu, Dec 17, 2009 at 10:29 AM, Will Rogers wjrog...@gmail.com wrote:

 On Thu, Dec 17, 2009 at 1:23 PM, Assaf Arkin as...@labnotes.org wrote:
   2. The version rjb-1.1.9 required by buildr-1.3.5 does not build when
 your
   JAVA_HOME has spaces in the path
 
  I'm not sure why you're getting the all-platforms gem with RJB 1.1.9
  dependency, but you shouldn't.   Could be one of the gems was in the
  switchover from Rubyforge to Gemcutter?

 The latest versions of the Ruby one click installer are compiled with
 mingw, not msvc6, and I believe that means they are not binary
 compatible with -mswin32 gems. Rubygems selects the basic
 all-platforms gems with this build of Ruby.


I think they're just using a different platform identifier, because their
suggestion is:

gem install --platform=mswin32
http://wiki.github.com/oneclick/rubyinstaller/gem-list

Could be targeted with a specific Buildr gem that's identical to -mswin32
but has the proper platform identifier to match one-click installer.

Assaf