Publish JSyn on Maven

[philburk]

GitHub has a Packages section that can be used to simplify the process.

[wsargent]

This would be great. I'm looking at adding some audio cues for exposing the GC behavior in Java https://twitter.com/will_sargent/status/1283075547111649280

[philburk]

@wsargent - #83 was merged so it should now be easy to publish JSyn on Maven.

[ligi]

isn't this a duplicate of #54 ?

[philburk]

@ligi in #54 you wrote:

FYI: as https://github.com/philburk/jsyn/pull/83 is merged and introduced gradle you can now consume it via jitpack (alternative to maven central - IMHO even better) like so: implementation 'com.github.philburk:jsyn:16.8.1'

Can you expand on this? Does jitpack make my GitHub releases automatically available without having to post on Maven?!

[ligi]

yes - exactly.

[philburk]

I did an experiment with a new project. I created a fresh project and added code to the build.gradle.kts file. It worked!

Added Jitpack.

repositories {
    mavenCentral()
    maven { url = uri("https://jitpack.io") }
}

Added JSyn dependency.

dependencies {
    testImplementation("org.junit.jupiter:junit-jupiter-api:5.8.1")
    testRuntimeOnly("org.junit.jupiter:junit-jupiter-engine:5.8.1")
    implementation("com.github.philburk:jsyn:v16.8.1")
}

Note that the kts gradle files have a different syntax from the Groovy gradle files.

[philburk]

Using jitpack should be documented.

[philburk]

Documented in README. Do we still need a Maven repo? Deprioritizing this for now.

[philburk]

There are some reasons not to rely solely on jitpack. https://github.com/gradle/gradle/issues/16310#issuecomment-785945980

Folks continue to ask for a Maven repo so I bumped the priority back up.