Don't expose jboss-logging-annotations

[lrozenblyum]

Description

Currently quarkus-core exposes transitive dependency on jboss-logging-annotations to other projects (due to usage of the default compile scope).

1. According to the official doc https://jboss-logging.github.io/jboss-logging-tools/ it should be provided
2. Currently it causes inconvenience: for example users of keycloak-services 26.1.0 which depends on quarkus-core:3.15.2 which brings jboss-logging-annotations:3.0.1.Final that causes compilation errors (most likely due to the bug: The annotation module should have a runtime dependency on jboss-logging jboss-logging/jboss-logging-tools#127). A workaround exists to set the dependency management for jboss-logging-annotations to 3.0.3.Final.

Yet it seems that it would be better to avoid exposing the jboss-logging-annotations at all.

Implementation ideas

Declare jboss-logging-annotations as provided dependency for quarkus-core

[gsmet]

@dmlloyd WDYT?

[dmlloyd]

Agreed, the annotations should be provided (in the dependencyManagement section when possible). Additionally, the jboss-logging-processor should not appear in the dependency list or dependencyManagement. Instead it should be given as an argument to annotationProcessorPaths in the configuration of the base maven-compiler-plugin execution (like this example in jboss-threads) in any module which uses it.