-
-
Notifications
You must be signed in to change notification settings - Fork 6.2k
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
[groovy] don't use wildcards in classpath instead point out exact jar #25212
base: master
Are you sure you want to change the base?
Conversation
The problem this introduces is that you are now locked to hard coded version numbers. |
is it not possible to |
That was the point of the wildcard. So you didn't have to do 6 arguments just for groovy shit |
ok up to you then, sidenote: when requesting custom groovy, it was already necessary to define the versions of groove, text and lang. but yeah... edit i mean, before wildcards... |
Is this possibly still relevant? https://stackoverflow.com/questions/14722657/java-classpath-wildcard-behaviour ie quote the asterisk.
|
@fuzzard ill test it today and feedback |
tested with
it does not work
|
I will mention, im not against this per se, as it doesnt effect me in the slightest. The existing code is however correct in its functionality, so the true fault lies outside of this code base. |
true, therefore i marked as improvement, it is also not %100 necessary for me, i can use out of tree patches, frankly the people who might face this issue is minority, so it is also ok to not merge. Whoever has this problem can google and find this ticket in case they need to. |
Description
The issue is triggered when java is used in containerized environment.
When the container tool mounts/binds ext4 fs directly or with an overlayfs, the wildcard used in CLASSPATH (-cp) of java is not processing all the files pointed. This seems to happen only when host and the contaniner has different architecture (ie: 32 vs 64). So not every containerized env has this issue.
Workarounds:
For overlays fs, giving an option xino=on prevents this happening, for systemd-nspawn, --bind argument does mount with xino=off, therefore i could not find a way to modify this.
For ext4 mounting to container, i could not find a workaround.
General workaround in Kodi Buildsystem is to point directly to jar files instead of using wildcards.
Motivation and context
It prevents some existing and potential future build errors
How has this been tested?
in archlinux x86_64 host running aarhc64 and armv7h container.
What is the effect on users?
fixes #24225
Screenshots (if appropriate):
Types of change
Checklist: