|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Ah, I've done it that way before myself, shame I forgot about it.
In a way it still repeats the language name (just encoded into the annotation name instead of an attribute value) but at least that way the JSR 223 engine name isn't spread out all over the place. I don't think there really is a difference in the migration scenario but as you say there is one with respect to obviousness. You'd also need two custom annotations with the advent of @ParameterScriptAssert.
Not sure what I like better.