You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@plc4x.apache.org by cd...@apache.org on 2022/10/03 16:11:25 UTC
svn commit: r57142 - in /dev/plc4x/0.10.0/rc2: ./ README RELEASE_NOTES apache-plc4x-0.10.0-source-release.zip apache-plc4x-0.10.0-source-release.zip.asc apache-plc4x-0.10.0-source-release.zip.sha512
Author: cdutz
Date: Mon Oct 3 16:11:25 2022
New Revision: 57142
Log:
Staging of rc2 of PLC4X 0.10.0
Added:
dev/plc4x/0.10.0/rc2/
dev/plc4x/0.10.0/rc2/README
dev/plc4x/0.10.0/rc2/RELEASE_NOTES
dev/plc4x/0.10.0/rc2/apache-plc4x-0.10.0-source-release.zip (with props)
dev/plc4x/0.10.0/rc2/apache-plc4x-0.10.0-source-release.zip.asc
dev/plc4x/0.10.0/rc2/apache-plc4x-0.10.0-source-release.zip.sha512
Added: dev/plc4x/0.10.0/rc2/README
==============================================================================
--- dev/plc4x/0.10.0/rc2/README (added)
+++ dev/plc4x/0.10.0/rc2/README Mon Oct 3 16:11:25 2022
@@ -0,0 +1,231 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ https://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ -->
+[](https://img.shields.io/maven-central/v/org.apache.plc4x/plc4j-api.svg)
+[](https://www.apache.org/licenses/LICENSE-2.0)
+[]()
+[](https://github.com/apache/plc4x/actions/workflows/ensure-platforms.yml)
+[](https://twitter.com/ApachePLC4X)
+
+
+<h1 align="center">
+ <br>
+ <img src="https://plc4x.apache.org/images/apache_plc4x_logo.png"
+ alt="Apache PLC4X Logo" title="Apache PLC4X Logo"/>
+ <br>
+</h1>
+<h3 align="center">The Industrial IoT adapter</h3>
+<h4 align="center">The ultimate goal of PLC4X is to create a set of libraries, that allow unified access to any type of
+ PLC</h4>
+
+***
+
+# Table of contents
+
+ * [About PLC4X](#about-apache-plc4x)
+ * [Getting Started](#getting-started)
+ * [Developers](#developers)
+ * [Community](#community)
+ * [Contributing](#contributing)
+ * [Licensing](#licensing)
+
+***
+
+## About Apache PLC4X
+
+Apache PLC4X is an effort to create a set of libraries for communicating with industrial grade programmable logic controllers (PLCs) in a uniform way.
+We are planning on shipping libraries for usage in:
+
+1. Java
+2. Go
+3. C (not ready for usage)
+4. Python (not ready for usage)
+5. C# (.Net) (not ready for usage)
+
+PLC4X also integrates with other Apache projects, such as:
+
+* [Apache Calcite](https://calcite.apache.org/)
+* [Apache Camel](https://camel.apache.org/)
+* [Apache Kafka-Connect](https://kafka.apache.org)
+* [Apache Karaf](https://karaf.apache.org/)
+* [Apache NiFi](https://nifi.apache.org/)
+
+And brings stand-alone (Java) utils like:
+
+* OPC-UA Server: Enables you to communicate with legacy devices using PLC4X with OPC-UA.
+* PLC4X Server: Enables you to communicate with a central PLC4X Server which then communicates with devices via PLC4X.
+
+It also provides (Java) tools for usage inside an application:
+
+* Connection Cache: New implementation of our framework for re-using and sharing PLC-connections
+* Connection Pool: Old implementation of our framework for re-using and sharing PLC-connections
+* OPM: Object-Plc-Mapping: Allows binding PLC fields to properties in java POJOs similar to JPA
+* Scraper: Utility to do scheduled and repeated data collection.
+
+## Getting started
+
+Depending on the programming language, the usage will differ, therefore please go to the
+[Getting Started](https://plc4x.apache.org/users/gettingstarted.html) on the PLC4X website to look up
+the language of choice.
+
+### Java
+
+NOTE: Currently the Java version which supports building of all parts of Apache PLC4X is at least Java 11 (Currently with Java 19 the Apache Kafka integration module is excluded from the build as the plugins it requires are incompatible with this version)
+
+See the PLC4J user guide on the website to start using PLC4X in your Java application:
+[https://plc4x.apache.org/users/getting-started/plc4j.html](https://plc4x.apache.org/users/getting-started/plc4j.html)
+
+## Developers
+
+### Environment
+
+Currently, the project is configured to require the following software:
+
+1. Java 11 JDK: For running Maven in general as well as compiling the Java and Scala modules `JAVA_HOME` configured to point to that.
+2. Git (even when working on the source distribution)
+3. (Optional, for running all tests) libpcap/Npcap for raw socket tests in Java or use of `passive-mode` drivers
+4. (Optional, for building the website) [Graphviz](https://www.graphviz.org/) : For generating the graphs in the documentation
+
+WARNING: The code generation uses a utility which requires some additional VM settings. When running a build from the root, the settings in the `.mvn/jvm.config` are automatically applied. When building only a sub-module, it is important to set the vm args: `--add-exports jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.parser=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.tree=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED`. In Intellij for example set these in the IDE settings under: Preferences | Build, Execution, Deployment | Build Tools | Maven | Runner: JVM Options.
+
+A more detailed description is available on our website:
+
+https://plc4x.apache.org/developers/preparing/index.html
+
+#### For building `PLC4C` we also need:
+
+All requirements are retrieved by the build itself
+
+#### For building `PLC4Go` we also need:
+
+All requirements are retrieved by the build itself
+
+#### For building `PLC4Py` we also need:
+
+1. Python 3.7 or higher
+2. Python pyenv
+
+#### For building `PLC4Net` we also need:
+
+1. DotNet SDK 6.0
+
+With this setup you will be able to build the Java part of PLC4X.
+
+The when doing a full build, we automatically run a prerequisite check and fail the build with an explanation, if not all requirements are meet.
+
+### Building with Docker
+
+If you don't want to bother setting up the environment on your normal system and you have Docker installed, you can also build everything in a Docker container:
+
+```
+ docker build -t plc4x .
+```
+
+### Getting Started
+
+You must have at least Java 11 installed on your system and connectivity to Maven Central
+(for downloading external third party dependencies). Maven 3.6 is required to build, so be sure it's installed and available on your system.
+
+NOTE: When using Java 19 currently the Apache Kafka integration module is excluded from the build as one of the plugins it requires has proven to be incompatible with this version.
+
+NOTE: There is a convenience Maven-Wrapper installed in the repo, when used, this automatically downloads and installs Maven. If you want to use this, please use `./mvnw` or `mvnw` instead of the normal `mvn` command.
+
+NOTE: When running from sources-zip, the `mvnw` might not be executable on `Mac` or `Linux`. This can easily be fixed by running the following command in the directory.
+
+```
+$ chmod +x mvnw
+```
+
+NOTE: If you are working on a `Windows` system, please use `mvnw.cmd` instead of `./mvnw` in the following build commands.
+
+Build PLC4X Java jars and install them in your local maven repository
+
+```
+./mvnw install
+```
+
+You can now construct Java applications that use PLC4X. The PLC4X examples
+are a good place to start and are available inside the `plc4j/examples`
+directory.
+
+The `Go` drivers can be built by enabling the `with-go` profile:
+
+```
+./mvnw -P with-go install
+```
+
+The `C# / .Net` implementation is currently in a `work in progress` state.
+In order to be able to build the `C# / .Net` module, you currently need to activate the:
+`with-dotnet` profiles.
+
+```
+./mvnw -P with-dotnet install
+```
+
+The Python implementation is currently in a somewhat unclean state and still needs refactoring.
+In order to be able to build the Python module, you currently need to activate the:
+`with-sandbox` and `with-python` profiles.
+
+```
+./mvnw -P with-sandbox,with-python install
+```
+
+In order to build everything the following command should work:
+
+```
+./mvnw -P with-c,with-dotnet,with-go,with-python,with-sandbox install
+```
+
+## Community
+
+Join the PLC4X community by using one of the following channels. We'll be glad to help!
+
+### Mailing Lists
+
+Subscribe to the following mailing lists:
+* Apache PLC4X Developer List: [dev-subscribe@plc4x.apache.org](mailto:dev-subscribe@plc4x.apache.org)
+* Apache PLC4X Commits List: [commits-subscribe@plc4x.apache.org](mailto:commits-subscribe@plc4x.apache.org)
+* Apache PLC4X Jira Notification List: [issues-subscribe@plc4x.apache.org](mailto:issues-subscribe@plc4x.apache.org)
+
+See also: [https://plc4x.apache.org/mailing-lists.html](https://plc4x.apache.org/mailing-lists.html)
+
+### Twitter
+
+Get the latest PLC4X news on Twitter: [https://twitter.com/ApachePlc4x](https://twitter.com/ApachePlc4x)
+
+## Contributing
+
+There are multiple forms in which you can become involved with the PLC4X project.
+
+These are, but are not limited to:
+
+* Providing information and insights
+* Testing PLC4X and providing feedback
+* Submitting Pull Requests
+* Filing Bug-Reports
+* Active communication on our mailing lists
+* Promoting the project (articles, blog posts, talks at conferences)
+* Documentation
+
+We are a very friendly bunch so donât be afraid to step forward.
+If you'd like to contribute to PLC4X, have a look at our
+[contribution guide](https://plc4x.apache.org/developers/contributing.html)!
+
+## Licensing
+
+Apache PLC4X is released under the Apache License Version 2.0.
Added: dev/plc4x/0.10.0/rc2/RELEASE_NOTES
==============================================================================
--- dev/plc4x/0.10.0/rc2/RELEASE_NOTES (added)
+++ dev/plc4x/0.10.0/rc2/RELEASE_NOTES Mon Oct 3 16:11:25 2022
@@ -0,0 +1,480 @@
+==============================================================
+Apache PLC4X 0.10.0
+==============================================================
+
+A lot of the work in this version went into refactoring and
+cleaning up our code generation. The code generation itself is
+now a lot cleaner and simpler as well as the code generated
+for Java. We also added a number of new field-types to allow
+implementing more sophisticated protocols. PLC4C now should
+also support all of the constructs mspec has to offer.
+
+New Features
+------------
+
+- Implemented a `PLC4X-Server` and `PLC4X-Driver` that allows
+ using the server as a proxy for communicating with PLCs.
+
+- The Modbus driver is now also available in the variants:
+ "modbus-rtu" and "modbus-ascii" (Both using Serial
+ communication, which however can be tunneled through a
+ "tcp" and "udp" transport)
+
+- The KNX driver in Java now supports reading "knxproj" files
+ exported from the new ETS version 6.
+
+- The NiFi integration module was updated and now is a
+ Records-based NiFi Processor
+
+Incompatible changes
+--------------------
+
+- The name of the Modbus TCP driver was changed from "modbus"
+ to "modbus-tcp".
+
+- Removed the Apache Edgent (incubating) integration and
+ examples related, as Edgent is abandoned and there were
+ CVEs reported, which will not be fixed.
+
+- We have replaced the BitString types with BYTE, WORD, DWORD,
+ and LWORD which generally match their unsigned integer
+ counterparts. So we are no longer returning lists of boolean
+ values for any of these types.
+
+Bug Fixes
+---------
+
+- Fixed a big bug in the KNX Datapoint decoding, which caused
+ byte-aligned data types to parse with an offset of 8 bit.
+ (This bug affected both the Java and the Go driver)
+
+==============================================================
+Apache PLC4X 0.9.0
+==============================================================
+
+New Features
+------------
+
+- The OPC UA driver has been replaced with a native driver. Previously
+ Eclipse Milo was being used.
+
+- Permit customized package names for code generation
+
+- Added an initial draft of a Discover and Browse API to PLC4J
+
+- PLC4Go now supports many more drivers
+
+- PLC4Go received a huge internal refactoring and cleanup
+
+- Major cleanup of PLC4C
+
+- S7 Driver now supports event and alarm handling on some S7 models
+
+Incompatible changes
+--------------------
+
+Bug Fixes
+---------
+
+PLC4X-200 OPC-UA Driver not connecting if params string is not provided
+PLC4X-201 OPC-UA PlcList underlying type not compatible with Eclipse Milo
+PLC4X-202 OPC-UA Driver cannot write Unsigned Types
+PLC4X-276 [S7] The most of the supported types don't work correctly
+PLC4X-278 Double Reading Error
+PLC4X-279 nioEventLoopGroup thread proliferation
+PLC4X-280 ADS route request swapped positions of route name and address
+PLC4X-291 DefaultPlcSubscriptionField cannot be cast to class OpcuaField
+PLC4X-298 [S7] When writing REAL values the Write
+ operation fails with an internal error
+PLC4X-299 Modbus - Kafka Connect Configuration
+PLC4X-312 CAN NOT READ STRING FROM S7 PLC
+PLC4X-314 CAN NOT WRITING MANY DATA TO S7 ONE TIME
+
+==============================================================
+Apache PLC4X 0.8.0
+==============================================================
+
+This is an ordinary PLC4X release, containing changes that
+accumulated over time. It doesn't have an explicit focus on
+a particular topic.
+
+New Features
+------------
+
+- The KNXnet/IP Driver now supports writing of values.
+
+- The Modbus driver now supports more common notations of
+ Modbus addresses using a pure-numeric notation.
+
+- The ADS, KNX, Modbus, S7 and simulated drivers have been
+ updated to support the IEC 61131-3 data-types.
+
+- We are now including PLC4Go as PLC4X implementation in
+ the programming language Go(lang)
+
+- Integration with the Milo OPC UA Server is now available.
+
+- Kafka Connect workers have been updated source and sink connectors
+ are now included.
+
+Incompatible changes
+--------------------
+
+- The syntax of the S7 addresses changed slightly allowing to
+ provide a string length. Without this, a STRING datatype will
+ read 254 characters, by adding the size in round brackets to
+ the type name will use the specified number.
+
+ Examples:
+
+ Read one String which is max 10 chars long:
+ %DB2:30:STRING(10)
+
+ Read an array of 3 Strings where each is max 10 chars long:
+ %DB2:30:STRING(10)[3]
+
+- The PLCValue types have been refactored to align with the types
+ defined in IEC 61131-3 (https://en.wikipedia.org/wiki/IEC_61131-3)
+ directly using the older Java types (PlcBoolean) is no longer
+ possible.
+
+Bug Fixes
+---------
+
+A lot of testing was done regarding the IEC 61131-3 data-types.
+This resulted in numerous bugfixes in many protocols.
+
+PLC4X-132 [S7] Communication to S7 PLC dies in some situations
+PLC4X-206 When writing short values exceptions are thrown
+ while preparing the write request.
+PLC4X-207 No registered handler found for message TPKTPacket[],
+ using default decode method - Communication with S7
+ and Modbus device hangs
+PLC4X-209 [S7] When writing INT and DINT values the Write
+ operation fails with an internal error
+PLC4X-210 [KNX] When running a KNX Tunneling Subscription
+ for a longer time there are packets that kill
+ the connection
+PLC4X-211 PlcValues seem to always return "true" on the
+ isXYZ" checks.
+PLC4X-212 When writing multiple values in one request the
+ item status is not correctly set
+PLC4X-213 [Modbus] The Modbus driver doesn't handle error
+ responses gracefully
+PLC4X-214 [Modbus] Holding register addresses have an offset
+ of 1 (Not reading the correct address)
+PLC4X-215 Drivers using the BaseOptimizer
+ (SingleFieldOptimizer) don't handle error responses
+ gracefully
+PLC4X-218 [Scraper] After stopping the scraper still the
+ statistics are logged and the application doesn't
+ terminate
+PLC4X-239 Read DTL (Date and Time)
+PLC4X-240 Protocol error in reading string
+PLC4X-246 S7 driver hangs on read
+PLC4X-245 [Modbus] Apache NiFi processor throws
+ java.io.IOException after a while
+PLC4X-255 Kafka Connector Source Task doesn't block within poll()
+ resulting in high CPU usage.
+PLC4X-261 Pooled connection manager returns a connection that isn't
+ connected in some situations.
+PLC4X-272 When splitting up large requests, too big sub-requests
+ are generated (S7)
+PLC4X-256 ReadBuffer truncate last byte of even small payloads
+PLC4X-262 Error in reading Array
+PLC4X-270 Ads driver does not accept double-digit array indexes
+
+==============================================================
+Apache PLC4X 0.7.0
+==============================================================
+
+This version is the first after a major refactoring of the driver
+core. All previous driver versions are now considered deprecated
+and have been replaced by versions using the new driver structure
+and generated driver codebase.
+
+New Features
+------------
+
+- Drivers now support structured types using PlcValues
+- The EIP (EtherNet/IP) driver no longer requires an external
+ library and is implemented fully in the PLC4X project
+- The Modbus driver no longer requires an external library
+ and is implemented fully in the PLC4X project
+- The new S7 Driver supports writing multiple entries in one
+ request (The API allowed this from the beginning now not
+ every item is wrapped in a single request. It should bring
+ significant performance gains when writing multiple values)
+- S7 Driver now supports String datatypes.
+- OSGi : Implementation of Drivers/Transports as OSGi services
+ to be able to use them in an OSGi container.
+- New Firmata protocol driver
+
+Incompatible changes
+--------------------
+
+- Due to the refactoring of the driver core there might be issues
+ running drivers built against older core versions.
+- This version doesn't provide a Beckhoff AMS/ADS driver as this
+ driver is still being ported to the new mspec format.
+- All drivers connection strings now follow the same pattern:
+ {protocol-code:(transport-code:)?//{transport-config}(?{params})?
+ Please check the drivers documentation on our website:
+ https://plc4x.apache.org/users/protocols/s7.html
+- The karaf-feature modules are removed as the drivers now all
+ provide both a feature.xml as well as a `kar` bundled archive
+
+Bug Fixes
+---------
+
+PLC4X-174 UDP Transport does not accept ports containing 0
+PLC4X-134 S7 is terminating the connection during handshake
+PLC4X-192 Support for conversion of complex connection string
+ parameters
+
+==============================================================
+Apache PLC4X 0.6.0
+==============================================================
+
+This is the last release of PLC4X with the "handwritten" drivers.
+This Minor release will thus receive updates and fixes until
+most users have switched to 0.7 and above (with generated drivers).
+
+If you are using the S7 Driver you should update to this Version
+as the critical (memory leak) bug PLC4X-163 is fixed.
+
+New Features
+------------
+- PLC4X-168 A shorter S7 Field Syntax is Introduced.
+This release contains no further features and mostly stabilization.
+
+Incompatible changes
+--------------------
+- Moved the C++, C# and Python drivers into the `sandbox`
+
+Bug Fixes
+---------
+- Fixed Promise Chain for InternalPlcWriteRequest
+- PLC4X-45 Add float support to Modbus Protocol
+- PLC4X-164 Fix wrong NOT FOUND exception in OPC UA Driver
+- PLC4X-166 Fixed Download Page
+- PLC4X-163 Fixed Netty ByteBuf Leaks for S7 Driver
+- PLC4X-158 Added Warning if no Pooled Driver is used for Scraper
+
+==============================================================
+Apache PLC4X 0.5.0
+==============================================================
+
+This is the first release containing our new generated drivers (AB-ETH)
+
+New Features
+------------
+
+- Implemented a new Apache Kafka Connect integration module
+- Implemented a new Apache NiFi integration module
+- Implemented a new Logstash integration module
+- Implemented a driver for the AB-ETH protocol
+- Implemented Apache Karaf features for S7 OSGI drivers
+- PLC4X-121 Develop Code Generation to allow Generated Drivers in multiple Languages
+
+Sandbox (Beta-Features)
+- Implemented a new BACnet/IP passive mode driver
+- Implemented a new Serial DF1 driver
+
+Incompatible changes
+--------------------
+
+Bug Fixes
+---------
+
+- PLC4X-104 S7 Driver Datatype TIME_OF_DAY causes ArrayOutOfBoundException
+- PLC4X-134 S7 is terminating the connection during handshake
+- PLC4X-139 PLC4X leaks sockets in case of connection problems
+- PLC4X-141 String with real length of greater 127 throw an exception
+- PLC4X-144 When requesting invalid addresses, the DefaultS7MessageProcessor produces errors
+
+==============================================================
+Apache PLC4X 0.4.0
+==============================================================
+
+This is the first release of Apache PLC4X as top-level project.
+
+New Features
+------------
+
+- The PlcConnection now supports a `ping` method to allow checking if an existing connection is still alive.
+- Support of the OPC-UA protocol with the `opc-ua-driver`.
+- Other Languages Support:
+-- Added first versions of a C# .Net PLC4X API (`plc4net`)
+-- Added first versions of a Python PLC4X API (`plc4py`)
+- Added an Interop server which allows to relay requests from other languages to a Java Server
+
+Incompatible changes
+--------------------
+
+- ElasticSearch example was updated to use ElasticSearch 7.0.1, this might cause problems with older Kibana versions.
+
+Bug Fixes
+---------
+
+
+==============================================================
+Apache PLC4X (incubating) 0.3.1
+==============================================================
+
+This is a bugfix-release, that fixes some problems with S7 driver.
+
+Bug Fixes
+---------
+
+- The S7 driver didn't correctly handle "fill-bytes" in multi-item read-responses and multi-item write-requests
+- PLC4X-83: fixed NPE when reading odd-length array of one-byte base types
+- PLC4X-82: renamed flags "F" to Siemens Standard "M" (Marker)
+- PLC4X-84: Fixed a bug in the DefaultS7MessageProcessor which didn't correctly merge together split up items
+
+
+==============================================================
+Apache PLC4X (incubating) 0.3.0
+==============================================================
+
+This is the third official release of Apache PLC4X.
+
+Some new features have been added (e.g. plc-scraper) multiple
+new integrations are included (apache-karaf, apache-calcite)
+and a lot of (technical) refactoring has been done to prepare
+future work on adapters in different languages.
+
+New Features
+------------
+
+- Object PLC Mapping (OPM) now has a Alias Registry to allow
+ variable substitution at runtime and write support
+- New module `plc-scraper` for applications that have to
+ scrape a lot of sps fields with high frequency
+- New integration `apache-karaf` to enable plc4j in a karaf
+ runtime environment
+
+Incompatible changes
+--------------------
+- The 'plc4j-core' module has been merged into 'plc4j-api'.
+ So there is no 'plc4j-core' module anymore. Just remove that
+ dependency.
+- The driver artifact names have changed so if you were using
+ a `plc4j-protocol-{name}` you now need to change this to
+ `plc4j-driver-{name}`
+
+Bug Fixes
+---------
+
+PLC4X-75 Fixing dependency to the wrap url-handler
+PLC4X-76 When receiving responses with more than 512 byte,
+ the IsoOnTcp protocol doesn't work
+PLC4X-77 When the last item in a request is a DINT, the
+ DefaultS7MessageProcessor dies
+PLC4X-78 Write operations seem to fail
+- Fixed a Bug where S7 was not able to read arrays.
+
+
+==============================================================
+Apache PLC4X (incubating) 0.2.0
+==============================================================
+
+This is the second official release of Apache PLC4X.
+
+Especially have we addressed all issues reported during
+our first release, that were of non-technical nature.
+These were tracked in:
+
+PLC4X-60 Fix findings by the last release
+
+New Features
+------------
+A new connection-pool was added, which allows automatic
+pooling and reuse of PLC connections.
+
+A new OPM module was added, which allows JPA like read-
+communication using POJOs, very similar to JPA.
+
+A stub of a new driver for the Emerson DeltaV protocol
+has been added, but is not yet a fully functional PLC4X
+driver. This is also a first test of our new `passive-
+mode-driver` concept.
+
+Incompatible changes
+--------------------
+
+We have refactored the API in order to eliminate the
+need of passing `x-requests` to `x-methods` and added
+an `execute` method to each request type. This greatly
+simplifies the client code. However this requires
+refactoring of applications using the direct PLC4X API.
+
+Miscellaneous changes
+---------------------
+
+We have increased the test coverage greatly and fixed
+a lot of little errors we found on the way.
+
+Known Issues
+------------
+
+Bug Fixes
+---------
+
+PLC4X-56 [S7] S7Field does not recognize addresses
+ with numElements present
+PLC4X-57 [S7] Response for address with numElements
+ contains only first item
+PLC4X-61 Installation fails plc4j-protocoll-ethernetip
+ needs license
+PLC4X-62 Modbus results deliver null-Value due to missing
+ implementation of getShort, getLong ...
+
+
+
+==============================================================
+Apache PLC4X (incubating) 0.1.0
+==============================================================
+
+This is the first official release of Apache PLC4X.
+It contains drivers for the following protocols:
+- Siemens S7comm (0x32)
+- Beckhoff ADS
+- Modbus
+- EtherNet/IP
+
+However the Siemens driver definitely is the most
+mature driver, the rest should be treated experimental.
+
+New Features
+------------
+
+PLC4X-29 [S7] Implement PDU Fragmentation
+PLC4X-39 Extend the Edgent integration with the new Subscription features of PLC4X
+
+Incompatible changes
+--------------------
+
+- NONE -
+
+Miscellaneous changes
+---------------------
+
+- NONE -
+
+Known Issues
+------------
+
+- NONE -
+
+Most drivers should be treated experimental and are not near production ready.
+The S7 driver is probably the furthest implemented and tested driver and hereby can be
+considered to be the most mature.
+
+Bug Fixes
+---------
+
+PLC4X-20 Jacoco doesn't seem to be working at all
+PLC4X-21 Code coverage doesn't seem to work
+PLC4X-47 S7 driver silently ignores surplus ReadRequestItems
+PLC4X-48 S7 driver fails to parse response with multiple items
Added: dev/plc4x/0.10.0/rc2/apache-plc4x-0.10.0-source-release.zip
==============================================================================
Binary file - no diff available.
Propchange: dev/plc4x/0.10.0/rc2/apache-plc4x-0.10.0-source-release.zip
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: dev/plc4x/0.10.0/rc2/apache-plc4x-0.10.0-source-release.zip.asc
==============================================================================
--- dev/plc4x/0.10.0/rc2/apache-plc4x-0.10.0-source-release.zip.asc (added)
+++ dev/plc4x/0.10.0/rc2/apache-plc4x-0.10.0-source-release.zip.asc Mon Oct 3 16:11:25 2022
@@ -0,0 +1,16 @@
+-----BEGIN PGP SIGNATURE-----
+
+iQIzBAABCgAdFiEE8VaBP/MVAH42umwTCJEnwVxg1rkFAmM7AvUACgkQCJEnwVxg
+1rnSOw//Xvp6HIRXM+0MW8q86GaA4Mey9umTJLiIr5PIFw71LtfTXiInas4Rr0HO
+ZQy0kJrfGMQKEGecvlu+0xKGu8Y9TIm47EnnE5Vi2V9uXSSQXVpSuGUOsXRs+ry1
+LrdXFfRuwfQXWJ0U6rT0beovlEa0DOzDuQxTDDkdqs0lvWEacZWKRvIFjyzzQhrl
+uv154n1MDPOpNMaq+gsQypkoEk7vFfCOzq21ixm2Pabx3Czp0iXjA6FXOzzPbjJF
+AuKXy0XIsd5ZvC/sjeAPQZNwOhS3hxsp1SSg2ZaaAo3KkA7j1uEJq91NivqUY/Wk
+IGMI9ifp1vp35EWonCSZvDmMVu0mP4mV/oLfQGSyjxsv+zIdtpKLfj4QFFolPddv
+fZzmtWPrv2/j9EGUKZGXclGgQTrFU6vKbZupmjyiZA6FAt3861Wo3xrNfipQqfLE
+OdEmI9cLCRViCScrpEfjEhN4p60ToIwdjop6YtjoK2MDKjSybdoHdIeJYYTyYIQa
+ApqbUPvAKt5AxjjDJd+kFguqx2mUVNDj+Av5w9tmFPoVmK7nGdmRRDFu3aE2ZOr2
+ErtHjRrT7H3EbWmf0lwSu6+VigdrFEKmbE2nJeFD9mQtJHbr7qdjJeqBbmUa8PQr
+L5WsqoVUDnsLxliaJGijbr7NsTNKr6/YZ2te/ITebGwhmlfFcbQ=
+=/+O/
+-----END PGP SIGNATURE-----
Added: dev/plc4x/0.10.0/rc2/apache-plc4x-0.10.0-source-release.zip.sha512
==============================================================================
--- dev/plc4x/0.10.0/rc2/apache-plc4x-0.10.0-source-release.zip.sha512 (added)
+++ dev/plc4x/0.10.0/rc2/apache-plc4x-0.10.0-source-release.zip.sha512 Mon Oct 3 16:11:25 2022
@@ -0,0 +1 @@
+ad8ba4a81f279cacb6d6ceddc5341d309696b06de3bb1942e320cb9aa4bf5183d62f4575ac0323641b5abbb6776d08c9239d8a5299aebbd91c8f2f95837c1eff
\ No newline at end of file