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

	Commit message (Collapse)	Author	Age
*	Migrated tests in devtools/build/lib/packages to JUnit 4.	Florian Weikert	2015-12-01
\| \| \| \| \|	-- MOS_MIGRATED_REVID=109079812
*	Open source more tests for packages/	Han-Wen Nienhuys	2015-10-22
\| \| \| \| \| \| \| \| \| \|	Tested: bazel test on merge-to-os-blaze.sh checked total test method count on blaze test //javatests/com/google/devtools/build/lib:PackagesTests //third_party/bazel/src/test/java/com/google/devtools/build/lib:packages-tests -- MOS_MIGRATED_REVID=105963077
*	Replace "Google Inc" with "The Bazel Authors" in every copyright notice.	Lukacs Berki	2015-10-21
\| \| \| \| \|	-- MOS_MIGRATED_REVID=105949508
*	Move PackageIdentifier to cmdline	Kristina Chodorow	2015-08-31
\| \| \| \| \| \| \| \|	This is necessary to have TargetResolver depend on it without making it depend on the packages target. First step of #389. -- MOS_MIGRATED_REVID=101790345
*	Make globs work in remote repositories.	Lukacs Berki	2015-07-08
\| \| \| \| \| \| \| \| \| \| \|	This involved quite a few changes, mainly changing a bunch of places where we refer to packages by a PathFragment to PackageIdentifier. The only wart is the code in PathPackageLocator: ideally, it would just call into PackageLookupFunction. Unfortunately, it is (through globbing and Parser.include) called from within a Skyframe function, and we don't want to have two eval() calls going on at the same time, so we cannot use that. There is a potential correctness issue there: PathPackageLocator now assumes where external repositories are put and assumes that they are there when it gets control, but my understanding is that the associated RepositoryValue is always evaluated before, so it works out okay. -- MOS_MIGRATED_REVID=97751539
*	Rollback of accidentally submitted change.	Lukacs Berki	2015-07-07
\| \| \| \| \|	-- MOS_MIGRATED_REVID=97648982
*	Make globs work in remote repositories.	Lukacs Berki	2015-07-07
\| \| \| \| \| \| \| \| \| \| \|	This involved quite a few changes, mainly changing a bunch of places where we refer to packages by a PathFragment to PackageIdentifier. The only wart is the code in PathPackageLocator: ideally, it would just call into PackageLookupFunction. Unfortunately, it is (through globbing and Parser.include) called from within a Skyframe function, and we don't want to have two eval() calls going on at the same time, so we cannot use that. There is a potential correctness issue there: PathPackageLocator now assumes where external repositories are put and assumes that they are there when it gets control, but my understanding is that the associated RepositoryValue is always evaluated before, so it works out okay. -- MOS_MIGRATED_REVID=97647787
*	Open source some packages tests.	Ulf Adams	2015-05-04
	-- MOS_MIGRATED_REVID=92727637