Skip to content

Conversation

@chadlwilson
Copy link
Contributor

@chadlwilson chadlwilson commented Oct 4, 2025

@chadlwilson chadlwilson force-pushed the fix-multi-string-notation-deprecation branch from 9fa963d to 8392535 Compare October 4, 2025 09:59
@toplac
Copy link

toplac commented Oct 8, 2025

@jk1 Are there any chances that this PR will be merged and a version released?

@chadlwilson
Copy link
Contributor Author

I'm wondering if we might need to community-fork this plugin to get some of the maintenance work done, as I am not sure there are any maintainers others than @jk1 here?

@chadlwilson
Copy link
Contributor Author

It's worth noting that this partially conflicts with #314 which attempts to change artifact resolution to use a different approach to address #313. My change doesn't change anything logically.

@chadlwilson chadlwilson mentioned this pull request Oct 27, 2025
@chadlwilson
Copy link
Contributor Author

I'll rebase shortly.

@chadlwilson chadlwilson marked this pull request as draft October 30, 2025 12:12
Multi-string dependency notation is deprecated with Gradle 9 for removal in Gradle 10.
@chadlwilson chadlwilson force-pushed the fix-multi-string-notation-deprecation branch from 8392535 to bece499 Compare October 30, 2025 16:43
@chadlwilson chadlwilson marked this pull request as ready for review October 30, 2025 16:43
@chadlwilson
Copy link
Contributor Author

@bdellegrazie done, PTAL :-)

@bdellegrazie bdellegrazie merged commit bb5519d into jk1:master Oct 30, 2025
1 check passed
@chadlwilson chadlwilson deleted the fix-multi-string-notation-deprecation branch October 30, 2025 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Gradle 9.1.0 + Plugin 2.9 => Gradle 10.x deprecation / fail warning generated for generateLicenseReport task

3 participants