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] Created: (BUILDR-249) Filter#run updates target timestamp when there are directory mappings
Date Wed, 11 Feb 2009 09:32:59 GMT
Filter#run updates target timestamp when there are directory mappings
---------------------------------------------------------------------

                 Key: BUILDR-249
                 URL: https://issues.apache.org/jira/browse/BUILDR-249
             Project: Buildr
          Issue Type: Bug
          Components: Core features
    Affects Versions: 1.3.4
            Reporter: Ittay Dror
             Fix For: 1.3.4


Filter#run first creates a variable, copy_map for all destinations that need refreshing (older
than source)
Then if the copy_map is not empty, it iterates each entry, if the source is a directory, it
creates the destination directory and continues. At the end it touches the root target directory.

Since if the destination directory exists, it is not touched (mkpath doesn't change timestamps),
the result is that if there is a source directory newer than an existing destination directory,
they will always appear in copy_map and as a result the root target timestamp is always updated,
which causes the jar task to alwyas run, which cases all those dependent on it to recompile.


I guess this is not evident normally, because of bug BUILDR-205 which causes the filter task
to not run at all if the root target already exist, but since I wanted resources to actually
be copied when needed, I worked around the bug by forcing the task to always run. 

-- 
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