It seems there is no usage of this LocatorServerConfigurationRule. It does look like a duplicate.
On Thu, Feb 16, 2017 at 4:37 PM, Anilkumar Gingade <aging...@pivotal.io> wrote: > I had similar rule added for locator startup...where you can start locator > by passing required properties. > Look for: LocatorServerConfigurationRule (we can remove this, instead of > having duplicate rules) > > -Anil. > > > > > On Thu, Feb 16, 2017 at 2:26 PM, Jinmei Liao <jil...@pivotal.io> wrote: > > > We've created a few JUnit rules to ease the pain of starting up > > locator/servers in different vms. Please check these rules out: > > > > LocatorServerStartupRule: > > this rule will allow you to easily start up locator/server in a give VM > > with the properties you would like to configure them, and get the > member's > > name, port, working directory back to work with. To use this rule, your > > dunit test DO NOT need to extend Junit4DistributedTest class. > > > > LocatorStartupRule: > > This will allow you to start up a locator in the current VM. good for > > integration tests. > > > > ServerStrartupRule: > > This will allow you to start up a server in the current VM. good for > > integration tests. > > > > GfshShellConnectorRule: > > This will give allow you to connect to a give jmx manager or a locator > and > > easily execute gfsh command with it. > > > > MBeanServerConnectorRule > > This will allow you to directly connect to the jmx manager using mbean > > connection. > > > > Please let me know if you run into problems when using these rules. There > > is always room for improvement. > > > > -- > > Cheers > > > > Jinmei > > > -- Cheers Jinmei
