Hello, I've been working on updating a Fortress app of mine to take advantage of avalon-repository. However, I've noticed that the DefaultInitialContext constructor has changed and the simpler constructors are now part of a DefaultInitialContextFactory. So a couple of things:
The javadocs on the avalon-repository site say "1.3" at the top, but this cannot be accurate. Or at least they aren't the latest 1.3 javadocs. I imagine they are probably closer to 1.2, but I'm not sure. This makes it harder to write my application. So, mini-proposal #1: * javadocs should be published for only the latest STABLE release unless otherwise noted in the link description Secondly, according to the APR versioning scheme [1] which we discussed before [2] and got a general consensus to adopt, these changes qualify as a MAJOR version number change because software written against 1.2 will not compile against the current 1.3 snapshots. This means 1.3 _should_ be a 2.0 release. This brings me to mini-proposal #2: * we need to official adopt a versioning scheme and begin enforcing it I think the APR rules make sense. We can work on a way to automate it or whatever, I don't care. We just need consistency. Thoughts? I'll bring the versioning scheme up as an official vote if necessary. J. Aaron Farr � SONY ELECTRONICS � DDP-CIM � (724) 696-7653 [1] http://apr.apache.org/versioning.html [2] http://marc.theaimsgroup.com/?t=107730780100003&r=1&w=2 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
