Hi all I just updated the Apache master pom as it has just been released in a new version yesterday. While at it, I checked the plugins and updated these to the most recent versions.
After that I cleaned up in the dependencies, by introducing version-properties for common libraries and defining them in a dependencyManagement section in the plc4x parent pom. I moved the version definition of those modules up that are common to multiple modules. As multiple modules will be sharing Netty for example, that version is now managed by the root, but Edgent and Camel is still managed inside the integration module. I did notice some strange dependencies and thought this would be a good use-case for the dependency plugins “analyse” goal. This reports used transitive dependencies, that are not explicitly imported. This is now treated as an error as well as dependencies that are imported and not used. Also if the scope is wrong, the tool will also complain (test-dependency imported as compile, compile that should be runtime, … stuff like that) From 10 years of maven experience this is a teenieweenie little pain in the a**, but it’s a huge relief in preventing even worse problems later on. Chris
