This is in the pom.xml's dependency sections of the SU which uses the shared lib.
For example: <dependency> <groupId>my.group.id</groupId> <artifactId>my-shared-lib</artifactId> <version>1.0</version> <scope>provided</scope> </dependency> Regards Lars Am Freitag 15 August 2008 14:35:53 schrieb Anderson Nielson: > Lars, > > Where did you puts this <scope>provided</scope> tag? > Which file? > > Thank you > > lhe77 wrote: > > 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
