[ https://jira.jboss.org/jira/browse/EJBTHREE-2021?page=com.atlassian.jira.... ] jaikiran pai commented on EJBTHREE-2021: ---------------------------------------- We actually don't have any new plans for EJB3 Plugin. We are moving to a new package manager utility. Anyway, the plugin was meant to apply EJB3 artifacts against just "default" and "all" configs. The reason was, we knew what files/configs were shipped within these servers. Anything other than "default" and "all" is a custom config and it is highly likely that it may not have the correct set of EJB3 configs required. Infact i don't know how the default-with-hornetq is created and what it contains. I *think* it's just a copy of the "default" with the jms-ra.rar being replaced by hornetq rar (although i am not sure). If you know the exact set of changes between these 2 configs, then you could perhaps try this: 1) Apply the EJB3 plugin against "default" 2) Then create the "default-with-hornetq" config by copying and modifying the patched "default" config. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/EJBTHREE-2021?page=com.atlassian.jira.... ] Christian Reichel commented on EJBTHREE-2021: --------------------------------------------- OK, seens good to me. This profile was generated by hornetq build.sh script for JBOSS AS 5. Thanks mate. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira