cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guido Casper <>
Subject [Vote] Marking internal classes
Date Sun, 18 Jul 2004 11:38:17 GMT
Guido Casper wrote:
> Vadim Gritsenko wrote:
>> 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.

Hm, noone (but me :-) seems to like the idea.

So maybe it's a good idea to first have a quick vote about whether to 
mark internal classes as such or to mark "published classes/interfaces" 
as such (and then decide how to mark them).


View raw message