Consider splitting the plugin in two: base and aggregate

[vlsi]

What feature do you want to see added?

Currently, the plugin is all-in-one, and it adds configurations and tasks only when user configures nmcp extension.

Have you considered going the other way around?

• Always generate the configurations and tasks, so users could add dependencies and wire the tasks
• Split plugin id in two: one that would scaffold zipPublication task, outgoing variant for others to consume; and the second plugin that would add aggregation capabilities (aggregating configuration, aggregate task, etc)

Currently, one can't use nmcpConsumer configuration via dependencies { nmcpConsumer(projects.core) } since the configuration is not created during plugin.apply call.

Upstream changes

No response

Are you interested in contributing this feature?

No response

[martinbonnin]

That sounds fair 👍 That would also probably fix #24 at the same time? (because the configurations would be regular configurations).

Only concern is having 2 different plugin ids... I'll look into this.

[martinbonnin]

@vlsi tentative PR is there: #29

Apologies for the large PR, for an overview of the changes, the README should be a good starting point.

There are now 2 plugin ids:

• com.gradleup.nmcp creates a Zip and Publish task for each publication. Configuring the central portal parameters is optional with that plugin.
• com.gradleup.nmcp.aggregation creates a single Publish task (publishAggregatedPublicationToCentralPortal)

Let me know what you think!

[martinbonnin]

Closed with #23