| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
|
| |
tool during incremental dexing
RELNOTES: none
PiperOrigin-RevId: 152838197
|
|
|
|
|
|
|
|
|
|
|
| |
provide a provider.
Previously we always executed the function, but didn't add the aspect to
the deps.
--
PiperOrigin-RevId: 148887089
MOS_MIGRATED_REVID=148887089
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 148275963
MOS_MIGRATED_REVID=148275963
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 147876411
MOS_MIGRATED_REVID=147876411
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 147793223
MOS_MIGRATED_REVID=147793223
|
|
|
|
|
|
|
|
| |
providers.
--
PiperOrigin-RevId: 147526961
MOS_MIGRATED_REVID=147526961
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Vanilla roll forward
--
PiperOrigin-RevId: 147512649
MOS_MIGRATED_REVID=147512649
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 147416635
MOS_MIGRATED_REVID=147416635
|
|
|
|
|
|
|
|
| |
[] can be fixed.
--
PiperOrigin-RevId: 147094979
MOS_MIGRATED_REVID=147094979
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145744124
MOS_MIGRATED_REVID=145744124
|
|
|
|
|
|
|
|
|
| |
This functionality is never used, have never been exposed to Skylark
and is a continuous pain to maintain and test.
--
PiperOrigin-RevId: 145079832
MOS_MIGRATED_REVID=145079832
|
|
|
|
|
|
|
|
| |
multiple jars have the same simple filename (e.g., l.jar)
--
PiperOrigin-RevId: 140880491
MOS_MIGRATED_REVID=140880491
|
|
|
|
|
|
|
| |
against rules. Aspects can attach to a rule if at least one set of required providers are present on the rule.
--
MOS_MIGRATED_REVID=140605023
|
|
|
|
|
|
|
|
| |
Also clean up the setting of aspect name in ConfiguredAspect and
AspectDefintion - it is now obtained from the AspectClass.
--
MOS_MIGRATED_REVID=140357052
|
|
|
|
|
|
|
| |
JavaCompilationInfoProvider is missing
--
MOS_MIGRATED_REVID=139842250
|
|
|
|
|
|
|
| |
This includes applying desugaring for mobile-install's stub apk.
--
MOS_MIGRATED_REVID=136111631
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133436157
|
|
|
|
|
|
|
|
|
|
|
|
| |
by class.
TransitiveInfoProviderMap enforces that the provider implements the interface it's keyed by
and provides accessors the reduce the amount of casting. This in general reduces boilerplate throughout wherever TransitiveInfoProviders are mapped by their class.
Also add shorthand for adding a provider where it only implements TransitiveInfoProvider once, reducing the redundant specification of the TransitiveInfoProvider class. Infer the class as the exclusive direct implementor of TransitiveInfoProvider to account for special cases like AutoValue and LicenseProvider.
--
MOS_MIGRATED_REVID=133386336
|
|
|
|
|
|
|
|
|
| |
"supports-workers" execution info tag.
This is a new requirement which helps Blaze decide whether an action can be executed via workers or not.
--
MOS_MIGRATED_REVID=126279864
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=123149803
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Rollback of commit e37c55eccbd4516b2db7aaf58ef95209dfad3ed4 is complete so rolling this semantically unrelated change forward again
*** Original change description ***
Automated [] rollback of commit b8946eabd60a199a66a1892701d52d9801c7fb1a.
--
MOS_MIGRATED_REVID=122736257
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=122626656
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=122620007
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=122473346
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=122342484
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
NativeAspectClass.
This a large refactoring of the aspects, currently we have the following:
- AspectClasses: The interface AspectClass is a implemented by either
SkylarkAspectClass or NativeAspectClass<NativeAspectFactory>.
They are wrappers for the AspectFactories and they hold the information about
the Class<> of the factory.
- AspectFactories (FooAspect.java): Represented by the interfaces
ConfiguredAspectFactory and NativeAspectFactory, also by
the interface ConfiguredNativeAspectFactory which is the union of the two
aforementioned interfaces.
All aspects implement ConfiguredNativeAspectFactory except Skylark aspects
which implement only ConfiguredAspectFactory.
After this CL the distinction between NativeAspectFactories and NativeAspectClasses
dissappear, namely aspect that extends NativeAspectClass is considered native
and if it implements ConfiguredAspectFactory it is configured.
Therefore the interfaces NativeAspectFactory and ConfiguredNativeAspectFactory
both disappear.
With this refactoring the aspectFactoryMap in the ConfiguredRuleClassProvider
changes its type from (String -> Class<? extends NativeAspectClass>)
to (String -> NativeAspectClass) which means it is now able to have an instance
of the aspect instead of its Class only.
By doing this, it is now possible to pass parameters when creating an
aspect in the ConfiguredRuleClassProvider.
--
MOS_MIGRATED_REVID=120819647
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119999213
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119104560
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118969066
|
|
--
MOS_MIGRATED_REVID=117186609
|