-
Notifications
You must be signed in to change notification settings - Fork 33
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
Make sure that there are no encoded symbols in the jar file paths #198
Conversation
@starksm64 I'm not sure what the process is nowadays so I didn't merge it but this looks good to me and would unblock some Hibernate Validator work if you could get something released. Thanks! |
Hey @starksm64, Bump?
|
So do you need a service release of the TCK? |
Hey,
yes, that would be nice. if we get this patch released then we'd be able to move forward with the Hibernate Validator work. Thanks! |
@marko-bekhta we discussed at the platform call today for requesting a service release to take this PR in. In order to do a service release, a challenge is need. Can you raise an issue here with the tag of |
Hey @Emily-Jiang |
Nothing else required, I'll release the 3.1.1 service today |
Thanks a lot! |
Thank you @marko-bekhta @starksm64 ! |
Hey @starksm64 ,
I was looking into problems running a TCK on CI after some unrelated upgrades, and noticed that using code source location can result in a path like:
where
@
is encoded (%40
) and which results in this file being not found. The suggested change to calltoURI
should address the encoding/decoding issue.