|
||||||||||||||||
|
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 |
||||||||||||||||
|
||||||||||||||||
|
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 |
||||||||||||||||
I was able to replicate this using wtp 3.3.2 and without using gwt at all. I was unable to replicate this using HEAD code from wtp 3.4 builds, which are currently at RC 4. This means the bug was fixed during the wtp 3.4 stream. wtp 3.3.2 was released in February, adn the stream has since been shut down, meaning no further patch builds are going to be made.
Unfortunately there's really nothing I can do in this situation. With the bug upstream, significant class changes between 3.3.x and 3.4.0 (making a patch difficult to backport), an inability to get a patch build even if we did identify and backport the specific bug, and because a work-around exists, I think I'm going to have to close this as wont-fix.
My suggestions are to use the workaround. =/ The reason the workaround works is because switching the output directory of the classes changes the project from a 'single root' project into a not-single-root one. This then goes through a proper and complete evaluation for what deltas should be produced, as opposed to single-root, which is streamlined but not versatile.