This would be really a funny thing, but how could we replace the classloader of a given application with a custom one? But what about a tool that decompiles all the product jars, changes the package structure and the import statements and repacks this into a new jar? ;-) Might be a megaseller...
Daniel > -----Urspr�ngliche Nachricht----- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Im Auftrag von Oliver Zeigermann > Gesendet: Donnerstag, 16. Dezember 2004 22:44 > An: Jakarta Commons Developers List > Betreff: Re: AW: [proposal] avoiding jar version nightmares > > 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- > version > > proposal is just one idea to enable this. > > Some versioning class loader as it was thought of in Projector would > really be a very elegant solution ;) > > Oliver > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
