Add Release Profile for distribution/proxy-native#21657
Conversation
|
|
||
| <profiles> | ||
| <profile> | ||
| <id>release</id> |
There was a problem hiding this comment.
For this PR, if you need a binary package of release distribution/proxy-native, you need to execute ./mvnw -am -pl distribution/proxy-native -B -DskipTests -Dmaven.javadoc.skip=true -Dcheckstyle.skip=true - Dspotless.apply.skip=true -Pnative,release clean package. This requires both GraalVM CE for JDK 17 and the native-image component of GraalVM installed on the device on which this command is executed. In which document should I state this?
There was a problem hiding this comment.
@strongduanmu I just want to make sure, does such a release note exist? 🤣
There was a problem hiding this comment.
@linghengqian I think we can add this requirement in ShardingSphere release document——https://shardingsphere.apache.org/community/cn/involved/release/shardingsphere/#3-%E5%8F%91%E5%B8%83-docker.
There was a problem hiding this comment.
-
I looked at the
Dockerfileand release process ofdistribution/proxyand found that all the raw materials used to build the Docker Image are extracted from the.tar.gzfile generated by the release profile. -
Is this an unwritten rule, or is it possible to make a Docker Image without making an intermediate
.tar.gz? I'm not quite sure if.tar.gzis only needed for distributing binaries. -
If this provision exists, I will fix the
Dockerfileofdistribution/proxy-nativewhen opening a new PR.
|
For #21347.
Changes proposed in this pull request:
distribution/proxy-native.0.9.16.Before committing this PR, I'm sure that I have checked the following options:
mvn clean install -B -T2C -DskipTests -Dmaven.javadoc.skip=true -e.