|Anonymous | Login||08-09-2020 18:02 UTC|
|Main | My View | View Issues | Change Log | Docs|
|Viewing Issue Simple Details [ Jump to Notes ]||[ View Advanced ] [ Issue History ] [ Print ]|
|ID||Category||Severity||Reproducibility||Date Submitted||Last Update|
|0005929||[Squeak] Tools||major||N/A||02-03-07 23:10||02-04-07 00:23|
|Summary||0005929: The #reorganize message is in dangerous confilct with the need to keep package catagories intact|
When a catagory is changed in a class a change record is generated.
When a changeset with that record is filed out all the catagories of the class are filed out in the reorganization not just the ones changed.
If the changeset is not harvested immediately then the chances that the filed out reorganization is out of sync with the organization in the image it is filed into will be huge.
The most important classes (Object, Morph) will be the most vulerable.
This is probably the most major problem in making cs safe to interoperate with MC packages.
Essentially by being sensitive to method catagory names MC breaks change sets.
If this is repaired then a good deal of the interoperability problems might be solved.
|There are no notes attached to this issue.|
|02-03-07 23:10||wiz||New Issue|
|02-04-07 00:23||wiz||Relationship added||child of 0005831|
|11-18-08 19:56||KenCausey||Relationship deleted||child of 0005831|
| Mantis 1.0.8[^]
Copyright © 2000 - 2007 Mantis Group
32 total queries executed.|
25 unique queries executed.