[BUILD-FAILURE]: Job 'PLC4X/PLC4X/develop [develop] [1890]'
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [1890]': Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/1890/;>PLC4X/PLC4X/develop [develop] [1890]"
[VOTE] Apache PLC4X 0.12.0 RC2
Apache PLC4X 0.13.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. Release tag: v0.12.0 Hash for the release tag: 47af22589818dc83c274dd6299449ec1a36f8fae 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-1054 [2] https://dist.apache.org/repos/dist/dev/plc4x/0.12.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
AW: [VOTE] Apache PLC4X 0.12.0 RC2
+1 (binding) Chris [OK] Download all staged artifacts under the url specified in the release vote email. [OK] Verify the signature is correct. [OK] Check if the signature references an Apache email address. [OK] Verify the SHA512 hashes. [OK] Unzip the archive. [OK] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. [OK] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. [OK] [RM] Verify the staged source README, RELEASE_NOTE files correspond to those in the extracted source bundle. [OK] [RM] Run RAT externally to ensure there are no surprises. [OK] Search for SNAPSHOT references * Only references in disabled code-blocks and modules. [OK] Search for Copyright references, and if they are in headers, make sure these files containing them are mentioned in the LICENSE file. [OK] Build the project according to the information in the README.md file. [OK] [RM] Build the project with all with-xyz profiles and tests enabled and an empty maven local repo. Von: Christofer Dutz Datum: Freitag, 16. Februar 2024 um 18:10 An: dev@plc4x.apache.org Betreff: [VOTE] Apache PLC4X 0.12.0 RC2 Apache PLC4X 0.13.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. Release tag: v0.12.0 Hash for the release tag: 47af22589818dc83c274dd6299449ec1a36f8fae 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-1054 [2] https://dist.apache.org/repos/dist/dev/plc4x/0.12.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
[DISCUSS] Apache PLC4X 0.12.0 RC2
This is the discussion thread for the corresponding VOTE thread. Please keep discussions in this thread to simplify the counting of votes. If you have to vote -1 please mention a brief description on why and then take the details to this thread.
[BUILD-FAILURE]: Job 'PLC4X/PLC4X/develop [develop] [1889]'
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [1889]': Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/1889/;>PLC4X/PLC4X/develop [develop] [1889]"
Re: [VOTE] Apache PLC4X 0.12.0 RC2
+1 (binding) Lukas - otluk [x] Download all staged artifacts under the url specified in the release vote email. [x] Verify the signature is correct. [x] Check if the signature references an Apache email address. [x] Verify the SHA512 hashes. [x] Unzip the archive. [x] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. [x] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. [x] [RM] Verify the staged source README, RELEASE_NOTE files correspond to those in the extracted source bundle. [x] [RM] Run RAT externally to ensure there are no surprises. [x] Search for SNAPSHOT references [x] Build the project according to the information in the README.md file. Built with: ./mvnw -P with-c,with-dotnet,with-java,with-python,with-sandbox,enable-all-checks,update-generated-code install -X OS: Linux Mint 21.3 x86_64 Kernel: 6.5.0-18-generic openjdk version "11.0.21" 2023-10-17 OpenJDK Runtime Environment (build 11.0.21+9-post-Ubuntu-0ubuntu122.04) OpenJDK 64-Bit Server VM (build 11.0.21+9-post-Ubuntu-0ubuntu122.04, mixed mode, sharing) .NET - SDK-Version: 8.0.102 Python 3.10.12 Am Fr., 16. Feb. 2024 um 18:09 Uhr schrieb Christofer Dutz < christofer.d...@c-ware.de>: > Apache PLC4X 0.13.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. > > Release tag: v0.12.0 > Hash for the release tag: 47af22589818dc83c274dd6299449ec1a36f8fae > > 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-1054 > [2] https://dist.apache.org/repos/dist/dev/plc4x/0.12.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 > >
Re: AW: Re-generated Generated Sources
Chris, I created a fresh instance of the plc4x project and ran ./mvnw -P update-generated-code,.os-mac-x86_64,skip-prerequisite-check -pl :plc4j-driver-eip -am clean package which ran to completion and regenerated the files. As a sanity check I updated the eip.mspec with one of my changes and reran the compiler and it worked as expected. Thanks for the quick response and pointer! Bob > On 02/16/2024 1:32 AM EST Christofer Dutz wrote: > > > Hi Robert, > > happy to help you with that. > > In general, I’ll be working on updating the documentation after the next > release (which I’ll start after finishing this mail) > But for now: We’ve introduced some minor changes to the build, so you’ll need > to make sure the following maven profiles are enabled: > > > * with-java (Without it, generally nothing java-related will be built at > all) > * update-generated-code (Without it, the code generation will not be > performed at all) > > > So, if you run the following command: > > > ./mvnw -Pwith-java,update-generated-code -pl :plc4j-driver-eip -am clean > package > > It will generally build the java eip driver and all modules it depends on. > > Hope that helps and looking forward to some pull-requests ;-) > > > Chris > > > > Von: R Thayer > Datum: Freitag, 16. Februar 2024 um 02:25 > An: dev@plc4x.apache.org > Betreff: Re: Re-generated Generated Sources > All, > What is the process to regenerate generated sources? > > New to plc4x but have live EIP/CIP traffic that i'm trying to model with the > eip.mspec and need to close the circle of eip.mspec==>generated-code in the > plc4j/drivers/eip/src/main/generated to verify correct mspec. Working > through ParserSerializerTestsuiteLittleEndian.xml to model MultipleServiceR/R > > The website discusses it and suggests "mvn compile". > This thinks it works but does not regenerate nor replace the files. > > Thanks, > > Robert Thayer > CC Software, Inc. > 702-726-1034
[BUILD-FAILURE]: Job 'PLC4X/PLC4X/develop [develop] [1883]'
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [1883]': Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/1883/;>PLC4X/PLC4X/develop [develop] [1883]"
[BUILD-FAILURE]: Job 'PLC4X/PLC4X/develop [develop] [1886]'
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [1886]': Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/1886/;>PLC4X/PLC4X/develop [develop] [1886]"
[BUILD-FAILURE]: Job 'PLC4X/PLC4X/develop [develop] [1888]'
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [1888]': Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/1888/;>PLC4X/PLC4X/develop [develop] [1888]"
AW: [VOTE] Apache PLC4X 0.12.0 RC1
-1 (binding) Chris [OK] Download all staged artifacts under the url specified in the release vote email. [OK] Verify the signature is correct. [OK] Check if the signature references an Apache email address. [OK] Verify the SHA512 hashes. [OK] Unzip the archive. [OK] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. [MINOR] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. * It turns out the “build with everything” statement needs an additional “update-generated-code” profile to really build everything. [OK] [RM] Verify the staged source README, RELEASE_NOTE files correspond to those in the extracted source bundle. [OK] [RM] Run RAT externally to ensure there are no surprises. [FAIL] Search for SNAPSHOT references * It seems the code-generation tests were not run during the release and therefore the artifacts there were not updated :-/ [OK] Search for Copyright references, and if they are in headers, make sure these files containing them are mentioned in the LICENSE file. [-] Build the project according to the information in the README.md file. [-] [RM] Build the project with all with-xyz profiles and tests enabled and an empty maven local repo. Von: Christofer Dutz Datum: Freitag, 16. Februar 2024 um 13:58 An: dev@plc4x.apache.org Betreff: [VOTE] Apache PLC4X 0.12.0 RC1 Apache PLC4X 0.12.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. Release tag: v0.12.0 Hash for the release tag: 90fc8c00de051abcad2789d7622c8d497209def4 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-1052 [2] https://dist.apache.org/repos/dist/dev/plc4x/0.12.0/rc1 [3] https://www.apache.org/dev/release.html#approving-a-release [4] https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release
[CANCELED][VOTE] Apache PLC4X 0.12.0 RC1
Found an issue … will fix it and stage an RC2 Chris Von: Christofer Dutz Datum: Freitag, 16. Februar 2024 um 14:54 An: dev@plc4x.apache.org Betreff: AW: [VOTE] Apache PLC4X 0.12.0 RC1 -1 (binding) Chris [OK] Download all staged artifacts under the url specified in the release vote email. [OK] Verify the signature is correct. [OK] Check if the signature references an Apache email address. [OK] Verify the SHA512 hashes. [OK] Unzip the archive. [OK] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. [MINOR] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. * It turns out the “build with everything” statement needs an additional “update-generated-code” profile to really build everything. [OK] [RM] Verify the staged source README, RELEASE_NOTE files correspond to those in the extracted source bundle. [OK] [RM] Run RAT externally to ensure there are no surprises. [FAIL] Search for SNAPSHOT references * It seems the code-generation tests were not run during the release and therefore the artifacts there were not updated :-/ [OK] Search for Copyright references, and if they are in headers, make sure these files containing them are mentioned in the LICENSE file. [-] Build the project according to the information in the README.md file. [-] [RM] Build the project with all with-xyz profiles and tests enabled and an empty maven local repo. Von: Christofer Dutz Datum: Freitag, 16. Februar 2024 um 13:58 An: dev@plc4x.apache.org Betreff: [VOTE] Apache PLC4X 0.12.0 RC1 Apache PLC4X 0.12.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. Release tag: v0.12.0 Hash for the release tag: 90fc8c00de051abcad2789d7622c8d497209def4 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-1052 [2] https://dist.apache.org/repos/dist/dev/plc4x/0.12.0/rc1 [3] https://www.apache.org/dev/release.html#approving-a-release [4] https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release
[VOTE] Apache PLC4X 0.12.0 RC1
Apache PLC4X 0.12.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. Release tag: v0.12.0 Hash for the release tag: 90fc8c00de051abcad2789d7622c8d497209def4 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-1052 [2] https://dist.apache.org/repos/dist/dev/plc4x/0.12.0/rc1 [3] https://www.apache.org/dev/release.html#approving-a-release [4] https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release
[BUILD-FAILURE]: Job 'PLC4X/PLC4X/develop [develop] [1887]'
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [1887]': Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/1887/;>PLC4X/PLC4X/develop [develop] [1887]"
[DISCUSS] Apache PLC4X 0.12.0 RC1
This is the discussion thread for the corresponding VOTE thread. Please keep discussions in this thread to simplify the counting of votes. If you have to vote -1 please mention a brief description on why and then take the details to this thread.
[BUILD-STABLE]: Job 'PLC4X/PLC4X/develop [develop] [1884]'
BUILD-STABLE: Job 'PLC4X/PLC4X/develop [develop] [1884]': Is back to normal.
Re: [CANCELED][VOTE] Apache PLC4X 0.12.0 RC1
-1 (binding) Found the mentioned issue and can confirm that I can not build from source. Lukas [OK] Download all staged artifacts under the url specified in the release vote email. [OK] Verify the signature is correct. [OK] Check if the signature references an Apache email address. [OK] Verify the SHA512 hashes. [OK] Unzip the archive. [OK] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. [MINOR] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. * It turns out the “build with everything” statement needs an additional “update-generated-code” profile to really build everything. Am Fr., 16. Feb. 2024 um 14:56 Uhr schrieb Christofer Dutz < christofer.d...@c-ware.de>: > Found an issue … will fix it and stage an RC2 > > Chris > > Von: Christofer Dutz > Datum: Freitag, 16. Februar 2024 um 14:54 > An: dev@plc4x.apache.org > Betreff: AW: [VOTE] Apache PLC4X 0.12.0 RC1 > -1 (binding) > > Chris > > [OK] Download all staged artifacts under the url specified in the release > vote email. > [OK] Verify the signature is correct. > [OK] Check if the signature references an Apache email address. > [OK] Verify the SHA512 hashes. > [OK] Unzip the archive. > [OK] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files > in the extracted source bundle. > [MINOR] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files > in the extracted source bundle. > > * It turns out the “build with everything” statement needs an > additional “update-generated-code” profile to really build everything. > [OK] [RM] Verify the staged source README, RELEASE_NOTE files correspond > to those in the extracted source bundle. > [OK] [RM] Run RAT externally to ensure there are no surprises. > [FAIL] Search for SNAPSHOT references > > * It seems the code-generation tests were not run during the release > and therefore the artifacts there were not updated :-/ > [OK] Search for Copyright references, and if they are in headers, make > sure these files containing them are mentioned in the LICENSE file. > [-] Build the project according to the information in the README.md file. > [-] [RM] Build the project with all with-xyz profiles and tests enabled > and an empty maven local repo. > > > Von: Christofer Dutz > Datum: Freitag, 16. Februar 2024 um 13:58 > An: dev@plc4x.apache.org > Betreff: [VOTE] Apache PLC4X 0.12.0 RC1 > Apache PLC4X 0.12.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. > > Release tag: v0.12.0 > Hash for the release tag: 90fc8c00de051abcad2789d7622c8d497209def4 > > 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-1052 > [2] https://dist.apache.org/repos/dist/dev/plc4x/0.12.0/rc1 > [3] https://www.apache.org/dev/release.html#approving-a-release > [4] > https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release >
AW: [DISCUSS] Apache PLC4X 0.12.0 RC1
Hi all, this release was the first done by the scripts in “tools”. With this I am trying to make releasing easier and to make it harder for RMs to miss things. However, the probably major difference is that the final release:perform-release step is executed in a Docker-container, which should make the build fully reproducible. I am planning on building some additional tooling, that allows people to validate releases additionally by downloading the content of the staging repo and doing binary comparisons with what’s built from the local sources. Also, could people download our releases and run the script and compare that what they are using in the company is binary identical what they would build locally. I think that’s going to be pretty cool. Happy voting … I would love to release the release on Tuesday, so please do me a favor and plan in some time for voting. Ideally as soon as possible, so we could possibly have a bit more time, in case an RC2 is needed, as I would love to have the release out the door before Building IoT Conference next week and to have our website in-line with the currently latest released version as soon as possible. Chris Von: Christofer Dutz Datum: Freitag, 16. Februar 2024 um 13:59 An: dev@plc4x.apache.org Betreff: [DISCUSS] Apache PLC4X 0.12.0 RC1 This is the discussion thread for the corresponding VOTE thread. Please keep discussions in this thread to simplify the counting of votes. If you have to vote -1 please mention a brief description on why and then take the details to this thread.
