You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During every Gradle sync, we check if an instance of the swagger-gradle-codegen plugin is available either locally or on a remote maven repo. If the plugin is not found, the sample projects are excluded from the build (as they can't run without the gradle plugin).
Currently, the URL provided by Gradle Portal is broken (is missing a trailing slash) and this is preventing the build from finding the plugin. A workaroud is currently to install the plugin on Maven Local (./gradlew plugin:publishToMavenLocal) but we should definitely fix the script.
The text was updated successfully, but these errors were encountered:
I'm fixing the URL provided by the gradlePluginPortal() directive.
This is causing a failure in finding the swagger-gradle-codenge gradle
plugin and is resulting in the build not including the sample projects
during a sync.
See #58 for more context on the problems.
Fixes#58Fixes#57
Checking out the project and opening it locally results in Gradle not properly discovering the sample projects (thanks @doug-precocity for reporting).
The issue is caused by our
settings.gradle.kts
file here:swagger-gradle-codegen/settings.gradle.kts
Lines 37 to 49 in 14a4279
During every Gradle sync, we check if an instance of the swagger-gradle-codegen plugin is available either locally or on a remote maven repo. If the plugin is not found, the sample projects are excluded from the build (as they can't run without the gradle plugin).
Currently, the URL provided by Gradle Portal is broken (is missing a trailing slash) and this is preventing the build from finding the plugin. A workaroud is currently to install the plugin on Maven Local (
./gradlew plugin:publishToMavenLocal
) but we should definitely fix the script.The text was updated successfully, but these errors were encountered: