Sounds pretty good. However, I guess the problem is you can not change
the class loader implementation of WebSphere or other commercial stuff
:(
Oliver
On Fri, 17 Dec 2004 23:16:42 +, Chris Lambrou <[EMAIL PROTECTED]> wrote:
>
> > Correct me if I'm wrong, but didn't Microsoft come up with s
Correct me if I'm wrong, but didn't Microsoft come up with some type
of solution to DLL hell in Windows 2000 or XP? I seem to recall
reading that a long time ago, but I'm not a Windows programmer, so I
have no idea. Does anyone else know?
The .NET equivalent of a jar file is called an assemb
What happens if you merge the jars for each product? For example, put
commons 1.x files into productA.jar and commons 2.x files into
productB.jar.
David
--- Daniel Florey <[EMAIL PROTECTED]> wrote:
> So how should we handle situations where two versions of the same
> component
> need to coexist
Daniel Florey wrote:
> Any proposals how to solve this issue in another way?
Correct me if I'm wrong, but didn't Microsoft come up with some type of
solution to DLL hell in Windows 2000 or XP? I seem to recall reading
that a long time ago, but I'm not a Windows programmer, so I have no
idea. D
Packages look like
com.some_domain.org.apache.xerces...
gg
-Original Message-
From: Oliver Zeigermann [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 16, 2004 1:44 PM
To: Jakarta Commons Developers List
Subject: Re: AW: [proposal] avoiding jar version nightmares
On Thu, 16 Dec 2004
On Thu, 16 Dec 2004 19:09:54 +0100, Daniel Florey <[EMAIL PROTECTED]> wrote:
> So I think we need a solution for this problem. My proposal would be to
> allow different major versions of commons components to coexist. If the
> class and package names are equal, this is not possible. My package-vers
