Remove Project Object Model Files from Coherence-HTTP-* Jars (Doc ID 2749133.1)

Last updated on FEBRUARY 16, 2023

Applies to:

Goal

The maven sync plugin uploads the jar artifact with the relevant pom file to
the artifactory instance specified. The pom files *should not* be in the jar
files for the libraries we ship, hence there is a bug in those libraries that
contain the pom file.
 

Looking 12.2.1.4.7 these modules have the issue:
 

(coherence/lib)$ for f in `ls coherence*.jar`; do jar tvf $f | grep
"pom\.xml"; done

  7305 Wed Nov 11 00:30:52 EST 2020
META-INF/maven/com.oracle.coherence/coherence-http-grizzly/pom.xml

  7397 Wed Nov 11 00:30:52 EST 2020
META-INF/maven/com.oracle.coherence/coherence-http-jetty/pom.xml

  6996 Wed Nov 11 00:30:52 EST 2020
META-INF/maven/com.oracle.coherence/coherence-http-netty/pom.xml

  6967 Wed Nov 11 00:30:52 EST 2020
META-INF/maven/com.oracle.coherence/coherence-http-simple/pom.xml
 

Hopefully, if you use the oracle maven sync plugin it will ignore those
embedded pom files. Admittedly, its odd having a discrepancy between the
embedded pom file and the advertised pom file but should be fix that in a bug.
 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.