General purpose things can go in the "helper" packages in the controller-client module; that module and jboss-dmr are the core management API.[1] Anything that goes in controller-client though, we have to be extremely anal as it's a forever commitment. Everything has to be in the perfect package with the perfect class name and method name. (I admit it's probably not perfect yet.) E.g. the cli's Util.getDeployments(ModelControllerClient) will only work against standalone so if it becomes public API it has to be in the helpers.standalone package. And I don't want anything that calls into subsystems in controller-client. [1] I'd thought about a separate module for helper stuff (what's currently in the o.j.a.controller.helpers packages in controller-client) but in the end we are committing to those APIs and they don't introduce new dependencies, so I didn't see any benefit to a separate module. On 4/13/11 10:09 AM, André Dietisheim wrote: -- Brian Stansberry Principal Software Engineer JBoss by Red Hat