> I'm not sure I agree with forcing you to add something. If we've moved a > formerly hard-coded property to now being configurable, you shouldn't have > to do anything.
Agreed for that particular use case. > If its a new value, we should have a sensible default > without requiring you to choose one Sensible defaults are not necessarily desirable, and I would imagine that is more likely true for complex overlays like ours. Let's consider a concrete example that I recall. Recently (relatively speaking) the following property was added: cas.themeResolver.defaultThemeName The default value was totally meaningless for us due to how we've implemented theming and it was helpful for the build to fail to force me to examine how theming had changed to bring other related changes in our overlay in line with the new approach. Again, I'm ambivalent: I see both benefits and liabilities to this change. M -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
