[ https://jira.jboss.org/browse/JBIDE-6861?page=com.atlassian.jira.plugin.s... ] Rob Stryker commented on JBIDE-6861: ------------------------------------ This seems to be a bug in how I am weighting the progress monitors. I'm basically allocating 100 work units for each resource, file or folder. So for example, Total work: 500 - blah.ear |- blah.ear/file1.txt (100 work units) |- blah.ear/file2.txt (100 work units) |- blah.ear/file3.txt (100 work units) |- blah.ear/file4.txt (100 work units) |- blah.ear/folder2 (100 work units) (sub monitor has total work of 500) |-blah.ear/folder2/file1 (100 submon work units, but only 20 top-level units) |-blah.ear/folder2/file2 (100 submon work units, but only 20 top-level units) |-blah.ear/folder2/file3 (100 submon work units, but only 20 top-level units) |-blah.ear/folder2/file4 (100 submon work units, but only 20 top-level units) |-blah.ear/folder2/inner_folder (100 submon work units, 20 top level units, inner monitor has total work of 500) |-blah.ear/folder2/inner_folder/file1 (100 inner_monitor units, 20 units against submon, only 5 top-level work units) |-blah.ear/folder2/inner_folder/file2 |-blah.ear/folder2/inner_folder/file3 |-blah.ear/folder2/inner_folder/file4 |-blah.ear/folder2/inner_folder/file5 As we can see, the deeper the folder structure, the less each piece of work counts. I'm not sure how to fix this without first traversing everything and finding out exactly how many resources there are to be coppied. I'd like to avoid such extra traversals if avoidable but I'm not sure I can. -- 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-6861?page=com.atlassian.jira.plugin.s... ] Rob Stryker resolved JBIDE-6861. -------------------------------- Resolution: Done Seems it was stalling because of a combnation of things. WTP assigns each module (even a child mod) equal weight. Why it stalled is because I had already exceeded the amount of work I said I'd do and so my child monitor was effectively done. Even though more work had to be done, the monitor stayed at fully complete (aka stalled the parent monitor) -- 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