Tim, Ovidiu Thank you for your very helpful comments and help in getting me started on this task! Some replies: 1. Making use of release-admin.xml directly makes sense from the point of view of centralizing the code to create configurations. However, at present, we are pulling only pulling in jboss-messaging.jar into testsuite/thirdparty from repository.jboss.com, and don't have direct access to release-admin.xml. We are looking for a way to set up the configuration which makes life easy as well as being well-suited to the existing testsuite organization. 2. The JBAS build and testsuite makes use of a number of names for directories relating to JMS and the existing JBossMQ implementation: trunk/messaging trunk/testsuite/src/main/jms trunk/testsuite/src/main/jmsra trunk/testsuite/src/main/jbossmq trunk/tetstsuite/src/resources/messaging trunk/testsuite/src/resources/jbossmq In incorporating these new Messaging tests, I tentatively chose the name messaging5 to be used as a basis for naming directories, files, and other related things. trunk/testsuite/src/main/messaging5 trunk/testsuite/src/resources/messaging5 .... This would allow me to keep all the new Messaging artifacts separate from the existing JBossMQ and JMS atrifacts, as you suggested. Is this name acceptable? Would another base name be preferable? Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968429#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...