I don't know the preferred policy for API changes. From monitoring this
list I got the impression that this can be complicated: old methods
first have to be deprecated before they can be removed/replaced in a
later release.
I am not sure if deprecation helps in all cases, e.g. if a method's
re
Eric Pugh wrote:
Re: [configuration] Exception handling - was Automatic reloadingI would like
to move on a 1.0 very aggressively now that the vote has passed. Part of me
feels that we should basically take the code as is and make that be 1.0. It
is very well tested, stable, and in use in some pr
, 2003 6:39 PM
To: Jakarta Commons Developers List
Subject: Re: [configuration] Exception handling - was Automatic reloading
[EMAIL PROTECTED] wrote:
> Emmanuel,
>
> ;-) thank you for putting my name in the author field of
> ReloadingStrategy, but I do not deserve this
[EMAIL PROTECTED] wrote:
Emmanuel,
;-) thank you for putting my name in the author field of
ReloadingStrategy, but I do not deserve this honour. This is all your
design.
That was your idea ;)
I have one remark and this is not specific to your code, but applies to
whole configuration: Our excepti
could then declare all your methods to
throw ConfigurationException to avoid signature changes in the
future.
-Original Message-
From: Oliver Heger [mailto:[EMAIL PROTECTED]
Sent: Friday, December 19, 2003 4:53 AM
To: Jakarta Commons Developers List
Subject: [configuration] Exception hand
Emmanuel,
;-) thank you for putting my name in the author field of
ReloadingStrategy, but I do not deserve this honour. This is all your
design.
I have one remark and this is not specific to your code, but applies to
whole configuration: Our exception handling is very inconsistent in some
poi
