Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Deprecate Context.build_file_parser. #7295
Some tasks rely on it for access to target aliases.
However since Context is public API, we go through a deprecation
Once this deprecation is complete, we can get rid of BuildFileParser
I'd rather not delete the test until the deprecation cycle is complete. A BuildFileParser is still technically retrievable as part of the public API until then... In practice I'm sure you're right, and no one is using that even outside our repo, but I'd rather err on the side of caution, and of respecting our deprecation principles...