almeidajeff opened a new pull request, #4125: URL: https://github.com/apache/ambari/pull/4125
…conflicts in server assembly ## What changes were proposed in this pull request? This PR adds `<excludes>` to the ambari-server assembly descriptor (`ambari-server/src/main/assemblies/server.xml`) to prevent legacy JARs from being packaged. Specifically, it excludes: - `net.sf.ehcache: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`) - conflicts with Jersey 2.x - `javax.ws.rs:jsr311-api` (JAX-RS 1.x) - conflicts with JAX-RS 2.x These JARs are brought transitively by dependencies such as Hadoop and swagger-jaxrs. The exclusions eliminate the need for manual post-installation cleanup (e.g., removing `ehcache-2.10.4.jar` from the Dockerfile) and prevent runtime `ClassNotFoundException` and `NoSuchMethodError` issues caused by classpath conflicts. ## How was this patch tested? - Built ambari-server with `mvn -pl ambari-server -am -DskipTests package` - Verified that the excluded JARs are not present in the assembly output - Confirmed ambari-server starts correctly without the legacy JARs - Verified Ambari UI loads and API calls work normally - No `ClassNotFoundException` or `NoSuchMethodError` related to ehcache/Jersey/JAX-RS observed in logs Please review [Ambari Contributing Guide](https://cwiki.apache.org/confluence/display/AMBARI/How+to+Contribute) before opening a pull request. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
