-Xdisable-assertion not working for project settings
Disabling assertions only for a single project (Scala Compiler > Advanced > Xdisable-assertions or setting the option -Xdisable-assertion directly) does not work (disabling them globally works fine).
Leave a comment
on 2012-10-02 01:13 *
By Iulian Dragos
Does this happen only in 2.10?
on 2012-10-02 01:54 *
By Simon Schäfer
No, this occurs in 2.9, too.
on 2012-10-11 02:43 *
By Iulian Dragos
Component changed from None to builder
Milestone set to Helium
on 2012-10-15 03:46 *
By Iulian Dragos
The new Sbt (0.13) is caching compiler instances. It looks like the compiler is not restarted when compiler settings changed. Would fix a couple of related issues too.
(In scala-ide:1523222027afaf8072dbe09780ee59b60cf7f829) Correctly update project settings when the preferences change.
The `PropertyStore` class is a snapshot, and during the move to sbt 0.13 the storage
became a lazy-val, meaning we started to lose project settings.
Fixed #1001241
Fixed #1001267
Branch: master
The `PropertyStore` class is a snapshot, and during the move to sbt 0.13 the storage
became a lazy-val, meaning we started to lose project settings.
Fixed #1001241
Fixed #1001267
Branch: master