[jira] Resolved: (BUILDR-400) Don't forbid projects to use their own compiler after one has been guessed

["Antoine Toulme (JIRA)" <ji...@apache.org>]

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

Antoine Toulme resolved BUILDR-400.
-----------------------------------

    Resolution: Fixed

22:35:38~/w/buildr>svn ci CHANGELOG spec/core/compile_spec.rb lib/buildr/core/compile.rb -m "fix for BUILDR-400: Don't forbid projects to use their own compiler after one has been guessed"
Sending        lib/buildr/core/compile.rb
Sending        spec/core/compile_spec.rb
Transmitting file data ..
Committed revision 930479.

> Don't forbid projects to use their own compiler after one has been guessed
> --------------------------------------------------------------------------
>
>                 Key: BUILDR-400
>                 URL: https://issues.apache.org/jira/browse/BUILDR-400
>             Project: Buildr
>          Issue Type: Improvement
>          Components: Compilers
>    Affects Versions: 1.3.5
>            Reporter: Antoine Toulme
>            Assignee: Antoine Toulme
>             Fix For: 1.4
>
>
> Currently, when one tries to set a compiler with the using method, you may get unexpected results.
> That's because Buildr tries to guess the compiler _before_ the compile task is created.
> We should not lock people from deciding what their compiler will be before the end of the project definition.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.