From ed73e4a2aa6911b81ffa2bf0b80398bc6ab008f8 Mon Sep 17 00:00:00 2001
From: Atsushi Eno <atsushieno@gmail.com>
Date: Sat, 9 Dec 2023 17:36:01 +0900
Subject: [PATCH] go back to "resolve `implementation` via maven" instead of
 `project()`.

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...
---
 build.gradle                    | 5 ++++-
 ktmidi-jvm-desktop/build.gradle | 6 ++----
 2 files changed, 6 insertions(+), 5 deletions(-)

diff --git a/build.gradle b/build.gradle
index 579b73d0a..8c2d31b0d 100644
--- a/build.gradle
+++ b/build.gradle
@@ -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()
diff --git a/ktmidi-jvm-desktop/build.gradle b/ktmidi-jvm-desktop/build.gradle
index 360bb496c..77058da88 100644
--- a/ktmidi-jvm-desktop/build.gradle
+++ b/ktmidi-jvm-desktop/build.gradle
@@ -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