[
https://issues.jboss.org/browse/DROOLS-514?page=com.atlassian.jira.plugin...
]
Michael Biarnes Kiefer edited comment on DROOLS-514 at 1/10/17 6:09 AM:
------------------------------------------------------------------------
Looking which modules use jetty: (kie 7.0.0-SNAPSHOT - master branch)..:
*droolsjbpm-build-bootstrap/pom.xm*l..:
<version.org.mortbay.jetty.runner>8.1.7.v20120910</version.org.mortbay.jetty.runner>
<dependency>
<groupId>org.mortbay.jetty</groupId>
<artifactId>jetty-runner</artifactId>
<version>${version.org.mortbay.jetty.runner}</version>
</dependency>
<dependency>
<groupId>org.eclipse.jetty</groupId>
<artifactId>jetty-proxy</artifactId>
<version>${version.org.eclipse.jetty}</version>
</dependency>
The version:
<version.org.eclipse.jetty>9.2.14.v20151106</version.org.eclipse.jetty> is
coming from jboss-ip-bom 7.0.0.CR6.
I removed org.eclipse.jetty:jetty-proxy:${version.org.eclipse.jetty} from
droolsjbpm-build-bootstrap/pom.xml as this is defined in jboss-ip-bom.
I also found jetty dependencies and imports in these modules: but all of them are
<scope>test</scope>
droolsjbpm-integration/kie-server-parent/kie-server-common/pom.xml
droolsjbpm-integration/kie-server-parent/kie-server-common/src/test/java/org/kie/server/common/rest/KieServerHttpRequestTest.java..:
droolsjbpm-integration/kie-server-parent/kie-server-common/src/test/java/org/kie/server/common/rest/ServerTestCase.java..:
Attached you will find the dependency-tree with jetty dependencies.
was (Author: mbiarnes):
Looking which modules use jetty: (kie 7.0.0-SNAPSHOT - master branch)..:
*droolsjbpm-build-bootstrap/pom.xm*l..:
<version.org.mortbay.jetty.runner>8.1.7.v20120910</version.org.mortbay.jetty.runner>
<dependency>
<groupId>org.mortbay.jetty</groupId>
<artifactId>jetty-runner</artifactId>
<version>${version.org.mortbay.jetty.runner}</version>
</dependency>
<dependency>
<groupId>org.eclipse.jetty</groupId>
<artifactId>jetty-proxy</artifactId>
<version>${version.org.eclipse.jetty}</version>
</dependency>
The version:
<version.org.eclipse.jetty>9.2.14.v20151106</version.org.eclipse.jetty> is
coming from jboss-ip-bom 7.0.0.CR6.
I removed org.eclipse.jetty:jetty-proxy:${version.org.eclipse.jetty} from
droolsjbpm-build-bootstrap/pom.xml as this is defined in jboss-ip-bom.
I also found jetty dependencies and imports in these modules: but all of them are
<scope>test</scope>
droolsjbpm-integration/kie-server-parent/kie-server-common/pom.xml
droolsjbpm-integration/kie-server-parent/kie-server-common/src/test/java/org/kie/server/common/rest/KieServerHttpRequestTest.java..:
droolsjbpm-integration/kie-server-parent/kie-server-common/src/test/java/org/kie/server/common/rest/ServerTestCase.java..:
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
Affects Versions: 6.1.0.Beta4
Reporter: Geoffrey De Smet
Assignee: Michael Biarnes Kiefer
Attachments: jetty-depTree.txt
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.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)