Replies: 8 comments
-
Hello, if you use Burnignwave Core with Burningwave JVM-Driver you need only the jvm-driver.properties of the Burningwave JVM-Driver library. You need also to include all classes of ToolFactory JVM Driver. Try with these and let me know if you solved |
Beta Was this translation helpful? Give feedback.
-
Hi @Roberto-Gentili and thanks for the reply. Honestly I have no clue which JVM driver I need nor what they even do, lol! There really weren't any docs that explained any of that and I just saw that both those drivers were included as Maven dependencies. I have no idea what they do, why they are needed, how they differ, or why I'd want one over the other. I followed the guide here Ether way, I feel like I've already tried what you are suggesting. I copied ALL class files from the following jars into my uber jar
When you say "Burningwave JVM-Driver" and "ToolFactory JVM Driver", I'm just guessing that those correspond with the jars above. All I know is what Maven downloaded, which is those jar names above, so the other descriptive names don't really match anything I can see. (and I know nothing about this library :) ) Also, is there a reason you moved this to the jvm-driver repo? The loading of config and displaying the banner seem to be part of the core, no? |
Beta Was this translation helpful? Give feedback.
-
You need to unpack all three jars (core-12.62.6.jar, jvm-driver-8.14.1.jar (this is the Burningwave JVM-Driver), jvm-driver-9.4.3.jar (this is the ToolFactory JVM-Driver)) and:
|
Beta Was this translation helpful? Give feedback.
-
Right, I did all of that initially with the exception of bullet # 3. (I just picked a I'm still a little skeptical since none of this seems to explain the error stack traces, why my config wasn't picked up, why the banner was trying to display, and why the input stream was null. I would expect classdefnotfoud errors or similar if it was just a matter of missing class files. |
Beta Was this translation helpful? Give feedback.
-
I close the issue as it is not a library problem but a problem due to its manipulation |
Beta Was this translation helpful? Give feedback.
-
Remember also to take all |
Beta Was this translation helpful? Give feedback.
-
@Roberto-Gentili Thanks for all the help on this. Unfortunately, I only had a few hours to look into this library and I'm out of time to keep troubleshooting right now. I've just settled for a massive list of opens that I keep adding to. If I'm able to come back to this and still have questions I'll reach out. Please let me know if there's a better place to ask questions other than this ticket tracker. |
Beta Was this translation helpful? Give feedback.
-
If your report is not a library problem, for example, you can open a discussion. Let's do one thing: I reopen the issue and move it to discussions. I think you can solve this issue by copying all |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm looking into using burningwave to help out a Java-based CLI tool which needs to support Java 16+. I've added this line of code inside my main method
If I include the burningwave core and jvm-driver jars in the classpath, everything seems to be working at first blush. However, my tool needs to be able to be called via
and therefore any libraries needed to bootstrap it are "shaded" into the main "uber" jar. When I copy the class files,
banner.bwb
file andjvm-driver.properties
file into my uber jar, I get this error.It's really hard to tell what all is going on there. The
StaticComponentContainer.showBanner
portion of the outermost exception makes me think the issue is related to showing the banner.Things I've tried
org/burningwave/banner.bwb
file exists inside my uber jarbanner.hide
setting but I'm not really sure how to do this (a system property would be MUCH easer than a properties file!)burningwave.static.properties
file in the root of my uber jar doesn't seem to get picked upsetFileName()
method, but it's really unclear how that works. Is it expecting a path inside the jar? A relative path? An absolute path? Can it point anywhere on disk? Does it need a prefix likefile://
? I tried passing several things tosetFileName()
, including a non-existent path and it basically seems to just get ignored.I really can't figure out how to debug any of this, and the stack traces in the error above are super confusing, lol.
And furthermore, even if I can get past this banner error, I still have other questions such as how I can incorporate the
jvm-driver.properties
file from both of the required jvm-driver jars which are dependencies into a single uber-jar.Beta Was this translation helpful? Give feedback.
All reactions