Cleaning up Jetty - Removing 'unnecessaries' things

Question

I\'m used to use Jetty as my web container.

What I did on my install steps is get the original tar ball and cleanup some directories and files<

Answer 1

I'm not breaking any license right?

Correct.

Can I bring any drawback for my system (performance/stability) doing that?

The only drawback is that the Log4J properties file is useful for controlling how much (or how little) logging is performed. Disabling logging altogether results in smaller log files, conserving disk space. (Shouldn't be an issue with TB drives.) If the logging properties file cannot be found, an application might default to DEBUG or INFO levels, rather than ERROR levels. So, Log4J is useful to tell all applications to only log critical information.

Eliminating extraneous examples (the test suite) tightens security by exposing less system information. It can also save a bit of memory because the test webapps cannot get loaded into memory.

Does anyone customize more than this on jetty?

You can clean the webapps directory as follows:

cd /opt/jetty
rm -rf webapps
mkdir -p webapps/root
echo "" > webapps/root/index.html

Restart Jetty.