DeploymentManagerImpl.start() causes TCK porting layer to fail

The latest JBoss 5 head causes the TCK porting layer to fail when deploying stuff on the server.

This is caused by the fact that the porting layer was built over an incomplete JBoss deployment SPI layer, which, interesting enough, made it work OK. Now that the implementation has been completed and JMXTarget.start() turned from a noop into a method with actual behavior, it tries to invoke MainDeployer.start(), which is NOT a JMX managed operation, and hence:

ReflectionException: null Cause: java.lang.NoSuchMethodException: Unable to find operation start(java.lang.String)

The fact that MainDeployer doesn't expose its start() method as a JMX operation is logical: start() is called from inside deploy(), so there's no need to invoke it externally.