Replies: 4 comments 2 replies
-
It has been upgraded in the |
Beta Was this translation helpful? Give feedback.
-
You might be able to use the Maven Shade (or gradle "Shadow") plugin to combine and repackage the Modbus library and its dependencies. Or to some other effect. |
Beta Was this translation helpful? Give feedback.
-
I'll evaluate upgrading |
Beta Was this translation helpful? Give feedback.
-
@syllamoh sorry, this can't be done in 0.6.x, see #1362 (comment) You'll have to figure out some trickery with shade or use the Milo |
Beta Was this translation helpful? Give feedback.
-
Hello
I'm using "eclipse-milo" (latest) library in my application. I want to use "com.digitalpetri.modbus:modbus-tcp:2.0.0" to handle modbus connectivity. But I'm having issue with package naming-mismatch. "eclipse-milo" comes with "com.digitalpetri.fsm:strict-machine:0.9" which define the interface FsmContext in the package "com.digitalpetri.strictmachine". It seems you have renamed this package as "com.digitalpetri.fsm" in the release "com.digitalpetri.fsm:strict-machine:1.0.0".
Hence "eclipse-milo" and "modbus-tcp" don't seem to work well together.
Do you project to upgrade "eclipse-milo" with "com.digitalpetri.fsm:strict-machine:1.0.0" or do you have any advice to deal with this issue?
Thanks you in advance
Beta Was this translation helpful? Give feedback.
All reactions