Larsen Keeping more than one version of the same package and class will cause excessive Administrative work Maven Build Environments will allow you to deploy a specific package/class and version to a profile maven allows you to compile/install and deploy the same package/class with a different version for Development, QA and Production profiles
http://maven.apache.org Martin Gainty ______________________________________________ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > Date: Sun, 4 Oct 2009 13:02:39 +0200 > Subject: Re: Loading Jar files in a particular order on Tomcat 6 > From: kolibria...@gmail.com > To: users@tomcat.apache.org > > 2009/10/4 Leon Rosenberg <rosenberg.l...@googlemail.com>: > > On Sun, Oct 4, 2009 at 1:00 AM, Eric B. <ebe...@hotmail.com> wrote: > >> "Caldarale, Charles R" <chuck.caldar...@unisys.com> wrote in message > > Back to the original post, > > why don't you simply patch (maybe automatically with ant) the jar file > > containing the 'old' version of the class and remove it? > > The jar files are provided and signed by an external vendor. > > > You won't be able to keep two different versions of a class in the > > same classloader anyway. > > I want to use the newest version only, of course. Normally, I would > simply place the jar with the newest versions first in the classpath. > But the tomcat server has no such control, instead it just loads jar > files from the WEB-INF/lib directory, which means that the order is > based on the OS filesystem. > > Apparently, there is no easy way to control the classpath for web > applications in Tomcat, so instead I have to make a custom classloader > that does loads classes from the jar files in a controlled order. > > - Rasmus > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > _________________________________________________________________ Hotmail: Powerful Free email with security by Microsoft. http://clk.atdmt.com/GBL/go/171222986/direct/01/
