cvs commit: jakarta-commons/collections/src/java/org/apache/commons/collections DualHashBidiMap.java AbstractDualBidiMap.java BidiMap.java HashBidiMap.java

scolebourne2003/10/06 16:47:17 Modified:collections/src/test/org/apache/commons/collections TestBidiMap.java TestAll.java collections/src/java/org/apache/commons/collections BidiMap.java Added: collections/src/test/or

cvs commit: jakarta-commons/collections/src/test/org/apache/commons/collections AbstractTestSortedMap.java

scolebourne2003/10/06 16:44:56 Modified:collections/src/test/org/apache/commons/collections AbstractTestSortedMap.java Log: Add first semblance of some SortedMap tests Revision ChangesPath 1.2 +26 -3 jakarta-commons/collections/src/test/

cvs commit: jakarta-commons/collections/src/test/org/apache/commons/collections/decorators TestTransformedSortedMap.java

scolebourne2003/10/06 16:44:23 Modified:collections/src/test/org/apache/commons/collections/decorators TestTransformedSortedMap.java Log: Actually test the class we are supposed to be testing Revision ChangesPath 1.4 +15 -9 jakarta-commo

Re: [codec] should we release a version 1.2 now?

I think 1.2 sounds better as well. URLCodec is also new in this release. Mike On Monday, October 6, 2003, at 03:05 PM, Gary Gregory wrote: A 1.1.1 release seems no longer appropriate since DigestUtils is a new feature; should we wrap up a 1.2 now? It feels like we had been planning a 1.1.1 for

Re: [digester][patch] xml schema support. removal

Simon Kitching wrote: On Tue, 2003-10-07 at 03:09, Jean-Francois Arcand wrote: Simon Kitching wrote: On Sun, 2003-10-05 at 07:26, Jean-Francois Arcand wrote: Doesn't it really suck that there is no parser-independent way of enabling w3c-standard xml schema support? Is everybody absolut

cvs commit: jakarta-commons-sandbox/hivemind/xdocs interceptors.xml

hlship 2003/10/06 14:27:19 Modified:hivemind/xdocs interceptors.xml Log: Simplify the initial interceptor example. Revision ChangesPath 1.9 +12 -14jakarta-commons-sandbox/hivemind/xdocs/interceptors.xml Index: interceptors.xml ===

Re: [digester][patch] xml schema support. removal

On Tue, 2003-10-07 at 03:09, Jean-Francois Arcand wrote: > Simon Kitching wrote: > > >On Sun, 2003-10-05 at 07:26, Jean-Francois Arcand wrote: > > > >Doesn't it really suck that there is no parser-independent way of > >enabling w3c-standard xml schema support? Is everybody absolutely sure > >ther

Re: [Collections][Gump] Test failures

I've fixed some tests that I broke last night. But I wasn't seeing these messages, so you may need to report back if you still have problems. Stephen - Original Message - From: "Stefan Bodewig" <[EMAIL PROTECTED]> > Hi, > > as Sam's nagging mechanism doesn't work yet - here's a report from

cvs commit: jakarta-commons/collections/data/test CommonsLinkedList.fullCollection.version3.obj BooleanComparator.version3.obj NodeCachingLinkedList.emptyCollection.version3.obj NodeCachingLinkedList.fullCollection.version3.obj CommonsLinkedList.emptyCollection.version3.obj

scolebourne2003/10/06 14:03:52 Added: collections/data/test CommonsLinkedList.fullCollection.version3.obj BooleanComparator.version3.obj NodeCachingLinkedList.emptyCollection.version3.obj No

cvs commit: jakarta-commons/collections/src/test/org/apache/commons/collections/comparators TestBooleanComparator.java

scolebourne2003/10/06 14:02:50 Modified:collections/src/test/org/apache/commons/collections TestNodeCachingLinkedList.java TestCommonsLinkedList.java collections/src/test/org/apache/commons/collections/comparators

[bugzilla] Use [component name] in title and email subject

