On Thu, Dec 17, 2009 at 7:27 AM, Alex Boisvert <[email protected]>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 <[email protected]> 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 > >> > >> > >> > > >
