>
> Jon Stevens wrote:
> >
> > If the above files do not exist, then attempt to look
> > for relative paths (ie: ../../jakarta-servletapi) to
> > the .jar files here:
> >
> > /jakarta-servletapi
> > /jsse*
> > /jmx*
>
> It is not clear to me why property files with reasonable defaults are
> "easy" whereas environment variables with the same defaults are "hard". It
> seems to me that the key discussion is what are reasonable defaults.
> Whatever.
Try fitting the current model of building Tomcat into relative paths and
you will see. It wasn't clear to me until I started hacking at it.
> More substantially, I'm troubled by thoses asterisks, and I have a similar
> problem with jakarta-servletapi. I routinely have multiple copies of
> various products on my system. One case in point is jakarta-servletapi as
> I routinely build both tomcat3 and tomcat4. To enable this, I have two
> copies of servletapi, one named jakarta-servletapi-4.0. Clearly this can
> be addressed via a properties file, I just want to be sure that the build
> system doesn't do me a "favor" by tossing in additional, randomly selected
> things into my path without warning.
Knowing where the problem is is key. In this case, I would propose that
the build for jakarta-servletapi is badly broken in that you can't
currently (by default) have multiple versions of it in your /build and
/dist directory at the same time.
I would say that the servlet api build process should be "fixed" to
build/install into directories with the version number attached.
/build/jakarta-tomcat-4.0
/build/jakarta-tomcat-3.2
/build/jakarta-ant-1.2
/build/jakarta-ant-1.3
/build/servletapi-2.2
/build/servletapi-2.3
/dist/servletapi-2.2
/dist/servletapi-2.3
/jakarta-tomcat-4.0
/jakarta-tomcat-3.2
/jakarta-ant-1.2
/jsse-1.0.1
This builds in the promise that things won't get confused.
Clarity: The first / is relative to whatever directory things are put
into, not your / on your disk.
-jon
--
Scarab -
Java Servlet Based - Open Source
Bug/Issue Tracking System
<http://scarab.tigris.org/>
