I see you've found my dirty laundry. :D Making our hack CL static isn't muddying the waters any further, though; I should have had the forethought to do that in the first place. "guignome" wrote : Ideally, jbossall-client should be defined as a maven dependency No, the Plugin here needs to work with whatever version of jbossall-client is present in the user's installation, and the dependency would bind the Mojo to a particular AS version. The genesis of that hack is to address a configuration property in the POM of the control-example: <!-- Include jbossall-client.jar on the CP --> | <additionalClasspathElements> | <additionalClasspathElement>${JBOSS_HOME}/client/jbossall-client.jar</additionalClasspathElement> | </additionalClasspathElements> ...which doesn't seem to be getting picked up. If that worked as advertised we could ditch the whole TCL replacement BS. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181667#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...