Yes, that's exactly what we were thinking of for the "Java
API". I argued exactly the same point about the refactoring as well :-)
And the tool is for just that reason -- maybe we can even reuse the existing beans.xml
excludes syntax, and apply the excludes that we can (i.e. not the ones conditional upon
the runtime env) at that point, via this generated class.
So, prototype away!
Have a look at my current "exact" scanning,
and perhaps we can just extend that to first apply this interface logic,
then fall back on the .txt file.
btw: we're currently using String collection of classes.
Afair we used to have Class collection, which would be more convenient here.