between M3 & M4, classes from org.jboss.deployers.spi package were moved from jboss-integration.jar to jboss-deployment.jar & classes from org.jboss.profileservice.spi package were moved from jboss-integration.jar to jboss-profileservice-spi.jar

Here's the classes that are no longer in jboss-integration.jar that used to be in that jar in AS6 M3 and piror:

org/jboss/deployers/spi/management/ContextStateMapper.class
org/jboss/deployers/spi/management/DelegatingComponentDispatcher.class
org/jboss/deployers/spi/management/deploy/DeploymentID.class
org/jboss/deployers/spi/management/deploy/DeploymentManager.class
org/jboss/deployers/spi/management/deploy/DeploymentOptions.class
org/jboss/deployers/spi/management/deploy/DeploymentProgress.class
org/jboss/deployers/spi/management/deploy/DeploymentStatus.class
org/jboss/deployers/spi/management/deploy/DeploymentStatus$CommandType.class
org/jboss/deployers/spi/management/deploy/DeploymentStatus$StateType.class
org/jboss/deployers/spi/management/deploy/DeploymentTarget.class
org/jboss/deployers/spi/management/DeploymentTemplate.class
org/jboss/deployers/spi/management/deploy/ProgressEvent.class
org/jboss/deployers/spi/management/deploy/ProgressListener.class
org/jboss/deployers/spi/management/KnownComponentTypes.class
org/jboss/deployers/spi/management/KnownComponentTypes$ConnectionFactoryTypes.class
org/jboss/deployers/spi/management/KnownComponentTypes$DataSourceTypes.class
org/jboss/deployers/spi/management/KnownComponentTypes$EJB3.class
org/jboss/deployers/spi/management/KnownComponentTypes$EJB.class
org/jboss/deployers/spi/management/KnownComponentTypes$JMSDestination.class
org/jboss/deployers/spi/management/KnownComponentTypes$JPA.class
org/jboss/deployers/spi/management/KnownComponentTypes$MBean.class
org/jboss/deployers/spi/management/KnownComponentTypes$MCBean.class
org/jboss/deployers/spi/management/KnownComponentTypes$Server.class
org/jboss/deployers/spi/management/KnownComponentTypes$Web.class
org/jboss/deployers/spi/management/KnownDeploymentTypes.class
org/jboss/deployers/spi/management/ManagementView.class
org/jboss/deployers/spi/management/NameMatcher.class
org/jboss/deployers/spi/management/RuntimeComponentDispatcher.class
org/jboss/profileservice/spi/DeploymentContentFlags.class
org/jboss/profileservice/spi/DeploymentOption.class
org/jboss/profileservice/spi/DeploymentRepository.class
org/jboss/profileservice/spi/DeploymentRepositoryFactory.class
org/jboss/profileservice/spi/metadata/ProfileDeploymentMetaData.class
org/jboss/profileservice/spi/metadata/ProfileKeyMetaData.class
org/jboss/profileservice/spi/metadata/ProfileMetaData.class
org/jboss/profileservice/spi/metadata/ProfileSourceMetaData.class
org/jboss/profileservice/spi/metadata/SubProfileMetaData.class
org/jboss/profileservice/spi/ModificationInfo.class
org/jboss/profileservice/spi/ModificationInfo$ModifyStatus.class
org/jboss/profileservice/spi/MutableProfile.class
org/jboss/profileservice/spi/NoSuchDeploymentException.class
org/jboss/profileservice/spi/NoSuchProfileException.class
org/jboss/profileservice/spi/Profile.class
org/jboss/profileservice/spi/ProfileDeployment.class
org/jboss/profileservice/spi/ProfileFactory.class
org/jboss/profileservice/spi/ProfileKey.class
org/jboss/profileservice/spi/ProfileRepository.class
org/jboss/profileservice/spi/ProfileService.class
org/jboss/profileservice/spi/types/ControllerStateMetaType.class

The org.jboss.deployers.spi classes appear to have been moved to jboss-deployment.jar, and the org.jboss.profileservice.spi classes are nowhere to be found in any of the jars under the the JBOSS_HOME/client/ dir, but can be found in the JBOSS_HOME/common/lib/jboss-as-profileservice.jar,

This broke the RHQ/JON as5 plugin which uses a bunch of the classes under both of these packages (org/jboss/profileservice/spi/ProfileService and org/jboss/deployers/spi/management/deploy/DeploymentManager, to name a couple of the most important ones). The as5 plugin adds the following set of jars to its classloader in order to find the classes it needs to connect to and use the Profile Service remotely:

private static final List<String> CLIENT_JARS = Arrays.asList(
// NOTE: The jbossall-client.jar aggregates a whole bunch of other jars from the client dir via its
// MANIFEST.MF Class-Path.
"client/jbossall-client.jar",
"client/trove.jar",
"client/javassist.jar",
"common/lib/jboss-security-aspects.jar",
"lib/jboss-managed.jar",
"lib/jboss-metatype.jar",
"lib/jboss-dependency.jar"
);

So as of AS6 M4, this set of jars no longer contains all of the required classes.

We can add client/jboss-deployment.jar and common/lib/jboss-as-profileservice.jar to this set of jars to get RHQ working with M4, but there are some fixes that should be made to JBAS before the final release:

1) jboss-deployment.jar should be added to the manifest classpath of jbossall-client.jar, since it contains mgmt client API classes.
2) the classes in common/lib/jboss-as-profileservice.jar from the org.jboss.profileservice.spi package also need to be made available in some jar under the client dir (perhaps jboss-profileservice-client.jar?), since they are mgmt client API classes. Whatever jar they are moved to should be included in the manifest classpath of jbossall-client.jar.
3) client/trove.jar, client/javassist.jar, common/lib/jboss-security-aspects.jar, lib/jboss-managed.jar, lib/jboss-metatype.jar, lib/jboss-dependency.jar should all be added to jbossall-client.jar's manifest classpath, since they are all required jars for a management client.