You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Peter Donald (JIRA)" <ji...@apache.org> on 2013/10/23 02:04:42 UTC

[jira] [Closed] (BUILDR-689) NoMethodError : undefined method `project=' for #

     [ https://issues.apache.org/jira/browse/BUILDR-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Donald closed BUILDR-689.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 1.4.15

I believe this is fixed. Thanks for the example. 

There was actually multiple bugs. 
- The user could define the a task with the same name as the assets task as we were lazily creating the task. It is now created before the project is defined.
- The "new" integration into the war task was coping the assets from the source directories rather than the target directory.

I believe both problems have been addressed.

> NoMethodError : undefined method `project=' for #<Rake::FileTask:0x7fc32e6e4be8>
> --------------------------------------------------------------------------------
>
>                 Key: BUILDR-689
>                 URL: https://issues.apache.org/jira/browse/BUILDR-689
>             Project: Buildr
>          Issue Type: Bug
>    Affects Versions: 1.4.14
>            Reporter: Alex Boisvert
>            Assignee: Peter Donald
>             Fix For: 1.4.15
>
>         Attachments: buildr-asset-bug.zip
>
>
> Reported by Chris Bozic on the user@ mailing list:
> 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



--
This message was sent by Atlassian JIRA
(v6.1#6144)