| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
|
|
|
| |
Per review feedback from commit efb2f17075a3dbc3d5875699252db7e35a28c8d7, add Fission feature
per_object_debug_info to MockCcSupport, replacing real -gsplit-dwarf
with a fake name and use it in the added Fission tests.
--
PiperOrigin-RevId: 145540550
MOS_MIGRATED_REVID=145540550
|
|
|
|
|
|
|
|
| |
Fixes #2372.
--
PiperOrigin-RevId: 145539067
MOS_MIGRATED_REVID=145539067
|
|
|
|
|
|
|
|
| |
Added tests for Java sandwich using java_binary, java_test and java_import.
--
PiperOrigin-RevId: 145538765
MOS_MIGRATED_REVID=145538765
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145538761
MOS_MIGRATED_REVID=145538761
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
This change is no longer needed because commit d9a7d3a789be559bd6972208af21adae871d7a44 is rollbacked
*** Original change description ***
Add --manifest_file option into BazelJavaBuilder
Now Bazel JavaBuilder can specifiy a file as the manifest file, before
this it just creates the manifest file on the fly.
--
PiperOrigin-RevId: 145534408
MOS_MIGRATED_REVID=145534408
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Change is abandoned because it's a wrong solution
See https://github.com/bazelbuild/bazel/issues/2242
*** Original change description ***
java_binary now supports long classpath that exceeds command line argment length limit
When classpath length exceeds the command line length limit, we create
an empty classpath jar whose manifest contaning the whole classpath
value.
See: https://github.com/bazelbuild/bazel/issues/2242
Fixed: https://github.com/bazelbuild/bazel/issues/1780
--
PiperOrigin-RevId: 145534282
MOS_MIGRATED_REVID=145534282
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145524911
MOS_MIGRATED_REVID=145524911
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For example for this library:
```
bazel run //src/tools/generate_workspace -- --artifact=com.wix:wix-embedded-mysql:2.1.3
```
I get this exception:
```
Exception in thread "main" java.lang.ClassCastException: sun.net.www.protocol.ftp.FtpURLConnection cannot be cast to java.net.HttpURLConnection
at com.google.devtools.build.workspace.maven.DefaultModelResolver.pomFileExists(DefaultModelResolver.java:143)
at com.google.devtools.build.workspace.maven.DefaultModelResolver.getModelSource(DefaultModelResolver.java:124)
at com.google.devtools.build.workspace.maven.DefaultModelResolver.resolveModel(DefaultModelResolver.java:96)
at com.google.devtools.build.workspace.maven.Resolver.resolveEffectiveModel(Resolver.java:172)
at com.google.devtools.build.workspace.maven.Resolver.resolveArtifact(Resolver.java:137)
at com.google.devtools.build.workspace.GenerateWorkspace.generateFromArtifacts(GenerateWorkspace.java:123)
at com.google.devtools.build.workspace.GenerateWorkspace.main(GenerateWorkspace.java:64)
```
The cause is the dependency's pom is resolved as `file://${basedir}/src/test/lib/org/apache/httpcomponents/httpclient/4.2.5/httpclient-4.2.5.pom`, which can't be tested with HTTP HEAD request, obviously.
This patch is workaround, until there will be some better handling of such cases.
Closes #2348.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2348
PiperOrigin-RevId: 145523022
MOS_MIGRATED_REVID=145523022
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
length limit
When classpath length exceeds the command line length limit, we create
an empty classpath jar whose manifest contaning the whole classpath
value.
See: https://github.com/bazelbuild/bazel/issues/2242
Fixed: https://github.com/bazelbuild/bazel/issues/1780
--
Change-Id: Id6dd503c17f7f17e4a4c37fa01da24e2a1ea2155
Reviewed-on: https://cr.bazel.build/8353
PiperOrigin-RevId: 145521892
MOS_MIGRATED_REVID=145521892
|
|
|
|
|
|
|
|
|
|
| |
Fixed: https://github.com/bazelbuild/bazel/issues/2242
--
Change-Id: I6aa7c97487b3add30df59c4483e409bb4d4c7532
Reviewed-on: https://cr.bazel.build/8399
PiperOrigin-RevId: 145520851
MOS_MIGRATED_REVID=145520851
|
|
|
|
|
|
|
|
| |
The tool will be used to construct resources jars separately from JavaBuilder.
--
PiperOrigin-RevId: 145511455
MOS_MIGRATED_REVID=145511455
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145507177
MOS_MIGRATED_REVID=145507177
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145495392
MOS_MIGRATED_REVID=145495392
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145473478
MOS_MIGRATED_REVID=145473478
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145473123
MOS_MIGRATED_REVID=145473123
|
|
|
|
|
|
|
|
| |
performed in order to expose it in build summary output.
--
PiperOrigin-RevId: 145457357
MOS_MIGRATED_REVID=145457357
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
After discussing with thomaswk@, we've decided not to put these in the android_sdk.
*** Original change description ***
Add attributes to android_sdk rule so that they will be available for open sourcing android_device.
--
PiperOrigin-RevId: 145444443
MOS_MIGRATED_REVID=145444443
|
|
|
|
|
|
|
|
| |
sourcing android_device.
--
PiperOrigin-RevId: 145429610
MOS_MIGRATED_REVID=145429610
|
|
|
|
|
|
|
|
|
|
|
| |
Now Bazel JavaBuilder can specifiy a file as the manifest file, before
this it just creates the manifest file on the fly.
--
Change-Id: I515d63a008e2c9e9113c56d3646b8bc78b76b3a7
Reviewed-on: https://cr.bazel.build/8352
PiperOrigin-RevId: 145428635
MOS_MIGRATED_REVID=145428635
|
|
|
|
|
|
|
|
| |
transition at the top level for the expanded set of apple rule classes
--
PiperOrigin-RevId: 145421255
MOS_MIGRATED_REVID=145421255
|
|
|
|
|
|
|
|
| |
that they are running in hjar compilation
--
PiperOrigin-RevId: 145413255
MOS_MIGRATED_REVID=145413255
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks Bazel tests on Windows: see https://github.com/bazelbuild/bazel/issues/2408
--
PiperOrigin-RevId: 145411907
MOS_MIGRATED_REVID=145411907
|
|
|
|
|
|
|
|
|
| |
Remove (output != null) check which is always true and cleanup dependent
conditionals.
--
PiperOrigin-RevId: 145409269
MOS_MIGRATED_REVID=145409269
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is part of unifying the test strategies; here, I'm working towards
sharing the test environment setup.
This change moves code from previously closed source code into the open
source parts. The internal change is not visible, making this look like an
addition rather than a move..
The next change hooks this up to Bazel. I did this in order to reduce the
size of the change to make it easier to debug, review, and so that it's
smaller in case we have to roll it back. Unfortunately, that requires
duplicating some of the code in StandaloneTestStrategy until the next change
lands.
--
PiperOrigin-RevId: 145387109
MOS_MIGRATED_REVID=145387109
|
|
|
|
|
|
|
|
| |
brings it in line with the behavior in objc_library.
--
PiperOrigin-RevId: 145330154
MOS_MIGRATED_REVID=145330154
|
|
|
|
|
|
|
|
|
|
| |
Completion failures are usually caught and printed at the top-level, but
if they occur inside an Error Prone check they get wrapped and reported
as error diagnostics.
--
PiperOrigin-RevId: 145322258
MOS_MIGRATED_REVID=145322258
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145322062
MOS_MIGRATED_REVID=145322062
|
|
|
|
|
|
|
|
|
| |
This is required for compatibility with existing runtimes specified
as filegroups.
--
PiperOrigin-RevId: 145314598
MOS_MIGRATED_REVID=145314598
|
|
|
|
|
|
|
|
| |
finding actions based on intermediate artifacts.
--
PiperOrigin-RevId: 145303065
MOS_MIGRATED_REVID=145303065
|
|
|
|
|
|
|
|
| |
--
Change-Id: I0aa54455ba4a17ad42a22c31a04f6417544ea6df
Reviewed-on: https://cr.bazel.build/8431
PiperOrigin-RevId: 145293680
MOS_MIGRATED_REVID=145293680
|
|
|
|
|
|
|
|
| |
One's unused, the other is ok as protected.
--
PiperOrigin-RevId: 145291062
MOS_MIGRATED_REVID=145291062
|
|
|
|
|
|
|
|
|
|
| |
that provider to retrieve the executable binary to act as the bundle_loader.
Also passes the bundle loader's ObjcProvider and ObjcProtoProviders to the dylib deduping mechanism to avoid dual linking of symbols into the tests.
--
PiperOrigin-RevId: 145284598
MOS_MIGRATED_REVID=145284598
|
|
|
|
|
|
|
|
| |
(as oposed to proto_library targets) would result in a crash.
--
PiperOrigin-RevId: 145283582
MOS_MIGRATED_REVID=145283582
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks Bazel-Install-Trigger on CI.
*** Original change description ***
Bazel client, Windows: impl. ForEachDirectoryEntry
Implement ForEachDirectoryEntry on Windows using
FindFirstFileW / FindNextFileW.
Supports long paths and traversing junctions.
See https://github.com/bazelbuild/bazel/issues/2107
See https://github.com/bazelbuild/bazel/issues/2181
--
PiperOrigin-RevId: 145282158
MOS_MIGRATED_REVID=145282158
|
|
|
|
|
|
|
|
|
|
| |
the scope.
This seems to only have been a problem when the error was in an unselect path, as the query would have failed earlier otherwise.
--
PiperOrigin-RevId: 145282112
MOS_MIGRATED_REVID=145282112
|
|
|
|
|
|
|
|
| |
Also refactoring JavaProvider to use the Builder pattern, given that it is going to encapsulate a fair number of other providers.
--
PiperOrigin-RevId: 145280532
MOS_MIGRATED_REVID=145280532
|
|
|
|
|
|
|
|
|
|
| |
This cl relieves us from hard-coding -l and -l: flags in Bazel. To be able to
express the behavior in CROSSTOOL, we need to know what type of library are we
dealing with.
--
PiperOrigin-RevId: 145271426
MOS_MIGRATED_REVID=145271426
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145156880
MOS_MIGRATED_REVID=145156880
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145152574
MOS_MIGRATED_REVID=145152574
|
|
|
|
|
|
|
|
|
| |
we only care about success or failure, and this avoids an internal
API use.
--
PiperOrigin-RevId: 145151690
MOS_MIGRATED_REVID=145151690
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145145109
MOS_MIGRATED_REVID=145145109
|
|
|
|
|
|
|
|
| |
Fixes bazelbuild/bazel#1342
--
PiperOrigin-RevId: 145144856
MOS_MIGRATED_REVID=145144856
|
|
|
|
|
|
|
|
|
|
|
|
| |
Because the event handler's inner handlers are removed after each query
command, caching the handler caused a subset of subsequent commands'
errors (those reported through the resolver's handler) to go unlogged.
Also fix a bug with cycle detection in DelegatingWalkableGraph.
--
PiperOrigin-RevId: 145124271
MOS_MIGRATED_REVID=145124271
|
|
|
|
|
|
|
|
| |
Also some apple binary test cleanup along the way.
--
PiperOrigin-RevId: 145123804
MOS_MIGRATED_REVID=145123804
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145122327
MOS_MIGRATED_REVID=145122327
|
|
|
|
|
|
|
|
| |
proto_library's wrt strict Java deps.
--
PiperOrigin-RevId: 145120944
MOS_MIGRATED_REVID=145120944
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145119990
MOS_MIGRATED_REVID=145119990
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145091484
MOS_MIGRATED_REVID=145091484
|
|
|
|
|
|
|
|
| |
with the internal GenRule implementation.
--
PiperOrigin-RevId: 145087704
MOS_MIGRATED_REVID=145087704
|
|
|
|
|
|
|
|
|
| |
The code has been untouched and unused for over a year (it's very likely
broken) and we have other priorities for now.
--
PiperOrigin-RevId: 145087310
MOS_MIGRATED_REVID=145087310
|