[ 
https://issues.apache.org/jira/browse/CXF-5172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kevin Ternes updated CXF-5172:
------------------------------

    Description: 
The build includes a dependency on slf4j-jdk14.  This jar appears in the built 
binary lib folder and in Maven:
{code:xml}
<dependency>
  <groupId>org.slf4j</groupId>
  <artifactId>slf4j-jdk14</artifactId>
</dependency>
{code}

This causes SL4j to bind to the jdk14 logger irrespective of the configuration 
of the application using Apache-CXF.  A better dependency would be on only the 
sl4j-api instead.  

This was an issue several years ago in CXF-2583.

  was:
The build includes a dependency on slf4j-jdk14.  This jar appears in the built 
binary lib folder and in Maven:
{code:xml}
<dependency>
  <groupId>org.slf4j</groupId>
  <artifactId>slf4j-jdk14</artifactId>
</dependency>
{code}

This causes SL4j to bind to the jdk14 logger irrespective of the configuration 
of the application using Apache-CXF.  A better dependency would be to bind to 
the sl4j-api instead.  

This was an issue several years ago in CXF-2583.

    
> sl4j binds to slf4j-jdk14
> -------------------------
>
>                 Key: CXF-5172
>                 URL: https://issues.apache.org/jira/browse/CXF-5172
>             Project: CXF
>          Issue Type: Improvement
>          Components: Build system, Configuration
>    Affects Versions: 2.7.6
>            Reporter: Kevin Ternes
>            Priority: Minor
>
> The build includes a dependency on slf4j-jdk14.  This jar appears in the 
> built binary lib folder and in Maven:
> {code:xml}
> <dependency>
>   <groupId>org.slf4j</groupId>
>   <artifactId>slf4j-jdk14</artifactId>
> </dependency>
> {code}
> This causes SL4j to bind to the jdk14 logger irrespective of the 
> configuration of the application using Apache-CXF.  A better dependency would 
> be on only the sl4j-api instead.  
> This was an issue several years ago in CXF-2583.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to