I'm not sure how anything that's been done in Capistrano could have
resulted in this error suddenly cropping up, since the shadowed-method
error has existed in cap since 2.0. If anyone wants to track it down
and see why this is suddenly an issue, I'd appreciate it.
- Jamis
On Wed, Aug 27, 2008 at 5:38 AM, Jonathan Weiss <[EMAIL PROTECTED]> wrote:
>
> Just an update, I had this problem too. Only uninstalling ruby-debug
> and ruby-debug-base helped. This must have been introduced in recent
> Capistrano versions.
>
> Jonathan
>
> On Fri, Aug 15, 2008 at 9:15 PM, gsterndale <[EMAIL PROTECTED]> wrote:
>>
>> Thanks Ama and Jamis! It was because I was requiring ruby-debug. All
>> is well now.
>>
>> Jamis, Capistrano is a huge time saver for us. Many thanks.
>>
>> On Aug 15, 3:02 pm, Jamis Buck <[EMAIL PROTECTED]> wrote:
>>> It works for me:
>>>
>>> $ cat capfile.test
>>> load 'deploy'
>>>
>>> task :start do
>>> puts "this should work"
>>> end
>>>
>>> namespace :thin do
>>> task :start do
>>> puts "this should work, too"
>>> end
>>> end
>>>
>>> $ cap -f capfile.test start thin:start
>>> * executing `start'
>>> this should work
>>> * executing `thin:start'
>>> this should work, too
>>>
>>> I suspect you're either using a third-party capistrano plugin or
>>> extension that defines a method called "start" somewhere, or you've
>>> defined such a method yourself somewhere in your capfile or deploy.rb.
>>>
>>> - Jamis
>>>
>>> On Aug 15, 2008, at 12:14 PM, gsterndale wrote:
>>>
>>>
>>>
>>> > This only seems to be happening with tasks named 'start'.
>>>
>>> > For example:
>>>
>>> > namespace :thin do
>>> > %w(start stop restart).each do |action|
>>> > desc "#{action} this app's Thin Cluster"
>>> > task action.to_sym, :roles => :app do
>>> > run "thin #{action} -C
>>> > #{shared_configuration_location_for(:thin)}"
>>> > end
>>> > end
>>> > end
>>>
>>> > On Aug 13, 5:20 pm, gsterndale <[EMAIL PROTECTED]> wrote:
>>> >> when doing a $ cap deploy:cold
>>>
>>> >> I'm getting the following error:
>>> >> /path/to/gems/capistrano-2.4.3/lib/capistrano/configuration/
>>> >> namespaces.rb:97:in `task': defining a task named `start' would
>>> >> shadow
>>> >> an existing method with that name (ArgumentError)
>>>
>>> >> I have tasks called 'start', 'stop' and 'restart' in sever different
>>> >> namespaces. The errors seem to have appeared after updating
>>> >> Capistrano
>>> >> to 2.4.3 from 2.1.0. Also, I updated Ruby from 1.8.4 to 1.8.6
>>> >> "enterprise".
>>>
>>> >> Can I no longer make tasks named 'start'?
>>>
>>> >> Has anyone else seen this?
>>>
>>> >> Thanks!
>>>
>>> > >
>>>
>>>
>>> smime.p7s
>>> 3KViewDownload
>>
>> >
>>
>
>
>
> --
> Jonathan Weiss
> http://blog.innerewut.de
> http://twitter.com/jweiss
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
