://issues.apache.org/jira/browse/RAT-158
Le mardi 3 février 2015 23:31:24 Igor Fedorenko a écrit :
MavenPluginManager#setupPluginRealm imports parameter is not used in
any meaningful way. No matter what packages are passed in, the created
plugin realm will have access to all classes from the provided parent
/maven-site-plugin/dependencies.html
[1] https://issues.apache.org/jira/browse/RAT-158
Le mardi 3 février 2015 23:31:24 Igor Fedorenko a écrit :
MavenPluginManager#setupPluginRealm imports parameter is not used in
any meaningful way. No matter what packages are passed in, the created
plugin realm
MavenPluginManager#setupPluginRealm imports parameter is not used in
any meaningful way. No matter what packages are passed in, the created
plugin realm will have access to all classes from the provided parent
classloader. I did some more digging and looks like this is how Maven
behaved for last
Le mardi 3 février 2015 16:42:47 Igor Fedorenko a écrit :
Does anyone have a usecase that demonstrates use of
MavenPluginManager#setupPluginRealm imports parameter? I've found
DefaultMavenReportExecutor from maven-reporting-exec, which provides
list of imported packages, but not sure how
Does anyone have a usecase that demonstrates use of
MavenPluginManager#setupPluginRealm imports parameter? I've found
DefaultMavenReportExecutor from maven-reporting-exec, which provides
list of imported packages, but not sure how to use it from a project.
From what I can tell, this parameter
