| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
| |
javac's bespoke zip implementation is now off by default:
https://bugs.openjdk.java.net/browse/JDK-7018859
--
MOS_MIGRATED_REVID=112600878
|
|
|
|
|
|
|
| |
its intended use.
--
MOS_MIGRATED_REVID=112598772
|
|
|
|
|
|
|
|
|
|
| |
This is part of removing the requirement of having base_workspace in your
package_path for bazel builds.
This also removes --experimental_objc_gcov_binary, since it doesn't seem to be needed anymore.
--
MOS_MIGRATED_REVID=112595137
|
|
|
|
|
|
|
|
|
| |
Previously the crashing logger would allow the server process to survive
which could leave things in a weird state if a crash was expected. Instead
of throwing an exception shut down the runtime.
--
MOS_MIGRATED_REVID=112589751
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updating the generate_workspace tool to:
- Respect dependency exclutions from the project object model (maven).
- Generate one rule per pom dependency or maven_jar source rule (using maven
group ID and artifact ID).
--
Change-Id: Ieb878f82be4352dcfb5755f8f71dfa7e592de78a
Reviewed-on: https://bazel-review.googlesource.com/#/c/2551/
MOS_MIGRATED_REVID=112574031
|
|
|
|
|
|
|
| |
what kind of performance we could get from how we imagine it would work under Windows.
--
MOS_MIGRATED_REVID=112572621
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The help message of this option had the effect inversed. The default
--block_for_lock setting makes the client block waiting for the lock
when needed, and the flag needs to be unset with --noblock_for_lock
to instead exit immediately.
Also rename the dummy noblock_for_lock variable to blockForLock to match
the naming convention. The variable is not used anywhere, as this class
only exists for the help messages.
--
MOS_MIGRATED_REVID=112566287
|
|
|
|
|
|
|
|
|
| |
Fixes #676.
--
Change-Id: I7474d3e3071c99452b6e1835d6f70671f34b1fd9
Reviewed-on: https://bazel-review.googlesource.com/#/c/2693
MOS_MIGRATED_REVID=112564791
|
|
|
|
|
|
|
| |
Fixes #790
--
MOS_MIGRATED_REVID=112563137
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112562308
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112561390
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112555666
|
|
|
|
|
|
|
| |
These are unnecessary because Bazel now carries these tools with itself in the @bazel_tools repository.
--
MOS_MIGRATED_REVID=112555031
|
|
|
|
|
|
|
|
| |
The avoids misleading "Building libfoo.jar (0 files)" progress messages for
sourcejar-only compilations.
--
MOS_MIGRATED_REVID=112512879
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112507181
|
|
|
|
|
|
|
| |
all so that custom implementations can have custom options passed around.
--
MOS_MIGRATED_REVID=112502778
|
|
|
|
|
|
|
|
|
|
|
| |
Also, don't require the :stl attribute to be defined by all rules that
use CcLibraryHelper.
This makes it possible for other languages to use CcLibraryHelper to
create a CppCompilationContext.
--
MOS_MIGRATED_REVID=112494452
|
|
|
|
|
|
|
|
| |
This is in preparation for removing the requirement that base_workspace be in
bazel's package_path.
--
MOS_MIGRATED_REVID=112489640
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112478681
|
|
|
|
|
|
|
|
| |
This is in preparation for removing the requirement that base_workspace be in
bazel's package_path.
--
MOS_MIGRATED_REVID=112477785
|
|
|
|
|
|
|
| |
Fixes #730.
--
MOS_MIGRATED_REVID=112475309
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112474631
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Refactored IntelliJSkylarkAspectTest. Eventually that test will be
merged with AndroidStudioInfoAspect test to validate implementation
equivalence.
2. Exposed ``root`` and ``is_source`` on Artifacts to Skylark.
3. Skylark aspect implementation outputs sources and dependencies
information.
--
MOS_MIGRATED_REVID=112473407
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112472854
|
|
|
|
|
|
|
| |
arguments (seems too messy for a family of functions).
--
MOS_MIGRATED_REVID=112472644
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112466264
|
|
|
|
|
|
|
|
|
|
|
| |
It is counter-intuitive to read ConnectToServer(false). By having
/*start=*/ in front of the boolean parameter the intention gets clear
(i.e., if it should or not start the Java server).
--
Change-Id: I74847deb6ec7daba62facd7a746d418943448182
Reviewed-on: https://bazel-review.googlesource.com/#/c/2680
MOS_MIGRATED_REVID=112466249
|
|
|
|
|
|
|
| |
The current set-up was overwriting the XML_OUTPUT_FILE of unittest_test, leading to weird error on ci.bazel.io.
--
MOS_MIGRATED_REVID=112462362
|
|
|
|
|
|
|
| |
It is currently unused and messes up IDEs because it requires a few dependencies that are not in the source tree (most notably, jimfs)
--
MOS_MIGRATED_REVID=112461226
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
While BuildViewTestCase now has an update() function, it also has a lot of
legacy cruft that doesn't match how the code is used in production. This also
makes the test code a bit simpler.
Also add a couple missing fail() statements.
This is in preparation for adding a couple more tests; we don't have good
test coverage for interaction between Skylark aspects and native rules and
vice versa, especially for error scenarios.
I may reuse some of the AspectTest code, but that inherits AnalysisTestCase.
Inheriting AnalysisTestCase here also makes that easier.
--
MOS_MIGRATED_REVID=112460142
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- update some comments
- add some comments to make it easier to follow
- delete some dead code, in particular the SkyframeDependencyResolver can
never be null; remove an non-applicable @Nullable annotation
I'm trying to figure out how the error handling code works, in order to add
support for interleaved loading+analysis, which requires handling loading
errors in this code path.
--
MOS_MIGRATED_REVID=112456674
|
|
|
|
|
|
|
|
|
| |
This make those test target compatible with --nolegacy_bazel_java_test.
--
Change-Id: I2316c9aa53327b417ecce5fd5dab95ec726da11d
Reviewed-on: https://bazel-review.googlesource.com/#/c/2690
MOS_MIGRATED_REVID=112446514
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112409554
|
|
|
|
|
|
|
|
|
|
| |
This method was used only twice. Now there is only one entry point for requesting
a rule in the external package (RepositoryFunction#getRule(String, Environment)).
This is a step towards supporting loading skylark rules in the workspace file from
remote repository.
--
MOS_MIGRATED_REVID=112407797
|
|
|
|
|
|
|
| |
This remove all C++ compilation in bootstrapping itself.
--
MOS_MIGRATED_REVID=112407516
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112404257
|
|
|
|
|
|
|
| |
Another step towards no C++ compilation outside of Bazel for bootstrapping.
--
MOS_MIGRATED_REVID=112399835
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112394770
|
|
|
|
|
|
|
|
| |
This simplify the bootstrap process and remove a C++ tool from
the bootstrap binary.
--
MOS_MIGRATED_REVID=112394555
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112394431
|
|
|
|
|
|
|
| |
deprecated.
--
MOS_MIGRATED_REVID=112392227
|
|
|
|
|
|
|
|
|
| |
to do such a load will result in a skyframe circular dependency exception.
As a side effect of this change, SkylarkImportFailedExceptions thrown by SkylarkImportLookupFunction are now caught by PackageFunction and wrapped and rethrown as a PackageFunctionException. Previously, the first exception wasn't caught, generating an uncaught exception error at top level.
--
MOS_MIGRATED_REVID=112328755
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112290581
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112285296
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112284252
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112280234
|
|
|
|
|
|
|
| |
See http://ci.bazel.io/job/Bazel/JAVA_VERSION=1.7,PLATFORM_NAME=darwin-x86_64/302/console
--
MOS_MIGRATED_REVID=112280018
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112273574
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Note: This specification currently does not have any effect, but soon...
In the default mode, when an aspect does not call any of the configuration
fragment methods on its AspectDefinition.Builder, the old behavior will
persist; aspects can only access fragments their associated rule has access
to, and have no guarantee as to what those fragments are.
This mode will become deprecated with a future CL.
If an aspect does call a configuration fragment method, it will have a
configuration fragment policy. In a future CL, this will mean it will be
restricted to accessing only those fragments, but will be understood as
requiring access to them for the purposes of dynamic configuration, even if
the rule it is attached to or created by does not otherwise require them.
Eventually, all aspects will be required to declare their configuration
fragments this way.
Skylark aspects may also declare configuration fragments as of this CL.
Two new parameters are added to the aspect() function, fragments and
host_fragments, mirroring the similar parameters for rules.
If both of these parameters are empty or unspecified, the default mode
is used, as with normal aspects.
Also in this CL:
* Minor javadoc fixes for AspectDefinition.
* Additional tests for AspectDefinition.
--
MOS_MIGRATED_REVID=112271713
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112267385
|