commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Colebourne" <scolebou...@btopenworld.com>
Subject Re: [configuration] [collections] ExtendedProperties
Date Mon, 29 Dec 2003 14:39:20 GMT
[collections] has no need for ExtendedProperties, and will not be depending
on [configuration].

My question is whether [configuration] is more complex to use than
ExtendedProperties. If there is no single equivalent class, then I'm not
sure I can deprecate in [collections].

Stephen

----- Original Message -----
From: "Shapira, Yoav" <Yoav.Shapira@mpi.com>
Howdy,
Deprecate from both if it's not used.  Keep it in Collections if it's
used only there, and deprecate the Configuration references to it
(unless we have a use-case for Collections depending on Configuration).

Yoav Shapira
Millennium ChemInformatics


>-----Original Message-----
>From: Henri Yandell [mailto:bayard@generationjava.com]
>Sent: Monday, December 29, 2003 8:22 AM
>To: Jakarta Commons Developers List
>Subject: Re: [configuration] [collections] ExtendedProperties
>
>
>Deprecate from both? :)
>
>Hen
>
>On Mon, 29 Dec 2003, Emmanuel Bourg wrote:
>
>> Actually ExtendedProperties isn't even used in [configuration], there
>> are just a method getConfiguration(ExtendedProperties) and a method
>> getExtendedProperties(Configuration) in ConfigurationConverter to
>> maintain compatibility with older code using ExtendedProperties.
>>
>> I'd suggest to deprecate it in favor of Configuration and let it in
>> [collection].
>>
>> Emmanuel Bourg
>>
>>
>> Stephen Colebourne wrote:
>> > [collections] currently has an ExtendedProperties class. IIRC, this
>class
>> > forms part of the [configuration] project. I've never thought it
fitted
>in
>> > [collections].
>> >
>> > Now [configuration] is promoted, is it time to deprecate the
>[collections]
>> > version??? Basically, I'm trying to kick out all inappropriate
classes
>from
>> > [collections].
>> >
>> > Stephen
>> >
>> >
>> >
---------------------------------------------------------------------
>> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>> > For additional commands, e-mail:
commons-dev-help@jakarta.apache.org
>> >
>> >
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: commons-dev-help@jakarta.apache.org




This e-mail, including any attachments, is a confidential business
communication, and may contain information that is confidential, proprietary
and/or privileged.  This e-mail is intended only for the individual(s) to
whom it is addressed, and may not be saved, copied, printed, disclosed or
used by anyone else.  If you are not the(an) intended recipient, please
immediately delete this e-mail from your computer system and notify the
sender.  Thank you.


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message