-
Notifications
You must be signed in to change notification settings - Fork 19
Expand file tree
/
Copy pathRELEASE_NOTES
More file actions
91 lines (78 loc) · 3.28 KB
/
Copy pathRELEASE_NOTES
File metadata and controls
91 lines (78 loc) · 3.28 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
==============================================================
(Unreleased) Apache PLC4X 1.0.0-SNAPSHOT
==============================================================
New Features
------------
- PLC4X Server: Now supports TLS as a transport (the default).
When no keystore is configured, the server generates an
ephemeral self-signed certificate on startup and logs its
SHA-256 fingerprint so clients can pin/trust it. Plaintext TCP
remains available as an explicit opt-in
(plc4x.server.plaintext=true).
- PLC4X Server: Now enforces mandatory username/password
authentication; no operation is permitted before a successful
auth handshake. If no credentials are configured, the server
starts with the default user "toddy" and a generated secure
password that is printed to the console once at startup.
Configured credentials are never logged.
- Go: Upgraded to Go 1.26 and re-synced to the latest upstream
PLC4X.
Incompatible changes
--------------------
- Dropped support for older Java versions, new baseline Java
version is Java 21.
- Migrated the build to Apache Maven 4.
- The S7-Event integration ("s7event") is out of sync with the
refactored (SPI3) driver and has been disabled; it is no longer
built or shipped.
- PLC4X Server: Was migrated from the SPI2 (Netty) core to SPI3.
It now listens via a plain ServerSocket/SSLServerSocket and no
longer depends on Netty.
- PLC4X Server: Authentication is now mandatory and TLS is the
default transport. Existing clients must provide credentials
and connect via TLS (or explicitly opt into plaintext). See the
matching note in the core 'plc4x' driver release notes.
Changed Maven Coordinates
-------------------------
- The Maven groupId of ALL extras modules changed from
"org.apache.plc4x" to "org.apache.plc4x.extras" so the extras
artifacts no longer collide with the main PLC4X repo. The
artifactIds are unchanged. Every consumer must update the
groupId in their dependency coordinates.
Bug Fixes
---------
- Kafka: The source and sink tasks no longer leak the connection
cache they create. Stopping a task now closes its
PlcConnectionCache, releasing the cached PLC connections.
- PLC4X Server: The connection cache is now created on start()
and closed on stop(), so stopping the server releases the
cached PLC connections instead of leaking them.
- OPC UA Server: The backend now closes its connection cache on
shutdown, and when its driver manager is replaced, instead of
leaking the cached PLC connections.
- PLC4X Server: Exclude BouncyCastle JAR signatures from the
shaded jar to avoid class-loading/verification errors when
loading the shaded artifact.
==============================================================
Apache PLC4X 0.13.1
==============================================================
New Features
------------
- Updated to Apache PLC4X 0.13.1
Incompatible changes
--------------------
Bug Fixes
---------
==============================================================
Apache PLC4X 0.13.0
==============================================================
New Features
------------
- NiFi: Added NiFi 2 support
Incompatible changes
--------------------
- NiFi: Deprecate the non-record based processors
- NiFi: Removed internal Avro Schemas
Bug Fixes
---------
- NiFi: Integration - Fix array reading (#423)