Thanks Ken...
I rechecked using my latest JG (essentially the 1.0.1 tag/branch) and the problem is still there.
I start with a JG 1.0+ server (with TinkerPop 3.7.0+)
using the same JG 1.0+ binaries (or any Gremlin binary 3.7.0+ with
JanusGraphGremlinPlugin plugin)
1) ext/plugins.txt WITH JanusGraphGremlinPlugin (janusgraph.imports)
2) run gremlin client/console
3) connect to JG server: ":remote connect tinkerpop.server conf/remote-objects.yaml session" (uses GraphBinary with serializeResultToString = true)
4) run ":remote console" (to send commands to the remote by default)
5) run "JanusGraphFactory.getGraphNames();"
6) error "Gremlin Server must be configured to use the JanusGraphManager"
(this is because the console executed the local method which of course has no Gremlin/Janus server)
7) run ":>
JanusGraphFactory.getGraphNames();" and I get the graph names as expected.
My current work-around is to simply remove "JanusGraphGremlinPlugin" from "plugins.txt" and the gremlin console executes remotely like it should.
\
For some reason, when the gremlin groovy console finds the "JanusGraphFactory" locally it executes it, ignoring the ":remote console" state.
I also tested with an old Janus 0.6.2 client (TinkerPop 1.21.0) and oddly that client worked as expected.
So it seems an issue with a TinkerPop 3.7.0+ client to a TinkerPop 3.7.0+ server.
To add the Janus plugin (to a gremlin binary), I just drop the Janus core and driver jar files to the gremlin lib.