We are using a set of custom maven plugin to perform a pretty complex build. Unfortunately, several artifacts useful for benerator are only created in the test classes folder and, thus, not accessible by benerator - even when binding benerator plugin execution to the 'test' phase.
I think this issue is not an exceptional case, since these artifacts allow container-less application execution which is typical for testing and generally useful for test data generation (in terms of speed).
So I would be glad if there was a possibility to include test-scoped artifacts, e.g. a plugin configuration flag.