This message was deleted.
# plugin-developments
Slackbot
09/20/2023, 6:12 PMThis message was deleted.
v
Vampire
09/20/2023, 6:28 PMYou mean
PluginManager.withPluginwithIdk
Kelvin Chung
09/20/2023, 6:29 PMYes
v
Vampire
09/20/2023, 6:30 PMThat would then probably be
plugins.withTypepluginsWhile not deprecated, it is preferred to use the methods of this interface or the {@link #getPluginManager() plugin manager} than use the plugin container.But if you really need by type, that's probably the way to go.
Vampire
09/20/2023, 6:31 PMBtw. I'm curious, why do you prefix all questions with "QQ:"?
You're the only one I know doing this, and practically all posts here are questions in one way or another anyway. 😄
k
Kelvin Chung
09/20/2023, 6:32 PMThat does seem to be a rough edge; I can imagine that, for complex plugins, you have a collection of smaller plugins with no IDs that you want to apply in a way that reordering the order they are applied won't break things.
Kelvin Chung
09/20/2023, 6:32 PM"QQ" is for "quick question"
v
Vampire
09/20/2023, 6:37 PMWell, you could give them IDs, but - especially if this is within your plugin project - I guess using type is fine.
I guess using by id is usually preferred as then it can work, whehter the plugin in question is on the classpath at all or not either way.
k
Kelvin Chung
09/20/2023, 6:40 PMI think the orthodoxy here is that "IDs are for plugins that you expect other people to apply", so a plugin that doesn't have one is for "internal use only", even though it doesn't really matter to Gradle anyways. I think I was expecting some kind of symmetry, but it could be just me.
v
Vampire
09/20/2023, 6:53 PMYeah, well, as I said,
plugins.withType