I can reproduce with a simple project having a package(:war) call.
Peter - FWIW, this patch seems to fix the issue:
smudge ~/g/buildr [trunk] (ruby 1.8.7) $ git di
diff --git a/lib/buildr/core/assets.rb b/lib/buildr/core/assets.rb
index 3566d9c..0a4f145 100644
--- a/lib/buildr/core/assets.rb
+++ b/lib/buildr/core/assets.rb
@@ -75,7 +75,8 @@ module Buildr #:nodoc:
# Access the asset task
def assets
if @assets.nil?
- @assets = AssetsTask.define_task(project._(:target, :main,
:webapp) => [])
+ @assets =
AssetsTask.define_task("#{[project.name](http://project.name)}:assets_task")
+ @assets.enhance([project._(:target, :main, :webapp)])
@assets.project = self
project.task('assets').enhance([@assets])
project.build.enhance([@assets])
Seems like a severe regression that would affect most web projects.
On Tue, Oct 22, 2013 at 8:51 AM, Chris Bozic <[email protected]> wrote:
after upgrading to buildr 1.4.14, I get a new error:
>
> NoMethodError : undefined method `project=' for
> #<Rake::FileTask:0x007fe27290a6d0>
>
> The above error occurs on a line in the buildfile where I am attempting to
> package(:war). When I downgrade to buildr 1.4.12 everything works again.
> Has anyone else seen this? If so, can you help me identify what I am
> doing wrong?
>
> Thanks,
> Chris
>
