bhasudha commented on issue #1943: URL: https://github.com/apache/hudi/issues/1943#issuecomment-675970485
@wfhartford I was able to reproduce this based on your steps. It seems like the [pom](https://repo1.maven.org/maven2/org/apache/hudi/hudi-spark_2.12/0.5.3/hudi-spark_2.12-0.5.3.pom) of maven artifact itself is published with the dynamic variables like '${scala.binary.version}' like you had mentioned. When building hudi using mvn from source this variable gets substituted with 2.11 or 2.12 depending on the profile chose while building. I believe this is not happening in the same effect in Gradle. I saw some posts pointing to same behavior - https://stackoverflow.com/questions/49992061/gradle-unable-to-resolve-maven-profile-dependency @bvaradar @vinothchandar do you think it makes sense to publish the poms with these variables substituted when publishing to maven central? ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
