maven-compiler-plugin | Apache Maven Compiler Plugin | Plugin library

changing pom.xml solved my problem:

You can add a manifest to your task since it is type Jar. Specifying an entrypoint with the Main-Class attribute should make your Jar executable.

You need to have an uber jar to run. Because the JVM needs to have all the necessary dependencies to run.

Add below plugin to your pom.xml:

For anyone who needs to get poi-ooxml up and running, this is my solution.

Maven downloads batik and other dependencies such ad xalan that are not necessary for this to work. Therefore, do not use Maven for this except for a couple of dependencies which I will mention.

1. Download and extract the official poi binary zip from poi.apache.org

2. From the downloaded and extracted zip, navigate to the auxiliary folder and modify the META-INF/services/org.apache.batik.script.InterpreterFactory file in the batik-all-1.13.jar using vim or vi. Comment out the line "org.apache.batik.bridge.RhinoInterpreterFactory" and save.

3. Add all jar files as an external library from the following directories: -auxilliary, lib and ooxml-lib. Add all jars from the poi-5.0.0 directory except for poi-ooxml-full-5.0.0.jar.

4. From maven, add the following dependencies and you are good to go :

I fixed the issue -- the problem was that I was I had entered the MondoDB dependencies under plugin

The problem is your Maven version is too old. It's not compatible with JDK 16.

Try to manually install maven version 3.8.1:

https://maven.apache.org/install.html

This will solve your problem without downgrading your JDK version.

You need to cast object to list.

ClassLoader.getSystemResource() will return a different kind of URL depending on how the test class is executed:

• from an IDE, it's a file ("file:/path/to/db/test.sql"), so Path.get(uri) is OK
• from Maven, it's a JAR (ZIP) entry ("jar:file:/path/to/dist-1.0-SNAPSHOT.jar!/db/test.sql"), so Path.get(uri) throws a FileSystemNotFoundException

The URL is enough to know if the entry exists.
If so, its content can be read using url.openStream().

Apache Arrow utilizes a pretty similar idea of Java off-heap storage as Apache Ignite does. For Apache Arrow it means that objects like IntVector don't actually store data in their on-heap layout. They just store a reference to a buffer containing an off-heap address of a physical representation. Technically it's a long offset pointing to a chunk of memory within JVM address space.

When you restart your JVM, address space changes. But in your Apache Ignite native persistence there's a record holding an old pointer. It leads to a SIGSEGV because it's not in the JVM address anymore (in fact it doesn't even exist after a restart).

You could use Apache Arrow serialization machinery to store data permanently in Apache Ignite or even somewhere else. But in fact after that you're going to lose Apache Arrow preciousness as a fast in-memory columnar store. It was initially designed to share off-heap data across multiple data-processing solutions.

Therefore I believe that technically it could be possible to leverage Apache Ignite binary storage format. In that case a custom BinarySerializer should be implemented. After that it would be possible to use it with the Apache Arrow vector classes.