[
https://jira.codehaus.org/browse/MNG-5791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=365559#comment-365559
]
Jason van Zyl commented on MNG-5791:
------------------------------------
Yes, in process you can use the thread context classloader but while forking
you want to use plugin.artifacts to create the classpath. I have a few blog
entries left to write to I'll include one about this change.
> slf4-api dissapears from classpath with 3.3.1
> ---------------------------------------------
>
> Key: MNG-5791
> URL: https://jira.codehaus.org/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: Stephane 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.1.6#6162)
