-
Notifications
You must be signed in to change notification settings - Fork 25
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
Update James SHA-1 #932
Update James SHA-1 #932
Conversation
There is an issue with apache/james-project@88e1ae8 It seems latests versions of the plugin have some conflicts with git worktrees and submodules. I saw in the commit log history that @vttranlina already did an attempt a year ago to upgrade to version 6 before doing a revert for a similar reason. However, the issue linked by Tung, that I found as well, has been merged into version 7.0 (used in the plugin update): git-commit-id/git-commit-id-maven-plugin#639 However can see here git-commit-id/git-commit-id-maven-plugin#642 (comment) that maybe our case has not been handled (the I think might need to ask James community if we can revert this plugin upgrade for now? And will open an issue as well on that plugin repo to see if we can get support :) |
|
65bc328
to
8c9837b
Compare
Waiting for this to be merged: apache/james-project#2085 tested locally, it seems to work perfectly :) |
Maybe need to cherry-pick commit 8609830 |
8c9837b
to
3be53f2
Compare
Rebased after the merge on apache for git commit id plugin upgrade |
https://james-jenkins.lin-saas.com/job/Tmail%20build/job/PR-932/3/testReport/ Related with bouncycastle upgrade.... Not sure what's causing this yet |
I'm unsure to really understand what's going on... Tests are failing with : If I change in the I tried to look at if maybe something seems wrong, look around in forums, but not uch. Or maybe there is an issue with zip compression when encrypting in bouncycastle 1.77? I found this bcgit/bc-java#1577 that looks similar but no answers to it. Also by looking around the net, I tried with just setting As technically we encrypt the data with the private key that the user uploaded to tmail, do we need that though? Might be a bad idea, but exploring options here... Anybody has other ideas? @chibenwa maybe, I think you have a better expertise on that :) |
Applying here @quantranhong1999 suggestion: forcing back to version 1.70 for tmail part of the build, where we know it works. Could open an issue to try to tackle that back later. @chibenwa would you be ok with this? |
Very sad but OK with me. Though bouncy-castle would be more stable TBH. |
Or maybe we do not do something right somewhere... but I've been banging my head a long time on this, it should not be a blocker for now as well I think |
Version 1.77 seems to create weird issues during encryption with zip compression when decrypting it
9198092
to
92cd14f
Compare
No description provided.