[nightly build] dbcp failed.
Failed build logs: http://vmbuild.apache.org/~commons/nightly/logs//20070506/dbcp.log - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [all] Going TLP?
On 5/1/07, Henri Yandell [EMAIL PROTECTED] wrote: On 5/1/07, Jochen Wiedmann [EMAIL PROTECTED] wrote: On 5/2/07, Henri Yandell [EMAIL PROTECTED] wrote: (http://wiki.apache.org/jakarta-commons/TLPResolution) and secondly, anyone want to volunteer to chair things? As you are one of the most active persons here and also the one who is pushing this forward: How about yourself? :-) A bunch of projects do a one year term, which I think is probably a very healthy thing. I'm happy to do the chair bit if no one else wants to, but I'll happily support anyone if they're interested. No one interested in volunteering as Commons chair? Otherwise I'll go ahead and kick off a vote on Monday on [EMAIL PROTECTED] Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (CONFIGURATION-268) XMLConfiguration does not fully support disabled delimiter parsing
XMLConfiguration does not fully support disabled delimiter parsing -- Key: CONFIGURATION-268 URL: https://issues.apache.org/jira/browse/CONFIGURATION-268 Project: Commons Configuration Issue Type: Bug Affects Versions: 1.4 Reporter: Oliver Heger Assigned To: Oliver Heger Fix For: 1.5 A call to setDelimiterParsingDisabled(true) should completely turn off the mechanism for searching for list delimiters and splitting property values. However XMLConfiguration.save() escapes list delimiters even in this mode. When later such a configuration file is loaded and delimiter parsing is turned off, the values of affected properties will contain the escape character. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (CONFIGURATION-268) XMLConfiguration does not fully support disabled delimiter parsing
[ https://issues.apache.org/jira/browse/CONFIGURATION-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493945 ] Oliver Heger commented on CONFIGURATION-268: Attributes are also affected, but here the situation is more complicated: We support multiple values for a single attribute, so somebody could do something like this: XMLConfiguration conf = new XMLConfiguration(); conf.setDelimiterParsingDisabled(true); conf.addProperty([EMAIL PROTECTED], 1,2,3); conf.addProperty([EMAIL PROTECTED], 4,5,6); If such a configuration is saved, our current implementation will produce the following element: test attr=1\,2\,3,4\,5\,6/ If this element is loaded when delimiter parsing is disabled, an attribute with two values is created, but the values contain the escaping character. (Note that this is not a problem when delimiters are enabled.) I think if delimiter parsing is disabled, attribute values should be read as they are without doing any modifications like removing escape characters. They may be part of the real attribute value. But because XML does not allow multiple occurrences of a single attribute, we always need a delimiter character for representing multiple attribute values. Now when loading a configuration file and delimiter parsing is disabled, deciding whether a delimiter character is used is not trivial. What we could do is using an untypical delimiter character, e.g. the pipe. Then the example element would look like test attr=1,2,3|4,5,6/ If an attribute value contained this delimiter character, it would have to be escaped. But we still cannot be 100% sure whether the user in deed wants to define an attribute with the single value 1,2,3\|4,5,6. XMLConfiguration does not fully support disabled delimiter parsing -- Key: CONFIGURATION-268 URL: https://issues.apache.org/jira/browse/CONFIGURATION-268 Project: Commons Configuration Issue Type: Bug Affects Versions: 1.4 Reporter: Oliver Heger Assigned To: Oliver Heger Fix For: 1.5 A call to setDelimiterParsingDisabled(true) should completely turn off the mechanism for searching for list delimiters and splitting property values. However XMLConfiguration.save() escapes list delimiters even in this mode. When later such a configuration file is loaded and delimiter parsing is turned off, the values of affected properties will contain the escape character. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [all] Going TLP?
On 06.05.2007, at 19:51, Henri Yandell wrote: On 5/1/07, Henri Yandell [EMAIL PROTECTED] wrote: On 5/1/07, Jochen Wiedmann [EMAIL PROTECTED] wrote: On 5/2/07, Henri Yandell [EMAIL PROTECTED] wrote: (http://wiki.apache.org/jakarta-commons/TLPResolution) and secondly, anyone want to volunteer to chair things? As you are one of the most active persons here and also the one who is pushing this forward: How about yourself? :-) A bunch of projects do a one year term, which I think is probably a very healthy thing. I'm happy to do the chair bit if no one else wants to, but I'll happily support anyone if they're interested. No one interested in volunteering as Commons chair? I would also do it (How come I am not in the list? Did I miss the call?) cheers -- Torsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [all] Going TLP?
On 5/6/07, Torsten Curdt [EMAIL PROTECTED] wrote: On 06.05.2007, at 19:51, Henri Yandell wrote: On 5/1/07, Henri Yandell [EMAIL PROTECTED] wrote: On 5/1/07, Jochen Wiedmann [EMAIL PROTECTED] wrote: On 5/2/07, Henri Yandell [EMAIL PROTECTED] wrote: (http://wiki.apache.org/jakarta-commons/TLPResolution) and secondly, anyone want to volunteer to chair things? As you are one of the most active persons here and also the one who is pushing this forward: How about yourself? :-) A bunch of projects do a one year term, which I think is probably a very healthy thing. I'm happy to do the chair bit if no one else wants to, but I'll happily support anyone if they're interested. No one interested in volunteering as Commons chair? I would also do it You've got my +1 :) (How come I am not in the list? Did I miss the call?) Yep. Though when I do the vote on general I'll include a Please add your name to the list if you're a commons developer and not listed yet. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-commons Wiki] Update of TLPResolution by MartinCooper
Dear Wiki user, You have subscribed to a wiki page or wiki category on Jakarta-commons Wiki for change notification. The following page has been changed by MartinCooper: http://wiki.apache.org/jakarta-commons/TLPResolution The comment on the change is: Add myself -- * Jörg Schaible[EMAIL PROTECTED] * Oliver Heger [EMAIL PROTECTED] * Matt Benson [EMAIL PROTECTED] + * Martin Cooper[EMAIL PROTECTED] NOW, THEREFORE, BE IT FURTHER RESOLVED, that XXX be appointed to the office of Vice President, Commons, to serve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
