RE: Running in Linux

[Julian Hyde]

> Is anyone running Halogen with Linux?
>
> I get a msg from JVM, both with command line and in eclipse:
>
> Unrecognized option: -XstartOnFirstThread
> Could not create the Java virtual machine.

Use the ant file I just checked in, and it enables the -XstartOnFirstThread
option only on Mac OS.

Julian

[luizfox]

Ok, I got it.

I had to add one line into your build.xml:

<pathelement location="${tp-lib.dir}/mysql-connector-java-5.0.7-
bin.jar"/>

I suppose it must be edited with any driver the user uses ( maybe you
don't get the error because ODBC driver already comes with the JVM).

I was becoming frustrated with it, but now even the Report screen
works fine.

Now it's time to get the fun ;D

[luizfox]

Julian,

Your build.xml works for me (Linux), but it doesn't load the MySQL
driver.

Where did you put
Class.forName("org.olap4j.driver.xmla.XmlaOlap4jDriver")?

The error:
<snip>
Caused by: java.sql.SQLException: No suitable driver found for
jdbc:mysql://localhost:3306/foodmart?user=foodmart&password=foodmart
</snip>

I'm having heavy problems with the classpath.

Thanks for any reply.

On 30 abr, 03:21, Julian Hyde <julianh...@gmail.com> wrote:

[william...@gmail.com]

Sorry you had so much trouble... hopefully we'll get a good build
process in place and iron out these type of install issues.

[Julian Hyde]

> luizfox wrote:
>
> Your build.xml works for me (Linux), but it doesn't load the MySQL
> driver.

People use such a wide variety of databases that it's not practical to deal
with them all in the build.xml. You'll have to modify build.xml to add your
specific driver to the path.

>
> Where did you put
> Class.forName("org.olap4j.driver.xmla.XmlaOlap4jDriver")?

I added that line to Olap4jServiceImpl.java manually. But note that if you
are running JDK 1.6, you don't need the Class.forName at all - JDBC 4.0
automatically loads all drivers declared in all jars on the classpath. But
in 1.5 and earlier, you still need that Class.forName line.

Julian