1) Make an inventory (using "mvn-all dependency:tree) of all modules that use jetty dependency and clearly indicate per module:

• Jetty groupId and Jetty version
• Scope: test or production
• Build classpath: normal dependency or plugin dependency (latter makes scope n/a)

2) In theory, we should have no normal dependency in a non-test scope to Jetty, as our stuff is deployed on JBoss EAP, Tomcat, Jetty and WildFly alike. Is this true?
GWT does use Jetty, but only during compilation (= plugin classpath, not the dependencies classpath). gwt-dev is a fat jar that includes jetty even... but gwt-dev shouldn' be in the dependencies either (but it is and it needs to be removed!).

3) Based on this inventory, discuss with ge0ffrey and mantis plan of attack.

Goal: Get rid of the jetty mess in kie-parent-with-dependencies.