-
Notifications
You must be signed in to change notification settings - Fork 41.6k
Description
This issue is follow-on from #34812. Our bootArchives configuration is very similar to Gradle's archives configuration. Following some advice from @jvandort, we've learned that Gradle is moving away from archives:
However, the important thing to note here is that the purpose of
archivesis not for it to be selected with attribute matching. We have specialized configurations for selecting specific artifacts:runtimeElementsandapiElementsin a java project, to name a few. archives is currently used a generic “bag of artifacts” which are to be built when theassembletask is executed. We are migrating away from thearchivesconfiguration by instead adding task dependencies directly to theassembletask instead of using thearchivesconfiguration as a middle-man. The reasoning for this is that we never intendedarchivesto participate in dependency-resolution.
We should do the same. We'll probably need to figure out how to do that in a backwards-compatible manner as I suspect that removing bootArchives without first deprecating it may cause problems for some users.