Issue 172 in metacello: Mechanism in validator to identify departures from recommendations for specifying versions

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

New issue 172 by [hidden email]: Mechanism in validator to identify  
departures from recommendations for specifying versions
http://code.google.com/p/metacello/issues/detail?id=172

With Issue 154, we are changing the set of optional messages used to define  
a project reference in a baseline and we are renaming several of the  
methods.

We just can't deprecate the old messages, because we shouldn't have to  
change all of the old versions just to avoid deprecation warnings.

For the same reason we can't make them validation warnings ...

It almost seems that we need to be able to run a validator pass that  
identifies deprecated usages ...

For example using className: is only necessary of the name of the class is  
not the same as the project name with 'ConfigrationOf' prepended. Same test  
for file:. Then there are the cases where you should use load: instead of  
loads:, etc.

Perhaps, these validations should kick in only when a particular version is  
being validated (by default) with the option to run these validations  for  
all versions and nested configs ...

The implication is that this should be a separate class of validation  
issue ... perhaps Recommendations...

That would give us Warnings, Recommendations, Critical Warnings, and Errors  
with a mechanism for filtering in the results ...