Versioning (again).

[Rod Widdowson]

This is a bit of an "Angels dancing on pins" question and I apologise for
it.

In IDP-712 there is a request to make the entity object available in the
RPUIContext.  There are very many wrong reasons why this might be needed,
but there are enough right reasons that I'm mindful to make the change.

If I add a method to do this in 3.2.0 I'm done. I've added an externally
visible method to the scripting functions in a backwards compatible manner.
Derived classes (not that there will be any) just continue to work.

But in fact the method exists - but it's protected.  So the proposed change
would be to make the protected public.  But I could envisage a very weird
setup in which a derived class stopped working (they overridden the method
as protected)

It’s academic because I'll bet that no one has ever (or will ever) extend
the class or not in this way, so I'd be inclined to just do the right thing.

But I'd like any clarity that those with more Java expertise than I (and a
better understanding of the versioning policy).

/R