[ https://jira.jboss.org/jira/browse/JBIDE-4118?page=com.atlassian.jira.plu... ] Rob Stryker commented on JBIDE-4118: ------------------------------------ What (if any) are the structural changes between 5.0 and 5.1? Anything major? Any jar renames? Anything absolutely requiring a new runtime type? -- 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/JBIDE-4118?page=com.atlassian.jira.plu... ] Rob Stryker resolved JBIDE-4118. -------------------------------- Resolution: Cannot Reproduce Bug I checked out the source, built the AS, and it seems to work with the 5.0 server type. Wizard can finish, server can start. If there are no severe structural changes, then for now I'll say a new servertype is not necessary. -- 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/JBIDE-4118?page=com.atlassian.jira.plu... ] Galder Zamarreño reopened JBIDE-4118: ------------------------------------- Hmmm, I still can't. I keep getting this message when trying to create the runtime: "The home directory does not exist, is missing key files, or is of the incorrect version." I'm running Tools 3.0.GA. Rob, did you verify this with GA or some other branch? -- 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/JBIDE-4118?page=com.atlassian.jira.plu... ] Rob Stryker commented on JBIDE-4118: ------------------------------------ Sorry Galder. I didn't read the issue thoroughly. It should be committed to both 3.0.1 and 3.1.0 streams already. And the messages have already been clarified. @Max: While you're right that new API's are a difference, the problem is that they've backported the fixes to 5.0.x stream, which means that if they do come out with a 5.0.2 or 5.0.3 stream, the new API's will still be there. In all honesty, If I were ever to rewrite this stuff entirely, I could probably have only 1 server type and make everything absolutely dynamic, reading the server's version from the installation folder and then calculate everything from classpath container information to startup information to deployment stuff. The need for a new "Server Type" really is not great at all. The only primary difference here is whether the server starts with "deploy to the server area" or "deploy to metadata". That's basically all that changes. And the user can adjust that at his will in the server editor. -- 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/JBIDE-4118?page=com.atlassian.jira.plu... ] Rob Stryker resolved JBIDE-4118. -------------------------------- Resolution: Done Galder: This was verified in 3.0.GA and was fixed in both 3.0.1 maintenance and 3.1 trunk a while ago. No commits were made on this JIRA as they were made in a previous commit. (commits 14204 and 14251) -- 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/JBIDE-4118?page=com.atlassian.jira.plu... ] Anton Klimkovich closed JBIDE-4118. ----------------------------------- Verified on 2.0.0.GA-R200905020417-H7. Steps to verify: EXECUTE: Preferences - > Server -> Runtime environments EXECUTE: Press Add buttom and select JBoss AS 5.0 EXECUTE: Add Jboss AS 5.1.0.CR1. ASSERT: Warning message: This server type expects a version of 5.0 but the server directory is of version 5.1.0.CR1. Finish button should be enabled. -- 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