[RESULT] [VOTE]Configuration release 1.1
The commons community has voted to release commons-configuration 1.1. Here are the results in detail: +1: 3 Emmanuel Bourg Dion Gillard Oliver Heger +/-0 : none -1: none I am going to cut the release at the coming weekend. Oliver Oliver Heger wrote: Dear community, since the 1.0 release of [configuration] we made some progress and added a couple of new features. To make these available for a larger user base, I think it is time to cut out a new 1.1 release. A complete list of changes since the 1.0 releaes can be found here: http://www.apache.org/~oheger/commons-configuration-1.1rc3-docs/changes-report.html. In the process of preparing the release there have been some release candidates. The latest is 1.1rc3, which can be inspected at http://www.apache.org/~oheger/commons-configuration-1.1rc3 (the tag for 1.1RC3 is named CONFIGURATION_1_1RC3). Here is my +1! Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE]Configuration release 1.1
Dear community, since the 1.0 release of [configuration] we made some progress and added a couple of new features. To make these available for a larger user base, I think it is time to cut out a new 1.1 release. A complete list of changes since the 1.0 releaes can be found here: http://www.apache.org/~oheger/commons-configuration-1.1rc3-docs/changes-report.html. In the process of preparing the release there have been some release candidates. The latest is 1.1rc3, which can be inspected at http://www.apache.org/~oheger/commons-configuration-1.1rc3 (the tag for 1.1RC3 is named CONFIGURATION_1_1RC3). Here is my +1! Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE]Configuration release 1.1
+1 ! Thank you for managing the release Oliver. Emmanuel Bourg Oliver Heger wrote: Dear community, since the 1.0 release of [configuration] we made some progress and added a couple of new features. To make these available for a larger user base, I think it is time to cut out a new 1.1 release. A complete list of changes since the 1.0 releaes can be found here: http://www.apache.org/~oheger/commons-configuration-1.1rc3-docs/changes-report.html. In the process of preparing the release there have been some release candidates. The latest is 1.1rc3, which can be inspected at http://www.apache.org/~oheger/commons-configuration-1.1rc3 (the tag for 1.1RC3 is named CONFIGURATION_1_1RC3). Here is my +1! Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE]Configuration release 1.1
On Mon, 28 Mar 2005 17:15:56 +0200, Emmanuel Bourg [EMAIL PROTECTED] wrote: +1 ! Thank you for managing the release Oliver. Emmanuel Bourg Oliver Heger wrote: Dear community, since the 1.0 release of [configuration] we made some progress and added a couple of new features. To make these available for a larger user base, I think it is time to cut out a new 1.1 release. A complete list of changes since the 1.0 releaes can be found here: http://www.apache.org/~oheger/commons-configuration-1.1rc3-docs/changes-report.html. In the process of preparing the release there have been some release candidates. The latest is 1.1rc3, which can be inspected at http://www.apache.org/~oheger/commons-configuration-1.1rc3 (the tag for 1.1RC3 is named CONFIGURATION_1_1RC3). Here is my +1! Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE]Configuration release 1.1
Looks good +1. On Mon, 28 Mar 2005 16:12:14 +0200, Oliver Heger [EMAIL PROTECTED] wrote: Dear community, since the 1.0 release of [configuration] we made some progress and added a couple of new features. To make these available for a larger user base, I think it is time to cut out a new 1.1 release. A complete list of changes since the 1.0 releaes can be found here: http://www.apache.org/~oheger/commons-configuration-1.1rc3-docs/changes-report.html. In the process of preparing the release there have been some release candidates. The latest is 1.1rc3, which can be inspected at http://www.apache.org/~oheger/commons-configuration-1.1rc3 (the tag for 1.1RC3 is named CONFIGURATION_1_1RC3). Here is my +1! Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][configuration]Release 1.1
Emmanuel Bourg wrote: Ok I checked again my application with the latest nightly build and it worked fine. I don't know what happened the last time I updated my commons configuration jar... Actually I do have a bug, the configuration is loaded twice but not cleared, so all properties are duplicated. I'm trying to build a reduced test case. Emmanuel Bourg smime.p7s Description: S/MIME Cryptographic Signature
Re: [VOTE][configuration]Release 1.1
Emmanuel Bourg wrote: Actually I do have a bug, the configuration is loaded twice but not cleared, so all properties are duplicated. I'm trying to build a reduced test case. I investigated the problem and found 2 issues: - the updateLastModified method in FileChangedReloadingStrategy didn't always work. It tried to build the File using the fileName of the configuration and then it called lastModified(). For some reason it returned 0 as if the file didn't exist, but I haven't been able to determine exactly the conditions. I fixed this bug by calling getFile() on the FileConfiguration instead of building the file from the file name. - the previous bug caused the configuration to be reloaded on every call to getProperty, and at some point load() has been called twice in a row, I'm not sure how though. In this case the properties are duplicated, I opened Bug 33814 to discuss this issue. Emmanuel Bourg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][configuration]Release 1.1
Okay, I would like to get out the release as soon as possible, too. Emmanuel, did you make some progress at the reloading stuff? Is there something I can do to help you? Oliver Eric Pugh wrote: You didn't break fulcrum.. Fulcrum Configuration is built by Gump against the CVS head, so the API change between 1.0 and 1.1 of commons-configuration cause compile errors. The sooner we can get a release out, the better.. I'll try next week to see if I can help! Eric -Original Message- From: Oliver Heger [mailto:[EMAIL PROTECTED] Sent: Friday, February 18, 2005 1:53 AM To: Jakarta Commons Developers List Subject: Re: [VOTE][configuration]Release 1.1 Welcome back, Eric! We were trying to get a 1.1 release out, but this is halted now because of problems in the reloading area. In which way did we break Fulcrum? Oliver Eric Pugh wrote: Folks, I have been really tied up in real life since before Christmas, but life has started calming down. I'll be looking at getting reinvolved again in the commons projects that are near and dear to my heart! For what it's worth, I am very excited about getting another rev of configuration out. (that and gump has been complaining about Fulcrum Configuration and the new API!). Eric -Original Message- From: robert burrell donkin [mailto:[EMAIL PROTECTED] Sent: Thursday, February 10, 2005 2:16 PM To: Jakarta Commons Developers List Subject: Re: [VOTE][configuration]Release 1.1 FWIW i've never regretted holding a release and i think the right decision's been made. - robert On Thu, 2005-02-10 at 19:43, Oliver Heger wrote: Of course, I don't want to force a release out which is not mature. Let's hold it. But I feel a bit disappointed that it seems to be so hard to get the required three +1s. I think we must be careful that we do not lose our momentum :-( Oliver Emmanuel Bourg wrote: I'm actually -1 for the release, I dropped the 1.1rc1 jar in my application yesterday and it broke with an exception related to the configuration reloading stuff. This may be linked to the issue reported by Jurgen Schlierf on the commons-user list. I'd like to investigate this bug before releasing the final 1.1. Emmanuel Bourg Oliver Heger wrote: Hi all, we need another +1 to get our release out. Nobody? Oliver Oliver Heger wrote: Dear community, since the 1.0 release of [configuration] a couple of new features have been added. The code base has been stable for a while now, so I think it is time to cut out a new 1.1 release before we start to implement further features and refactorings. A complete list of changes since the 1.0 releaes can be found here: http://jakarta.apache.org/commons/configuration/changes-report.html I have created a release candidate, which can be inspected at http://www.apache.org/~oheger/commons-configuration-1.1rc1/ (the tag for 1.1RC1 is named CONFIGURATION_1_1RC1). Here is my +1! Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][configuration]Release 1.1
Oliver Heger wrote: Okay, I would like to get out the release as soon as possible, too. Emmanuel, did you make some progress at the reloading stuff? Is there something I can do to help you? Oliver I haven't had a chance to test it yet, I should have some time this week. Emmanuel Bourg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][configuration]Release 1.1
Emmanuel Bourg wrote: I haven't had a chance to test it yet, I should have some time this week. Ok I checked again my application with the latest nightly build and it worked fine. I don't know what happened the last time I updated my commons configuration jar... I'm +1 for a 1.1-rc2 release followed by a final 1.1 Emmanuel Bourg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][configuration]Release 1.1
Strange! Okay, I would like to have a look at bug 33723 and maybe add a unit test that checks for absolute path names (to be sure). 33691 is open, too, but I think this has been more or less solved in the meantime. Here we could only modify the constructor of SubsetConfiguration that does not take a delimiter as argument to set the default delimiter. And we could prevent trailing dots in the prefix. I hope I come to these things tomorrow. Then it's time for the second RC! Oliver Emmanuel Bourg wrote: Emmanuel Bourg wrote: I haven't had a chance to test it yet, I should have some time this week. Ok I checked again my application with the latest nightly build and it worked fine. I don't know what happened the last time I updated my commons configuration jar... I'm +1 for a 1.1-rc2 release followed by a final 1.1 Emmanuel Bourg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][configuration]Release 1.1
Oliver Heger wrote: Strange! Okay, I would like to have a look at bug 33723 and maybe add a unit test that checks for absolute path names (to be sure). 33691 is open, too, but I think this has been more or less solved in the meantime. Here we could only modify the constructor of SubsetConfiguration that does not take a delimiter as argument to set the default delimiter. And we could prevent trailing dots in the prefix. I hope I come to these things tomorrow. Then it's time for the second RC! Regarding bug 33691 I'm not sure we should change the code of SubsetConfiguration, this may just be a documentation issue. Emmanuel Bourg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE][configuration]Release 1.1
I'll take a loo at the latest as well, I need to update some dependencies anyway for Turbine! -Original Message- From: Oliver Heger [mailto:[EMAIL PROTECTED] Sent: Monday, February 28, 2005 12:09 PM To: Jakarta Commons Developers List Subject: Re: [VOTE][configuration]Release 1.1 Strange! Okay, I would like to have a look at bug 33723 and maybe add a unit test that checks for absolute path names (to be sure). 33691 is open, too, but I think this has been more or less solved in the meantime. Here we could only modify the constructor of SubsetConfiguration that does not take a delimiter as argument to set the default delimiter. And we could prevent trailing dots in the prefix. I hope I come to these things tomorrow. Then it's time for the second RC! Oliver Emmanuel Bourg wrote: Emmanuel Bourg wrote: I haven't had a chance to test it yet, I should have some time this week. Ok I checked again my application with the latest nightly build and it worked fine. I don't know what happened the last time I updated my commons configuration jar... I'm +1 for a 1.1-rc2 release followed by a final 1.1 Emmanuel Bourg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE][configuration]Release 1.1
You didn't break fulcrum.. Fulcrum Configuration is built by Gump against the CVS head, so the API change between 1.0 and 1.1 of commons-configuration cause compile errors. The sooner we can get a release out, the better.. I'll try next week to see if I can help! Eric -Original Message- From: Oliver Heger [mailto:[EMAIL PROTECTED] Sent: Friday, February 18, 2005 1:53 AM To: Jakarta Commons Developers List Subject: Re: [VOTE][configuration]Release 1.1 Welcome back, Eric! We were trying to get a 1.1 release out, but this is halted now because of problems in the reloading area. In which way did we break Fulcrum? Oliver Eric Pugh wrote: Folks, I have been really tied up in real life since before Christmas, but life has started calming down. I'll be looking at getting reinvolved again in the commons projects that are near and dear to my heart! For what it's worth, I am very excited about getting another rev of configuration out. (that and gump has been complaining about Fulcrum Configuration and the new API!). Eric -Original Message- From: robert burrell donkin [mailto:[EMAIL PROTECTED] Sent: Thursday, February 10, 2005 2:16 PM To: Jakarta Commons Developers List Subject: Re: [VOTE][configuration]Release 1.1 FWIW i've never regretted holding a release and i think the right decision's been made. - robert On Thu, 2005-02-10 at 19:43, Oliver Heger wrote: Of course, I don't want to force a release out which is not mature. Let's hold it. But I feel a bit disappointed that it seems to be so hard to get the required three +1s. I think we must be careful that we do not lose our momentum :-( Oliver Emmanuel Bourg wrote: I'm actually -1 for the release, I dropped the 1.1rc1 jar in my application yesterday and it broke with an exception related to the configuration reloading stuff. This may be linked to the issue reported by Jurgen Schlierf on the commons-user list. I'd like to investigate this bug before releasing the final 1.1. Emmanuel Bourg Oliver Heger wrote: Hi all, we need another +1 to get our release out. Nobody? Oliver Oliver Heger wrote: Dear community, since the 1.0 release of [configuration] a couple of new features have been added. The code base has been stable for a while now, so I think it is time to cut out a new 1.1 release before we start to implement further features and refactorings. A complete list of changes since the 1.0 releaes can be found here: http://jakarta.apache.org/commons/configuration/changes-report.html I have created a release candidate, which can be inspected at http://www.apache.org/~oheger/commons-configuration-1.1rc1/ (the tag for 1.1RC1 is named CONFIGURATION_1_1RC1). Here is my +1! Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dipl.-Inform. Oliver Heger Zentrale Informationsverarbeitung (ZIV) / Bereich Anwenderverfahren Klinikum der Philipps-Universität Marburg Baldingerstraße, D-35037 Marburg Tel: +49 6421 28-66923 mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][configuration]Release 1.1
Hi all, we need another +1 to get our release out. Nobody? Oliver Oliver Heger wrote: Dear community, since the 1.0 release of [configuration] a couple of new features have been added. The code base has been stable for a while now, so I think it is time to cut out a new 1.1 release before we start to implement further features and refactorings. A complete list of changes since the 1.0 releaes can be found here: http://jakarta.apache.org/commons/configuration/changes-report.html I have created a release candidate, which can be inspected at http://www.apache.org/~oheger/commons-configuration-1.1rc1/ (the tag for 1.1RC1 is named CONFIGURATION_1_1RC1). Here is my +1! Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][configuration]Release 1.1
I'm actually -1 for the release, I dropped the 1.1rc1 jar in my application yesterday and it broke with an exception related to the configuration reloading stuff. This may be linked to the issue reported by Jurgen Schlierf on the commons-user list. I'd like to investigate this bug before releasing the final 1.1. Emmanuel Bourg Oliver Heger wrote: Hi all, we need another +1 to get our release out. Nobody? Oliver Oliver Heger wrote: Dear community, since the 1.0 release of [configuration] a couple of new features have been added. The code base has been stable for a while now, so I think it is time to cut out a new 1.1 release before we start to implement further features and refactorings. A complete list of changes since the 1.0 releaes can be found here: http://jakarta.apache.org/commons/configuration/changes-report.html I have created a release candidate, which can be inspected at http://www.apache.org/~oheger/commons-configuration-1.1rc1/ (the tag for 1.1RC1 is named CONFIGURATION_1_1RC1). Here is my +1! Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][configuration]Release 1.1
Of course, I don't want to force a release out which is not mature. Let's hold it. But I feel a bit disappointed that it seems to be so hard to get the required three +1s. I think we must be careful that we do not lose our momentum :-( Oliver Emmanuel Bourg wrote: I'm actually -1 for the release, I dropped the 1.1rc1 jar in my application yesterday and it broke with an exception related to the configuration reloading stuff. This may be linked to the issue reported by Jurgen Schlierf on the commons-user list. I'd like to investigate this bug before releasing the final 1.1. Emmanuel Bourg Oliver Heger wrote: Hi all, we need another +1 to get our release out. Nobody? Oliver Oliver Heger wrote: Dear community, since the 1.0 release of [configuration] a couple of new features have been added. The code base has been stable for a while now, so I think it is time to cut out a new 1.1 release before we start to implement further features and refactorings. A complete list of changes since the 1.0 releaes can be found here: http://jakarta.apache.org/commons/configuration/changes-report.html I have created a release candidate, which can be inspected at http://www.apache.org/~oheger/commons-configuration-1.1rc1/ (the tag for 1.1RC1 is named CONFIGURATION_1_1RC1). Here is my +1! Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][configuration]Release 1.1
FWIW i've never regretted holding a release and i think the right decision's been made. - robert On Thu, 2005-02-10 at 19:43, Oliver Heger wrote: Of course, I don't want to force a release out which is not mature. Let's hold it. But I feel a bit disappointed that it seems to be so hard to get the required three +1s. I think we must be careful that we do not lose our momentum :-( Oliver Emmanuel Bourg wrote: I'm actually -1 for the release, I dropped the 1.1rc1 jar in my application yesterday and it broke with an exception related to the configuration reloading stuff. This may be linked to the issue reported by Jurgen Schlierf on the commons-user list. I'd like to investigate this bug before releasing the final 1.1. Emmanuel Bourg Oliver Heger wrote: Hi all, we need another +1 to get our release out. Nobody? Oliver Oliver Heger wrote: Dear community, since the 1.0 release of [configuration] a couple of new features have been added. The code base has been stable for a while now, so I think it is time to cut out a new 1.1 release before we start to implement further features and refactorings. A complete list of changes since the 1.0 releaes can be found here: http://jakarta.apache.org/commons/configuration/changes-report.html I have created a release candidate, which can be inspected at http://www.apache.org/~oheger/commons-configuration-1.1rc1/ (the tag for 1.1RC1 is named CONFIGURATION_1_1RC1). Here is my +1! Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][configuration]Release 1.1
+1 ! Emmanuel Bourg Oliver Heger wrote: Dear community, since the 1.0 release of [configuration] a couple of new features have been added. The code base has been stable for a while now, so I think it is time to cut out a new 1.1 release before we start to implement further features and refactorings. A complete list of changes since the 1.0 releaes can be found here: http://jakarta.apache.org/commons/configuration/changes-report.html I have created a release candidate, which can be inspected at http://www.apache.org/~oheger/commons-configuration-1.1rc1/ (the tag for 1.1RC1 is named CONFIGURATION_1_1RC1). Here is my +1! Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE][configuration]Release 1.1
Dear community, since the 1.0 release of [configuration] a couple of new features have been added. The code base has been stable for a while now, so I think it is time to cut out a new 1.1 release before we start to implement further features and refactorings. A complete list of changes since the 1.0 releaes can be found here: http://jakarta.apache.org/commons/configuration/changes-report.html I have created a release candidate, which can be inspected at http://www.apache.org/~oheger/commons-configuration-1.1rc1/ (the tag for 1.1RC1 is named CONFIGURATION_1_1RC1). Here is my +1! Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
