One thing on the agenda for next week is moving towards a canonical server configuration model where the profile service repository has one jar/deployment regardless of how many configurations its used in. Related tasks: Define initial persistent format of the profile repository https://jira.jboss.org/jira/browse/JBAS-3768 OSGi Bundle Repository support https://jira.jboss.org/jira/browse/JBAS-4363 http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040005 Refactor the conf/jboss-service.xml services ; should be remove conf/jboss-service.xml https://jira.jboss.org/jira/browse/JBAS-4814 Split system and application deployments https://jira.jboss.org/jira/browse/JBAS-5954 Re-package system deployments https://jira.jboss.org/jira/browse/JBAS-5955 The first hurdle is updating the build to produce a repository of jars/deployments, and then properly describing: - the class dependency requirements for deployments - the association of deployments with profile service configurations; (minimal, default, all, ...) This is what I'm starting to look at. How this is split up for what gets done for the 5.0.0.GA, EAP and future 5.1 releases is an issue as well since we are pressed to get the 5.0.0.GA/EAP out. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176870#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...