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

	Commit message (Collapse)	Author	Age
*	Automated rollback of commit 82e68b75304438c96ff878a0c2b8d18b42002486.	aehlig	2017-12-19
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	Fixes #4322, #4306. * Reason for rollback * Introduces a deadlock (see https://github.com/bazelbuild/bazel/issues/4322) * Original change description * Make FileSystem operate on LocalPath instead of Path. PiperOrigin-RevId: 179549866
*	Make FileSystem operate on LocalPath instead of Path.	tomlu	2017-12-14
\| \| \| \|	PiperOrigin-RevId: 179082062
*	More BUILD file refactorings.	philwo	2017-09-06
\| \| \| \| \| \| \| \| \|	Split collect, concurrent, vfs, windows into package-level BUILD files. Move clock classes out of "util", into their own Java package. Move CompactHashSet into its own Java package to break a dependency cycle. Give nestedset and inmemoryfs their own package-level BUILD files. PiperOrigin-RevId: 167702127
*	Don't pass in our own source root. ScopeEscapableFileSystem doesn't like it ↵	janakr	2017-07-14
\| \| \| \| \| \| \| \|	in some situations (which I don't fully understand). Fixes failing Bazel test. PiperOrigin-RevId: 161874315
*	If globbing throws an IOException, fail to construct the package instead of ↵	janakr	2017-07-14
	constructing the package with an error. Prior to this change, if a Package.Builder object was constructed, it was guaranteed that a Package (possibly with errors) would be created. This is no longer true: if an IOException is set on the Package.Builder object, it will throw a NoSuchPackageException during #build(). PiperOrigin-RevId: 161832111