Issue 129 in metacello: MBProjectInfo doesn't update when it's currentVersion changes...

Status: Accepted
Owner: [hidden email]
Labels: Type-Defect Priority-Medium Product-Browser

New issue 129 by [hidden email]: MBProjectInfo doesn't update when it's  
currentVersion changes...
http://code.google.com/p/metacello/issues/detail?id=129

the currentVersion is a function of the currentVersion of the project  
info's configurationInfo and when a new dev version is created it is  
possible that the new dev version will get a new current version and the  
MBProjectInfo's referencing that project should change their  
printString/state

to reproduce:

load Seaside30 3.0.4-baseline, create a new 3.0.5 development version
go to Grease and create a new 1.0.5 development version

The Grease Core reference in Seaside30 should change to show 1.0.5 (and  
turn bold) ... it does not

Comment #1 on issue 129 by [hidden email]: MBProjectInfo doesn't update  
when it's currentVersion changes...
http://code.google.com/p/metacello/issues/detail?id=129

fixed in 1.59 (dkh.277)

still need tests ...