Noel J. Bergman wrote:
>>Well we did deprecate the Component interface many many months ago. We
>>were not very good at jkeeping you folks on board and in step :-(
>>
>>
>
>Uh ... actually, I think it shows considerable hubris on the part of the
>Avalon group to assume that they can deprecate and then break an API within
>a YEAR, much less a few months.
>
>
Agreed.
>>careful depecation scehdule in Avalon-Framework and then
>>
>>
>Avalon-Cornerstone.
>
>With all due respect, I think that the notion of careful deprecation
>schedule doesn't seem to have been fully grasped by that group. ONE DOES
>NOT BREAK CLIENT CODE, especially on such a short schedule.
>
>
A small but important note. There have been several attempts to correct
this issue however that has been opposed with sustained -1s on
corrections. If you go back over the archives you will find dozens of
emails raising the issue and referencing the impact on the James
community. Unfortunately the "Avalon Group" have not sucessfully
managed to deal with this issue properly to-date - which, as a
representative of that "group", I find embarasing and frustrating.
Steve.
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
