Mailing-List: contact users-help@buildr.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@buildr.apache.org
Received-SPF: pass (athena.apache.org: domain of alex.boisvert@gmail.com
 designates 209.85.216.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=sRcgajuBzbZR2cq2sP603uEJUWjvYARjO7gIRHF38SXYFBHzx+l16OpssDfA5kaNKl
         7dRG/vKPsJx9oBn3+U0KpCpdo+Aw+Vz7WQRlpmJRKC5uBVeOr6kMqMFo6mVOlzo63aaT
         WlagQnrfYS5pVgf2y4KJazlPEdDXA98OqiIWc=
MIME-Version: 1.0
In-Reply-To: <ED4E7500-0677-415B-822C-53F22A11584F@decodified.com>
References: <0CC3C114-910D-406A-97D6-3CF915A7337E@decodified.com>
	<AANLkTimQcNeMCB_T+ugWm0FY7WzaXkhNKnVuzy4qhAPS@mail.gmail.com>
	<ED4E7500-0677-415B-822C-53F22A11584F@decodified.com>
Date: Thu, 7 Oct 2010 15:11:17 -0700
Message-ID: <AANLkTi=-A1qPUiHpWMNowY0ZqAu3+x1ACmDv4R0gJnA9@mail.gmail.com>
Subject: Re: Problem with Growl notifications
From: Alex Boisvert <alex.boisvert@gmail.com>
To: users@buildr.apache.org
Content-Type: multipart/alternative; boundary=00c09f905f7c56829e04920e2cdf

--00c09f905f7c56829e04920e2cdf
Content-Type: text/plain; charset=ISO-8859-1

Hi Mathias,

The growl integration code is as follows,

  def growl_notify(type, title, message)
    begin
      # Loading Ruby Cocoa can slow the build down (hooks on Object class),
so we're
      # saving the best for last and only requiring it at the very end.
      require 'osx/cocoa'
      icon = OSX::NSApplication.sharedApplication.applicationIconImage
      icon =
OSX::NSImage.alloc.initWithContentsOfFile(File.join(File.dirname(__FILE__),
'../resources/buildr.icns'))

      # Register with Growl, that way you can turn notifications on/off from
system preferences.
      OSX::NSDistributedNotificationCenter.defaultCenter.

 postNotificationName_object_userInfo_deliverImmediately(:GrowlApplicationRegistrationNotification,
nil,
          { :ApplicationName=>'Buildr', :AllNotifications=>['Completed',
'Failed'],
            :ApplicationIcon=>icon.TIFFRepresentation }, true)

      OSX::NSDistributedNotificationCenter.defaultCenter.

 postNotificationName_object_userInfo_deliverImmediately(:GrowlNotification,
nil,
          { :ApplicationName=>'Buildr', :NotificationName=>type,
            :NotificationTitle=>title, :NotificationDescription=>message },
true)
    rescue Exception => e
      # We get here in two cases: system doesn't have Growl installed so one
of the OSX
      # calls raises an exception; system doesn't have osx/cocoa, e.g.
MacPorts Ruby 1.9,
      # so we also need to rescue LoadError.
      puts e
      puts e.backtrace
    end
  end

I suggest that you try an interactive Ruby session (irb), paste the code
there and see if calling:

growl_notify('type', 'title', 'message')

works on your machine or produces an exception.

alex

On Thu, Oct 7, 2010 at 3:00 PM, Mathias <mathias@decodified.com> wrote:

> Actually, on my machine it does not issue any growl notifications at all,
> neither during cc nor "regular" builds.
> I'm not sure though, whether it did not actually work at some point, a few
> weeks ago, when I tried buildr for the first time.
> Back then it was still buildr 1.4.1.
> Could there be upgrade leftovers somewhere?
> What would be the best way to "reset" buildr to a clean "post-install"
> state?
>
> Cheers,
> Mathias
>
> ---
> mathias@decodified.com
> http://www.decodified.com
>
> On 07.10.2010, at 22:52, Alex Boisvert wrote:
>
> > On Thu, Oct 7, 2010 at 2:16 PM, Mathias <mathias@decodified.com> wrote:
> >
> >> Guys,
> >>
> >> I am evaluating Buildr as the potential build tool of choice for a
> larger,
> >> multi-module Scala project of ours.
> >> I am especially interested in the "continuous compilation" feature, that
> >> seems to work nicely so far.
> >> However, for some reason the advertised Growl notifications do not seem
> to
> >> work.
> >>
> >
> > Are you saying growl doesn't work when using continuous compilation?   Or
> at
> > all?
> >
> > I don't think notifications have been integrated into the continuous
> > compilation feature.  Would be easy to ...
> >
> > alex
>
>

--00c09f905f7c56829e04920e2cdf--