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

Publishing a settings plugin #191

Open
sgammon opened this issue Aug 1, 2023 · 4 comments
Open

Publishing a settings plugin #191

sgammon opened this issue Aug 1, 2023 · 4 comments

Comments

@sgammon
Copy link

sgammon commented Aug 1, 2023

Expected Behavior

Some plugins, for example the Gradle Enterprise Plugin, accurately show on the Plugin Portal when they are settings-time plugins:

Screenshot 2023-08-01 at 3 43 51 PM

Current Behavior

It is unclear how other plugins can trigger this UI

Context

We are the authors of a settings-time plugin (the Buildless plugin), but our page shows regular installation instructions which can confuse users.

@ov7a
Copy link
Member

ov7a commented Aug 2, 2023

Thank you for your interest in Gradle!

This feature request is in the backlog of the relevant team, but this area of Gradle is currently not a focus one, so it might take a while before it gets implemented.


There is no way to set this up from the user side right now. The enterprise plugin is the only plugin for which this is implemented (hardcoded, to be precise).

@sgammon
Copy link
Author

sgammon commented Aug 3, 2023

@ov7a you don't think it's a bit unfair to plugin authors and users? hm :/ okay. Thank you in any case for your help

@ov7a
Copy link
Member

ov7a commented Aug 4, 2023

@sgammon I understand how you feel, and I'm not happy about this situation too.

@sgammon
Copy link
Author

sgammon commented Sep 23, 2023

@ov7a / cc @hansd

Screenshot 2023-09-23 at 2 29 28 PM

another day, another user is confused because Gradle Plugin Portal prefers its own plugins with capabilities not granted to others (in an ecosystem they control -- a sign of monopolistic behavior, I might add)

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

No branches or pull requests

2 participants