NihalJain commented on code in PR #6366:
URL: https://github.com/apache/hbase/pull/6366#discussion_r1896653038
##########
pom.xml:
##########
@@ -925,13 +916,11 @@
<lz4.version>1.8.0</lz4.version>
<snappy.version>1.1.10.4</snappy.version>
<zstd-jni.version>1.5.5-2</zstd-jni.version>
- <!--
- Note that the version of protobuf shipped in hbase-thirdparty must
match the version used
- in hbase-protocol-shaded and hbase-examples. The version of
jackson-[annotations,core,
- databind] must be kept in sync with the version of
jackson-jaxrs-json-provider shipped in
- hbase-thirdparty.
+ <hbase-thirdparty.version>4.1.10-SNAPSHOT</hbase-thirdparty.version>
+ <!--Version of protobuf that hbase uses internally (we shade our pb)
+ Must match what is out in hbase-thirdparty include.
Review Comment:
> That's super annoying.
>
> Okay but maybe there's a hack. Can we use the bundle and process goals
from https://maven.apache.org/plugins/maven-remote-resources-plugin/index.html
to package up this property and then import it from the hbase-protocol-shaded
build via
https://www.mojohaus.org/properties-maven-plugin/read-project-properties-mojo.html
?
I tried this approach. Unfortunately this also did not work as "Properties
used in plugin configurations must be available during the POM parsing phase."
We can read/inject a property only after parsing is done; So the
`compile-protoc` would still build with whatever is set as initial value for
`internal.protobuf.version` in pom.xml
--
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]
