Hi,

I've been looking at the makebase script and thinking about potential
use cases.

Currently, we copy conf recursively but create an empty webapps. This is
inconsistent as any directories under conf will (nearly always) be web
application specific config.

I think we should either copy web applications and config or not copy both.

My suggestion is not to copy web applications and config (i.e. sub dirs
of /conf) by default and to add a -webapps option (or similar) to the
makebase script and only copy them when the option is present.

Thoughts?

I've been trying to think of other use cases and all the ones I can come
up with are either covered by what we have (with the above) or are
getting into the realm of editing config files which is - I think -
further than we want to go.

Can anyone think of any other options we might want to consider?

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to