[Mondrian] switching to maven

Kurtis Walker kwalker at pentaho.com
Tue Nov 1 14:56:07 EDT 2016

Hi Julian,

  I considered that option.  I elected to stay with MySql because there are a number of tests, specifically around native evaluation, that match specifically to either mysql or oracle sql patterns.  The tests are basically a no-op for other dbs.  I agree hsqldb would be a more pure option, but would need to come with refactoring lots of tests.


From: mondrian-bounces at pentaho.org <mondrian-bounces at pentaho.org> on behalf of Julian Hyde <julianhyde at gmail.com>
Sent: Tuesday, November 1, 2016 2:06 PM
To: Mondrian developer mailing list
Subject: Re: [Mondrian] switching to maven

I did most of this on the Mondrian 4 branch a while ago. The one thing I did differently was to use an embedded in-memory hsqldb rather than MySQL. It requires a bit more memory but because everything is in-memory and comes a JAR file which is a maven dependency I think it's simpler than using jcabi-mysql-maven-plugin.


On Nov 1, 2016, at 10:36 AM, Kurtis Walker <kwalker at pentaho.com<https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=kwalker@pentaho.com>> wrote:


In the coming weeks we will be switching the Mondrian 3 build from ant to mvn.  The proposed changes are in a branch on my fork.  https://github.com/kurtwalker/mondrian/tree/mavenize  Key highlights include:

  *   Integration tests can use an embedded mysql server, thus removing the need to set up foodmart and steelwheels
  *   schema workbench code is separated into a separate sub-module
  *   Generated source gets its own source dir

Let me know if you have any concerns.


Mondrian mailing list
Mondrian at pentaho.org<https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=Mondrian@pentaho.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pentaho.org/pipermail/mondrian/attachments/20161101/6689b37e/attachment-0001.html 

More information about the Mondrian mailing list