[
https://issues.apache.org/jira/browse/ACCUMULO-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Tubbs resolved ACCUMULO-2165.
-----------------------------------------
Resolution: Fixed
I think the underlying issue is resolved. The plugin cannot get the classpath
the same way as a regular Accumulo instance... as that defeats the whole point
of the plugin. It needs to get it from the build environment instead.
> maven-plugin's classpath is not assembled similarly to a real accumulo or mac
> -----------------------------------------------------------------------------
>
> Key: ACCUMULO-2165
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2165
> Project: Accumulo
> Issue Type: Bug
> Components: maven-plugin
> Reporter: John Vines
> Assignee: Christopher Tubbs
> Fix For: 1.6.0
>
>
> the maven plugin uses AbstractAccumuloMojo#configureMiniClasspath to assemble
> the classpath. All it does it get the list of artifacts in the order reported
> by project.getArtifacts(), which includes maven dependencies, including the
> sisu forks of guice and guava. This causes the maven-plugin to use a heavily
> bastardized classpath which is both out of order of normal accumulo
> classpaths but also with additional libraries injected.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
