You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Assaf Arkin (JIRA)" <ji...@apache.org> on 2008/07/28 19:07:31 UTC
[jira] Resolved: (BUILDR-108) Trace to explain why a compile is
done
[ https://issues.apache.org/jira/browse/BUILDR-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Assaf Arkin resolved BUILDR-108.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.3.3
> 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
> Fix For: 1.3.3
>
> 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.