Kristin Cowalcijk created SEDONA-284:
----------------------------------------
Summary: Property values in dependency deduced POMs for shaded
modules were not substituted
Key: SEDONA-284
URL: https://issues.apache.org/jira/browse/SEDONA-284
Project: Apache Sedona
Issue Type: Bug
Reporter: Kristin Cowalcijk
Fix For: 1.4.1
The deployed POMs of {{sedona-spark-shaded}} and {{flink-shaded}} were
{{dependency-reduced-pom.xml}} generated by maven-shade-plugin. The generated
POMs does not have their property values substituted. For example, the
artifactId in the deployed POM of sedona-spark-shaded should be
{{{}sedona-spark-shaded-3.0_2.12{}}}, while it is actually
{{{}sedona-spark-shaded-${spark.compat.version}_$\{scala.compat.version{}}}}:
{code:xml}
<modelVersion>4.0.0</modelVersion>
<parent>
<artifactId>sedona-parent</artifactId>
<groupId>org.apache.sedona</groupId>
<version>1.4.0</version>
</parent>
<artifactId>sedona-spark-shaded-${spark.compat.version}_${scala.compat.version}</artifactId>
{code}
Fortunately, more recent versions of maven-shade-plugin can substitute property
values when generating the dependency reduced POM, so we can simply upgrade the
maven-shade-plugin to generate correct POMs for shaded modules. The problem
went away after upgrading maven-shade-plugin from 2.1 to 3.4.1.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
