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

Migrate to Maven Central for jar distribution, Jcenter and Bintray are being shut down by May 1 2021 #55

Open
mkdillard opened this issue Feb 5, 2021 · 15 comments
Assignees
Labels
🎉 enhancement New feature or request

Comments

@mkdillard
Copy link

Thanks for proposing a new feature!

Motivation

Existing jar distribution through jcenter bintray will be shutting down on May 1, 2021. This renders the current repository based distribution broken.

https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/

Proposed solution

Migrate build artifacts to use maven central repository instead of jcenter bintray

Alternatives

Users can grab the github release artifacts and upload to local repositories themselves, but not centralized and a higher barrier to entry for some users.

Additional context

N/A

@mkdillard mkdillard added the 🎉 enhancement New feature or request label Feb 5, 2021
@Hywan Hywan self-assigned this Mar 2, 2021
@Hywan
Copy link
Contributor

Hywan commented Mar 2, 2021

Yup, we will do that :-).

@samkirton
Copy link

bump

only a couple of days left until the dependency is not available

@mathieuancelinserli
Copy link

Hey @Hywan, any news about this one ?

It would be super helpful to have wasmer-java on maven central now that bintray is down.

Maybe we can help you in some way ?

@Hywan
Copy link
Contributor

Hywan commented May 28, 2021

I know I'm late on this one. Sorry! Any help is welcomed 🙂!

@ftomassetti
Copy link

@Hywan unfortunately this basically means that the project cannot be used at the moment

@dazraf
Copy link

dazraf commented Sep 21, 2021

Hi,

I maintain a few OSS packages, publishing to Maven central and I can attest that it's tricky to configure, semi-manual and a very slow process!

An alternative is to publish to Github Packages! This looks a lot easier - would you like me to help?

cheers,
dazraf

@ftomassetti
Copy link

I think that users need GitHub credentials to download from GitHub packages, and that would be complicate for all CI processes using the package. I also find the Maven central publication suboptimal but alternatives cause problems for users of the package

@dazraf
Copy link

dazraf commented Sep 22, 2021

@ftomassetti good points - also Github Packages has tiered pricing to consider which is not great.
I wish I could help with this topic - I've done this work before on gradle and maven projects. It's really one for someone with maintainer access (and access to various secrets including the gpg keys registered with sonatype). 😔

@angelcervera
Copy link

Any update? Maybe we can consider this project deprecated and not under maintenance. A solution would be to find another maintainer.

@kezhenxu94
Copy link

kezhenxu94 commented Feb 14, 2023

Hey, any update or need any help? I’m recently investigating the possible to integrate this project into our OSS project but found it’s not published to maven central yet. Would be really helpful if you can published it to the maven central. Thanks!

if you need help I’m really willing to help.

@Erhannis
Copy link

I think jitpack can pull dependencies straight from github - I'm not sure if there are caveats or what. It MAY already work without you even needing to do anything (the library or two I've tried before did) or it may have e.g. compilation limits or something, dunno

@Hywan
Copy link
Contributor

Hywan commented Sep 15, 2023

You should ping @syrusakbary. I'm no longer working at Wasmer.

@Oliver-makes-code
Copy link

Any updates? I wanna use wasm for a project but I can't import this

@acheong08
Copy link

acheong08 commented Jan 22, 2024

It's relatively easy to self host a mavel repository. I was able to upload a version to a Reposilite instance in a few minutes: https://maven.duti.dev/#/releases/org/wasmer/wasmer-jni-amd64-linux

I wouldn't use it though since this is pretty much unmaintained. Anyone know of an alternative?

@acheong08
Copy link

Well, I was originally looking to use wasm so I can avoid having to mess with multiple jars for each operating system. Seems like the runtime is still platform specific. Sticking to hawtjni

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🎉 enhancement New feature or request
Projects
None yet
Development

No branches or pull requests