Community
Participate
Working Groups
Kurt -- I just realized I forgot that, in the launch configuration for the JUnit test suite, we're supposed to have assertions enabled (click on the Arguments tab in the run configuration, and put "-ea" in the VM arguments). (There was an incorrect assertion in Rename that was failing that I just fixed.) When these are enabled, "assert accessNode != null" on line 248 of MakePrivateEntityPublicRefactoring is failing for tests 4, 6, and 7_1.
Created attachment 148649 [details] Update to Make Private Public - tests passing I believe those 2 assertions at lines 248 and 249 are actually not necessary the necessary checks happen in the methods themselves to determine the change being made. I've removed those and added an update attachment that patches only the refactoring code file, namely MakePrivateEntityPublicRefactoring.java.
Sounds good. You can go ahead and commit that patch. Actually, you don't even have to post patches now that you're a committer. :-) Just mention that it's fixed in CVS. Jeff
Committed to CVS