Eventually, we will require a versionString in a project reference, so it is
probably a good idea to add the critical warning now to get folks used to the
idea:)
#noVersionSpecified warns of no version being specified in the version, but no
specific warning has been defined for the baseline.
I suggest that we use #missingRecommendedProjectSpecField for the time being.
Original issue reported on code.google.com by henrichs...@gmail.com on 26 Jan 2012 at 5:56
Original issue reported on code.google.com by
henrichs...@gmail.com
on 26 Jan 2012 at 5:56