[jboss-jira] [JBoss JIRA] (DROOLS-514) Clean up jetty dependencies in kie-parent-with-dependencies pom.xml

[Geoffrey De Smet (JIRA)]

Geoffrey De Smet created DROOLS-514:
---------------------------------------

             Summary: Clean up jetty dependencies in kie-parent-with-dependencies pom.xml
                 Key: DROOLS-514
                 URL: https://issues.jboss.org/browse/DROOLS-514
             Project: Drools
          Issue Type: Task
      Security Level: Public (Everyone can see)
    Affects Versions: 6.1.0.Beta4
            Reporter: Geoffrey De Smet
            Assignee: Michael Biarnes Kiefer


1) Make an inventory (using "mvn-all dependency:tree) of all modules that use jetty dependency and clearly indicate:
- 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.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)