[
https://issues.apache.org/jira/browse/BUILDR-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730916#action_12730916
]
Daniel Spiewak commented on BUILDR-297:
---------------------------------------
HELPWANTED on the testing front. I have some ideas as to how it can be tested,
but none of them are pretty. Idea number one is that we split off a separate
thread in the specs for the CC task. Then, we touch files and monitor the
mtime of directories (not sure how well that'll work). Idea number two is to
adjust the implementation somewhat so that we can mock the important bits,
allowing the specs to just hook directly into the task, preventing it from
doing anything and allowing a less hacky monitoring strategy. Opinions? Ideas?
> Add Support for Continuous Compilation Mode
> -------------------------------------------
>
> Key: BUILDR-297
> URL: https://issues.apache.org/jira/browse/BUILDR-297
> Project: Buildr
> Issue Type: New Feature
> Components: Core features
> Affects Versions: 1.3.4
> Reporter: Daniel Spiewak
> Assignee: Daniel Spiewak
>
> Buildr should include a project_local :cc task which activates a continuous
> compilation mode. This mode should monitor source and test directories for
> changes, triggering a recompilation as necessary. Given Buildr's primitive
> recompilation detection (especially with Groovy and Scala) and its extremely
> long startup time on JRuby, this feature should save a great deal of time,
> particularly in a quick-rebuild scenario. For this reason, I am assigning it
> a priority of "Major".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
