Skip to content

Commit

Permalink
go back to "resolve implementation via maven" instead of project().
Browse files Browse the repository at this point in the history
JavaCPP brings in another complication that `XYZ-platform` does not exist as a
module but created as part of `XYZ` module. There is no way to resolve the
`-platform` jar.

We may have to fight the Gradle package resolution failure issue if it still
happens, but now we removed all those platforms jars from `rtmidi-javacpp`
things may work now...
  • Loading branch information
atsushieno committed Dec 9, 2023
1 parent bf3e051 commit ed73e4a
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 5 deletions.
5 changes: 4 additions & 1 deletion build.gradle
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,10 @@ plugins {

allprojects {
group = 'dev.atsushieno'
version = '0.6.2'
if (name == "rtmidi-javacpp")
version = libs.versions.rtmidi.javacpp.get()
else
version = '0.6.2'

repositories {
google()
Expand Down
6 changes: 2 additions & 4 deletions ktmidi-jvm-desktop/build.gradle
Original file line number Diff line number Diff line change
Expand Up @@ -2,15 +2,13 @@ plugins {
id 'org.jetbrains.kotlin.jvm'
id 'maven-publish'
id 'signing'
id "org.bytedeco.gradle-javacpp-platform" version "1.5.9"
}

dependencies {
implementation project(":ktmidi")
implementation libs.alsakt
//implementation libs.rtmidi.javacpp
//implementation libs.rtmidi.javacpp.platform
implementation project(":rtmidi-javacpp")
implementation libs.rtmidi.javacpp
implementation libs.rtmidi.javacpp.platform

implementation libs.kotlinx.coroutines.core
implementation libs.kotlinx.datetime
Expand Down

0 comments on commit ed73e4a

Please sign in to comment.