I suggest that [version] should contain utilities for determining and handling versions, and that those utilities can handle version information that is reflection-based so that you don't have to implement an interface explicitely.
Implementing an interface explicitely could create versioning trouble, since if it was successful and every project implemented the interface, when using other projects we could have versioning conflicts when the different packages were created using different versioning components. We would create the problems we were supposed to solve. So, the utilities must be forgiving and intelligent when determining versions of other classes. This would also make it easier for the other jakarta projects to insert version information for their classes. I would very much like to see this determination done in a rule-based fashion (with a bunch of predicates) so that it will be possible to create rules for already existing classes you don't have control over. Versioning problems occurs first and foremost in other people's code, especially non-open-source and legacy code where you (without [version]) have few possibilities to fix it. One should probably look at [lang] (basic reflection and predicates) and [clazz]. /O -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
