Fixing test expected values.  There is a difference in measures available in [Warehouse and Sales] in the 3.x FoodMart.xml vs. 4.0.
Fixing test expected values and role definitions.  The test expected failures when referring to the [Customers] hierarchy, but the full [Customer] dim had been granted access.
Also expected MDX results still had the Mondrian 3.x naming.
Merge pull request #146 from mkambol/unitTests

Minor corrections to 2 unit tests
Fixing expected values in CacheControlTest.  The schema was modified awhile back but the checksums had not been updated in the ref.xml file.
Merge pull request #147 from mkambol/unitTests

Fixing expected values in CacheControlTest.
Fixing test expected values where 4.0 schema differs from 3.x.
Merge pull request #148 from mkambol/unitTests

Fixing test expected values where 4.0 schema differs from 3.x.
Merging expected SQL for testNegativeMatching()  from change e7e1bd5.  This had been missed in the previous cherry pick.
The test now passes with aggregates turned off, but is failing with aggregates--the fact table and not agg table is used.
Ordering in expected values was inconsistent with the query and schema definition.  The ordering of the expected values was in order of customer_id, but the MDX specified the
primary ordering is by Customers.CurrentMember.OrderKey, which for [Name] is defined with orderByColumn='full_name'.
Expected results for an Order() expression were incorrect.  orderByColumn='full_name', but expected results were in customer_id order.
Merge pull request #149 from mkambol/unitTests

More unit test fixes.
Merging in a fix from master.

Fix bug MONDRIAN-1122, "Aggregation is not supported over a list with more than 1000 predicates". We should not check the size of the list of constraints for composite slicer; it is only a problem if we are evaluating distinct-count measures, and they are relatively unusual.
(cherry picked from commit 5b5dbac)
Merge pull request #150 from mkambol/unitTests

Merging in a fix from master.
Fixes a test failure. Unimplemented methods in CompositeSegmentCache were preventing events from bubbling up correctly.
(cherry picked from commit 7d511c5)
Merge pull request #151 from mkambol/unitTests

Fixes a test failure. Unimplemented methods in CompositeSegmentCache wer...
Merge of Julian's "unwrap" branch back into lagunitas.

21852eddc643  Remove RolapCubeMember, RolapMemberInCube, NoCacheRolapCubeHierarchyMemberReader, CacheRolapCubeHierarchyMemberReader, MemberNoCacheHelper. Now, members can only belong to a RolapCubeLevel, not a RolapLevel. Remove a lot of downcasts to RolapMember, RolapCubeLevel and RolapCubeHierarchy, and other cleanup.
9fd5986d0  Fix a compilation error, and log MONDRIAN-1502 to highlight a remaining issue with parent-child hierarchies
0c2ad8eec  Slim down DelegatingRolapMember; it no longer inherits from RolapMember. Slim down RolapMember; it no longer inherits from OlapMemberBase, and I've moved some fields into the flags field. Move createMemberReader into RolapSchemaLoader.
33ff486044 Update intellij projects to write classes to bin/classes and bin/test/classes. This matches the output paths used by build.xml, and therefore the resources will be present on the classpath as long as you've built at least once using ant.
7a3455c6  Change a parameter from RolapLevel to RolapCubeLevel, because it always is.
[MONDRIAN-1735]  Fixing tests which check the list of cubes returned from SchemaReader.getCubes().  The list now includes a set of dummy cubes associated with
shared dimensions, with names like "$dimname".
[MONDRIAN-1735]  Removed the EnableRolapCubeMemberCache, which was no longer being used after Julian's unwrap changes.
[MONDRIAN-1735] Localization resources could fail to load due to changes associated with the unwrap merge.

Resources can be associated with the cube directly (e.g. [Sales].[Store].[CA]), or "shared" ([Store].[CA]).
Logic for handling the location of resources was lost with the removal of RolapCubeMember.
[MONDRIAN-1727]  Dimensions with a closure table have an additional hierarchy, which was causing failures in cases where the default hierarchy is being retrieved.

RolapHierarchy has a "closureFor" field which formerly was always set to null.  This change sets the value when appropriate, and uses it to filter out closures
when determining which hierarchy is the default.