Yeah … We should start compiling such a thing … good point. I added a top-section to our RELEASE_NOTES document that will keep track of such changes.
Thanks, Chris Datum: Freitag, 23. November 2018 um 18:55 Do you have a changelog or upgrading document? Maybe you should, if this is going to break next release On November 23, 2018 at 12:47:31, Christofer Dutz ([email protected]<mailto:[email protected]>) wrote: Hi all, as we just ran into this problem: We have recently worked on splitting up the driver modules into drivers and protocol implementations. The reason for this is that this way we can separate the different protocol layers more easily and we can produce different variants of drivers more easily. So for example we can now provide a Modbus-TCP and a Modbus-SERIAL driver without having to pull in the whole set of dependencies for all variants (You probably only use one of them). As a result of this in the project structure we now have not only: * Api * Protocol * Utils But now also a * Drivers Part of the repo. In order to use the s7 driver, you need to adjust the artifact-id of the driver from “plc4j-protocol-s7” to “plc4j-driver-s7” (please adjust the other driver names accordingly) Also did we recently merge the API and the Core module. Now all you need to include in order to implement a PLC4X application, is to reference the API module, because this now also contains the DriverManager. So if you are referencing the core module, you should probably remove it soon. So much for the refactorings. Chris
