Issue 113 in metacello: configuration validation may create shadow packages for unloaded mcz files

Status: Accepted
Owner: [hidden email]
Labels: Type-Defect Priority-High Version-1.0-beta.28.4  
Milestone-1.0-beta.28.4

New issue 113 by [hidden email]: configuration validation may create  
shadow packages for unloaded mcz files
http://code.google.com/p/metacello/issues/detail?id=113

I noticed this running in Metacello 1.0-beta.28.4 in a PharoCore1.2 image  
where I had done the following load:

   (ConfigurationOfMetacello project version: #development)
     load: #('default' 'Tests').

which excludes the OB-Metacello package, but when validation was complete  
the package OB-Metacello-DaleHenrichs.81 showed up in the MonticelloProwser  
package list...browsing the contents shows that no code was loaded, but we  
definitely ended up with an MCPackage and associate versionInfo stuffed  
into MCWorkingCopy allManagers ...

Not sure if this is problem in only PharoCore1.2 or not...

Updates:
        Labels: -Type-Defect Type-Task

Comment #1 on issue 113 by [hidden email]: configuration validation may  
create shadow packages for unloaded mcz files
http://code.google.com/p/metacello/issues/detail?id=113

Ooops this looks like it is actually a bug in MetacelloBrowser, not  
Metacello itself ... I had done a validate through the MetacelloBrowser UI  
clicking on another config that was not loaded was enough to create a whole  
slug of empty packages ...

Switch this to a task to fix the bug in MetacelloBrowser...

Updates:
        Status: Fixed

Comment #2 on issue 113 by [hidden email]: configuration validation may  
create shadow packages for unloaded mcz files
http://code.google.com/p/metacello/issues/detail?id=113

taken care of ...

Name: MetacelloBrowser-DaleHenrichs.38
Author: DaleHenrichs
Time: 23 February 2011, 5:30:54 pm
UUID: df7ea49d-b9b2-41ee-a032-3b0eaaee670f
Ancestors: MetacelloBrowser-DaleHenrichs.37