You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Ittay Dror (JIRA)" <ji...@apache.org> on 2008/11/03 15:13:44 UTC
[jira] Created: (BUILDR-196) diagnostics about why compilation /
packaging is triggered
diagnostics about why compilation / packaging is triggered
----------------------------------------------------------
Key: BUILDR-196
URL: https://issues.apache.org/jira/browse/BUILDR-196
Project: Buildr
Issue Type: Improvement
Components: Compilers
Affects Versions: 1.3.2
Reporter: Ittay Dror
Fix For: 1.3.4
The checks in #needed? methods of CompileTask and ArchiveTask are non trivial. This means that when compilation is triggered, it is hard to know why (see previous bug for a use case).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (BUILDR-196) diagnostics about why compilation /
packaging is triggered
Posted by "Assaf Arkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Assaf Arkin updated BUILDR-196:
-------------------------------
Fix Version/s: (was: 1.3.4)
Priority: Minor (was: Major)
> diagnostics about why compilation / packaging is triggered
> ----------------------------------------------------------
>
> Key: BUILDR-196
> URL: https://issues.apache.org/jira/browse/BUILDR-196
> Project: Buildr
> Issue Type: Improvement
> Components: Compilers
> Affects Versions: 1.3.2
> Reporter: Ittay Dror
> Priority: Minor
>
> The checks in #needed? methods of CompileTask and ArchiveTask are non trivial. This means that when compilation is triggered, it is hard to know why (see previous bug for a use case).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.