buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ittay Dror (JIRA)" <j...@apache.org>
Subject [jira] Commented: (BUILDR-182) drb wishes
Date Tue, 21 Oct 2008 19:50:44 GMT

    [ https://issues.apache.org/jira/browse/BUILDR-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641555#action_12641555
] 

Ittay Dror commented on BUILDR-182:
-----------------------------------

3. add a hook that a task can implement to reinitialize itself on each run. in the same way
that actions and prerequisites are saved and restored a task may need to restore other variables.


> drb wishes
> ----------
>
>                 Key: BUILDR-182
>                 URL: https://issues.apache.org/jira/browse/BUILDR-182
>             Project: Buildr
>          Issue Type: Wish
>          Components: Extensions
>    Affects Versions: 1.3.4
>            Reporter: Ittay Dror
>
> Add hooks to Snapshot, so there can be better control over what tasks are redefined in
each build:
> 1. some tasks are defined lazily to save performance when buildr runs directly. however,
for performance reasons i don't want to define them in each subsequent run. furthermore, some
of those tasks may have logic to not execute in subsequent builds under some circumstances.
> ==> add option to add tasks to the snapshot
> 2. some tasks may need to recreate their prerequisites in each run. for example in C++
a library depends on the obj files from which it is linked. but in each run the list of objects
needs to be reconstructed to account for changes in the files. this can be handled by lazily
defining this list (since drb always returns the prerequisites to their original state), yet,
it may be easier if a hook is provided that instructs drb to recreate a task completely in
subsequent runs.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message