We have recently switched our Master repository from Metadata API format to Source format. When validating before a deployment, we are still seeing validation errors that reference line numbers (for instance on a field in an object). However, because our repo is in Source format, that line number reference is not helpful in determining where the problem actually is. Is there anyway to decipher that error message (line reference) to determine where the issue is?
Thank you @Kermit Del Rosario, but not really the same scenario. My question is specific to the format of the XML (Metadata API vs Source). Errors that reference specific line numbers are really useful when your xml is in Metadata API format where every component in an object is present in a single xml file, but not at all useful when in Source format where each component is it's own file within a shared object folder.
