In all other situations, Carsten is right - this might cause backward incompatibility. This is important for user-facing classes. Should we start marking classes as internal, like "<b>INTERNAL!!!</b>" in javadoc or some such?
What about introducing @cocoon.usage tags I proposed a while ago like: @cocoon.usage published
or: @cocoon.usage flowscript
etc.
This might someday also be used to generate separate Javadocs for different APIs.
Guido
