You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Antoine Toulme (JIRA)" <ji...@apache.org> on 2016/08/14 06:27:22 UTC
[jira] [Resolved] (BUILDR-454) Definition-level parent-child
references-by-name fail in 1.4.0 but not in 1.3.5
[ https://issues.apache.org/jira/browse/BUILDR-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Toulme resolved BUILDR-454.
-----------------------------------
Resolution: Fixed
I applied your patch with a slight change. Thanks!
> Definition-level parent-child references-by-name fail in 1.4.0 but not in 1.3.5
> -------------------------------------------------------------------------------
>
> Key: BUILDR-454
> URL: https://issues.apache.org/jira/browse/BUILDR-454
> Project: Buildr
> Issue Type: Bug
> Components: Core features
> Affects Versions: 1.4
> Environment: OS X 10.6.3, JRuby 1.4.0 (but it shouldn't matter)
> Reporter: Rhett Sutphin
> Assignee: Antoine Toulme
> Fix For: 1.5
>
> Attachments: circular_project_deps.patch
>
>
> A buildfile like this one:
> define "root" do
> define "child" do
> puts project('root')._('foo.resource')
> end
> end
> will work fine on buildr 1.3.5. However, it fails with a circular dependency error on 1.4.0 RC4:
> RuntimeError : Circular dependency detected: TOP => root => root:child => root
> /private/tmp/buildr-problem/buildfile:3
> I don't think this need block the release because the following workaround succeeds in both:
> define "root" do
> define "child" do
> puts project.parent._('foo.resource')
> end
> end
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)