[Mondrian] RE: [Olap4j-devel] Flat3Map broke the build

Julian Hyde jhyde at pentaho.com
Fri Jul 10 15:25:26 EDT 2009

Update. I upgraded mondrian and olap4j to commons-collections-3.2, published
mondrian- to the maven repository, and the olap4j build is fixed
The mondrian build has two new test exceptions. Can you look at these
please, Eric. (The configuration is JDK 1.5 + MySQL.)
mondrian- does not include Eric's change 12930 backing out
Flat3Map reverting to HashMap. I'd prefer to stay on Flat3Map if possible.
Will and Aaron,
Do you see any problems upgrading to commons-collections-3.2? (E.g.
dependencies in other components.) If so let me know, and we will revisit
the decision.


From: Julian Hyde [mailto:jhyde at pentaho.com] 
Sent: Friday, July 10, 2009 9:41 AM
To: 'Eric McDermid'
Cc: olap4j-devel at lists.sourceforge.net; 'Mondrian developer mailing list'
Subject: [Olap4j-devel] Flat3Map broke the build

Your change seems to have borked the build. Flat3Map was introduced in
commons-collections version 3, and mondrian currently uses
commons-collections 2.1.
It seemed to build and run for me. I have no idea why.
I made the situation worse by checking the mondrian build into Pentaho's
maven repository and making olap4j dependent on it. So now olap4j is borked
as well.
Can you look into this, and come up with an easy way to fix the build.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pentaho.org/pipermail/mondrian/attachments/20090710/dea38c3a/attachment.html 

More information about the Mondrian mailing list