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

add pluginManagement in settings.gradle file #293

Closed
santitigaga opened this issue Nov 4, 2022 · 1 comment · Fixed by #301
Closed

add pluginManagement in settings.gradle file #293

santitigaga opened this issue Nov 4, 2022 · 1 comment · Fixed by #301
Assignees
Labels

Comments

@santitigaga
Copy link
Contributor

Is your feature request related to a problem? Please describe.
By default, the plugin resolves from the public Gradle Plugin Portal. Many build authors would also like to resolve plugins from private repositories because the plugins contain proprietary implementation details, or just to have more control over what plugins are available to their builds, or only because the default repository is not available.

Describe the solution you'd like
it would be great to create the project with pluginManagement block in the settings.gradle file, this being the first block in the file.
This block should be added when the users execute the task updateProject too.

Additional context

Using gradle plugins

@santitigaga santitigaga added the good first issue Good for newcomers label Nov 4, 2022
@Gaviria9601 Gaviria9601 self-assigned this Nov 4, 2022
juancgalvis added a commit that referenced this issue Jan 12, 2023
juancgalvis added a commit that referenced this issue Jan 12, 2023
juancgalvis added a commit that referenced this issue Jan 12, 2023
* add pluginManagement closes #293
@github-actions
Copy link

🎉 This issue has been resolved in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants