update crypto libs and json#130
update crypto libs and json#130gjvanderheiden wants to merge 24 commits intohap-java:masterfrom gjvanderheiden:update_crypto_and_json_lib
Conversation
|
Note for a review:
|
fix typo in enum value
|
Can this PR pushed further? |
Signed-off-by: Eugen Freiter <freiter@gmx.de>
Remove event parameter
let me do some testing to verify that new libs are working fine with apple devices. |
|
@gjvanderheiden new pairing but old key new pairing and new key (complete fresh installation) |
Signed-off-by: Eugen Freiter <freiter@gmx.de>
|
Quite puzzled here. You're testing in openhab? I guess this is a version conflict. The linenumbers in the stacktrace don't make any sense to me in the source code. |
|
I always test with clean registry. Especially with object steaming. |
|
im testing with openHAB as i have more tests cases there and would like to keep it also backward compatible. |
|
Awesome. Thank you for testing this. |
|
I use hap-java and calimero-project/camino-core(https://github.com/calimero-project/calimero-core) in my small project at home, to control my KNX system. Didn't run in any issues with this branch, but my java project is simple in lib dependencies. |
|
update on testing status: so, im not able to test it with openHAB. |
|
@yfreyou are running into bndtools/bnd#2227 |
|
@J-N-K yes, it is that issue. but i have not found any solution. probably i need to do something like that but not sure how. |
|
ok. but now what? This PR is open for a long time now. Close it or push it. I'm sorry but I'm losing my interest in this project, stuff takes too long. |
@gjvanderheiden yeah. this is not the fastest project. i cannot decide on this PR as i could not tested. |
Perform maven build
Added release automation via Github workflow and upload to Maven Central for SNAPSHOTs and releases.
We don’t really need to build an assembly - most people will just consume this via maven, and if they don’t, they can do their own packaging.
Setup for release
Turns out wagon-scm doesn’t pick up the github properties the way the release plugin does. This fixes the site deploy. Fixes #141
Fix site-deploy
When we change the properties that we’re advertising over mDNS we unregister and re-register the service. However, we were calling unregister after changing the properties. This happened to work with our version of jmdns, which only compared the qualified name. jmdns has quite a few forks however, and it’s best to adhere to the implied contract when calling unregisterService. This is adapted from a fix proposed by J-N-K
Without this, the snapshot won’t auto-close.
Fix for unregistering service when re-advertising
I found that this pull request didn't work for me. That's why i created #137. |
|
This worked for me. @bentech - your branch didn't. Can you give more details on what didn't work here? There's only two functional differences between your branches:
That appears to be correct, as BouncyCastle fixed their implementation to do the same in 1.55 : bcgit/bc-java@9d0edfb#diff-9954afe44e634c0de04829e35b8a8903e2397865524bf3020794ed0aade8ce04 |
extend support for custom min/max/step to further characteristics
… update_crypto_and_json_lib # Conflicts: # CHANGES.md
|
Bump. More than a half year later... So what's the deal? |
|
Ignore my branch. I did ineed have an upstream problem. |
Pull Request Checklist
Please confirm that you've done the following when opening a new pull request: