citrusframework / citrusframework/citrus
Dependency clash between citrus-http and citrus-remote-server
- Dominant language
- Java
- Stars
- 485
- Forks
- 155
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 6
Description
**Citrus Version**
2.8.0
**Expected behavior**
When I use `citrus-http` in combination with the `citrus-remote-server`, the tests should be executed.
**Actual behavior**
When I use `citrus-http` in combination with the `citrus-remote-server`, the tests are not executed due to a dependency clash between both dependencies.
**Workaround**
As a workaround, it is possible to exclude the `jetty-server` from the `citrus-remote-server` dependency.
```xml
com.consol.citrus
citrus-remote-server
org.eclipse.jetty
jetty-server
```
**Suggested solution**
Ensure that the `jetty-server` of the `citrus-http` module is the same as the transitive `jetty-server` dependency of `com.sparkjava.spark-core`
Contributor guide
Research direction
Inspect the Maven dependency declarations for citrus-http and citrus-remote-server, then compare their jetty-server versions with the transitive dependency from com.sparkjava.spark-core. Confirm the dependency versions are compatible and verify that tests execute without the documented jetty-server exclusion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100