JitPack.io

Hi Which repository was this for?

Hi @yooksi , Thank you for the detailed report! This will help us track down the issue

We have identified the issue and are working on a fix. As a workaround, adding junit platform launcher to dependencies solves the issue: ```gradle testRuntime 'org.junit.platform:junit-platform-launcher:1.5.0' ```

Hi @yooksi, This issue should be fixed now. Sorry about the interruption

Hi The repository settings page has a Commands section where you can specify which commands to execute during each build phase.

Btw, you can currently use it as a Gradle/Maven dependency from: https://jitpack.io/#Comcast/FreeFlow/d4bdd5edca

Hi Thanks for reporting and for the nice words! Had a quick look and it appears that the plugin publishes a jar but not a pom https://jitpack.io/com/github/Darkyenus/sbt-robovm/-1.12-g12bb28f-1/build.log and that's why...

Aha, so sbt publishes the pom to: `~/.m2/repository/org/roboscala/sbt-robovm_2.10_0.13/1.12.0/sbt-robovm-1.12.0.pom` while JitPack expects it to be: `~/.m2/repository/org/roboscala/sbt-robovm/1.12.0/sbt-robovm-1.12.0.pom` That is the issue.

Ok, got an update. One of our users got it working by renaming the directory where files are published: https://github.com/avdv/sbt-release/blob/252c2556a4efcf80cdc4078dacea94ec76185342/build.sbt#L9-L17 ``` publishM2 := { publishM2.value val d = file(sys.env("HOME")) /...

Hi @marco-brandizi Thank you for your suggestion! Overall its a good idea so will look into how we could add this feature