[GitHub] [plc4x] dependabot[bot] opened a new pull request #322: build(deps): bump asciidoctorj from 2.5.1 to 2.5.3
dependabot[bot] opened a new pull request #322: URL: https://github.com/apache/plc4x/pull/322 Bumps [asciidoctorj](https://github.com/asciidoctor/asciidoctorj) from 2.5.1 to 2.5.3. Release notes Sourced from https://github.com/asciidoctor/asciidoctorj/releases;>asciidoctorj's releases. v2.5.3 This release brings the latest version of Asciidoctor, 2.0.17, Asciidoctor PDF, 1.6.2. Improvement Upgrade to asciidoctorj 2.0.17 (https://github-redirect.dependabot.com/asciidoctor/asciidoctorj/issues/1074;>#1074) Upgrade to asciidoctorj-pdf 1.6.2 (https://github-redirect.dependabot.com/asciidoctor/asciidoctorj/issues/1073;>#1073) Upgrade to asciidoctorj-diagram 2.2.1 (https://github-redirect.dependabot.com/asciidoctor/asciidoctorj/issues/1066;>#1066) (https://github.com/abelsromero;>@abelsromero) (https://github-redirect.dependabot.com/asciidoctor/asciidoctorj/issues/1065;>#1065) Upgrade to jruby 9.2.20.1 (https://github-redirect.dependabot.com/asciidoctor/asciidoctorj/issues/1074;>#1074) Upgrade to rouge 3.27.0 (https://github-redirect.dependabot.com/asciidoctor/asciidoctorj/issues/1073;>#1073) Upgrade CLI to use JCommander 1.81 (https://github.com/abelsromero;>@abelsromero) (https://github-redirect.dependabot.com/asciidoctor/asciidoctorj/issues/1067;>#1067) Build Improvement Add Java17 to CI pipelines (https://github.com/abelsromero;>@abelsromero) (https://github-redirect.dependabot.com/asciidoctor/asciidoctorj/issues/1055;>#1055) Improve pipelines to better display Asciidoctor test upstream (https://github.com/abelsromero;>@abelsromero) (https://github-redirect.dependabot.com/asciidoctor/asciidoctorj/issues/1057;>#1057) Documentation Clarify execution order for extensions (https://github.com/rockyallen;>@rockyallen) (https://github-redirect.dependabot.com/asciidoctor/asciidoctorj/issues/1068;>#1068) Added docs for attributes and positional attributes in extensions (https://github-redirect.dependabot.com/asciidoctor/asciidoctorj/issues/1072;>#1072) Added docs for how to log from extensions (https://github-redirect.dependabot.com/asciidoctor/asciidoctorj/issues/1071;>#1071) Release Meta Released on: 2022-01-12 Released by: https://github.com/robertpanzer;>@robertpanzer Release Beer: Dogfish 90 Minute Imperial IPA v2.5.2 This release brings the latest version of Asciidoctor, 2.0.16 and Asciidoctor PDF, 1.6.0. Improvement: Upgrade to asciidoctorj 2.0.16 (https://github-redirect.dependabot.com/asciidoctor/asciidoctorj/issues/1052;>#1052) Upgrade to asciidoctorj-pdf 1.6.0 (https://github-redirect.dependabot.com/asciidoctor/asciidoctorj/issues/1040;>#1040) Bug Fixes: Avoid using of deprecated attributes toc2 and toc-placement. Deprecated Attributes.setTableOfContents2(). Added new constants Placement.PREAMBLE and Placement.MACRO as parameters for Attributes.setTableOfConstants(). (https://github.com/abelsromero;>@abelsromero) (https://github-redirect.dependabot.com/asciidoctor/asciidoctorj/issues/1037;>#1037) Build Improvement: Use JavaCompile options.release instead of sourceCompatibility and targetCompatibility to target Java 8 (https://github-redirect.dependabot.com/asciidoctor/asciidoctorj/issues/1042;>#1042) Upgrade nexus publishing and staging to new gradle-nexus.publish-plugin (https://github-redirect.dependabot.com/asciidoctor/asciidoctorj/issues/1043;>#1043) Upgrade remaining dependency on junit 4.12 to 4.13.2 (https://github-redirect.dependabot.com/asciidoctor/asciidoctorj/issues/1044;>#1044) ... (truncated) Changelog Sourced from https://github.com/asciidoctor/asciidoctorj/blob/main/CHANGELOG.adoc;>asciidoctorj's changelog. == 2.5.3 (2022-01-12) Improvement:: Upgrade to asciidoctorj 2.0.17 (https://github-redirect.dependabot.com/asciidoctor/asciidoctorj/issues/1074;>#1074) Upgrade to asciidoctorj-pdf 1.6.2 (https://github-redirect.dependabot.com/asciidoctor/asciidoctorj/issues/1073;>#1073) Upgrade to asciidoctorj-diagram 2.2.1 (https://github-redirect.dependabot.com/asciidoctor/asciidoctorj/issues/1066;>#1066) (https://github.com/abelsromero;>@abelsromero) (https://github-redirect.dependabot.com/asciidoctor/asciidoctorj/issues/1065;>#1065) Upgrade to jruby 9.2.20.1 (https://github-redirect.dependabot.com/asciidoctor/asciidoctorj/issues/1074;>#1074) Upgrade to rouge 3.27.0 (https://github-redirect.dependabot.com/asciidoctor/asciidoctorj/issues/1073;>#1073) Upgrade CLI to use JCommander 1.81 (https://github.com/abelsromero;>@abelsromero) (https://github-redirect.dependabot.com/asciidoctor/asciidoctorj/issues/1067;>#1067) Build Improvement:: Add Java17 to CI pipelines (https://github.com/abelsromero;>@abelsromero) (https://github-redirect.dependabot.com/asciidoctor/asciidoctorj/issues/1055;>#1055) Improve pipelines to better display Asciidoctor test
Re: [CODE GENERATION] Updates from today
+1 awesome job Chris and Sebastian ! #teamToddy Am Di., 22. Feb. 2022 um 21:24 Uhr schrieb Christofer Dutz < christofer.d...@c-ware.de>: > Hi all, > > the last few days I was working hard on creating a new C template module > based on our latest refactorings. There I noticed I need not only a target > type (The type of the expression output) but also the current type when > working with expressions. Sebastian stumbled over the same problem in Java. > At first, I wanted to pass along the current type but Sebastian convinced > me to do it in the mspec parser. > > So today we enabled the mspec parser to assign a type to each literal of > an expression. This is particularly interesting for variable expressions. > > Now in the code-generation we can simply access the type of a variable at > every step of the generation process. This will allow simplifying the > templates quite a bit. > > But the super-awesome side-effect is, that now the parser ensures > expressions are valid and you're not referencing properties that don't > exist. This will help with developing syntactically and semantically > correct protocol specs. > > We even thought, that now it would make sense to have a test in every > protocol module, which simply tries to parse the mspec and to report errors > early. > > So much for the update .. I bet 99,99% of our users will not even notice > any change ;-) > > Chris >
[CODE GENERATION] Updates from today
Hi all, the last few days I was working hard on creating a new C template module based on our latest refactorings. There I noticed I need not only a target type (The type of the expression output) but also the current type when working with expressions. Sebastian stumbled over the same problem in Java. At first, I wanted to pass along the current type but Sebastian convinced me to do it in the mspec parser. So today we enabled the mspec parser to assign a type to each literal of an expression. This is particularly interesting for variable expressions. Now in the code-generation we can simply access the type of a variable at every step of the generation process. This will allow simplifying the templates quite a bit. But the super-awesome side-effect is, that now the parser ensures expressions are valid and you're not referencing properties that don't exist. This will help with developing syntactically and semantically correct protocol specs. We even thought, that now it would make sense to have a test in every protocol module, which simply tries to parse the mspec and to report errors early. So much for the update .. I bet 99,99% of our users will not even notice any change ;-) Chris
[BUILD-STABLE]: Job 'PLC4X/PLC4X/develop [develop] [798]'
BUILD-STABLE: Job 'PLC4X/PLC4X/develop [develop] [798]': Is back to normal.
[GitHub] [plc4x] chrisdutz commented on pull request #321: Dynamically determine ETS project number
chrisdutz commented on pull request #321: URL: https://github.com/apache/plc4x/pull/321#issuecomment-1047635314 Regarding a knxproj file being added to the project. I would probably suggest not to do that. Even if it's theroretically not a problem. We would be adding a sort-of-binary file to the repo, which might be a problem. But the most important thing is, that it contains the xml descriptors of KNX products. While the project file itself is probably not a problem, these static XML files are probably not licensed under an Apache compatible licence. We would probably get problems with releases if we added such a file. If we don't need the static product-descriptors and can live with the project-xml, I would probably opt for manipulating a knxproj file to remove all the stuff that's not a project-xml. In that case I think there probably shouldn't be any issues. -- 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: dev-unsubscr...@plc4x.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [plc4x] sruehl merged pull request #321: Dynamically determine ETS project number
sruehl merged pull request #321: URL: https://github.com/apache/plc4x/pull/321 -- 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: dev-unsubscr...@plc4x.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [plc4x] sruehl commented on pull request #321: Dynamically determine ETS project number
sruehl commented on pull request #321: URL: https://github.com/apache/plc4x/pull/321#issuecomment-1047629037 Thanks for your contribution! :) -- 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: dev-unsubscr...@plc4x.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
