-
-
Notifications
You must be signed in to change notification settings - Fork 6
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 AdoptOpenJdk api V3 #15
Comments
I don't really plan on working on njre anymore as I don't have any use for it and it's not particularly depended on. I'll still look at PRs and I'm open to transfering ownership to another maintainer. |
As my repos seems to be the ones the most using njre, it would make sense ... :) I can own & maintain njre if you wish so ! |
Sounds good to me ! I'll transfer ownership. |
Ok, I'll take good care of it :) |
@raftario I may have some free time these next times, I'm ready for transfer when u are :)
|
I already added you as a contributor on npm and initiated the GitHub repo transfer 👍 |
Didn't see the acceptance mail in the middle of all github notifs mails :) |
@nvuillam What ended up being the status of this issue? I just tried to use |
@jhale1805 i've been lazy... while it worked i did nothing, are u sure V2 does not work anymore ? |
@nvuillam I tried both examples in the docs and each one gave a JSON parsing error that resulted from the response being the HTML of a server timeout page. That said, while I've been programming for several years, I'm still new to JavaScript, so I could also totally believe that I did something wrong, even though I copy and pasted the exact code from the examples. As for contributing, I'll definitely take a look. I'm currently a student so I don't know how much time I'll have. I also found an alternate way to accomplish my immediate goal, but this package does seem valuable to other projects I'd like to tackle in the future so I'll see what I can figure out. |
Reading through their migration guide, it looks like it might be as simple as changing the base url for the request... Update: that migration guide is for switching to eclipse maintained builds, which doesn't include as wide of a variety of jdk/jre builds However, the v3 API seems pretty straightforward, and it looks like binaries can now be requested directly instead of requiring an intermediary request for the path to the binary. In all, we'd have to fill out the |
That seems to be a great little student project, I'll write a note for your teachers, they'll surely appreciate that you already contribute to open source :) |
I'm not sure if relevant for you, but I published an own package (like a decade ago) based on |
I inherited njre maintenance after using it for https://github.com/nvuillam/node-java-caller ... which looks quite similar to node-java-connector ^^ |
* migrate to adoptium API v3; fixes #15 * adjust whitespace * use adoptopenjdk API by default * fix vendor param description * linting Will help to fix nvuillam/npm-groovy-lint#288 --------- Co-authored-by: Mark Heiges <mark.heiges@semanticbits.com>
@mheiges v1.0.0 has been released with your updates, and I also upgrade many dependencies :) Thanks again for the PR ! |
Ad discussed here with AdoptOpenJdk maintainers, it is strongly encouraged to migrate to their V3 api, as the V2 has been marked as deprecated
It would be nice to migrate njre to V3 :)
https://api.adoptopenjdk.net/
The text was updated successfully, but these errors were encountered: