aflierl commented on issue #125: URL: https://github.com/apache/plc4x-extras/issues/125#issuecomment-3909153121
I haven't made a PR yet because I wanted to check the root cause of this. While explicitly listing the dependencies (again) fixes the symptoms, the actual issue is that the build *should* correctly resolve these dependencies from the PLC4X main project but does not. After digging around in POMs for a few hours, I realized there is a severe artifactId conflict between the main PLC4X project and PLC4X-extras. Both define a `tools` module with `<artifactId>plc4j-tools</artifactId>`. PLC4X: https://github.com/apache/plc4x/blob/develop/plc4j/tools/pom.xml PLC4X-extras: https://github.com/apache/plc4x-extras/blob/develop/plc4j/tools/pom.xml This creates ambiguity during the build *and on Maven Central* so I fear the releases are broken since when this change was introduced. I would suggest to rename the one in PLC4X-extras to `plc4j-extras-tools`. If you are OK with that, I can make a PR with that. Against which branch should I make the PR? (i.e. do you want this fixed as a 0.13.2 or 0.14.x release) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
