Jar has a very low set of overlap with other target types, including that jar sources *must* be .java, and no other target allows .java sources. As such, the difficulty in crafting a useful `build_target` invocation that allows both `jar` and anything else is high, and the usefulness is dubious. Just use `jar()` directly instead. This depends on the changes to make all of the jar() specific keyword arguments be handled by typed_kwargs so that the deprecation messages are correct and consistent.pull/12020/head
parent
a62a42b272
commit
d7acccd36d
3 changed files with 18 additions and 3 deletions
@ -0,0 +1,8 @@ |
|||||||
|
## Deprecate 'jar' as a build_target type |
||||||
|
|
||||||
|
The point of `build_target()` is that what is produced can be conditionally |
||||||
|
changed. However, `jar()` has a significant number of non-overlapping arguments |
||||||
|
from other build_targets, including the kinds of sources it can include. Because |
||||||
|
of this crafting a `build_target` that can be used as a Jar and as something |
||||||
|
else is incredibly hard to do. As such, it has been deprecated, and using |
||||||
|
`jar()` directly is recomended. |
Loading…
Reference in new issue