You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@buildr.apache.org by Daniel Spiewak <dj...@gmail.com> on 2009/08/17 15:54:45 UTC
Re: [jira] Commented: (BUILDR-278) tasks/*.rake files are loaded
after the buildfile
Could we take a look at this? He *did* supply a patch with specs back in
May. I can if no one else is up for it, but a change like this should
probably be reviewed by someone more familiar with the Buildr bootstrap
process.
Daniel
On Sun, Aug 16, 2009 at 11:42 PM, Rhett Sutphin (JIRA) <ji...@apache.org>wrote:
>
> [
> https://issues.apache.org/jira/browse/BUILDR-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743967#action_12743967]
>
> Rhett Sutphin commented on BUILDR-278:
> --------------------------------------
>
> I'd like to see this patch (or some other fix) get into buildr before the
> next release. Is there anything I can do to help it along?
>
> > tasks/*.rake files are loaded after the buildfile
> > -------------------------------------------------
> >
> > Key: BUILDR-278
> > URL: https://issues.apache.org/jira/browse/BUILDR-278
> > Project: Buildr
> > Issue Type: Bug
> > Components: Core features
> > Affects Versions: 1.3.4
> > Environment: Any
> > Reporter: Rhett Sutphin
> > Attachments:
> 0001-Move-rakelib-loading-into-load_tasks-so-the-the-file.patch
> >
> >
> > In buildr 1.3.4, the files in tasks/*.rake are loaded after the buildfile
> itself. This means that their contents are not available while loading the
> buildfile. This, in turn, means that some buildfiles that worked under
> 1.3.3 don't work in 1.3.4.
> > Thread:
> http://markmail.org/search/?q=buildr#query:buildr%20list%3Aorg.apache.buildr.users+page:1+mid:oc5eaimyxt6o4xqa+state:results
> > It appears that this may be a consequence of the fix for BUILDR-255.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
Re: [jira] Commented: (BUILDR-278) tasks/*.rake files are loaded
after the buildfile
Posted by Alex Boisvert <bo...@intalio.com>.
Same here; I'm not intimately familiar with the bootstrap process and
Rake's import so I would feel better if Assaf voiced in on it.
alex
On Mon, Aug 17, 2009 at 6:54 AM, Daniel Spiewak <dj...@gmail.com> wrote:
> Could we take a look at this? He *did* supply a patch with specs back in
> May. I can if no one else is up for it, but a change like this should
> probably be reviewed by someone more familiar with the Buildr bootstrap
> process.
>
> Daniel
>
> On Sun, Aug 16, 2009 at 11:42 PM, Rhett Sutphin (JIRA) <jira@apache.org
> >wrote:
>
> >
> > [
> >
> https://issues.apache.org/jira/browse/BUILDR-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743967#action_12743967
> ]
> >
> > Rhett Sutphin commented on BUILDR-278:
> > --------------------------------------
> >
> > I'd like to see this patch (or some other fix) get into buildr before the
> > next release. Is there anything I can do to help it along?
> >
> > > tasks/*.rake files are loaded after the buildfile
> > > -------------------------------------------------
> > >
> > > Key: BUILDR-278
> > > URL: https://issues.apache.org/jira/browse/BUILDR-278
> > > Project: Buildr
> > > Issue Type: Bug
> > > Components: Core features
> > > Affects Versions: 1.3.4
> > > Environment: Any
> > > Reporter: Rhett Sutphin
> > > Attachments:
> > 0001-Move-rakelib-loading-into-load_tasks-so-the-the-file.patch
> > >
> > >
> > > In buildr 1.3.4, the files in tasks/*.rake are loaded after the
> buildfile
> > itself. This means that their contents are not available while loading
> the
> > buildfile. This, in turn, means that some buildfiles that worked under
> > 1.3.3 don't work in 1.3.4.
> > > Thread:
> >
> http://markmail.org/search/?q=buildr#query:buildr%20list%3Aorg.apache.buildr.users+page:1+mid:oc5eaimyxt6o4xqa+state:results
> > > It appears that this may be a consequence of the fix for BUILDR-255.
> >
> > --
> > This message is automatically generated by JIRA.
> > -
> > You can reply to this email to add a comment to the issue online.
> >
> >
>