You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Eric Pugh <ep...@upstate.com> on 2004/09/06 15:06:05 UTC
RE: [configuration]Last call for patches
Hi all,
Just getting back into the swing of things after vacation. Seems like a bit
of activity in configuration, so I hope I don't accidentally step on
anyone's toes.. I was really hoping that getVector had been eradicated
everywhere.. I know we spent quite a lot of effort doing that. But, maybe
as far as turbine is concerned, it was only in the 2.4 branch...
At any rate, since it is marked as deprecated, and Henning has put back all
the unit tests, I guess we can let it lie... I hate releasing a 1.0 w/
deprecated code, on the other hand, getting to 1.0 is the main job!
Eric
> -----Original Message-----
> From: Henning P. Schmiedehausen [mailto:hps@intermeta.de]
> Sent: Monday, August 16, 2004 5:59 PM
> To: commons-dev@jakarta.apache.org
> Subject: Re: [configuration]Last call for patches
>
>
> Emmanuel Bourg <sm...@lfjr.net> writes:
>
> >Pak, Young-rok wrote:
>
> >> I want this feature in Commons-Configuration. I think it'll be
> easily add to current version. If you agree to my proposal, I
> will be able to help you.
>
> >Hi, this would certainly be a useful addition to [configuration] but
> >it's too late to include it in the 1.0 release. Could you please open a
> >request for enhancement in bugzilla and detail your proposal? If you can
> >contribute some code it's even better of course :)
>
> The current 1.0-RC candidate is _NOT_ compatible to the various
> pre-1.0 snapshots that are in wide use with e.g. Turbine.
>
> If you drop it in, there will be complaints about the missing
> getVector() methods from the Configuration interface.
>
> I will rework the Turbine code for the 2.3.1 release, however, it
> would be _very_ nice, if these methods (which are Vector
> getVector(String) and Vector getVector(String, Vector)) are kept for
> the 1.0 release to allow projects that are currently using the
> snapshots to migrate to 1.0 without having to rebuild.
>
> I'm all for deprecating these methods and removing them for 1.1. But
> _please_ keep them for 1.0.
>
> I have a patch for this that I want to put into CVS later today.
>
> Regards
> Henning
>
> --
> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
> hps@intermeta.de +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: 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
Re: [configuration]Last call for patches
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
"Eric Pugh" <ep...@upstate.com> writes:
>Hi all,
[...]
>the unit tests, I guess we can let it lie... I hate releasing a 1.0 w/
>deprecated code, on the other hand, getting to 1.0 is the main job!
I'm -0 on releasing c-c with the changed behaviour w.r.t
get<valueType>(String propertyName) (e.g. getString() or getBoolean()).
All snapshots up to 1.0-rc1 returned null if no property exists. Since
1.0-rc1, this throws an Exception. This will also catch a lot of code
that uses c-c unaware.
There is now also the problem, that get<valueType>(String
propertyName) differ in their semantics from get<valueType>(String
propertyName, <valueType> default).
Emmanuel proposed to add a switch to change the behaviour.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [configuration]Last call for patches
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
"Eric Pugh" <ep...@upstate.com> writes:
>Hi all,
>Just getting back into the swing of things after vacation. Seems like a bit
>of activity in configuration, so I hope I don't accidentally step on
>anyone's toes.. I was really hoping that getVector had been eradicated
>everywhere.. I know we spent quite a lot of effort doing that. But, maybe
>as far as turbine is concerned, it was only in the 2.4 branch...
>At any rate, since it is marked as deprecated, and Henning has put back all
>the unit tests, I guess we can let it lie... I hate releasing a 1.0 w/
>deprecated code, on the other hand, getting to 1.0 is the main job!
I tried the 1.0-rc with existing stuff like Turbine 2.3 and Torque 3.1
and they were all rather upset to find getVector() missing... :-)
This is not about "cleaning up current code". This is about being
compatible to existing and released code that uses c-c.
If we rip these out, there is no way to migrate existing code from the
various snapshots to clean 1.0. IMHO this would really upset our
users.
We will have a release of c-c with getVector() (1.0) and then rip it
out immediately afterwards. If one needs a released version to remove
all these snapshots used in many projects, they should use 1.0. If one
needs newer stuff, they must rework their code.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org