Hello, Could we make bugzilla add the component name used in email subjects? Or at least have a convention to manually add components to titles? Seeing a header like: "DO NOT REPLY [Bug 23620] New: - Tweak the fix-bang" forces me to look at the message where: "DO NOT REPLY [Bug 23620] New:

[codec] should we release a version 1.2 now?

A 1.1.1 release seems no longer appropriate since DigestUtils is a new feature; should we wrap up a 1.2 now? It feels like we had been planning a 1.1.1 for quite some time to capture some bug fixes. Gary

cvs commit: jakarta-commons-sandbox/hivemind/framework/src/java/org/apache/commons/hivemind/impl ProxyBuilder.java

hlship 2003/10/06 11:24:55 Modified:hivemind/framework/src/java/org/apache/commons/hivemind/impl ProxyBuilder.java Log: Make ProxyBuilder's constructor public. Revision ChangesPath 1.3 +8 -2 jakarta-commons-sandbox/hivemind/framework/s

[jira] Commented: (JELLY-90) SecurityException when using Jelly in applet or JAWS sandbox

The following comment has been added to this issue: Author: Paul Libbrecht Created: Mon, 6 Oct 2003 1:33 PM Body: May I add, that, indeed, there seems to be a principle at several places of the jelly code to ignore security exceptions (James has made comments on that). It would be

DO NOT REPLY [Bug 23558] - Problem with BeanUtils.setProperty when the name of property of Bean have on second caracter a uppercase

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 21618] - MappedPropertyDescriptor requires more permissions than necessary

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: Bug and patch for NodeCachingLinkedList

Thanks for taking care of this! Seems to work great now. David -Original Message- From: Phil Steitz [mailto:[EMAIL PROTECTED] Sent: Sunday, October 05, 2003 1:03 AM To: Jakarta Commons Developers List Subject: Re: Bug and patch for NodeCachingLinkedList Should be fixed now in CVS, in

[jira] Created: (JELLY-90) SecurityException when using Jelly in applet or JAWS sandbox

Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=JELLY-90 Here is an overview of the issue: ---

DO NOT REPLY [Bug 23491] - Can't configure PerUserPoolDataSource for use with tomcat

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 23620] - Support for Portlets (168)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 23620] - Support for Portlets (168)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 23620] - Support for Portlets (168)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 23620] New: - Support for Portlets (168)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: [digester][patch] xml schema support. removal

Simon Kitching wrote: On Sun, 2003-10-05 at 07:26, Jean-Francois Arcand wrote: Hi Robert, robert burrell donkin wrote: hi Jean-Francois i'm very reluctant to apply a patch that breaks backwards compatibility but i'd be happier to deprecate them. That was my initial response t

Re: [digester][patch] xml schema support. removal

robert burrell donkin wrote: On Saturday, October 4, 2003, at 07:26 PM, Jean-Francois Arcand wrote: Hi Robert, robert burrell donkin wrote: hi Jean-Francois the current code could then be factored out allow schema support for xerces 2.1. the new code you posted could form the basis of an

[Collections][Gump] Test failures

Hi, as Sam's nagging mechanism doesn't work yet - here's a report from my last nightly builds: Stefan [java] There were 9 errors: [java] 1) testSerializeDeserializeThenCompare(TestBeanMap.bulkTestMapEntrySet.testSerializeDeserializeThenCompare) java.io.NotSerializableException: org.a

DO NOT REPLY [Bug 20813] - FileUpload does not take 'charset' parameter of the 'Content-Type' header into consideration

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

[HiveMind] more on BuilderFactory

Hi, I had a few more ideas on how BuilderFactory can be improved. These improvements mainly address the usage and extensibility of the service. Right now the BuilderFactory is very flexible, but this comes at a cost: the syntax is fairly complicated: there are four attributes and 17 different nes

Re: [general] Maven-generated pages don't point to mailing list page

I am somewhat confused now. What is the genral guideline? Tetsuya Kitahata wrote: Please use http://jakarta.apache.org/site/mail2.html#commons instead of http://jakarta.apache.org/site/mail.html Regards, -- Tetsuya. ([EMAIL PROTECTED]) On Thu, 02 Oct 2003 13:58:09 -0400 (Subject: [general] Ma