No comments, so I'm going to go with "A) Keep two versions of this profile.xml file in the source tree". Looking at how these files end up in the various configs, it's a bit untidy so I'm going to clean up a bit. The following current content in the server module's src/etc/conf ends up creating the content in the conf dir of each config. | |-- default | | |-- bootstrap | | | |-- aop.xml | | | |-- bindings.xml | | | |-- classloader.xml | | | |-- deployers.xml | | | |-- jmx.xml | | | |-- logging.xml | | | |-- profile.xml | | | `-- vfs.xml | | |-- bootstrap-minimal.xml | | |-- bootstrap.xml | | |-- java.policy | | |-- jax-ws-catalog.xml | | |-- jboss-log4j.xml | | |-- jboss-minimal.xml | | |-- jboss-service.xml | | |-- jndi.properties | | |-- login-config.xml | | |-- props | | | |-- jbossws-roles.properties | | | |-- jbossws-users.properties | | | |-- jmx-console-roles.properties | | | `-- jmx-console-users.properties | | |-- standardjboss.xml | | |-- standardjbosscmp-jdbc.xml | | `-- xmdesc | | |-- AttributePersistenceService-xmbean.xml | | |-- ClientUserTransaction-xmbean.xml | | |-- JNDIView-xmbean.xml | | |-- Log4jService-xmbean.xml | | |-- NamingBean-xmbean.xml | | `-- NamingService-xmbean.xml | |-- standard | | |-- ear-deployer-jboss-beans.xml | | |-- jboss-service.xml | | `-- jndi.properties | `-- web | |-- jboss-service.xml | `-- jmx-invoker-service.xml | Without objection, I'm going to: 1) Rename "default" to "all". This drives the creation of the "all" config and is the foundation for "default", "web" and "standard". 2) Replace all/bootstrap/profile.xml with the clustered version. 3) Create a new default/bootstrap folder containing the non-clustered profile.xml. 4) Change the build/build.xml to use 3) in the "default" config, inherited by "web" and "standard". 5) Create a new "minimal" dir under conf. 6) Move bootstrap-minimal and jboss-minimal to it (and rename them), rather than leaving them grouped with "all". 7) Change build/build.xml to reflect 6) in the "minimal" config build. Basically, make the organization of the files reflect the way build/build.xml consumes them. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224154#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...