Apologies for the delayed response. What would folks think about moving the org.apache.pirk.test package in src/main/java to src/test/java (rename/refactor the package appropriately) and then use the maven-jar-plugin to create a test-jar from which we run the distributed tests?
That would seem to resolve the test class issues (some of the src/test/java tests relying on classes in src/main/java) and allow the responder to be refactored appropriately. On Thu, Oct 20, 2016 at 12:22 AM, Darin Johnson <[email protected]> wrote: > I threw up a WIP for phase 1 of the submodule refactor. This involved > pulling out the pieces for the storm, spark, and mapreduce responsers. > Mostly ran into some difficulties of hard coded conditionals for each > framework in DistributedTestSuite and/or BaseTests. > > The next logical module to pull out is Responder. However, in order to do > so we need to pull DistributedTestSuite and BaseTests. While this seems OK > with the main code base, it's not so with the test code base as a few of > the tests explicitly rely on BaseTests and Inputs. > > I'd like to get some comments on where people believe the BaseTests and > Inputs Classes belong within the code base, so that I can plan this out > accordingly. >
