[ https://issues.jboss.org/browse/JBIDE-12716?page=com.atlassian.jira.plugi... ] Lucia Jelinkova updated JBIDE-12716: ------------------------------------ Steps to Reproduce: # Add path on the runtime detection preference page # Remove the path # Add another path RESULT: The previously removed path is listed in the table -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12716?page=com.atlassian.jira.plugi... ] Snjezana Peco resolved JBIDE-12716. ----------------------------------- Resolution: Done The problem has been introduced by fixing JBIDE-12447. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12716?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-12716: ---------------------------------------- Fix Version/s: 4.0.0.CR1 (was: 4.0.0.Beta1) Priority: Blocker (was: Major) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12716?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-12716: ---------------------------------------- Fix Version/s: 4.0.0.Beta1 (was: 4.0.0.CR1) Assignee: Rob Stryker (was: Snjezana Peco) scratch that - the removed paths never seem to get removed. rob - can you look? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12716?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-12716: ------------------------------------- This definitely seems inconsistant. Perhaps it only works on a clean workspace somehow? After continuing in the same workspace and trying to replicate a second time, no real luck. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12716?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-12716: --------------------------------------- I have fixed this issue in my tree. Is trunk open to commit? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12716?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-12716: -------------------------------- Attachment: JBIDE-12716.patch I have a patch for this issue: QE: The changes I'm making affect how and when the dialog will persist the changes made in the preference page. If everything is working perfect, changes should ONLY ever be persisted when "Apply" or "OK" are pressed on the preference page. Everything else should be considered temporary changes ONLY. When you edit a runtime path, in the subsequent dialogs, cancel should make sure the 'change' is not even shown in the preference page. The preference page should no longer randomly close and re-open to refresh itself, but changes must be persisted when the user expects, and NOT persisted when they do not expect it. To anyone else: The reason for this original bug is as follows: 1) The 'remove' button was only keeping the change in the local model until performOK or performApply was pressed, when it would persist the change. This was correct 2) The 'add' button was persisting the change immediately upon 'add' and its dialogs being finished. The issue here was that a call to remove would locally remove the runtime path. A call to 'add' would add the new one and persist that change. Since the core model never had the 'removed' object actually removed, the 'add' called to the core model would persist only the addition, and the never-actually-removed entry would still be persisted. The preference page would close and reopen (?!) and then you would see both entries. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12716?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-12716: ---------------------------------------- Labels: respin-a (was: ) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12716?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-12716: ------------------------------------- +1 for respin-a. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12716?page=com.atlassian.jira.plugi... ] Petr Suchý closed JBIDE-12716. ------------------------------ Now it's working. Verified on JBT 4.0.0.Beta1a v20121018-1718-B33 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira