hey folks...I have an odd issue going on with a pl...
# community-support
a
hey folks...I have an odd issue going on with a plugin I've created using the gradle init script. It's being published as "com.mycompanyplugin1.0" despite the fact I'm using the gradlePlugin template that is generated by the init script and I set the group and name in the build file. My gradlePlugin configuration looks like this: gradlePlugin { create("plugin") { id = "com.mycompany.plugin-id" displayName = "plugin display name" description = "plugin description" implementationClass = "com.mycompany.Plugin" } } I'm expecting it would be published looking something like: com.mycompany.plugin-idcom.mycompany.plugin id.gradle.plugin1.0 Would appreciate if anyone has some ideas what might be going on here! Thanks :)
e
it should publish both a marker with that id and the usual maven publication (project.group : project.name : project.version), the marker simply pointing to the real artifact
you can have any number of IDs for your plugin and any number of plugins in your project, which will lead to one marker per id all pointing to the one regular publication
a
ah ok, so if I have a project directory of "plugin" as generated by the init script, then that's going to conflict with other publications that have the same group
e
same group and name
a
yeah which we use the same group across our codebase...I didn't realize name was being used behind the scenes and thought that having a unique id would be good enough
I think we just found the root cause of a different bug i've been trying to figure out 🙂
thanks @ephemient! I will look into this
e
ah yeah you're gonna run into many issues if you have the same group:name in different modules, even if they're not published
a
yeah this was my issue! solved 2 problems with this question you've answered for me! Thank you so much!