When aggregation is empty, don't throw an error (it causes project sync to fail)

What feature do you want to see added?

Here's the situation: I'm in the process of setting up publishing in my project, so there's lots to do. I just added nmcp and I'm in the process of setting it up, but I haven't finished yet.

I realise I haven't set up the signing plugin, so I add it and try refresh my project. But I run into a problem:

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'my-project'.
> Nmcp: the aggregation is empty. This is usually a misconfiguration. If this is intentional, set `allowEmptyAggregation` to true.

Obviously it's a problem that should be fixed, but the issue is because nmcp throws an exception in the configuration phase I've now lost IDE support, which would help me resolve the issue.

Suggestions:

• Make it a configuration-time warning, and a runtime-error.
• Report it problem using the Problems API https://docs.gradle.org/current/samples/sample_problems_api_usage.html

Upstream changes

No response

Are you interested in contributing this feature?

No response

Start by locating the code that raises “the aggregation is empty” during Gradle configuration, then read the linked Gradle Problems API sample. Determine how the empty aggregation should be reported without removing IDE support; done should preserve a useful configuration-time diagnostic while allowing project sync to continue as proposed.