| Best strategy to have jars deploy into WEB-INF/lib? [message #207902] |
Sat, 02 February 2008 10:57  |
Eclipse User |
|
|
|
I'm trying to figure out the best strategies and options for ensuring that
jars in my build path get deployed into WEB-INF/lib. I have jars in my
build path, but except for my JSF jars, nothing else automatically goes
into WEB-INF/lib.
I found that the only way to get this to happen is to manually (outside of
Eclipse) copy those jars into WebContext/WEB-INF/lib. I find it hard to
believe that's the correct way to do it.
I searched this newsgroup and I found conversations on this over 2 years
ago. I saw references to manually editing some obscure XML files to force
those jars to deploy.
Am I missing something?
|
|
|
|
|
| Re: Best strategy to have jars deploy into WEB-INF/lib? [message #207933 is a reply to message #207926] |
Sat, 02 February 2008 20:39  |
| Eclipse User |
|
|
|
Originally posted by: dcarver.starstandard.org
David Karr wrote:
> Actually, it looks like when I add a User Library to my build path, that
> also becomes one of the available choices in the J2EE Module
> Dependencies table, which when checked, will deploy itself to
> WEB-INF/lib. I had thought that before, but it had seemed like some
> user libraries didn't make it in there, but I don't see that now.
>
> Jars like this make more sense as User Libraries as opposed to separate
> projects.
Yeah, that will work as well.
Dave
|
|
|
Powered by
FUDForum. Page generated in 0.04843 seconds
Home