Java's official versioning spec  seems curiously irrelevant. It talks
about API specifications, and implementations thereof; not the sort of
scenario most people deal with. It's primary use-case seems to be
applets (it amuses me how Sun documents can be dated this way;)
I'm not so sure this concept is irrelevant to general purpose application
* Does your application architecture expose abstractions as
interfaces (or abstract classes)?
* Do you have more than one implementation of those abstractions?
* Do the implementations rev independently of (and probably at a faster
rate than) the abstractions?
If so, exactly the same versioning model is quite reasonable.
To unsubscribe, e-mail: <mailto:ant-...@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-...@jakarta.apache.org>