Pharo Issue Tracker - Manuscript (Case [Issue]20947) Nautilus - NautilusRefactoring package should not depends on Nautilus package

Manuscript Notification

	Denis Kudryashov opened Case 20947: NautilusRefactoring package should not depends on Nautilus package and assigned it to Everyone: Cleanup in Nautilus: 1. Pharo Image • You are subscribed to this case

Now we have circle dependency between NautilusRefactoring and Nautilus packages.
NautilusRefactoring should not depends on Nautilus while Nautilus should just use it to provide refactoring operations.

And it will solve another dependency which prevent Nautilus removal

	Priority: 5 – Fix If Time		Status: Work Needed
	Assigned to: Everyone		Milestone: Pharo7.0

Go to Case

No longer need updates? Unsubscribe from this case.

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

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