Craig R. McClanahan wrote:
Subscribers to COMMONS-DEV will see that I'm proposing to remove the dependency
on [collections] from both [beanutils] and [digester]. Both dependencies are
very thin, and doing this will avoid penalizing [beanutils]/[digester]
customers for what [collections] did.
Costin Manolache wrote:
Craig R. McClanahan wrote:
Subscribers to COMMONS-DEV will see that I'm proposing to remove the
dependency
on [collections] from both [beanutils] and [digester]. Both
dependencies are
very thin, and doing this will avoid penalizing [beanutils]/[digester]
customers for
Remy Maucherat wrote:
Costin Manolache wrote:
If I remember correctly ( and if it didn't change ), tomcat needs
modeler in a parent classloader. Modeler has an optional dependency on
digester, which depends on beanutils and collections. They both depend
on logging, and modeler also depends on
-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Costin Manolache
Sent: Monday, February 02, 2004 2:04 AM
To: [EMAIL PROTECTED]
Subject: Re: Jakarta Collections 3.0?
Remy Maucherat wrote:
Costin Manolache wrote:
If I remember correctly ( and if it didn't change ), tomcat needs
modeler
Quoting Costin Manolache [EMAIL PROTECTED]:
If I remember correctly ( and if it didn't change ), tomcat needs
modeler in a parent classloader. Modeler has an optional dependency on
digester, which depends on beanutils and collections. They both depend
on logging, and modeler also depends
wrote:
Jess Holle wrote:
Can anyone shed any light on the plans for Tomcat using Jakarta
Collections 3.0?
I ask as we currently bundle Jakarta Collections for use in and out
of the servlet engine. We wish to use a consistent version
throughout. Given that Tomcat bundles Jakarta Collections
Costin Manolache wrote:
If I remember correctly ( and if it didn't change ), tomcat needs
modeler in a parent classloader. Modeler has an optional dependency on
digester, which depends on beanutils and collections. They both depend
on logging, and modeler also depends on jmx.
So unless some
Can anyone shed any light on the plans for Tomcat using Jakarta
Collections 3.0?
I ask as we currently bundle Jakarta Collections for use in and out of
the servlet engine. We wish to use a consistent version throughout.
Given that Tomcat bundles Jakarta Collections within its common/lib
Jess Holle wrote:
Can anyone shed any light on the plans for Tomcat using Jakarta
Collections 3.0?
I ask as we currently bundle Jakarta Collections for use in and out of
the servlet engine. We wish to use a consistent version throughout.
Given that Tomcat bundles Jakarta Collections within
Remy Maucherat wrote:
Jess Holle wrote:
Can anyone shed any light on the plans for Tomcat using Jakarta
Collections 3.0?
I ask as we currently bundle Jakarta Collections for use in and out
of the servlet engine. We wish to use a consistent version
throughout. Given that Tomcat bundles
: Thursday, January 29, 2004 11:35 AM
To: Tomcat Developers List
Subject: Re: Jakarta Collections 3.0?
Remy Maucherat wrote:
Jess Holle wrote:
Can anyone shed any light on the plans for Tomcat using Jakarta
Collections 3.0?
I ask as we currently bundle Jakarta Collections for use in and out
Shapira, Yoav wrote:
Howdy,
You know, tomcat only uses one class (LRUMap), whose implementation
wasn't really changed in the 3.0 release, only the package name. So
this is a trivial patch...
Well, digester and beanutils use more of collections, so it's more
complex that that :/
Rémy
Shapira
Millennium ChemInformatics
-Original Message-
From: Jess Holle [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 29, 2004 11:19 AM
To: Tomcat Developers List
Subject: Jakarta Collections 3.0?
Can anyone shed any light on the plans for Tomcat using Jakarta
Collections 3.0?
I ask
Howdy,
Well, digester and beanutils use more of collections, so it's more
complex that that :/
I'll take a deeper look to see what's involved ;)
Yoav Shapira
This e-mail, including any attachments, is a confidential business communication, and
may contain information that is confidential,
14 matches
Mail list logo
