We won't be breaking plugins. I don't want to move to this for the reasons
stated before. This code also is way less maintainable, and looks like it
could break easily.  I really think that clarity should win out here over
an abuse of java reflection.

On 10 Jul,2014, at 17:15 , Anis KADRI <anis.ka...@gmail.com> wrote:

> I want to say that this should be default...but we won't change the API
> again and won't break plugins again.

Both could be supported at the same time, just by using a different base
class

Reply via email to