On Wednesday 11 August 2004 00:44, Stefano Mazzocchi wrote: > Niclas Hedhman wrote: > > Gang, > > I would like to propose that we work towards an Avalon Framework 4.5 > > Release, with the following 'features' included; > > > > * AvailabilityAware interfaces (proposed (CTR) last week) > > * JDK 1.5 compatibility (4.2 doesn't compile on Java2 ver 5 ) > > * Bug fixes, like the equals()/hashCode() I encountered recently. > > * Move to a single "avalon" top level group, and use "avalon/framework" > > * Other? > > > > > > Considering the additions, I think "4.5" is a reasonable increment. > > WDYAT? > > > > I don't see a need to rush the release, and we can allow plenty of time > > to sort out any details that people may have. > > will 4.5 be compatible with 4.x series? > > If not, it should be 5.0
Yes, it will be fully compatible with 4.x; AvailabilityCapable (someone pointed out that xxxAware was used by WebWorks) is a 100% compatible change in all directions, believe it or not. Old components in new containers, and any other combination. Old containers doesn't support dependent components to temporarily disappear, and hence can fully ignore the interface. And components that are AvailabilityCapable doesn't need the interface, if no such 'intermittent unavailbility' occurs. There has been concerns over the 'grouping change', that we should keep the avalon-xxx repo structures. I am -0.1 on keeping the avalon-xxx. Cheers Niclas -- +------//-------------------+ / http://www.bali.ac / / http://niclas.hedhman.org / +------//-------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
