buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lacton (JIRA)" <j...@apache.org>
Subject [jira] Updated: (BUILDR-108) Trace to explain why a compile is done
Date Sun, 27 Jul 2008 15:45:31 GMT

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

Lacton updated BUILDR-108:
--------------------------

    Attachment: BUILDR-108.patch

> Trace to explain why a compile is done
> --------------------------------------
>
>                 Key: BUILDR-108
>                 URL: https://issues.apache.org/jira/browse/BUILDR-108
>             Project: Buildr
>          Issue Type: Improvement
>          Components: Compilers
>    Affects Versions: 1.3.3
>         Environment: Trunk revision 679935
>            Reporter: Lacton
>            Priority: Trivial
>         Attachments: BUILDR-108.patch
>
>
> In one of my projects, I found it hard to understand why buildr was recompiling a module.
Adding a trace helped me understand what was happening. Maybe it will be useful to others.

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