bazel - a fast, scalable, multi-language and extensible build system

	Commit message (Collapse)	Author	Age
*	Move WrappingProviderHelper into static class in WrappingProvider.	Googler	2017-06-20
\| \| \| \| \| \|	Cuts down on file count and makes it easier to find these methods. PiperOrigin-RevId: 159560422
*	Create a general WrappingProvider concept and use for java_proto_library and ↵	Googler	2017-06-20
	friends. The wrapping provider contains its own provider map containing any providers that may conflict. This can be used generally for any aspect that wants to override its base providers (during migration), and due to the generality we should be able to cut down on code size and complexity. Once we have this, we can more easily and uniformly bind aspects to Skylark for aspect-on-aspect functionality. The Skylark providers can be instantiated with a wrapping provider if one is present, or fall through to the base target if they aren't. We will also likely save a bit of memory from cutting down on wrapping classes. PiperOrigin-RevId: 159461325