Make AjcForkOptions abstract and instantiate it via ObjectFactory #1197
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For better compatibility with Gradle 9.
In Gradle 9 we plan to replace task/extension properties with Provider API lazy types (Property/Provider/ConfigurableFileCollection). And with that BaseForkOptions will become abstract and have abstract methods, see change:
https://github.com/gradle/gradle/pull/30374/files#diff-c132a92f383d74b12cf1b727c41b2dbc07fffecb7f1ad19c6b1e343ee75cbd30
During smoke tests we found out that AcjForkOptions extends BaseForkOptions. But with Gradle 9 API it then fails with:
A solution to make it compatible with Gradle 9 is to make
AjcForkOptions
abstract and instantiate it via ObjectFactory. This is also ok for previous Gradle versions.