[jira] [Commented] (MNG-5791) slf4-api dissapears from classpath with 3.3.1

["Karim Drifi (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-5791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091752#comment-15091752 ] 

Karim Drifi commented on MNG-5791:
----------------------------------

Hello, I have the exact same issue but I don't understand how to deal with it. how can I use the plugin.artifact to create the classpath ? Can you show me a code example that replace "Thread.currentThread().getContextClassLoader();"

Sincerely yours,

Karim Drifi.

> slf4-api dissapears from classpath with 3.3.1
> ---------------------------------------------
>
>                 Key: MNG-5791
>                 URL: https://issues.apache.org/jira/browse/MNG-5791
>             Project: Maven
>          Issue Type: Bug
>          Components: Class Loading
>    Affects Versions: 3.3.1
>         Environment: OS X, Hotspot 1.7.0_75
>            Reporter: Stéphane Landelle
>
> I have a plugin where I fetch the classpath from the current thread's classloader: https://github.com/gatling/gatling-maven/blob/gatling-maven-parent-2.1.2/gatling-maven-plugin/src/main/java/io/gatling/mojo/GatlingMojo.java#L256
> slf4j-api is in the project's compile scope:
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ gatling-sample21
> ...
> [INFO] |  |  +- org.slf4j:slf4j-api:jar:1.7.10:compile
> ...
> Until maven 3.2.5 included, the slf4j-api is indeed in the current thread's classloader:
> uri=/Users/slandelle/.m2/repository/org/slf4j/slf4j-api/1.7.10/slf4j-api-1.7.10.jar
> But it's missing when running when 3.3.1. I checked that the parent Classloader is null. 
> This happens ONLY with slf4j-api! All the other project dependencies jars are properly passed.
> Please advise.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)