Issue 122 in metacello: misleading error message regarding stable versions

Status: Accepted
Owner: [hidden email]
Labels: Type-Defect Priority-Medium Product-Core Milestone-1.0-beta.28.3.2

New issue 122 by [hidden email]: misleading error message regarding  
stable versions
http://code.google.com/p/metacello/issues/detail?id=122

 From Mariano:

Hi Dale. THe error message "Version #stable is not defined in  
ConfigurationOfSqueakDBX"  is misleading, because #stable is indeed defined  
in ConfigurationOfSqueakDBX  but there is no version defined for the pharo  
iamge where I am loading. Example:

ConfoigurationOfSqueakDBX >> stable: spec
     <symbolicVersion: #stable>

     spec for: #'pharo1.0.x' version: '1.2'.
     spec for: #'pharo1.1.x' version: '1.2'.


And I try to do:  (ConfigurationOfSqueakDBX project version: #stable) load
in a Pharo 1.2.

I think the error should be: "There is not any stable version defined for  
Pharo 1.2 in ConfigurationOfSqueakDBX"
or something like that...

Cheers

Mariano

Comment #1 on issue 122 by [hidden email]: misleading error message  
regarding stable versions
http://code.google.com/p/metacello/issues/detail?id=122

Mariano, at the point that the error is being generated, I don't know  
explicitly why there is no symbolic version, but I was thinking that I  
could change the error message to say:

   "The symbolic version #stable is not defined in ConfigurationOfSqueakDBX  
for the current platform"

would that be better?

Updates:
        Status: Fixed
        Labels: Fixed-1.0-beta.29

Comment #2 on issue 122 by [hidden email]: misleading error message  
regarding stable versions
http://code.google.com/p/metacello/issues/detail?id=122

looks like this fix is acceptable