Add test case for MONDRIAN-939, fix for MONDRIAN-1280 seems to fix that as well
[MONDRIAN-1512]  Correcting the inline SQL used by Impala.
[PPP-3081] license header updates on all .java, .js, and .jsp
license header comment fix for .jsp files
Merge pull request #138 from mkambol/mondrian1512

[MONDRIAN-1512]  Correcting the inline SQL used by Impala.
[MONDRIAN-1703]  Determination of the aggStar in SqlTupleReader is independent of the determination of the measures present in a native filter.  This left open the possibility that
one or more measures could be missing from the aggregate table that was selected, since only one of the measures is set in context.
E.g. filter (<set>, measure.[a] > measure.[b]) can be natively evaluated only if the columns for both measure [a] and [b] are present in the agg table.
To side step the issue, this fix omits the having constraint if we determine that a measure is not present.
[MONDRIAN-1703]  Added one more test query to verify the negative case.
Merge pull request #142 from mkambol/mondrian1703

[MONDRIAN-1703]  NPE when finding measure in aggregate table bitkeys
[MONDRIAN-1729][SP-632]  "Query required more than 12 iterations" error when query should complete.

This change addresses a case where the ordering in which segments are processed by SegmentBuilder.rollup() could impact the resulting segment.  In some cases,
if a column of the second axis was wildcarded, it could incorrectly result in the axis being set as having incompatible predicates (lostPredicate=true).  Similarly,
the intersecting values could be mishandled, depending on the ordering of segments with wildcarded columns.
Test cases committed with this change check for equivalent rollups with segments processed in forward and reverse order.
Merge pull request #157 from mkambol/MONDRIAN-1729

[MONDRIAN-1729][SP-632]  "Query required more than 12 iterations" error when query should complete.
[ENGOPS-142] Match up mondrianschemaworkbench plugins version.
Mondrianschemaworkbench plugins project should match up with Mondrian versioning. Version propertization allows the release builds to automatically map any release version of this artifact with the matching Mondrian version.
This is follow-up work for the versioning scheme used for the 5.0.0 Pentaho Suite release.
xref commit  https://github.com/pentaho/pentaho-mondrianschemaworkbench-plugins/commit/5f1d3fef2ea5a39ae7feb27ae9f66f436212ddb0
[MONDRIAN-1729][SP-632] Missed a case where the first header loaded (used for initializing the AxisInfo) contains a wildcarded column that should be downgraded to
a specific list when computing segment intersection.
MONDRIAN-1658 - handling the case where a crossjoin is given an empty set for one of its parameters.
[MONDRIAN-1729][SP-632]  Made the segments list an UnmodifiableArrayList.
Merge pull request #161 from kurtwalker/MONDRIAN-1658

MONDRIAN-1658
Merge pull request #160 from mkambol/MONDRIAN-1729

[MONDRIAN-1729][SP-632] Missed a case where the first header loaded
[MONDRIAN-1766]  Role restrictions are not honored in some cases if the number of MemberGrants exceeds the maxconstraints property value

This change introduces a final pass filter of the tuple list generated by NativeSet to assure that all items in the list are accessible.  Since this could be costly,
it short-circuits the checks except where one or more hierarchies actually have a role restriction defined.
[MONDRIAN-1766]  Code cleanup.  Inlined conditional.
Merge pull request #168 from mkambol/mondrian-1766

[MONDRIAN-1766]  Role restrictions are not honored in some cases if the number of MemberGrants exceeds the maxconstraints property value
[MONDRIAN-1694]  Mondrian applies non empty to native filter when "matches" is used.

This change adds a check for NonEmpty prior to applying a context constraint when evaluating a native filter.  A SqlContextConstraint forces a join to the fact table,
which will drop any tuples not associated with fact data.