Brtdku

I created a jar of a Scala application using maven-assembly-plugin. Now when I execute the jar with java -jar pathtojarmyapp.jar it throws the following error:

Exception in thread "main" Exception in thread "Timer-0" java.lang.RuntimeException: java.sql.SQLException: No suitable driver found for jdbc:calcite:

        at org.apache.calcite.tools.Frameworks.withPrepare(Frameworks.java:159)

        at org.apache.calcite.tools.Frameworks.withPlanner(Frameworks.java:114)

        Caused by: java.sql.SQLException: No suitable driver found for jdbc:calcite:

        at java.sql.DriverManager.getConnection(Unknown Source)

        at java.sql.DriverManager.getConnection(Unknown Source)

        at org.apache.calcite.tools.Frameworks.withPrepare(Frameworks.java:153)

        ... 17 more

java.lang.RuntimeException: java.sql.SQLException: No suitable driver found for jdbc:calcite:

        at org.apache.calcite.tools.Frameworks.withPrepare(Frameworks.java:159)

        at org.apache.calcite.tools.Frameworks.withPlanner(Frameworks.java:114)

        at java.util.TimerThread.mainLoop(Unknown Source)

        at java.util.TimerThread.run(Unknown Source)

Caused by: java.sql.SQLException: No suitable driver found for jdbc:calcite:

        at java.sql.DriverManager.getConnection(Unknown Source)

        at java.sql.DriverManager.getConnection(Unknown Source)

        at org.apache.calcite.tools.Frameworks.withPrepare(Frameworks.java:153)

        ... 8 more

When I run the application through an IDE (IntelliJ) it works fine.

Can anyone tell me why this is happening?

EDIT1: I opened the jar file and saw that the calcite-core jar is present in org/apache/calcite jar.

EDIT2: I tried changing the version of calcite-core. I was using 1.15.0 earlier and now I'm using 1.18.0 but the error is still there.

Seems there is a bug in the Apache Flink - https://issues.apache.org/jira/browse/FLINK-4581

Although I still haven't found a solution to the calcite-core driver problem, I managed to find another way to execute the jar.

I added the following two plugins to my pom.xml. The maven-dependency-plugincopies all the relevant dependency jars into a lib folder and the maven-jar-plugin makes a single executable jar file.

                <groupId>org.apache.maven.plugins</groupId>

                <artifactId>maven-dependency-plugin</artifactId>

                <configuration>

                    <outputDirectory>${project.build.directory}/lib</outputDirectory>

                    <excludeTransitive>false</excludeTransitive>

                    <stripVersion>false</stripVersion>

                </configuration>

                <executions>

                    <execution>

                        <id>copy-dependencies</id>

                        <phase>package</phase>

                        <goals>

                            <goal>copy-dependencies</goal>

                        </goals>

                    </execution>

                </executions>

            </plugin>



            <plugin>

                <groupId>org.apache.maven.plugins</groupId>

                <artifactId>maven-jar-plugin</artifactId>

                <version>2.4</version>

                <configuration>

                    <archive>

                        <manifest>

                            <addClasspath>true</addClasspath>

                            <classpathPrefix>lib/</classpathPrefix>

                            <mainClass>com.example.MainClass</mainClass>

                        </manifest>

                    </archive>

                </configuration>

            </plugin>

Note: Adding <mainClass>com.example.MainClass</mainClass> will make manifest.mf aware of what the main class is.