FogBugz (Case [Issue]20086) Tools - Critics raise error when manifest define bans for unexisted classes

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

FogBugz (Case [Issue]20086) Tools - Critics raise error when manifest define bans for unexisted classes

Pharo Issue Tracker
FogBugz Notification
avatar
Denis Kudryashov opened Case 20086: Critics raise error when manifest define bans for unexisted classes and assigned it to Everyone:
Bug in Project:  Tools: 1. Pharo Image  •  You are subscribed to this case
Try load TaskIt package and then browse some of it method. Debugger will be opened.
<code>
Metacello new
baseline: 'TaskIt';
repository: 'github://sbragagnolo/taskit';
load.
(#TKTTask asClass >> #future) browse
<code>
Priority Priority: 5 – Fix If Time Status Status: Work Needed
Assigned To Assigned to: Everyone Milestone Milestone: Later

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]
https://lists.gforge.inria.fr/mailman/listinfo/pharo-bugtracker