If I not manage it myself - I cannot use maven-enforce-plugin to ensure dependency convergence in my dependencies.
If you want to use the convergence rule I would say it is only fair enough that you manage it yourself. IMO the plugin behaves not correct anyways. If you would specify explicitly a dependency to hibernate-core and hibernate-commons-annotations I could understand a failure, but in this case you only depend on hibernate-core in which case the normal dependency resolution should apply.
Several Hibernate projects depend on hibernate-commons-annotations, we can hardly release all projects always at the same time just to ensure all dependencies are in sync.
If anything I consider this an issue of HCANN. Maybe the dependency to jboss-logging should be marked as provided.
If you want to use the convergence rule I would say it is only fair enough that you manage it yourself. IMO the plugin behaves not correct anyways. If you would specify explicitly a dependency to hibernate-core and hibernate-commons-annotations I could understand a failure, but in this case you only depend on hibernate-core in which case the normal dependency resolution should apply.
Several Hibernate projects depend on hibernate-commons-annotations, we can hardly release all projects always at the same time just to ensure all dependencies are in sync.
If anything I consider this an issue of HCANN. Maybe the dependency to jboss-logging should be marked as provided.