--- Jeff Turner <[EMAIL PROTECTED]> wrote:
> > It used to be protected at one stage ... can't
> seem to recall why it was made
> > public. Is there any code in Avalon that it would
> break?
>
> Er.. yes, actually.
>
> Two cases in Phoenix:
>
>
src/java/org/apache/avalon/framework/camelot/State.java
>
src/java/org/apache/avalon/phoenix/components/phases/BlockDAG.java
>
> In both cases, moving the constructor calls from
> outside to inside is
> pretty easy, and the code looks just as good. I
> don't think these
> examples represent a new use-case for non-typesafe
> Enums.
>
> Still, it's a backwards-incompatible change. Should
> we create a CVS
> branch "avalon-5_0" for things like this?
-1.
In cases like this, where the API change is not
backwards compatible, but necessary due to security
or other important issues, we change it in CVS,
promote
the version of Framework to 4.1, and we make a
release.
There are two key things to keep in mind:
1) The reason of the change needs to be WELL
documented
2) We also look at other things we want to include in
the release.
I would make the change in CVS, but wait until at
least
September 12 before we make another release. We need
to plan these things--especially since we made a big
announcement for the 4.0 release.
__________________________________________________
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
