[
https://issues.apache.org/jira/browse/AMBARI-26597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18076039#comment-18076039
]
Jefferson Almeida commented on AMBARI-26597:
--------------------------------------------
I have opened a pull request to address this issue by excluding the legacy JARs
from the ambari-server assembly descriptor. The PR adds `<excludes>` to prevent
ehcache 2.x, Jersey 1.x, and JAX-RS 1.x JARs (which are brought transitively by
dependencies like Hadoop and swagger-jaxrs) from being packaged, eliminating
the need for manual post-installation cleanup and preventing runtime classpath
conflicts.
Pull Request: [https://github.com/apache/ambari/pull/4125|http://example.com/]
> Exclude legacy JARs (ehcache 2.x, Jersey 1.x, JAX-RS 1.x) from ambari-server
> assembly to prevent runtime conflicts
> ------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-26597
> URL: https://issues.apache.org/jira/browse/AMBARI-26597
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 3.0.0
> Environment: Docker, RHEL 9, or the environment where you tested
> Reporter: Jefferson Almeida
> Priority: Major
>
> The ambari-server assembly includes legacy JARs transitively brought by
> dependencies that conflict with the versions currently used by Ambari at
> runtime:
> * {{net.sf.ehcache:ehcache}} (2.x) conflicts with ehcache 3.x used by Ambari
> * Jersey 1.x JARs ({{{}jersey-core{}}}, {{{}jersey-server{}}},
> {{{}jersey-json{}}}, {{{}jersey-servlet{}}}, {{{}jersey-client{}}}) conflict
> with Jersey 2.x
> * {{javax.ws.rs:jsr311-api}} (JAX-RS 1.x) conflicts with JAX-RS 2.x
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
