keith-turner commented on issue #7: URL: https://github.com/apache/accumulo-proxy/issues/7#issuecomment-1307833562
@DomGarguilo Fluo is multi-module project like Accumulo, its config may be a bit more complicated than you need. So the base pom defines the plugin below https://github.com/apache/fluo/blob/44e134a9d90685b57fc60a8bcc9a8919e79e4e3b/pom.xml#L294-L333 Then in a module plugin it actives it as follows. It does this in a profile so that when test are not running it does not start miniaccumulo. https://github.com/apache/fluo/blob/44e134a9d90685b57fc60a8bcc9a8919e79e4e3b/modules/integration-tests/pom.xml#L116-L133 Its important to define the accumulo,hadoop, zk, and thrift versions outside the plugin. The maven plugin is built against Accumulo 2.0 and if this is not done it may use older version in the launched processes. https://github.com/apache/fluo/blob/44e134a9d90685b57fc60a8bcc9a8919e79e4e3b/modules/integration-tests/pom.xml#L28-L29 The following code gets creates an accumulo client in the test. It uses the client properties file created by mini accumulo that the plugin started. https://github.com/apache/fluo/blob/44e134a9d90685b57fc60a8bcc9a8919e79e4e3b/modules/integration-tests/src/main/java/org/apache/fluo/integration/ITBase.java#L89 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
