This content has been marked as final. Show 1 reply
Would it be all right if I added a third method to MutableClassInfo (see below), so I can get rid of the problem?
If this fixes your problem, sure.
My main concern is whether there could be other classes outside of JBoss Reflection project implementing MutableClassInfo interface.
I doubt they do, as this was never properly finished.
(only a mad man would do this :-)
And even if they do, we're changing the version to indicate that there were api changes,
hence users can either change their code or stick with the old one.