Hi folks, as I uploaded the wrong jars (with the wrapper jar in it) I hereby reopen the Vote with RC2. Note that nothing changed with the git tags and hashes (same commit still) and staging repo only the staged files are different.
Apache PLC4X Build-Tools Code-Generation 1.1.0 has been staged under [2] and it’s time to vote on accepting it for release. All Maven artifacts are available under [1]. Voting will be open for 72hr. A minimum of 3 binding +1 votes and more binding +1 than binding -1 are required to pass. Repository: https://gitbox.apache.org/repos/asf/plc4x-build-tools.git Release tag: release/code-generation/1.1.0 Hash for the release tag: 3b21d09085720f8ab48a294da34d7f9b2fb08de3 Per [3] "Before voting +1 PMC members are required to download the signed source code package, compile it as provided, and test the resulting executable on their own platform, along with also verifying that the package meets the requirements of the ASF policy on releases." You can achieve the above by following [4]. [ ] +1 accept (indicate what you validated - e.g. performed the non-RM items in [4]) [ ] -1 reject (explanation required) [1] https://repository.apache.org/content/repositories/orgapacheplc4x-1019 [2] https://dist.apache.org/repos/dist/dev/plc4x/build-tools/code-generation/1.1.0/rc2/ [3] https://www.apache.org/dev/release.html#approving-a-release [4] https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release
