Skip to content

Remove bootArchives configuration in favour of adding task dependencies to assemble #34963

Open
@wilkinsona

Description

@wilkinsona

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 archives is not for it to be selected with attribute matching. We have specialized configurations for selecting specific artifacts: runtimeElements and apiElements in a java project, to name a few. archives is currently used a generic “bag of artifacts” which are to be built when the assemble task is executed. We are migrating away from the archives configuration by instead adding task dependencies directly to the assemble task instead of using the archives configuration as a middle-man. The reasoning for this is that we never intended archives to 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions