Bug #3777
closed
Move Tomcat libraries into metacat build
Added by Michael Daigle almost 16 years ago.
Updated almost 15 years ago.
Description
Right now, the Tomcat libraries (javax.http...) are referenced via the Tomcat install directory on the build machine. These libs should be included in metacat code for build purposes (not for distribution).
We used to include those libs back in the Tomcat 3 days, but took them out as
the servlet library jars changed in Tomcat 3, 4, 5, and 6. So now we use the
locally installed version of the jar that comes with Tomcat to build. We
should consider whether adding these jars to Metacat is really an advantage --
we have to have Tomcat, and we have to differentiate which version of Tomcat is
being used in order to find the right jar file for servlet support. Having
those be in Metacat may not gain us much, and we'd have to differentiate which
to use in any given build. I'd opt for improving the build logic to discover
the jar files in the locally installed Tomcat. And I agree with Duane -- it
would be nice if the default app.deploy.dir used the standard webapps location,
as that is where most people will want to put it. So, I vote for changing back
to:
app.deploy.dir=${build.tomcat.dir}/webapps
Then if we need a different location in our particular install we can change it
as needed when we build and install locally. But the default should be the
standard webapps location.
Review comments on ticket 3824
This is not practical. The server should reference the libraries of the native install.
Original Bugzilla ID was 3777
Also available in: Atom
PDF