You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@buildr.apache.org by Eung-ju Park <eu...@gmail.com> on 2008/09/13 14:01:41 UTC
Current Rakefile is broken
I tried to build buildr but it raise error like below.
$ rake
(in /Users/eungju/src/buildr)
rake aborted!
undefined method `include' for []:Array
/Users/eungju/src/buildr/rakefile:46
(See full trace by running task with --trace)
I don't know about rake but I tried something. I guess attached patch will
fix it.
--
* LukeSkywalker: Is the dark side stronger?
* MasterYoda: No...no...no. Quicker, easier, more seductive.
Re: Current Rakefile is broken
Posted by Eung-ju Park <eu...@gmail.com>.
Sorry my patch doesn't work. It just delays error :-)
On Sat, Sep 13, 2008 at 11:17 PM, Eung-ju Park <eu...@gmail.com> wrote:
>
>
> On Sat, Sep 13, 2008 at 10:12 PM, lacton <la...@users.sourceforge.net>wrote:
>
>> On Sat, Sep 13, 2008 at 2:01 PM, Eung-ju Park <eu...@gmail.com> wrote:
>> > I tried to build buildr but it raise error like below.
>> >
>> > $ rake
>> > (in /Users/eungju/src/buildr)
>> > rake aborted!
>> > undefined method `include' for []:Array
>> > /Users/eungju/src/buildr/rakefile:46
>> > (See full trace by running task with --trace)
>>
>> That's interesting. When I run 'rake' with no task name, I get "Don't
>> know how to build task 'default'".
>>
>> What version of rake are you using? (i.e., 'rake --version')
>> What SVN revision are you building from? (i.e., 'svn info | grep
>> Revision')
>
>
> here it is
> $ ruby --version
> ruby 1.8.6 (2008-03-03 patchlevel 114) [universal-darwin9.0]
> $ rake --version
> rake, version 0.8.2
> $ svn info | grep Revision
> Revision: 694906
>
>
>
>>
>>
>> > I don't know about rake but I tried something. I guess attached patch
>> will
>> > fix it.
>>
>> Which patch are you referring to?
>
>
> Mailing list doesn't deliver attachment files. Here is the patch
>
> Index: Rakefile
> ===================================================================
> --- Rakefile (revision 694906)
> +++ Rakefile (working copy)
> @@ -43,11 +43,12 @@
> ENV['incubating'] = 'true'
> ENV['staging'] = "people.apache.org:~/public_html/#{spec.name
> }/#{spec.version}"
>
> -task('apache.license').prerequisites.include(spec.files).
> +task 'apache:license' do |task|
> + task.prerequisites.include(spec.files).
> exclude('.class', '.png', '.jar', '.tif', '.textile', '.icns',
> 'README', 'LICENSE', 'CHANGELOG', 'DISCLAIMER', 'NOTICE',
> 'etc/KEYS', 'etc/git-svn-authors')
> +end
>
> -
> task 'spec:check' do
> print 'Checking that we have JRuby, Scala and Groovy available ... '
> fail 'Full testing requires JRuby!' unless which('jruby')
>
>
>
>>
>>
>> Lacton
>>
>
>
> --
> * LukeSkywalker: Is the dark side stronger?
> * MasterYoda: No...no...no. Quicker, easier, more seductive.
>
--
* LukeSkywalker: Is the dark side stronger?
* MasterYoda: No...no...no. Quicker, easier, more seductive.
Re: Current Rakefile is broken
Posted by Assaf Arkin <ar...@intalio.com>.
On Thu, Sep 25, 2008 at 1:32 PM, Victor Hugo Borja <vi...@gmail.com> wrote:
> Eung-ju, Thanks for testing :)
>
> On Thu, Sep 25, 2008 at 10:39 AM, Assaf Arkin <ar...@intalio.com> wrote:
>
>> Perhaps we should cut a 1.3.3 release, then use this as a starting
>> point for 1.3.4?
>>
>
> I've tested the rake-0.8.2 branch with the new rake version and all was ok
> for me,
> so I updated the requirement to 0.8.3.
>
> Yeah, I think it's time for a new buildr release.
OK. I cleared out the list of issues remaining for 1.3.3, I expect
one more issue from the Ode team about release tagging. Can everyone
have a look at the remaining list:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310734&fixfor=12313289
Assaf
>
>
>> Assaf
>>
>> >
>> > I've also tested that branch with rake-0.8.1, and everything seems
>> normal.
>> > So, could anyone try it ?.
>> >
>> > On Sat, Sep 20, 2008 at 2:15 PM, Assaf Arkin <ar...@intalio.com> wrote:
>> >
>> >> On Sat, Sep 20, 2008 at 2:20 AM, lacton <la...@users.sourceforge.net>
>> >> wrote:
>> >> > Reading your proposed patch, I get the feeling that if we try to
>> >> > support simultaneously rake 0.8.1 and rake 0.8.2, the code won't be as
>> >> > clean and simple as it is now.
>> >> >
>> >> > If possible, I'd rather we adopt an all-or-nothing approach. Either
>> >> > we support rake 0.8.1 only, or we fully migrate the trunk to rake
>> >> > 0.8.2.
>> >>
>> >> One or the other.
>> >>
>> >> I think this, though, is a different problem. If you check out the
>> >> source code and run rake install, the target gem will use Rake 0.8.1
>> >> (as per buildr.gemspec), but the rake install task will run buildr
>> >> compile (on buildr.buildfile). This instance of buildr is run from
>> >> source, a classical bootstrap problem, and ends up picking the latest
>> >> version of Rake.
>> >>
>> >> I committed a change to make it use the _buildr script, which runs
>> >> Buildr from source and forces it to use Rake 0.8.1.
>> >>
>> >> Assaf
>> >>
>> >>
>> >> >
>> >> > I'd like to hear others' opinions about this issue.
>> >> >
>> >> > Lacton
>> >> >
>> >> > On Fri, Sep 19, 2008 at 3:51 PM, Eung-ju Park <eu...@gmail.com>
>> wrote:
>> >> >> I have investigated changes of rake 0.8.2. Behavior of
>> >> >> Rake::Application#have_rakefile was changed.
>> >> >>
>> >> >> Below patch would be helpful to build buildr with rake 0.8.2.
>> >> >>
>> >> >> Index: lib/buildr/core/application.rb
>> >> >> ===================================================================
>> >> >> --- lib/buildr/core/application.rb (revision 697069)
>> >> >> +++ lib/buildr/core/application.rb (working copy)
>> >> >> @@ -225,10 +225,20 @@
>> >> >> @gems = installed
>> >> >> end
>> >> >>
>> >> >> + # In rake 0.8.2 have_rakefile returns location of rakefile. It
>> >> doesn't
>> >> >> set @rakefile
>> >> >> + def have_buildfile
>> >> >> + location_or_boolean = have_rakefile
>> >> >> + if location_or_boolean.kind_of? String
>> >> >> + @rakefile = location_or_boolean
>> >> >> + return !@rakefile.nil?
>> >> >> + end
>> >> >> + location_or_boolean
>> >> >> + end
>> >> >> +
>> >> >> def find_buildfile
>> >> >> here = original_dir
>> >> >> Dir.chdir(here) unless Dir.pwd == here
>> >> >> - while ! have_rakefile
>> >> >> + while ! have_buildfile
>> >> >> Dir.chdir('..')
>> >> >> if Dir.pwd == here || options.nosearch
>> >> >> error = "No Buildfile found (looking for:
>> #{@rakefiles.join(',
>> >> >> ')})"
>> >> >>
>> >> >>
>> >> >> On Sun, Sep 14, 2008 at 2:11 AM, lacton <
>> lacton@users.sourceforge.net
>> >> >wrote:
>> >> >>
>> >> >>> On Sat, Sep 13, 2008 at 6:58 PM, Eung-ju Park <eu...@gmail.com>
>> >> wrote:
>> >> >>> > I guess two changes makes buildr can't work with rake 0.8.2.
>> >> >>> >
>> >> >>> > 1.
>> >> >>> >
>> >> >>>
>> >>
>> http://github.com/jimweirich/rake/commit/68303da1aeda78533c044f2a01a99a619fdb1932Prerequisites
>> >> >>> > are no longer FileLists
>> >> >>> >
>> >> >>> > 2.
>> >> >>> >
>> >> >>>
>> >>
>> http://github.com/jimweirich/rake/commit/41a334b4e6bd3175202675ad289668f457ef73a9Applied
>> >> >>> > optparse patch
>> >> >>> > Buildr::Application extends Rake::Application. In rake 0.8.2,
>> >> >>> command-line
>> >> >>> > argument parsing has changed. So there is some mismatch.
>> >> >>>
>> >> >>> Thanks for the information. It looks like migrating buildr to rake
>> >> >>> 0.8.2 will take some time.
>> >> >>>
>> >> >>> Lacton
>> >> >>>
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> * LukeSkywalker: Is the dark side stronger?
>> >> >> * MasterYoda: No...no...no. Quicker, easier, more seductive.
>> >> >
>> >>
>> >
>> >
>> >
>> > --
>> > vic
>> >
>> > Quaerendo invenietis.
>> >
>>
>
>
>
> --
> vic
>
> Quaerendo invenietis.
>
Re: Current Rakefile is broken
Posted by Victor Hugo Borja <vi...@gmail.com>.
Eung-ju, Thanks for testing :)
On Thu, Sep 25, 2008 at 10:39 AM, Assaf Arkin <ar...@intalio.com> wrote:
> Perhaps we should cut a 1.3.3 release, then use this as a starting
> point for 1.3.4?
>
I've tested the rake-0.8.2 branch with the new rake version and all was ok
for me,
so I updated the requirement to 0.8.3.
Yeah, I think it's time for a new buildr release.
> Assaf
>
> >
> > I've also tested that branch with rake-0.8.1, and everything seems
> normal.
> > So, could anyone try it ?.
> >
> > On Sat, Sep 20, 2008 at 2:15 PM, Assaf Arkin <ar...@intalio.com> wrote:
> >
> >> On Sat, Sep 20, 2008 at 2:20 AM, lacton <la...@users.sourceforge.net>
> >> wrote:
> >> > Reading your proposed patch, I get the feeling that if we try to
> >> > support simultaneously rake 0.8.1 and rake 0.8.2, the code won't be as
> >> > clean and simple as it is now.
> >> >
> >> > If possible, I'd rather we adopt an all-or-nothing approach. Either
> >> > we support rake 0.8.1 only, or we fully migrate the trunk to rake
> >> > 0.8.2.
> >>
> >> One or the other.
> >>
> >> I think this, though, is a different problem. If you check out the
> >> source code and run rake install, the target gem will use Rake 0.8.1
> >> (as per buildr.gemspec), but the rake install task will run buildr
> >> compile (on buildr.buildfile). This instance of buildr is run from
> >> source, a classical bootstrap problem, and ends up picking the latest
> >> version of Rake.
> >>
> >> I committed a change to make it use the _buildr script, which runs
> >> Buildr from source and forces it to use Rake 0.8.1.
> >>
> >> Assaf
> >>
> >>
> >> >
> >> > I'd like to hear others' opinions about this issue.
> >> >
> >> > Lacton
> >> >
> >> > On Fri, Sep 19, 2008 at 3:51 PM, Eung-ju Park <eu...@gmail.com>
> wrote:
> >> >> I have investigated changes of rake 0.8.2. Behavior of
> >> >> Rake::Application#have_rakefile was changed.
> >> >>
> >> >> Below patch would be helpful to build buildr with rake 0.8.2.
> >> >>
> >> >> Index: lib/buildr/core/application.rb
> >> >> ===================================================================
> >> >> --- lib/buildr/core/application.rb (revision 697069)
> >> >> +++ lib/buildr/core/application.rb (working copy)
> >> >> @@ -225,10 +225,20 @@
> >> >> @gems = installed
> >> >> end
> >> >>
> >> >> + # In rake 0.8.2 have_rakefile returns location of rakefile. It
> >> doesn't
> >> >> set @rakefile
> >> >> + def have_buildfile
> >> >> + location_or_boolean = have_rakefile
> >> >> + if location_or_boolean.kind_of? String
> >> >> + @rakefile = location_or_boolean
> >> >> + return !@rakefile.nil?
> >> >> + end
> >> >> + location_or_boolean
> >> >> + end
> >> >> +
> >> >> def find_buildfile
> >> >> here = original_dir
> >> >> Dir.chdir(here) unless Dir.pwd == here
> >> >> - while ! have_rakefile
> >> >> + while ! have_buildfile
> >> >> Dir.chdir('..')
> >> >> if Dir.pwd == here || options.nosearch
> >> >> error = "No Buildfile found (looking for:
> #{@rakefiles.join(',
> >> >> ')})"
> >> >>
> >> >>
> >> >> On Sun, Sep 14, 2008 at 2:11 AM, lacton <
> lacton@users.sourceforge.net
> >> >wrote:
> >> >>
> >> >>> On Sat, Sep 13, 2008 at 6:58 PM, Eung-ju Park <eu...@gmail.com>
> >> wrote:
> >> >>> > I guess two changes makes buildr can't work with rake 0.8.2.
> >> >>> >
> >> >>> > 1.
> >> >>> >
> >> >>>
> >>
> http://github.com/jimweirich/rake/commit/68303da1aeda78533c044f2a01a99a619fdb1932Prerequisites
> >> >>> > are no longer FileLists
> >> >>> >
> >> >>> > 2.
> >> >>> >
> >> >>>
> >>
> http://github.com/jimweirich/rake/commit/41a334b4e6bd3175202675ad289668f457ef73a9Applied
> >> >>> > optparse patch
> >> >>> > Buildr::Application extends Rake::Application. In rake 0.8.2,
> >> >>> command-line
> >> >>> > argument parsing has changed. So there is some mismatch.
> >> >>>
> >> >>> Thanks for the information. It looks like migrating buildr to rake
> >> >>> 0.8.2 will take some time.
> >> >>>
> >> >>> Lacton
> >> >>>
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> * LukeSkywalker: Is the dark side stronger?
> >> >> * MasterYoda: No...no...no. Quicker, easier, more seductive.
> >> >
> >>
> >
> >
> >
> > --
> > vic
> >
> > Quaerendo invenietis.
> >
>
--
vic
Quaerendo invenietis.
Re: Current Rakefile is broken
Posted by Assaf Arkin <ar...@intalio.com>.
On Wed, Sep 24, 2008 at 9:22 PM, Victor Hugo Borja <vi...@gmail.com> wrote:
> Assaf,
>
> Today I've been working on a rake-0.8.2 branch, I think I've finished with
> the changes to get compatible with
> the latest version of rake.
> http://github.com/vic/buildr/commits/rake-0.8.2
Thanks. Incidentally, Rake 0.8.3 was just released to the world, but
0.8.3 looks like bug fixes for 0.8.2, it's the transition from 0.8.1
to 0.8.2 that has me worried.
Perhaps we should cut a 1.3.3 release, then use this as a starting
point for 1.3.4?
Assaf
>
> I've also tested that branch with rake-0.8.1, and everything seems normal.
> So, could anyone try it ?.
>
> On Sat, Sep 20, 2008 at 2:15 PM, Assaf Arkin <ar...@intalio.com> wrote:
>
>> On Sat, Sep 20, 2008 at 2:20 AM, lacton <la...@users.sourceforge.net>
>> wrote:
>> > Reading your proposed patch, I get the feeling that if we try to
>> > support simultaneously rake 0.8.1 and rake 0.8.2, the code won't be as
>> > clean and simple as it is now.
>> >
>> > If possible, I'd rather we adopt an all-or-nothing approach. Either
>> > we support rake 0.8.1 only, or we fully migrate the trunk to rake
>> > 0.8.2.
>>
>> One or the other.
>>
>> I think this, though, is a different problem. If you check out the
>> source code and run rake install, the target gem will use Rake 0.8.1
>> (as per buildr.gemspec), but the rake install task will run buildr
>> compile (on buildr.buildfile). This instance of buildr is run from
>> source, a classical bootstrap problem, and ends up picking the latest
>> version of Rake.
>>
>> I committed a change to make it use the _buildr script, which runs
>> Buildr from source and forces it to use Rake 0.8.1.
>>
>> Assaf
>>
>>
>> >
>> > I'd like to hear others' opinions about this issue.
>> >
>> > Lacton
>> >
>> > On Fri, Sep 19, 2008 at 3:51 PM, Eung-ju Park <eu...@gmail.com> wrote:
>> >> I have investigated changes of rake 0.8.2. Behavior of
>> >> Rake::Application#have_rakefile was changed.
>> >>
>> >> Below patch would be helpful to build buildr with rake 0.8.2.
>> >>
>> >> Index: lib/buildr/core/application.rb
>> >> ===================================================================
>> >> --- lib/buildr/core/application.rb (revision 697069)
>> >> +++ lib/buildr/core/application.rb (working copy)
>> >> @@ -225,10 +225,20 @@
>> >> @gems = installed
>> >> end
>> >>
>> >> + # In rake 0.8.2 have_rakefile returns location of rakefile. It
>> doesn't
>> >> set @rakefile
>> >> + def have_buildfile
>> >> + location_or_boolean = have_rakefile
>> >> + if location_or_boolean.kind_of? String
>> >> + @rakefile = location_or_boolean
>> >> + return !@rakefile.nil?
>> >> + end
>> >> + location_or_boolean
>> >> + end
>> >> +
>> >> def find_buildfile
>> >> here = original_dir
>> >> Dir.chdir(here) unless Dir.pwd == here
>> >> - while ! have_rakefile
>> >> + while ! have_buildfile
>> >> Dir.chdir('..')
>> >> if Dir.pwd == here || options.nosearch
>> >> error = "No Buildfile found (looking for: #{@rakefiles.join(',
>> >> ')})"
>> >>
>> >>
>> >> On Sun, Sep 14, 2008 at 2:11 AM, lacton <lacton@users.sourceforge.net
>> >wrote:
>> >>
>> >>> On Sat, Sep 13, 2008 at 6:58 PM, Eung-ju Park <eu...@gmail.com>
>> wrote:
>> >>> > I guess two changes makes buildr can't work with rake 0.8.2.
>> >>> >
>> >>> > 1.
>> >>> >
>> >>>
>> http://github.com/jimweirich/rake/commit/68303da1aeda78533c044f2a01a99a619fdb1932Prerequisites
>> >>> > are no longer FileLists
>> >>> >
>> >>> > 2.
>> >>> >
>> >>>
>> http://github.com/jimweirich/rake/commit/41a334b4e6bd3175202675ad289668f457ef73a9Applied
>> >>> > optparse patch
>> >>> > Buildr::Application extends Rake::Application. In rake 0.8.2,
>> >>> command-line
>> >>> > argument parsing has changed. So there is some mismatch.
>> >>>
>> >>> Thanks for the information. It looks like migrating buildr to rake
>> >>> 0.8.2 will take some time.
>> >>>
>> >>> Lacton
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> * LukeSkywalker: Is the dark side stronger?
>> >> * MasterYoda: No...no...no. Quicker, easier, more seductive.
>> >
>>
>
>
>
> --
> vic
>
> Quaerendo invenietis.
>
Re: Current Rakefile is broken
Posted by Eung-ju Park <eu...@gmail.com>.
I tried rake-0.8.2 branch. It works good with rake 0.8.1 and rake 0.8.2.
My OS is Mac OS X. Ruby is Macports ruby 1.8.7 (2008-08-11 patchlevel 72).
On Thu, Sep 25, 2008 at 1:22 PM, Victor Hugo Borja <vi...@gmail.com>wrote:
> Assaf,
>
> Today I've been working on a rake-0.8.2 branch, I think I've finished with
> the changes to get compatible with
> the latest version of rake.
> http://github.com/vic/buildr/commits/rake-0.8.2
>
> I've also tested that branch with rake-0.8.1, and everything seems normal.
> So, could anyone try it ?.
>
> On Sat, Sep 20, 2008 at 2:15 PM, Assaf Arkin <ar...@intalio.com> wrote:
>
> > On Sat, Sep 20, 2008 at 2:20 AM, lacton <la...@users.sourceforge.net>
> > wrote:
> > > Reading your proposed patch, I get the feeling that if we try to
> > > support simultaneously rake 0.8.1 and rake 0.8.2, the code won't be as
> > > clean and simple as it is now.
> > >
> > > If possible, I'd rather we adopt an all-or-nothing approach. Either
> > > we support rake 0.8.1 only, or we fully migrate the trunk to rake
> > > 0.8.2.
> >
> > One or the other.
> >
> > I think this, though, is a different problem. If you check out the
> > source code and run rake install, the target gem will use Rake 0.8.1
> > (as per buildr.gemspec), but the rake install task will run buildr
> > compile (on buildr.buildfile). This instance of buildr is run from
> > source, a classical bootstrap problem, and ends up picking the latest
> > version of Rake.
> >
> > I committed a change to make it use the _buildr script, which runs
> > Buildr from source and forces it to use Rake 0.8.1.
> >
> > Assaf
> >
> >
> > >
> > > I'd like to hear others' opinions about this issue.
> > >
> > > Lacton
> > >
> > > On Fri, Sep 19, 2008 at 3:51 PM, Eung-ju Park <eu...@gmail.com>
> wrote:
> > >> I have investigated changes of rake 0.8.2. Behavior of
> > >> Rake::Application#have_rakefile was changed.
> > >>
> > >> Below patch would be helpful to build buildr with rake 0.8.2.
> > >>
> > >> Index: lib/buildr/core/application.rb
> > >> ===================================================================
> > >> --- lib/buildr/core/application.rb (revision 697069)
> > >> +++ lib/buildr/core/application.rb (working copy)
> > >> @@ -225,10 +225,20 @@
> > >> @gems = installed
> > >> end
> > >>
> > >> + # In rake 0.8.2 have_rakefile returns location of rakefile. It
> > doesn't
> > >> set @rakefile
> > >> + def have_buildfile
> > >> + location_or_boolean = have_rakefile
> > >> + if location_or_boolean.kind_of? String
> > >> + @rakefile = location_or_boolean
> > >> + return !@rakefile.nil?
> > >> + end
> > >> + location_or_boolean
> > >> + end
> > >> +
> > >> def find_buildfile
> > >> here = original_dir
> > >> Dir.chdir(here) unless Dir.pwd == here
> > >> - while ! have_rakefile
> > >> + while ! have_buildfile
> > >> Dir.chdir('..')
> > >> if Dir.pwd == here || options.nosearch
> > >> error = "No Buildfile found (looking for:
> #{@rakefiles.join(',
> > >> ')})"
> > >>
> > >>
> > >> On Sun, Sep 14, 2008 at 2:11 AM, lacton <lacton@users.sourceforge.net
> > >wrote:
> > >>
> > >>> On Sat, Sep 13, 2008 at 6:58 PM, Eung-ju Park <eu...@gmail.com>
> > wrote:
> > >>> > I guess two changes makes buildr can't work with rake 0.8.2.
> > >>> >
> > >>> > 1.
> > >>> >
> > >>>
> >
> http://github.com/jimweirich/rake/commit/68303da1aeda78533c044f2a01a99a619fdb1932Prerequisites
> > >>> > are no longer FileLists
> > >>> >
> > >>> > 2.
> > >>> >
> > >>>
> >
> http://github.com/jimweirich/rake/commit/41a334b4e6bd3175202675ad289668f457ef73a9Applied
> > >>> > optparse patch
> > >>> > Buildr::Application extends Rake::Application. In rake 0.8.2,
> > >>> command-line
> > >>> > argument parsing has changed. So there is some mismatch.
> > >>>
> > >>> Thanks for the information. It looks like migrating buildr to rake
> > >>> 0.8.2 will take some time.
> > >>>
> > >>> Lacton
> > >>>
> > >>
> > >>
> > >>
> > >> --
> > >> * LukeSkywalker: Is the dark side stronger?
> > >> * MasterYoda: No...no...no. Quicker, easier, more seductive.
> > >
> >
>
>
>
> --
> vic
>
> Quaerendo invenietis.
>
--
* LukeSkywalker: Is the dark side stronger?
* MasterYoda: No...no...no. Quicker, easier, more seductive.
Re: Current Rakefile is broken
Posted by Victor Hugo Borja <vi...@gmail.com>.
On Thu, Sep 25, 2008 at 3:36 PM, Assaf Arkin <ar...@intalio.com> wrote:
> On Wed, Sep 24, 2008 at 9:22 PM, Victor Hugo Borja <vi...@gmail.com>
> wrote:
> > Assaf,
> >
> > Today I've been working on a rake-0.8.2 branch, I think I've finished
> with
> > the changes to get compatible with
> > the latest version of rake.
> > http://github.com/vic/buildr/commits/rake-0.8.2
> >
> > I've also tested that branch with rake-0.8.1, and everything seems
> normal.
> > So, could anyone try it ?.
>
Oh my fault, I meant rake-0.8.3 :)
--
vic
Quaerendo invenietis.
Re: Current Rakefile is broken
Posted by Assaf Arkin <ar...@intalio.com>.
On Wed, Sep 24, 2008 at 9:22 PM, Victor Hugo Borja <vi...@gmail.com> wrote:
> Assaf,
>
> Today I've been working on a rake-0.8.2 branch, I think I've finished with
> the changes to get compatible with
> the latest version of rake.
> http://github.com/vic/buildr/commits/rake-0.8.2
>
> I've also tested that branch with rake-0.8.1, and everything seems normal.
> So, could anyone try it ?.
Very different from what I had in mind. I was thinking of using
Rake.application with necessary deviations, but keeping the two as
consistent and close to each other as possible.
Assaf
>
> On Sat, Sep 20, 2008 at 2:15 PM, Assaf Arkin <ar...@intalio.com> wrote:
>
>> On Sat, Sep 20, 2008 at 2:20 AM, lacton <la...@users.sourceforge.net>
>> wrote:
>> > Reading your proposed patch, I get the feeling that if we try to
>> > support simultaneously rake 0.8.1 and rake 0.8.2, the code won't be as
>> > clean and simple as it is now.
>> >
>> > If possible, I'd rather we adopt an all-or-nothing approach. Either
>> > we support rake 0.8.1 only, or we fully migrate the trunk to rake
>> > 0.8.2.
>>
>> One or the other.
>>
>> I think this, though, is a different problem. If you check out the
>> source code and run rake install, the target gem will use Rake 0.8.1
>> (as per buildr.gemspec), but the rake install task will run buildr
>> compile (on buildr.buildfile). This instance of buildr is run from
>> source, a classical bootstrap problem, and ends up picking the latest
>> version of Rake.
>>
>> I committed a change to make it use the _buildr script, which runs
>> Buildr from source and forces it to use Rake 0.8.1.
>>
>> Assaf
>>
>>
>> >
>> > I'd like to hear others' opinions about this issue.
>> >
>> > Lacton
>> >
>> > On Fri, Sep 19, 2008 at 3:51 PM, Eung-ju Park <eu...@gmail.com> wrote:
>> >> I have investigated changes of rake 0.8.2. Behavior of
>> >> Rake::Application#have_rakefile was changed.
>> >>
>> >> Below patch would be helpful to build buildr with rake 0.8.2.
>> >>
>> >> Index: lib/buildr/core/application.rb
>> >> ===================================================================
>> >> --- lib/buildr/core/application.rb (revision 697069)
>> >> +++ lib/buildr/core/application.rb (working copy)
>> >> @@ -225,10 +225,20 @@
>> >> @gems = installed
>> >> end
>> >>
>> >> + # In rake 0.8.2 have_rakefile returns location of rakefile. It
>> doesn't
>> >> set @rakefile
>> >> + def have_buildfile
>> >> + location_or_boolean = have_rakefile
>> >> + if location_or_boolean.kind_of? String
>> >> + @rakefile = location_or_boolean
>> >> + return !@rakefile.nil?
>> >> + end
>> >> + location_or_boolean
>> >> + end
>> >> +
>> >> def find_buildfile
>> >> here = original_dir
>> >> Dir.chdir(here) unless Dir.pwd == here
>> >> - while ! have_rakefile
>> >> + while ! have_buildfile
>> >> Dir.chdir('..')
>> >> if Dir.pwd == here || options.nosearch
>> >> error = "No Buildfile found (looking for: #{@rakefiles.join(',
>> >> ')})"
>> >>
>> >>
>> >> On Sun, Sep 14, 2008 at 2:11 AM, lacton <lacton@users.sourceforge.net
>> >wrote:
>> >>
>> >>> On Sat, Sep 13, 2008 at 6:58 PM, Eung-ju Park <eu...@gmail.com>
>> wrote:
>> >>> > I guess two changes makes buildr can't work with rake 0.8.2.
>> >>> >
>> >>> > 1.
>> >>> >
>> >>>
>> http://github.com/jimweirich/rake/commit/68303da1aeda78533c044f2a01a99a619fdb1932Prerequisites
>> >>> > are no longer FileLists
>> >>> >
>> >>> > 2.
>> >>> >
>> >>>
>> http://github.com/jimweirich/rake/commit/41a334b4e6bd3175202675ad289668f457ef73a9Applied
>> >>> > optparse patch
>> >>> > Buildr::Application extends Rake::Application. In rake 0.8.2,
>> >>> command-line
>> >>> > argument parsing has changed. So there is some mismatch.
>> >>>
>> >>> Thanks for the information. It looks like migrating buildr to rake
>> >>> 0.8.2 will take some time.
>> >>>
>> >>> Lacton
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> * LukeSkywalker: Is the dark side stronger?
>> >> * MasterYoda: No...no...no. Quicker, easier, more seductive.
>> >
>>
>
>
>
> --
> vic
>
> Quaerendo invenietis.
>
Re: Current Rakefile is broken
Posted by Victor Hugo Borja <vi...@gmail.com>.
Assaf,
Today I've been working on a rake-0.8.2 branch, I think I've finished with
the changes to get compatible with
the latest version of rake.
http://github.com/vic/buildr/commits/rake-0.8.2
I've also tested that branch with rake-0.8.1, and everything seems normal.
So, could anyone try it ?.
On Sat, Sep 20, 2008 at 2:15 PM, Assaf Arkin <ar...@intalio.com> wrote:
> On Sat, Sep 20, 2008 at 2:20 AM, lacton <la...@users.sourceforge.net>
> wrote:
> > Reading your proposed patch, I get the feeling that if we try to
> > support simultaneously rake 0.8.1 and rake 0.8.2, the code won't be as
> > clean and simple as it is now.
> >
> > If possible, I'd rather we adopt an all-or-nothing approach. Either
> > we support rake 0.8.1 only, or we fully migrate the trunk to rake
> > 0.8.2.
>
> One or the other.
>
> I think this, though, is a different problem. If you check out the
> source code and run rake install, the target gem will use Rake 0.8.1
> (as per buildr.gemspec), but the rake install task will run buildr
> compile (on buildr.buildfile). This instance of buildr is run from
> source, a classical bootstrap problem, and ends up picking the latest
> version of Rake.
>
> I committed a change to make it use the _buildr script, which runs
> Buildr from source and forces it to use Rake 0.8.1.
>
> Assaf
>
>
> >
> > I'd like to hear others' opinions about this issue.
> >
> > Lacton
> >
> > On Fri, Sep 19, 2008 at 3:51 PM, Eung-ju Park <eu...@gmail.com> wrote:
> >> I have investigated changes of rake 0.8.2. Behavior of
> >> Rake::Application#have_rakefile was changed.
> >>
> >> Below patch would be helpful to build buildr with rake 0.8.2.
> >>
> >> Index: lib/buildr/core/application.rb
> >> ===================================================================
> >> --- lib/buildr/core/application.rb (revision 697069)
> >> +++ lib/buildr/core/application.rb (working copy)
> >> @@ -225,10 +225,20 @@
> >> @gems = installed
> >> end
> >>
> >> + # In rake 0.8.2 have_rakefile returns location of rakefile. It
> doesn't
> >> set @rakefile
> >> + def have_buildfile
> >> + location_or_boolean = have_rakefile
> >> + if location_or_boolean.kind_of? String
> >> + @rakefile = location_or_boolean
> >> + return !@rakefile.nil?
> >> + end
> >> + location_or_boolean
> >> + end
> >> +
> >> def find_buildfile
> >> here = original_dir
> >> Dir.chdir(here) unless Dir.pwd == here
> >> - while ! have_rakefile
> >> + while ! have_buildfile
> >> Dir.chdir('..')
> >> if Dir.pwd == here || options.nosearch
> >> error = "No Buildfile found (looking for: #{@rakefiles.join(',
> >> ')})"
> >>
> >>
> >> On Sun, Sep 14, 2008 at 2:11 AM, lacton <lacton@users.sourceforge.net
> >wrote:
> >>
> >>> On Sat, Sep 13, 2008 at 6:58 PM, Eung-ju Park <eu...@gmail.com>
> wrote:
> >>> > I guess two changes makes buildr can't work with rake 0.8.2.
> >>> >
> >>> > 1.
> >>> >
> >>>
> http://github.com/jimweirich/rake/commit/68303da1aeda78533c044f2a01a99a619fdb1932Prerequisites
> >>> > are no longer FileLists
> >>> >
> >>> > 2.
> >>> >
> >>>
> http://github.com/jimweirich/rake/commit/41a334b4e6bd3175202675ad289668f457ef73a9Applied
> >>> > optparse patch
> >>> > Buildr::Application extends Rake::Application. In rake 0.8.2,
> >>> command-line
> >>> > argument parsing has changed. So there is some mismatch.
> >>>
> >>> Thanks for the information. It looks like migrating buildr to rake
> >>> 0.8.2 will take some time.
> >>>
> >>> Lacton
> >>>
> >>
> >>
> >>
> >> --
> >> * LukeSkywalker: Is the dark side stronger?
> >> * MasterYoda: No...no...no. Quicker, easier, more seductive.
> >
>
--
vic
Quaerendo invenietis.
Re: Current Rakefile is broken
Posted by Assaf Arkin <ar...@intalio.com>.
On Sat, Sep 20, 2008 at 2:20 AM, lacton <la...@users.sourceforge.net> wrote:
> Reading your proposed patch, I get the feeling that if we try to
> support simultaneously rake 0.8.1 and rake 0.8.2, the code won't be as
> clean and simple as it is now.
>
> If possible, I'd rather we adopt an all-or-nothing approach. Either
> we support rake 0.8.1 only, or we fully migrate the trunk to rake
> 0.8.2.
One or the other.
I think this, though, is a different problem. If you check out the
source code and run rake install, the target gem will use Rake 0.8.1
(as per buildr.gemspec), but the rake install task will run buildr
compile (on buildr.buildfile). This instance of buildr is run from
source, a classical bootstrap problem, and ends up picking the latest
version of Rake.
I committed a change to make it use the _buildr script, which runs
Buildr from source and forces it to use Rake 0.8.1.
Assaf
>
> I'd like to hear others' opinions about this issue.
>
> Lacton
>
> On Fri, Sep 19, 2008 at 3:51 PM, Eung-ju Park <eu...@gmail.com> wrote:
>> I have investigated changes of rake 0.8.2. Behavior of
>> Rake::Application#have_rakefile was changed.
>>
>> Below patch would be helpful to build buildr with rake 0.8.2.
>>
>> Index: lib/buildr/core/application.rb
>> ===================================================================
>> --- lib/buildr/core/application.rb (revision 697069)
>> +++ lib/buildr/core/application.rb (working copy)
>> @@ -225,10 +225,20 @@
>> @gems = installed
>> end
>>
>> + # In rake 0.8.2 have_rakefile returns location of rakefile. It doesn't
>> set @rakefile
>> + def have_buildfile
>> + location_or_boolean = have_rakefile
>> + if location_or_boolean.kind_of? String
>> + @rakefile = location_or_boolean
>> + return !@rakefile.nil?
>> + end
>> + location_or_boolean
>> + end
>> +
>> def find_buildfile
>> here = original_dir
>> Dir.chdir(here) unless Dir.pwd == here
>> - while ! have_rakefile
>> + while ! have_buildfile
>> Dir.chdir('..')
>> if Dir.pwd == here || options.nosearch
>> error = "No Buildfile found (looking for: #{@rakefiles.join(',
>> ')})"
>>
>>
>> On Sun, Sep 14, 2008 at 2:11 AM, lacton <la...@users.sourceforge.net>wrote:
>>
>>> On Sat, Sep 13, 2008 at 6:58 PM, Eung-ju Park <eu...@gmail.com> wrote:
>>> > I guess two changes makes buildr can't work with rake 0.8.2.
>>> >
>>> > 1.
>>> >
>>> http://github.com/jimweirich/rake/commit/68303da1aeda78533c044f2a01a99a619fdb1932Prerequisites
>>> > are no longer FileLists
>>> >
>>> > 2.
>>> >
>>> http://github.com/jimweirich/rake/commit/41a334b4e6bd3175202675ad289668f457ef73a9Applied
>>> > optparse patch
>>> > Buildr::Application extends Rake::Application. In rake 0.8.2,
>>> command-line
>>> > argument parsing has changed. So there is some mismatch.
>>>
>>> Thanks for the information. It looks like migrating buildr to rake
>>> 0.8.2 will take some time.
>>>
>>> Lacton
>>>
>>
>>
>>
>> --
>> * LukeSkywalker: Is the dark side stronger?
>> * MasterYoda: No...no...no. Quicker, easier, more seductive.
>
Re: Current Rakefile is broken
Posted by lacton <la...@users.sourceforge.net>.
Reading your proposed patch, I get the feeling that if we try to
support simultaneously rake 0.8.1 and rake 0.8.2, the code won't be as
clean and simple as it is now.
If possible, I'd rather we adopt an all-or-nothing approach. Either
we support rake 0.8.1 only, or we fully migrate the trunk to rake
0.8.2.
I'd like to hear others' opinions about this issue.
Lacton
On Fri, Sep 19, 2008 at 3:51 PM, Eung-ju Park <eu...@gmail.com> wrote:
> I have investigated changes of rake 0.8.2. Behavior of
> Rake::Application#have_rakefile was changed.
>
> Below patch would be helpful to build buildr with rake 0.8.2.
>
> Index: lib/buildr/core/application.rb
> ===================================================================
> --- lib/buildr/core/application.rb (revision 697069)
> +++ lib/buildr/core/application.rb (working copy)
> @@ -225,10 +225,20 @@
> @gems = installed
> end
>
> + # In rake 0.8.2 have_rakefile returns location of rakefile. It doesn't
> set @rakefile
> + def have_buildfile
> + location_or_boolean = have_rakefile
> + if location_or_boolean.kind_of? String
> + @rakefile = location_or_boolean
> + return !@rakefile.nil?
> + end
> + location_or_boolean
> + end
> +
> def find_buildfile
> here = original_dir
> Dir.chdir(here) unless Dir.pwd == here
> - while ! have_rakefile
> + while ! have_buildfile
> Dir.chdir('..')
> if Dir.pwd == here || options.nosearch
> error = "No Buildfile found (looking for: #{@rakefiles.join(',
> ')})"
>
>
> On Sun, Sep 14, 2008 at 2:11 AM, lacton <la...@users.sourceforge.net>wrote:
>
>> On Sat, Sep 13, 2008 at 6:58 PM, Eung-ju Park <eu...@gmail.com> wrote:
>> > I guess two changes makes buildr can't work with rake 0.8.2.
>> >
>> > 1.
>> >
>> http://github.com/jimweirich/rake/commit/68303da1aeda78533c044f2a01a99a619fdb1932Prerequisites
>> > are no longer FileLists
>> >
>> > 2.
>> >
>> http://github.com/jimweirich/rake/commit/41a334b4e6bd3175202675ad289668f457ef73a9Applied
>> > optparse patch
>> > Buildr::Application extends Rake::Application. In rake 0.8.2,
>> command-line
>> > argument parsing has changed. So there is some mismatch.
>>
>> Thanks for the information. It looks like migrating buildr to rake
>> 0.8.2 will take some time.
>>
>> Lacton
>>
>
>
>
> --
> * LukeSkywalker: Is the dark side stronger?
> * MasterYoda: No...no...no. Quicker, easier, more seductive.
Re: Current Rakefile is broken
Posted by Eung-ju Park <eu...@gmail.com>.
I have investigated changes of rake 0.8.2. Behavior of
Rake::Application#have_rakefile was changed.
Below patch would be helpful to build buildr with rake 0.8.2.
Index: lib/buildr/core/application.rb
===================================================================
--- lib/buildr/core/application.rb (revision 697069)
+++ lib/buildr/core/application.rb (working copy)
@@ -225,10 +225,20 @@
@gems = installed
end
+ # In rake 0.8.2 have_rakefile returns location of rakefile. It doesn't
set @rakefile
+ def have_buildfile
+ location_or_boolean = have_rakefile
+ if location_or_boolean.kind_of? String
+ @rakefile = location_or_boolean
+ return !@rakefile.nil?
+ end
+ location_or_boolean
+ end
+
def find_buildfile
here = original_dir
Dir.chdir(here) unless Dir.pwd == here
- while ! have_rakefile
+ while ! have_buildfile
Dir.chdir('..')
if Dir.pwd == here || options.nosearch
error = "No Buildfile found (looking for: #{@rakefiles.join(',
')})"
On Sun, Sep 14, 2008 at 2:11 AM, lacton <la...@users.sourceforge.net>wrote:
> On Sat, Sep 13, 2008 at 6:58 PM, Eung-ju Park <eu...@gmail.com> wrote:
> > I guess two changes makes buildr can't work with rake 0.8.2.
> >
> > 1.
> >
> http://github.com/jimweirich/rake/commit/68303da1aeda78533c044f2a01a99a619fdb1932Prerequisites
> > are no longer FileLists
> >
> > 2.
> >
> http://github.com/jimweirich/rake/commit/41a334b4e6bd3175202675ad289668f457ef73a9Applied
> > optparse patch
> > Buildr::Application extends Rake::Application. In rake 0.8.2,
> command-line
> > argument parsing has changed. So there is some mismatch.
>
> Thanks for the information. It looks like migrating buildr to rake
> 0.8.2 will take some time.
>
> Lacton
>
--
* LukeSkywalker: Is the dark side stronger?
* MasterYoda: No...no...no. Quicker, easier, more seductive.
Re: Current Rakefile is broken
Posted by lacton <la...@users.sourceforge.net>.
On Sat, Sep 13, 2008 at 6:58 PM, Eung-ju Park <eu...@gmail.com> wrote:
> I guess two changes makes buildr can't work with rake 0.8.2.
>
> 1.
> http://github.com/jimweirich/rake/commit/68303da1aeda78533c044f2a01a99a619fdb1932Prerequisites
> are no longer FileLists
>
> 2.
> http://github.com/jimweirich/rake/commit/41a334b4e6bd3175202675ad289668f457ef73a9Applied
> optparse patch
> Buildr::Application extends Rake::Application. In rake 0.8.2, command-line
> argument parsing has changed. So there is some mismatch.
Thanks for the information. It looks like migrating buildr to rake
0.8.2 will take some time.
Lacton
Re: Current Rakefile is broken
Posted by Eung-ju Park <eu...@gmail.com>.
I guess two changes makes buildr can't work with rake 0.8.2.
1.
http://github.com/jimweirich/rake/commit/68303da1aeda78533c044f2a01a99a619fdb1932Prerequisites
are no longer FileLists
2.
http://github.com/jimweirich/rake/commit/41a334b4e6bd3175202675ad289668f457ef73a9Applied
optparse patch
Buildr::Application extends Rake::Application. In rake 0.8.2, command-line
argument parsing has changed. So there is some mismatch.
On Sun, Sep 14, 2008 at 12:02 AM, Eung-ju Park <eu...@gmail.com> wrote:
> rake 0.8.2 causes the problem. 'rake install' works after I downgrade rake
> to 0.8.1.
>
>
> On Sat, Sep 13, 2008 at 11:17 PM, Eung-ju Park <eu...@gmail.com> wrote:
>
>>
>>
>> On Sat, Sep 13, 2008 at 10:12 PM, lacton <la...@users.sourceforge.net>wrote:
>>
>>> On Sat, Sep 13, 2008 at 2:01 PM, Eung-ju Park <eu...@gmail.com> wrote:
>>> > I tried to build buildr but it raise error like below.
>>> >
>>> > $ rake
>>> > (in /Users/eungju/src/buildr)
>>> > rake aborted!
>>> > undefined method `include' for []:Array
>>> > /Users/eungju/src/buildr/rakefile:46
>>> > (See full trace by running task with --trace)
>>>
>>> That's interesting. When I run 'rake' with no task name, I get "Don't
>>> know how to build task 'default'".
>>>
>>> What version of rake are you using? (i.e., 'rake --version')
>>> What SVN revision are you building from? (i.e., 'svn info | grep
>>> Revision')
>>
>>
>> here it is
>> $ ruby --version
>> ruby 1.8.6 (2008-03-03 patchlevel 114) [universal-darwin9.0]
>> $ rake --version
>> rake, version 0.8.2
>> $ svn info | grep Revision
>> Revision: 694906
>>
>>
>>
>>>
>>>
>>> > I don't know about rake but I tried something. I guess attached patch
>>> will
>>> > fix it.
>>>
>>> Which patch are you referring to?
>>
>>
>> Mailing list doesn't deliver attachment files. Here is the patch
>>
>> Index: Rakefile
>> ===================================================================
>> --- Rakefile (revision 694906)
>> +++ Rakefile (working copy)
>> @@ -43,11 +43,12 @@
>> ENV['incubating'] = 'true'
>> ENV['staging'] = "people.apache.org:~/public_html/#{spec.name
>> }/#{spec.version}"
>>
>> -task('apache.license').prerequisites.include(spec.files).
>> +task 'apache:license' do |task|
>> + task.prerequisites.include(spec.files).
>> exclude('.class', '.png', '.jar', '.tif', '.textile', '.icns',
>> 'README', 'LICENSE', 'CHANGELOG', 'DISCLAIMER', 'NOTICE',
>> 'etc/KEYS', 'etc/git-svn-authors')
>> +end
>>
>> -
>> task 'spec:check' do
>> print 'Checking that we have JRuby, Scala and Groovy available ... '
>> fail 'Full testing requires JRuby!' unless which('jruby')
>>
>>
>>
>>>
>>>
>>> Lacton
>>>
>>
>>
>> --
>> * LukeSkywalker: Is the dark side stronger?
>> * MasterYoda: No...no...no. Quicker, easier, more seductive.
>>
>
>
>
> --
> * LukeSkywalker: Is the dark side stronger?
> * MasterYoda: No...no...no. Quicker, easier, more seductive.
>
--
* LukeSkywalker: Is the dark side stronger?
* MasterYoda: No...no...no. Quicker, easier, more seductive.
Re: Current Rakefile is broken
Posted by Eung-ju Park <eu...@gmail.com>.
rake 0.8.2 causes the problem. 'rake install' works after I downgrade rake
to 0.8.1.
On Sat, Sep 13, 2008 at 11:17 PM, Eung-ju Park <eu...@gmail.com> wrote:
>
>
> On Sat, Sep 13, 2008 at 10:12 PM, lacton <la...@users.sourceforge.net>wrote:
>
>> On Sat, Sep 13, 2008 at 2:01 PM, Eung-ju Park <eu...@gmail.com> wrote:
>> > I tried to build buildr but it raise error like below.
>> >
>> > $ rake
>> > (in /Users/eungju/src/buildr)
>> > rake aborted!
>> > undefined method `include' for []:Array
>> > /Users/eungju/src/buildr/rakefile:46
>> > (See full trace by running task with --trace)
>>
>> That's interesting. When I run 'rake' with no task name, I get "Don't
>> know how to build task 'default'".
>>
>> What version of rake are you using? (i.e., 'rake --version')
>> What SVN revision are you building from? (i.e., 'svn info | grep
>> Revision')
>
>
> here it is
> $ ruby --version
> ruby 1.8.6 (2008-03-03 patchlevel 114) [universal-darwin9.0]
> $ rake --version
> rake, version 0.8.2
> $ svn info | grep Revision
> Revision: 694906
>
>
>
>>
>>
>> > I don't know about rake but I tried something. I guess attached patch
>> will
>> > fix it.
>>
>> Which patch are you referring to?
>
>
> Mailing list doesn't deliver attachment files. Here is the patch
>
> Index: Rakefile
> ===================================================================
> --- Rakefile (revision 694906)
> +++ Rakefile (working copy)
> @@ -43,11 +43,12 @@
> ENV['incubating'] = 'true'
> ENV['staging'] = "people.apache.org:~/public_html/#{spec.name
> }/#{spec.version}"
>
> -task('apache.license').prerequisites.include(spec.files).
> +task 'apache:license' do |task|
> + task.prerequisites.include(spec.files).
> exclude('.class', '.png', '.jar', '.tif', '.textile', '.icns',
> 'README', 'LICENSE', 'CHANGELOG', 'DISCLAIMER', 'NOTICE',
> 'etc/KEYS', 'etc/git-svn-authors')
> +end
>
> -
> task 'spec:check' do
> print 'Checking that we have JRuby, Scala and Groovy available ... '
> fail 'Full testing requires JRuby!' unless which('jruby')
>
>
>
>>
>>
>> Lacton
>>
>
>
> --
> * LukeSkywalker: Is the dark side stronger?
> * MasterYoda: No...no...no. Quicker, easier, more seductive.
>
--
* LukeSkywalker: Is the dark side stronger?
* MasterYoda: No...no...no. Quicker, easier, more seductive.
Re: Current Rakefile is broken
Posted by Eung-ju Park <eu...@gmail.com>.
On Sat, Sep 13, 2008 at 10:12 PM, lacton <la...@users.sourceforge.net>wrote:
> On Sat, Sep 13, 2008 at 2:01 PM, Eung-ju Park <eu...@gmail.com> wrote:
> > I tried to build buildr but it raise error like below.
> >
> > $ rake
> > (in /Users/eungju/src/buildr)
> > rake aborted!
> > undefined method `include' for []:Array
> > /Users/eungju/src/buildr/rakefile:46
> > (See full trace by running task with --trace)
>
> That's interesting. When I run 'rake' with no task name, I get "Don't
> know how to build task 'default'".
>
> What version of rake are you using? (i.e., 'rake --version')
> What SVN revision are you building from? (i.e., 'svn info | grep Revision')
here it is
$ ruby --version
ruby 1.8.6 (2008-03-03 patchlevel 114) [universal-darwin9.0]
$ rake --version
rake, version 0.8.2
$ svn info | grep Revision
Revision: 694906
>
>
> > I don't know about rake but I tried something. I guess attached patch
> will
> > fix it.
>
> Which patch are you referring to?
Mailing list doesn't deliver attachment files. Here is the patch
Index: Rakefile
===================================================================
--- Rakefile (revision 694906)
+++ Rakefile (working copy)
@@ -43,11 +43,12 @@
ENV['incubating'] = 'true'
ENV['staging'] = "people.apache.org:~/public_html/#{spec.name
}/#{spec.version}"
-task('apache.license').prerequisites.include(spec.files).
+task 'apache:license' do |task|
+ task.prerequisites.include(spec.files).
exclude('.class', '.png', '.jar', '.tif', '.textile', '.icns',
'README', 'LICENSE', 'CHANGELOG', 'DISCLAIMER', 'NOTICE',
'etc/KEYS', 'etc/git-svn-authors')
+end
-
task 'spec:check' do
print 'Checking that we have JRuby, Scala and Groovy available ... '
fail 'Full testing requires JRuby!' unless which('jruby')
>
>
> Lacton
>
--
* LukeSkywalker: Is the dark side stronger?
* MasterYoda: No...no...no. Quicker, easier, more seductive.
Re: Current Rakefile is broken
Posted by lacton <la...@users.sourceforge.net>.
On Sat, Sep 13, 2008 at 2:01 PM, Eung-ju Park <eu...@gmail.com> wrote:
> I tried to build buildr but it raise error like below.
>
> $ rake
> (in /Users/eungju/src/buildr)
> rake aborted!
> undefined method `include' for []:Array
> /Users/eungju/src/buildr/rakefile:46
> (See full trace by running task with --trace)
That's interesting. When I run 'rake' with no task name, I get "Don't
know how to build task 'default'".
What version of rake are you using? (i.e., 'rake --version')
What SVN revision are you building from? (i.e., 'svn info | grep Revision')
> I don't know about rake but I tried something. I guess attached patch will
> fix it.
Which patch are you referring to?
Lacton