[ https://issues.jboss.org/browse/JBIDE-10463?page=com.atlassian.jira.plugi... ] Juergen Zimmermann commented on JBIDE-10463: -------------------------------------------- Maybe this issue is related to JBIDE-10430 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10463?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-10463: -------------------------------- Attachment: JBIDE-10463.v2.patch This is a better patch, complete with confirmation dialog. It resets the classpath, as a full build is not enough to ensure all models are updated properly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10463?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-10463: ------------------------------------- Juergen: The patch I committed was not as7.1 specific, but rather, had to do with changes to the default classpath page not being immediately put into effect without a workspace restart. The issue was replicated on all adapters. If you're suggesting the ability to change default classpaths and have it refresh automatically means "M5 cannot be considered to support JBossAS7.1", then I would have to disagree, as the level of support for AS7.1 is equal to that of all previous adapters. If on the other hand you simply want modules/org/jboss/ejb3/main/*.jar added to the default list for AS7.1, that's a very different issue and one I did not address in this JIRA. The workaround is to add the modules/org/jboss/ejb3/main/*.jar entry to the list of default classpaths for 7.1, then restart eclipse. It should work fine from then on. It's possible I can convince max and others that adding this ejb jar to the defaults is worth a rebuild, but this would only take affect in a new workspace. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10463?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-10463. --------------------------------- Resolution: Done This specific issue will only be fixed in beta1. I have opened https://issues.jboss.org/browse/JBIDE-10473 to investigate adding the requried ejb jar to the list of default classpaths. I do not, however, expect it to be accepted for m5. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10463?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-10463. --------------------------------- Now a newly added default classpath entry gets added to the given runtime and affected projects immediately. Verified in jbosstools-3.3_stable_branch.aggregate-Update-2012-02-24_23-15-15-H93.zip -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira