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 <[email protected]> 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
>
> ---
> [email protected]
> http://www.decodified.com
>
> On 07.10.2010, at 22:52, Alex Boisvert wrote:
>
> > On Thu, Oct 7, 2010 at 2:16 PM, Mathias <[email protected]> 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
>
>
