Replies: 5 comments 4 replies
-
Thanks, @dukeh3. It's mainly because of this: #175 You can easily fork, and modify the corresponding property in the pom file. |
Beta Was this translation helpful? Give feedback.
-
hello, @dukeh3. please note the repository on which you're commenting (nostr-java) uses java 1.8 whereas the java22 variant (nostr-java-avlo-fork) is a fork of the nostr-java 1.8 repo. that being said, you make a good point re: jdk21 vs jdk22. if you've already made a jdk21 nostr-java-avlo-fork variant, you're welcome to submit a pull request to that repo. otherwise, i'll produce a jdk21 variant of nostr-java-avlo-fork soon and notify you when it's available. |
Beta Was this translation helpful? Give feedback.
-
I didn't think about that, and wasn't aware of it, when changing to 22 in the latest release. Might have to downgrade again to 21... |
Beta Was this translation helpful? Give feedback.
-
pom jdk downgrade to v.21 (plus various updates 1 and 2 to my fork of eric's develop branch) are available via my repo branch java21. eric- per your interest, you can examine/comment/critique/merge its diffs as you see fit, or otherwise lmk if you'd prefer i submit a PR to your develop (or other) branch instead. |
Beta Was this translation helpful? Give feedback.
-
Ok I have created a PR on my version of nostr-java and downgraded it to java 21. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I was looking into finding a good java library for nostr to use in my key-manager, and found your (as far as I have seen) excellent library. But why do you use java 22, and not the LTS version java 21? Its a pain to use non LTS version of java in production
Beta Was this translation helpful? Give feedback.
All reactions