[ https://jira.jboss.org/browse/JBIDE-7146?page=com.atlassian.jira.plugin.s... ] Rob Stryker commented on JBIDE-7146: ------------------------------------ To explain the patch a bit: The bug was that making a file in ProjectA deployable or undeployable would save a blank setting in ProjectB, ProjectC, ProjectD etc. The patch still appears to save an empty .settings file in ProjectA if ProjectA has no deployable files, however, this will only happen if ProjectA had a file marked deployable, and then later marked that file undeployable, leaving 0 remaining deployable files. In this case, the setting still needs to be saved, because to *not* save it would leave ProjectA/file1 as deployable in the settings file even though you just marked it as undeployable. 1) So, the bug of having 15 projects change on every mark / unmark deployable has been fixed. Now only the project that has changed will have a settings file changed 2) If ProjectA has had a file's status change TO deployable, the settings file should obviously be changed to mark this 3) If ProjectA has had a file's status change to NOT deployable, the settings file should still obviously be changed to remove the previously-set attribute. Hope that helps clarify. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-7146?page=com.atlassian.jira.plugin.s... ] Rob Stryker resolved JBIDE-7146. -------------------------------- Resolution: Done was after hte branch, so for beta2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira