David Pitera commented on TINKERPOP-1900:

>From a cursory glance it seems that the ones that might be useful are the 
>Helpers/Utilities/Factories/Abstract setup classes (classes that are not 
>specific tests for specific classes in the TinkerPop project), so for example:






This is not an exhaustive list. Also, I think you can just package the entire 
test directory using this technique: 
 YMMV but I don't think it'll be too beefy. Didn't look too in-depth at the 
plugin but maybe you can specify a sub-dir and move just the helpers and what 
not there.

> Jar gremlin server /src/test directory
> --------------------------------------
>                 Key: TINKERPOP-1900
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1900
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: server
>    Affects Versions: 3.2.7
>            Reporter: David Pitera
>            Priority: Major
> There are utility classes inside the /src/test directory that would be useful 
> for implementor's implementing internal sever components (for example, one 
> implementing a Channelizer might make use of 
> AbstractGremlinServerIntegrationTest and TestClientFactory). If we update the 
> packaging so that the gremlin-server jars include these binaries, 
> implementor's can make use of existing code without duplicating it.

This message was sent by Atlassian JIRA

Reply via email to