You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2018/02/22 21:21:00 UTC
[jira] [Commented] (TINKERPOP-1900) Jar gremlin server /src/test
directory
[ https://issues.apache.org/jira/browse/TINKERPOP-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16373468#comment-16373468 ]
stephen mallette commented on TINKERPOP-1900:
---------------------------------------------
I guess I can agree that some of those classes might be helpful. You named two specific classes but, do you have a full list of test classes you would want to have?
tbh, i don't really like the idea of putting test classes in the main packaging, but let's see just which classes you think would be useful first before i generate any solid opinion.
> 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
(v7.6.3#76005)