[GitHub] [plc4x] dependabot[bot] opened a new pull request #304: build(deps): bump asciidoctor-maven-plugin from 2.1.0 to 2.2.1

2022-01-09 Thread GitBox


dependabot[bot] opened a new pull request #304:
URL: https://github.com/apache/plc4x/pull/304


   Bumps 
[asciidoctor-maven-plugin](https://github.com/asciidoctor/asciidoctor-maven-plugin)
 from 2.1.0 to 2.2.1.
   
   Release notes
   Sourced from https://github.com/asciidoctor/asciidoctor-maven-plugin/releases;>asciidoctor-maven-plugin's
 releases.
   
   v2.2.1
   V2.2.1 contains a fix that could impact Jenkins users (https://github-redirect.dependabot.com/asciidoctor/asciidoctor-maven-plugin/issues/545;>#545)
 when Jenkins creates a working directorin with _ prefix.
   Thanks https://github.com/liampuk;>@​liampuk 
for reporting!
   Improvements
   
   https://github-redirect.dependabot.com/asciidoctor/asciidoctor-maven-plugin/pull/546;>#546
 Fix excluding sources when enclosing parent path starts with _
   
   Release Meta
   Released on: 2021-07-24
   Released by: https://github.com/abelsromero;>@​abelsromero
   Soundtrack: Chrysalis (Opeth)
   v2.2.0
   V2.2.0 aim has been in maintenance and accessibility.
   The highlights...
   
   Documentation has been migrated to Antora site https://docs.asciidoctor.org/maven-tools/latest/;>docs.asciidoctor.org/maven-tools.
   All tests have been migrated to Java  JUnit5.
   Removed usage of AsciidoctorJ internal componentes.
   Upgraded Asciidoctorj to latests v2.5. and jRuby to v9.2.17.0.
   
   As always, thanks to all contributors! Specially those taking time 
providing report issues and feedback :+1:
   Improvements
   
   https://github-redirect.dependabot.com/asciidoctor/asciidoctor-maven-plugin/pull/542;>#542
 Allow running a refresh build on included sources (for 
auto-refresh  http mojos)
   
   Documentation
   
   https://github-redirect.dependabot.com/asciidoctor/asciidoctor-maven-plugin/pull/498;>#498
 Migrate docs (README) to Antora site and publish them in gh-pages
   https://github-redirect.dependabot.com/asciidoctor/asciidoctor-maven-plugin/pull/507;>#507
 Remove ambiguity in usage of maven properties docs
   https://github-redirect.dependabot.com/asciidoctor/asciidoctor-maven-plugin/pull/509;>#509
 Add ID to 'attributes' description, to be able to generate direct url from 
other docs
   https://github-redirect.dependabot.com/asciidoctor/asciidoctor-maven-plugin/pull/523;>#523
 Fix broken links to extension api documentation (https://github.com/djarnis73;>@​djarnis73)
   https://github-redirect.dependabot.com/asciidoctor/asciidoctor-maven-plugin/pull/529;>#529
  Remove local antora site generator stuff (https://github.com/uniqueck;>@​uniqueck)
   
   Build / Infrastructure
   
   https://github-redirect.dependabot.com/asciidoctor/asciidoctor-maven-plugin/pull/521;>#521
 Upgrade tests to JUni5
   https://github-redirect.dependabot.com/asciidoctor/asciidoctor-maven-plugin/pull/524;>#524
 Rename main branch
   https://github-redirect.dependabot.com/asciidoctor/asciidoctor-maven-plugin/pull/525;>#525
 Set maven wrapper to use maven v3.8.1
   https://github-redirect.dependabot.com/asciidoctor/asciidoctor-maven-plugin/pull/526;>#526
 Upgrade Asciidoctorj to v2.4.3 and jRuby to v9.2.14.0
   https://github-redirect.dependabot.com/asciidoctor/asciidoctor-maven-plugin/pull/531;>#531
 Upgrade Asciidoctorj to v2.5.0 and jRuby to v9.2.17.0
   https://github-redirect.dependabot.com/asciidoctor/asciidoctor-maven-plugin/pull/534;>#534
 Upgrade Asciidoctorj to v2.5.1
   https://github-redirect.dependabot.com/asciidoctor/asciidoctor-maven-plugin/pull/539;>#539
 Added 'Asciidoctor' organization to pom
   https://github-redirect.dependabot.com/asciidoctor/asciidoctor-maven-plugin/pull/540;>#540
 Remove AppVeyor CI build
   https://github-redirect.dependabot.com/asciidoctor/asciidoctor-maven-plugin/pull/544;>#544
 Update distributionManagement to deploy directly without 
Bintray
   
   
   
   ... (truncated)
   
   
   Changelog
   Sourced from https://github.com/asciidoctor/asciidoctor-maven-plugin/blob/main/CHANGELOG.adoc;>asciidoctor-maven-plugin's
 changelog.
   
   == v2.2.1 (2021-07-24)
   Bug Fixes::
   
   Fix excluding sources when enclosing parent path starts with _ (https://github-redirect.dependabot.com/asciidoctor/asciidoctor-maven-plugin/issues/546;>#546)
   Treat dot files and folders same as internal https://github-redirect.dependabot.com/asciidoctor/asciidoctor-maven-plugin/issues/5505;>#5505)
   
   == v2.2.0 (2021-07-18)
   Improvements::
   
   Allow running a refresh build on included sources (for 
auto-refresh  http mojos) (https://github-redirect.dependabot.com/asciidoctor/asciidoctor-maven-plugin/issues/542;>#542)
   
   Documentation::
   
   Migrate docs (README) to Antora site and publish them in gh-pages (https://github-redirect.dependabot.com/asciidoctor/asciidoctor-maven-plugin/issues/498;>#498)
   Remove ambiguity in usage of maven properties docs (https://github-redirect.dependabot.com/asciidoctor/asciidoctor-maven-plugin/issues/507;>#507)
   Add ID to 'attributes' description, to be able to generate direct url 
from other docs 

Re: [DISCUSS] Extend PlcDriver with "supportedTransports"?

2022-01-09 Thread Cesar Garcia
How are they?

Not only the transport, but also the data structures of the items.

This would allow the user to have a reference of what you can request in
the items.

Looking to the future, this would be a must for the OPC-UA server.

Kind regards,

El dom, 9 ene 2022 a las 6:10, Christofer Dutz ()
escribió:

> Hi all,
>
> I know initially I built the Plc4X API to generally allow any form of
> driver to use any form of transport.
> However, this only would have worked in theory.
>
> I think we should probably have every driver provide a list of supported
> transports.
> This would also help make tool integration easier.
>
> If we see that for example sometimes, we have ModbusRTU passed along
> TCP/UDP connections via serial-to-ethernet adapters, we can definitely
> support that and if we come across a mode of operation, that we haven't
> encountered, it should be easy to extend.
>
> But this way we could ensure that we build the drivers in a way that they
> know what to expect.
>
> What do you think?
>


-- 
*CEOS Automatización, C.A.*
*GALPON SERVICIO INDUSTRIALES Y NAVALES FA, C.A.,*
*PISO 1, OFICINA 2, AV. RAUL LEONI, SECTOR GUAMACHITO,*

*FRENTE A LA ASOCIACION DE GANADEROS,BARCELONA,EDO. ANZOATEGUI*
*Ing. César García*

*Cel: +58 414-760.98.95*

*Hotline Técnica SIEMENS: 0800 1005080*

*Email: support.aan.automat...@siemens.com
*


[DISCUSS] Extend PlcDriver with "supportedTransports"?

2022-01-09 Thread Christofer Dutz
Hi all,

I know initially I built the Plc4X API to generally allow any form of driver to 
use any form of transport.
However, this only would have worked in theory.

I think we should probably have every driver provide a list of supported 
transports.
This would also help make tool integration easier.

If we see that for example sometimes, we have ModbusRTU passed along TCP/UDP 
connections via serial-to-ethernet adapters, we can definitely support that and 
if we come across a mode of operation, that we haven't encountered, it should 
be easy to extend.

But this way we could ensure that we build the drivers in a way that they know 
what to expect.

What do you think?