Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish JSyn on Maven #82

Open
philburk opened this issue Jul 2, 2020 · 9 comments
Open

Publish JSyn on Maven #82

philburk opened this issue Jul 2, 2020 · 9 comments

Comments

@philburk
Copy link
Owner

philburk commented Jul 2, 2020

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

@wsargent
Copy link

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
Copy link
Owner Author

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

@ligi
Copy link
Contributor

ligi commented Aug 25, 2021

isn't this a duplicate of #54 ?

@philburk philburk self-assigned this Apr 10, 2023
@philburk
Copy link
Owner Author

@ligi in #54 you wrote:

FYI: as #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
Copy link
Contributor

ligi commented Apr 10, 2023

yes - exactly.

@philburk
Copy link
Owner Author

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
Copy link
Owner Author

Using jitpack should be documented.

@philburk philburk added this to the v17.1.0 milestone Apr 10, 2023
philburk added a commit that referenced this issue Apr 11, 2023
@philburk
Copy link
Owner Author

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

@philburk philburk removed this from the v17.1.0 milestone Apr 22, 2023
@philburk
Copy link
Owner Author

philburk commented Jan 4, 2024

There are some reasons not to rely solely on jitpack.
gradle/gradle#16310 (comment)

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants