search

krfkeith / metacello

Automatically exported from code.google.com/p/metacello
0 stars 0 forks source link

#stable version shouldn't cause upgrade from project reference #150

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
a project reference of #stable, should only cause load activity when the target 
project is not present ... if the target project is present no upgrade should 
take place (it does presently)

A direct load of a #stable version should always load the specified version...

Project references have always been subject to the version comparison rule 
where the project is a) never downgraded and b) only upgraded if the 
specification is for a later version.

#stable implies an even looser coupling to the specified project, so I think it 
makes sense that a #stable project reference will only cause a version to be 
loaded if the project is not already loaded into the image

Original issue reported on code.google.com by henrichs...@gmail.com on 6 Sep 2011 at 5:28

GoogleCodeExporter commented 9 years ago 
proposed fix in Metacello 1.0-beta.31.2 (dkh.655)

Original comment by henrichs...@gmail.com on 3 Jan 2012 at 7:19

GoogleCodeExporter commented 9 years ago

Original comment by henrichs...@gmail.com on 18 Jan 2012 at 5:59

GoogleCodeExporter commented 9 years ago 
fixed earlier in Metacello 1.0-beta.31.2 (dkh.655)

Original comment by henrichs...@gmail.com on 25 Jan 2012 at 9:48