Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not apply required compilation dependencies from Gradle plugins #1

Open
andrew-k-21-12 opened this issue Jul 11, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@andrew-k-21-12
Copy link
Owner

Now if someone applies, for example, io.github.andrew-k-21-12.kjs-box.frontend-entry-point Gradle plugin, the corresponding target project automatically gets some Kotlin Wrappers dependencies for its jsMain source set.

While such approach allows to configure required Gradle projects faster, it lacks flexibility and forces the end users either to have prescribed compilation dependencies (what can introduce regression or force the related APIs to be updated) or to put additional efforts to set custom dependencies resolution in Gradle.

Review all Gradle plugins and consider ways to avoid automatic pulling of dependencies from them into target projects.

@andrew-k-21-12 andrew-k-21-12 added the enhancement New feature or request label Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant