Revert "Removed reflection on Kotlin binding" #124
Merged
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.
This partially reverts #101 to maximize the compatibility with complex build setups.
As per the general rule classpath should be consistent and interesting plugins should be added in the same classpath, there is a special use case we want to support:
Given the following structure:
buildSrc/src/main/kotlin/my-constants.gradle.kts
-> uses this plugin to create some constantsbuild.gradle.kts
-> appliesmy-constants
and thekoltin
plugin.Without this reflection logic, you'll be forced to promote the
koltin
plugin as well to thebuildSrc
classpath.