-
Notifications
You must be signed in to change notification settings - Fork 885
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
Jingle and Jingle File Transfer #489
Conversation
c6918f1
to
0bb230e
Compare
That would be great to have jingle file transfert to be able to send image files (camera, graph, etc...) to jabber client from openhab. What should I do to have a small review of the code quality ? Thanks |
fb5152f
to
58f7163
Compare
Sorry for the late response. My priority is to get the next Smack release out, but after that, I'll look at your code. Meanwhile, I have tirggered a CI run for this PR. Feel free to address any issues potentially found by the run. |
Thanks you so much! I'll address the issues from the CI in the next 7 days. |
Note that you can always run the checks locally via |
On my local it is working without error
That must be a version problem of some kind. I'll find it. Thanks |
Run |
yes sorry I went to quickly over it. That should be the right one
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've stopped the review half though, since this appears to be a half baked pull request (why isn't it marked WIP?). I think, if you want to continue working on Jingle support, then the initial work should be done outside of the Smack repository. Create an extra library with your code, that pulls in Smack as dependency. And, once the code is ready, it can be donated back to Smack.
@@ -131,6 +131,9 @@ allprojects { | |||
androidJavadocOffline = { getAndroidJavadocOffline() } | |||
junit4Projects = [ | |||
':smack-core', | |||
':smack-extensions', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am trying to phase out junit 4 in favor of junit 5 in Smack, so please don't add more projects here.
|
||
/** | ||
* Manager for JingleFileTransfer (XEP-0234). | ||
* Manager for XEP-0234 - JingleFileTransfers. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure why this was changed. I liked the old style more, as XEP numbers are less important than humand readable text. But the missing spaces should be added, after all, the title of the XEP is "Jingle File Transfer".
|
||
/** | ||
* Class representing the base of a JingleFileRequest. | ||
* TODO: Implement. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So this is not implemented? Why is it here than?
break; | ||
} | ||
} | ||
LOGGER.log(Level.FINE, "Reading/Writing finished."); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Those log statements are harmful. Especially when they only consist of a static string.
|
||
/** | ||
* Backend logic of an incoming file request (They request a file). | ||
* TODO: Implement. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again, this is not implemented? Then why isn't this PR marked as WIP?
Thanks for running again the CI tools against my PR. The 'TODO: Implement.' comments you spot in the code are wrong. The class are definitively implemented. I'll do the correction. I'll changes also to junit 5, the other comment readability problem and the logging. If I do an extra library with this code, can I still use the same package names as yours ? ie org.jivesoftware.smackx ? |
I'd suggest that you substitute |
Closing, feel free to reopen a new PR once you want to donate code back for review. |
This PR adds initial support (elements and providers) for XEP-0166 and XEP-0234
I took the work from https://github.com/vanitasvitae/Smack/tree/jftPR and made the modifications to the new code base.