Re: [integration-dev] Repo Location - Java OpenFlow Controller Benchmarking Tool
yes, this sounds reasonable. But I would prefer placing the tool into openflowplugin repository as:
1. there are more committers - so the development (and reviews) will be more swift,
2. openflowplugin already hosts a few applications in their repository.
By the way, are there more commits except for  ? Because I can see no dependency on openflowjava in pom.xml.
From: Williams, Marcus <marcus.williams@...>
Sent: 27 October 2015 18:36
Cc: integration-dev@...; Jamo Luhrsen
Subject: [integration-dev] Repo Location - Java OpenFlow Controller Benchmarking Tool
Raksha has been working on a Java OpenFlow Controller Benchmarking Tool  (I’m sure many of you have seen her emails come across the wire).
The patches have been pushed to Integration/Test, mainly because that is where the tool will be utilized. It has since been noted that Integration/Test does not have infrastructure (java focused Jenkins jobs to verify/build etc.) to handle Java based patches and except for myself there are few to do reviews on Java code.
Discussion has focused on the possibility of moving the tool into the openflowjava repo, as the tool uses openflowjava as a dependency and it could be thought of as a more ‘advanced’ client using openflowjava lib.
Does this sound reasonable?
/** Marcus */
SDN Controller Team
Software Defined Networking Division
Network Platforms Group