Community
Participate
Working Groups
As described in bug 269604, RefreshTests have been disabled because they fail due to the blocked bugs. When these bugs are fixed, RefreshTests should be re-enabled.
Hmm, from the description you reference in that other bug, I'm surprised you depend on those two bugs. I thought your refresh problem was covered by the enhancement to try and do an incremental build when an aspect is deleted? (bug 269576). Just for the record again, AspectJ is deliberately designed to full build when an aspect is deleted (it is not an oversight) and I have tests that verify that behaviour, my tests will break and need updating when I implement the enhancement. The bugs you did say this depends on are: Bug 269562 relates to an issue with duplicate type names in split packages. I know the test project you gave me also exhibited this problem as well, but it doesn't stop a simpler refresh test from passing when 269576 is fixed. Bug 269554 relates to projects full building when a workspace is first started up. This is a brand new behaviour - are you able to test this? I thought each test in AJDT currently created the project it was going to use, then did its work, then deleted it. Are you already setup to either: start eclipse against an already defined workspace containing a previously build project, or restart eclipse during a test?
Oops. Should be bug 269576, not bug 269554. Right. Bug 269576 is regarding aspect deletion causing a full build even when one is not necessary. And bug 269562 is also about a full build happening even when one doesn't need to. When bug 269576 is resolved, I'll look at RefreshTests again and see if that is all I need to have them pass.
Move to the 2.0.2 release.
No longer slated for the next release.
