FogBugz (Case [Issue]12310) Tools - Move to package from nautilus does not fully take extensions into account so it breaks code :(

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

FogBugz (Case [Issue]12310) Tools - Move to package from nautilus does not fully take extensions into account so it breaks code :(

Pharo Issue Tracker
FogBugz Notification
avatar
Bug in Project:  Tools: 1. Pharo Image  •  You are subscribed to this case
And now I do not know what I can do because all the longDescription methods on RB-Critics are extensions of *Manifest-Core. So the resulting situation is just correct.
I cannot fix the problem.
I do not understand why this is even a problem.
Priority changed:
5 – Fix If Time  changed to  1 – Show Stopper !!!!!!

Subcases changed:
Added subcase 12309.

Priority Priority: 1 – Show Stopper !!!!!! Status Status: Work Needed
Assigned To Assigned to: Everyone Milestone Milestone: Pharo3.0

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

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

FogBugz

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