On 10/05/2012 01:24 PM, Igor Fedorenko
feature label. This is currently reviewed as -1 by Igor simply
used Groovy instead of BeanShell to test plugin. The suggested
script is way more powerful and verifies more stuff than what
BeanShell one did. It's simply better quality. Source features
widely used, and I'd like to discuss whether a -1 for using
instead of BeanShell is really fair.
The issue here is long term maintenance of the code. Using
some cases and groovy in others introduces technical debt, and
though this particular case may seem minor and even unfair,
technical dept tends to accumulate pretty fast.
Since BeanShell is a subset of Java, and Groovy is a super-set of
Java, it makes BeanShell a subset of Groovy, and renaming *.bsh to
*.groovy would work.
Also, I don't understand your argument about technical debt. Why
using a new language introduce some technical debt?