I think Daniel is right. This would not change anything. I am not quite sure the problem is yet obvious to anyone: The *same* classloader must return two *different* versions of the *same* class for different parts of your software which seems impossible for an ordinary class loader unless the classes are in a different package. That's why Daniel proposes to put imcompible class versions in different packages.
Any better solution? Oliver On Fri, 17 Dec 2004 22:12:41 +0100, Daniel Florey <[EMAIL PROTECTED]> wrote: > Don't know. But I think the classloader will still not know which class to > pick as the names are still identical. So it might depend on the load order > of the jars which product will fail. > Or did I got it wrong? > > Daniel > > > -----Ursprüngliche Nachricht----- > > Von: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] > > Im Auftrag von David Graham > > Gesendet: Freitag, 17. Dezember 2004 21:33 > > An: Jakarta Commons Developers List > > Betreff: Re: AW: [proposal] avoiding jar version nightmares > > > > 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
