-
Notifications
You must be signed in to change notification settings - Fork 5
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
SAK-45827 - gradebook classic jsf upgrade #20
base: 21.x
Are you sure you want to change the base?
Conversation
…on the data, where it actually makes sense
Remove the SpreadsheetUITag stuff and manually build the table Change some of the date/time formatting pieces
If/when this ever gets merged, some points of emphasis for testing:
|
IS someone willing to test this? It looks like a lot of effort! We don't use GB Classic much at all but this change looks solid ..... |
@austin48 are you willing to test this? You seem to be the only one still running gb1 |
@ottenhoff , Yes I can take a look at it. It's quite a big change, so it could take some time. We have some customizations to the All Grades tab, so I'll have to see if this affects our changes. Also, the JIRA number doesn't seem to match the title. |
Well, dang, did I do all those commits under the wrong jira? Should be SAK-45872 |
@ottenhoff and @maurercw, I just realized that this patch only applies to Sakai 22+. (haha, after I tried applying but failed to compile this patch for our Sakai 21.x instance, I think, due to errors on methods not supported in 21). I can try testing on a "vanilla" 22 instance, but it will be a bummer that I won't be able to test with our customizations for a while (I'm not scheduled to start upgrading to 22 until early 2023). |
Pretty sure I did it against 21x, but I'd have to go back and confirm since
it's been a while!
Chris
…On Tue, May 24, 2022, 5:55 PM austin48 ***@***.***> wrote:
@ottenhoff <https://github.com/ottenhoff> and @maurercw
<https://github.com/maurercw>, I just realized that this patch only
applies to Sakai 22+. (haha, *after* I tried applying but failed to
compile this patch for our Sakai 21.x instance, I think, due to errors on
methods not supported in 21).
I can try testing on a "vanilla" 22 instance, but it will be a bummer that
I won't be able to test with our customizations for a while (I'm not
scheduled to start upgrading to 22 until early 2023).
—
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACBPNZ47E3YE5QCMGD62RZ3VLVF63ANCNFSM5A7CZJBA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
i'm seeing compile errors on 21.x like
or did I not apply the patches correctly? |
I think the errors I mentioned above are due to our custom code in gradebook1. I can't reproduce the error when compiling a "vanilla" version of the gradebook1 21.x branch with this patch into our custom Sakai 21.x. Short of removing our custom code piece by piece (I tried removing a few places in our custom code that looked like it was using jsf faces context) until I find the problem, anyone have any guesses? |
I fixed our build error, sort of... There was a custom dependency that I think was no longer being used, but I don't know why it would make this fail (maybe it used an older version of jsf?) so I commented it out and the build completed. However, now on start up, I'm getting many errors like:
It looks like this PR's patch contains many changes to faces-config's xmlns. Again, it works fine on a vanilla Sakai install, but there must be more incompatibilities with our custom code... maybe more dependencies that use old JSF? do we also have to update those dependencies to use jsf2? I'd hate to keep playing whack-a-mole trying to merge this patch into our custom code. |
No description provided.