Nicola Ken Barozzi wrote:
> From: "Leo Sutic" <[EMAIL PROTECTED]>
>
>>Was there any concensus on what to do with
>>framework? Do we go with:
>>
>>org.apache.avalon.framework
>>org.apache.avalon
>>org.apache.framework
>
>
> Then, why not rename Avalon to . ?
> Yeah, let's take out the name Avalon alltogether!
>
> Sorry if I intervene here, but as a heavy avalon user, I would like to
> remind all that we are dead tired of changing package names.
>
> org.apache.avalon.framework is ok, or does making it shorter improve the
> code? :-P
>
> Sorry, but these changes are quite frustrating and unnecessary...
Nothing released will be changed. Framework will not migrate until a
major version change. That major version change will get rid of cruft
(deprecated packages) and hopefully have something else that compells
you to want to use it. But we will still maintain the 4.x series until
we feel ready to let go (which will be after a 5.0 release). We are
not all in agreement on what should go into a 5.0 release, and so
it will be a nice long while.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
