-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Overcome 'String too large to record' issue with Truffle #40549
Conversation
This is better than the current state, but it is not yet the absolutely correct Relates: quarkusio#39387
List<String> allJarPaths = Stream.concat(parentFirst.stream(), regular.stream()).map(p -> p.toAbsolutePath().toString()) | ||
.toList(); | ||
recorder.set(allJarPaths); |
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 agree we could merge this as it's better to not fail but I'm thinking that we are definitely not registering the appropriate paths.
From what I can see, it points to the jars in ~/.m2
, which is definitely not expected.
@aloubyansky I suppose we have a way to point to the jars relative to the application? I'm not entirely sure though if the path would be the same in the case of a legacy-jar vs fast-jar vs uber-jar?
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 agree we could merge this as it's better to not fail but I'm thinking that we are definitely not registering the appropriate paths
Yup, I mentioned that in the issue as well
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.
@aloubyansky I suppose we have a way to point to the jars relative to the application? I'm not entirely sure though if the path would be the same in the case of a legacy-jar vs fast-jar vs uber-jar?
It would depend on the packaging. In case of uber-jar
it would be paths to the artifacts in the local Maven repo relative to the application root.
Status for workflow
|
public void set(String value) { | ||
System.setProperty("java.class.path", value); | ||
public void set(List<String> allJarPaths) { | ||
System.setProperty("java.class.path", String.join(":", allJarPaths)); |
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.
Is this meant to be OS-dependent?
This is better than the current state, but it is not yet the absolutely correct