diff options
| author | gjoranv <gv@verizonmedia.com> | 2021-05-01 17:47:56 +0200 |
|---|---|---|
| committer | gjoranv <gv@verizonmedia.com> | 2021-05-01 23:46:23 +0200 |
| commit | 97801ce0bf8921478d65e389b75adb245af63f7d (patch) | |
| tree | 3077ba0e1d28ff32e0b9d0ef8b63456a6959bf9a /container-dev | |
| parent | e3ba7773401be957ea99f65d5108608e61a34763 (diff) | |
Exclude jakarta artifacts that conflict or overlap
.. with jaxb/javax artifacts. The jakarta bind-api artifact makes
user projects that include vespa-http-client-extensions import
its version of javax.xml.bind (2.3.2), rather than the version
exported from jdisc (2.3).
- Note that, contrary to logic, we must also exclude it from
container-test to avoid user projects from getting it in scope
provided instead of (the correct) test scope.
Diffstat (limited to 'container-dev')
| -rw-r--r-- | container-dev/pom.xml | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/container-dev/pom.xml b/container-dev/pom.xml index cfe9c0a6d8e..06c68b52e67 100644 --- a/container-dev/pom.xml +++ b/container-dev/pom.xml @@ -104,6 +104,18 @@ <artifactId>vespa_jersey2</artifactId> <version>${project.version}</version> <type>pom</type> + <exclusions> + <exclusion> + <!-- Conflicts with javax.xml.bind:jaxb-api:2.3, which is "exported" via jdisc_core.--> + <groupId>jakarta.xml.bind</groupId> + <artifactId>jakarta.xml.bind-api</artifactId> + </exclusion> + <exclusion> + <!-- Conflicts with javax.activation:javax.activation-api:1.2.0, which is "exported" via jdisc_core. --> + <groupId>jakarta.activation</groupId> + <artifactId>jakarta.activation-api</artifactId> + </exclusion> + </exclusions> </dependency> <dependency> <groupId>com.yahoo.vespa</groupId> |