On Tue, Mar 26, 2013 at 10:58 AM, Robert Burrell Donkin <[email protected]> wrote: > Tentacles is a little unusual in using Java assertions. When assertions are > off, then [1] no longer works as expected (rather than running with > debugging checks off). > > For applications in runnable jars, I think using assertions to allow > debugging is a cool idea - controlling logging levels is sometimes tricky in > this situation. However - by the principle of least surprise - when on the > golden path, I think tentacles should function correctly whether assertions > are on or off. > > Opinions?
Totally agree. I've never once remembered to turn them on, have always ran into the issue of the dir not getting created, and *then* remembered about assertions needing to be on. And I wrote the stinking code. I rarely used assertions before and have completely stopped using them since. It's a clear no-no for code that must run, and really, who wants even their checks to be optional? Feel free to hack it up. Side note, wow I didn't know anyone but be had ever used tentacles :) -David
