Manuscript (Case [Issue]22319) Refactoring - Extracting an already existing method should not raise an error!

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Manuscript (Case [Issue]22319) Refactoring - Extracting an already existing method should not raise an error!

Pharo Issue Tracker
Manuscript Notification
avatar
Stephane Ducasse reactivated Case 22319: Extracting an already existing method should not raise an error! and assigned it to Everyone:
Bug in Project:  Refactoring: 1. Pharo Image  •  You are subscribed to this case
Is it really fixed? Because in my system /Users/ducasse/Documents/Pharo/images/UUML/UUML.image
Pharo7.0.0rc1
Build information: Pharo-7.0.0+rc1.build.1375.sha.7fccf8d31bff3b1e71165a82ec40ffa1743192b9 (32 Bit)
Unnamed
it does not work!
Status changed:
Resolved (Fixed upstream)  changed to  Work Needed

Assigned To changed:
Stephane Ducasse  changed to  Everyone

Priority Priority: 3 – Must Fix Status Status: Work Needed
Assigned To Assigned to: Everyone Milestone Milestone: Pharo7.0

Go to Case
No longer need updates? Unsubscribe from this case.

Don't want Manuscript notifications anymore? Update your preferences.

Manuscript

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
https://lists.gforge.inria.fr/mailman/listinfo/pharo-bugtracker