This message was deleted.
# community-supports
Slackbot
11/21/2023, 10:21 PMThis message was deleted.
🧵 1
j
Joseph Ottinger
11/21/2023, 10:26 PMOkay, I was setting the group incorrectly - now it’s set properly, and I’m seeing deployment in
~/.m2/repository/com/foo/bar/gradle-plugin/1.2.6/*id("com.foo.bar.gradle-plugin") version "1.2.6"j
Javi
11/21/2023, 10:28 PMthe id is not based on the artifact coordinates, you need to set it explicitly with the Gradle plugin
Javi
11/21/2023, 10:29 PMj
Joseph Ottinger
11/21/2023, 10:29 PMwell, using the id from the plugins { create {… }} block isn’t working either
j
Javi
11/21/2023, 10:30 PMHave you added
mavenLocal()pluginManagementrepositoriesj
Joseph Ottinger
11/21/2023, 10:30 PMyes
j
Javi
11/21/2023, 10:30 PMWhich task are you calling to publish it locally?
j
Joseph Ottinger
11/21/2023, 10:31 PM./gradlew publishPluginMavenPublicationToMavenLocalj
Javi
11/21/2023, 10:31 PMCall
publishToMavenLocalJavi
11/21/2023, 10:31 PMProbably you are not publishing the marker artifact for that ID
j
Joseph Ottinger
11/21/2023, 10:32 PMand that fixed it. What the heck.
j
Javi
11/21/2023, 10:32 PMJavi
11/21/2023, 10:33 PMTwo artifacts are published, the normal one plus one associated to the ID, you can see the folder if you check the m2 tree
j
Joseph Ottinger
11/21/2023, 10:33 PMYeah, I saw it
Joseph Ottinger
11/21/2023, 10:33 PMShould I expect
./gradlew publish👍 1
Joseph Ottinger
11/21/2023, 10:34 PMI was doing too much specific invocation?
👍 1
j
Javi
11/21/2023, 10:34 PMI haven't tried to run
publish./gradlew publish --dry-runpublishToMavenLocalJavi
11/21/2023, 10:35 PMBut take care, maybe it can be publishing the plugin everywhere (MavenCentral, MavenLocal, whatever). So I would check it with
--dry-runj
Joseph Ottinger
11/21/2023, 10:35 PMWell, our actual repository requires access from circleci, so I can’t REALLY break it, but yeah
r
Ryan Schmitt
11/21/2023, 10:39 PMI save time by typing./gradlew publishToMavenLocal
./gradlew pTMLv
Vampire
11/22/2023, 2:07 AMpublishpublishToMavenLocal