[ https://jira.jboss.org/jira/browse/JBAS-5792?page=com.atlassian.jira.plug... ] Michael Brackx commented on JBAS-5792: -------------------------------------- This is not a feature request to include a certain feature/jar in the default profile. I consider this a bug, as a certain feature/jar that was included in 4.2.2.GA in the default profile is no longer available in 4.2.3.GA. A minor release version upgrade should be compatible (correct me if i am wrong). 4.2.3.GA is not, some ear's deploying on 4.2.2.GA default profile are not deploying on 4.2.3.GA default profile. I might agree with you (or not) that this particular feature/jar should not be in the default profile, but this is not relevant in this case. You should stick to decisions made for 4.2.2.GA, as this is a minor upgrade. -- 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/JBAS-5792?page=com.atlassian.jira.plug... ] Brian Stansberry resolved JBAS-5792. ------------------------------------ Resolution: Won't Fix Good point; I didn't focus properly on the fact your ear was working in 4.2.2. I'm not going to restore the jar though; it's already removed in a GA release. It's previous presence was a bug, as it was missing dependencies (JBAS-5397). Restoring it would also mean adding jgroups.jar to the default config in a 4.2.4, which could break users who deploy their own jgroups.jar with a different version. So there's no good answer here. Thank you for the report. This will help others who have the same problem. -- 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