Smalltalk
›
Pharo
›
Pharo Issue Tracker
Search
everywhere
only in this topic
Advanced Search
FogBugz (Case [Issue]20086) Tools - Critics raise error when manifest define bans for unexisted classes
‹
Previous Topic
Next Topic
›
Classic
List
Threaded
♦
♦
Locked
1 message
Pharo Issue Tracker
Reply
|
Threaded
Open this post in threaded view
♦
♦
|
FogBugz (Case [Issue]20086) Tools - Critics raise error when manifest define bans for unexisted classes
FogBugz Notification
Yuriy Tymchuk
edited
Case 20086
: Critics raise error when manifest define bans for unexisted classes
:
Bug
in
Tools: 1. Pharo Image • You are subscribed to this case
this is not cool :(. I guess this has to be fixed in Manifest. We will see
Priority
: 5 – Fix If Time
Status
: Work Needed
Assigned to
: Yuriy Tymchuk
Milestone
: Later
Go to Case
No longer need updates?
Unsubscribe from this case.
Don't want FogBugz notifications anymore?
Update your preferences.
A FogBugz case was edited by Yuriy Tymchuk. Case ID: 20086 Title: Critics raise error when manifest define bans for unexisted classes Status: Work Needed Category: Bug Project: Tools Area: 1. Pharo Image Priority: 5 - Fix If Time Milestone: Later Assigned To: Yuriy Tymchuk URL: https://pharo.fogbugz.com/f/cases/20086 this is not cool :(. I guess this has to be fixed in Manifest. We will see You are subscribed to this case. If you do not want to receive automatic notifications in the future, unsubscribe (https://pharo.fogbugz.com/default.asp?pre=preUnsubscribe&pg=pgEditBug&command=view&ixBug=20086) from this case.
_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
https://lists.gforge.inria.fr/mailman/listinfo/pharo-bugtracker
Free forum by Nabble
Edit this page