I decided to simply put the shared lib jar file into folder "<SMX>/lib/optional" and each SU which needs the lib just has the dependency defined with <scope>provided</scope>. This will prevent each SU which uses this shared lib to ship with the shared lib which will save you a lot of space depending on your use case.
Until now I can't see any backdraws doing so. Regards Lars Am Freitag 15 August 2008 13:49:03 schrieb Anderson Nielson: > I am facing the same problem. A good question: when and how to use a shared > library or not? > > Best Regards > > pratibhaG wrote: > > I have created a jar using maven and added a dependency as you said. Now > > everything works fine. > > If I use this as an alternative to shared library what harm do you see in > > it? Can I use it? > > > > What am I missing while using shred library? > > > > Pratibha
