"Eric Pugh" <[EMAIL PROTECTED]> writes:
>I think we should remove the Vector support now that we are past 1.0.
>Should we add a VectorConfiguration class that decorates a regular
>Configuration and adds in the Vector methods?
Yep, nuke it!
>Or just not worry about it? Alternatively, should a VectorConfiguration
>live in the Turbine 2.3 source tree?
Turbine 2.x (x > 3) will solely use getList(). I was just worrying
about current Turbine 2.x (x <= 3) users that want to upgrade their
application dependencies from mumble-SNAPSHOT to 1.0 and suddently
find methods gone. The 1.0 release avoids this and for 1.1, we will be
better off without getVector().
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire
Linux, Java, perl, Solaris -- Consulting, Training, Development
"Fighting for one's political stand is an honorable action, but re-
fusing to acknowledge that there might be weaknesses in one's
position - in order to identify them so that they can be remedied -
is a large enough problem with the Open Source movement that it
deserves to be on this list of the top five problems."
-- Michelle Levesque, "Fundamental Issues with
Open Source Software Development"
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
