[ https://issues.jboss.org/browse/JBDS-1925?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-1925: ----------------------------- Description: Current versions of SpringIDE included in JBDS are: JBDS 4.x :: SpringIDE 2.5 JBDS 5.0 :: SpringIDE 2.7.2 The purpose of this JIRA is to determine if we'd be better off using 2.8 instead of 2.7. was: Current versions of SpringIDE included in JBDS are: JBDS 4.x :: SpringIDE 2.5 JBDS 5.0 :: SpringIDE 2.6 The purpose of this JIRA is to determine if we'd be better off using 2.7 instead of 2.6. -- 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/JBDS-1925?page=com.atlassian.jira.plugin.... ] Jaroslav Jankovič commented on JBDS-1925: ----------------------------------------- Where could I find this version of plugin? In "http://download.jboss.org/jbosstools/updates/requirements/springide/" the latest version is 2.7.2. -- 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/JBDS-1925?page=com.atlassian.jira.plugin.... ] Jaroslav Jankovič edited comment on JBDS-1925 at 11/25/11 4:54 AM: ------------------------------------------------------------------- I tested SpringIDE 2.8.0 against: 1. Plugin doesn't affect JBDS stability 2. Plugin doesn't significantly interfere with other standard JBDS UI parts 3. Plugin can be installed without errors 4. Creating Spring project 5. Creating Spring context file 6. Creating Sprint Web Flow definition file 7. Spring explorer view is present and correctly shows all config files with all elements in it 8. Beans Cross References view is present and correctly shows beans when linked with editor 9. AOP Event Trace view is present and correctly shows event trace 10. All expected XSD namespaces found when creating Spring config file 11. All Spring context files found when creating Spring Web Flow definition file 12. Spring beans code completion in context file 13. OpenOn beans, classes, properties in context file 14. Open/ Open Java Element in spring explorer on some bean 15. Opening Dependency Graph in spring explorer on config file name 16. Opening Dependency Graph in spring explorer on some bean 17. Reviewing Dependency Graph (Open Java/Config Type) 18. Refactoring java classes (context file must be kept up-to-date) 19. Opening Graphical Editor in spring explorer on Web Flow definition File 20. Reviewing Graphical Editor (Open Config File) 2 test cases fail: no.8: Beans Cross References view is present and correctly shows beans when linked with editor - there are no beans when opening this view and linked in with editor. Also it is not working when select option "Select the Beans Cross reference for the entire file" no.16: Opening Dependency Graph in spring explorer on some bean - when click on Option "Open Dependency Graph" on some bean, nothings happened. This option shouldn't be there if it is not working. was (Author: jjankovi): I tested SpringIDE 2.8.0 against: 1. Plugin doesn't affect JBDS stability 2. Plugin doesn't significantly interfere with other standard JBDS UI parts 3. Plugin can be installed without errors 4. Creating Spring project 5. Creating Spring context file 6. Creating Sprint Web Flow definition file 7. Spring explorer view is present and correctly shows all config files with all elements in it 8. Beans Cross References view is present and correctly shows beans when linked with editor 9. AOP Event Trace view is present and correctly shows event trace 10. All expected XSD namespaces found when creating Spring config file 11. All Spring context files found when creating Spring Web Flow definition file 12. Spring beans code completion in context file 13. OpenOn beans, classes, properties in context file 16. Open/ Open Java Element in spring explorer on some bean 14. Opening Dependency Graph in spring explorer on config file name 15. Opening Dependency Graph in spring explorer on some bean 16. Reviewing Dependency Graph (Open Java/Config Type) 17. Refactoring java classes (context file must be kept up-to-date) 18. Opening Graphical Editor in spring explorer on Web Flow definition File 19. Reviewing Graphical Editor (Open Config File) 2 test cases fail: no.8: Beans Cross References view is present and correctly shows beans when linked with editor - there are no beans when opening this view and linked in with editor. Also it is not working when select option "Select the Beans Cross reference for the entire file" no.15: Opening Dependency Graph in spring explorer on some bean - when click on Option "Open Dependency Graph" on some bean, nothings happened. This option shouldn't be there if it is not working. -- 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/JBDS-1925?page=com.atlassian.jira.plugin.... ] Jaroslav Jankovič resolved JBDS-1925. ------------------------------------- Resolution: Done -- 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/JBDS-1925?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-1925: ---------------------------------- So, the upshot here is we should NOT move up to SpringIDE 2.8.0... correct? I might prefer to see this JIRA "rejected" or "won't fix" rather than "resolved" to reflect the fact that we won't be moving up to 2.8.0. -- 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/JBDS-1925?page=com.atlassian.jira.plugin.... ] Jaroslav Jankovič commented on JBDS-1925: ----------------------------------------- Nick, there is no workaround, at least I haven't found any, so I recommend NOT to using SpringIDE 2.8.0. -- 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/JBDS-1925?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-1925: ------------------------------------ So - just to confirm - the Beans Cross Reference view is completely unusable? -- 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/JBDS-1925?page=com.atlassian.jira.plugin.... ] Jaroslav Jankovič edited comment on JBDS-1925 at 11/28/11 12:55 PM: -------------------------------------------------------------------- Test case failure no.8 is blocker - it means that Bean Cross Reference view is unusable which is one of three views provided by SpringIDE. Test case failure no.16 is not such a big problem - opening Dependency Graph is working when click on config file name (test case 15), which is a usual way how to open it. was (Author: jjankovi): Test case failure no.8 is blocker - it means that Bean Cross Reference view is unusable which is one of three views provided by SpringIDE. Test case failure no.16 is not such a big problem - opening Dependency Graph is working when click on config file name (test case 15), which is a usual way hot to open it. -- 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/JBDS-1925?page=com.atlassian.jira.plugin.... ] Jaroslav Jankovič commented on JBDS-1925: ----------------------------------------- I created two JIRAs for SpringIDE: * https://jira.springsource.org/browse/IDE-1226 * https://jira.springsource.org/browse/IDE-1227 Note, that priority for IDE-1226 should be Critical, not Minor as set, but I don't have permission to edit it. -- 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/JBDS-1925?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-1925: -------------------------------------- Fix Version/s: 5.0.0.Beta1 (was: 5.0.0.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/JBDS-1925?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-1925: ----------------------------------- I was just attempting some basic testing of new application (SpringMVC template project) creation and deployment to the built-in tcServer. The server failed to start and app deployment failed. My goal was to show the same app deployed locally and in CloudFoundry. This was in STS 2.0.0. So I went back to using STS 2.7.2 for that particular demo/presentation. -- 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/JBDS-1925?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-1925: ----------------------------- Fix Version/s: 5.0.0.CR1 (was: 5.0.0.Beta3) Component/s: Upstream Upstream issues in SpringIDE are still unresolved despite their releasing a 2.9.1 build, so bumping back to CR1. This may in fact fall off of JBDS 5.0.0 planning if we can't get critical upstream issues fixed. -- 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/JBDS-1925?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-1925: -------------------------------------- Fix Version/s: 5.0.0.GA (was: LATER) (was: 5.0.0.CR1) -- 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/JBDS-1925?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-1925: ----------------------------- Fix Version/s: 5.0.2.GA (was: 5.0.1.GA) Slip to 5.0.2 -- 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