Compilation errors in the mirahc stage will still cause the app (whatever version is already on disk) to be installed in "jrake install"
(This is true only when the compiler is invoked using the org.mirah.ant.Compile task; shelling out with exec works properly.)
What's the rationale for calling the ant.Compile task rather than using exec? This is a pretty frustrating bug, especially when you get in the habit of running rake install && adb logcat.
rake install && adb logcat
I believe exec will spawn another JVM, so you pay startup costs for the redundant process.
That makes sense. I submitted a fix on the mirah side of things; think you can test it out?
This is stale; the issue was fixed by mirah/mirah#140.