Class Bug

java.lang.Object
org.olap4j.impl.Bug

public abstract class Bug extends Object
Holder for constants which indicate whether particular issues have been fixed. Reference one of those constants in your code, and it is clear which code can be enabled when the bug is fixed. Generally a constant is removed when its bug is fixed.

Developers, please use the naming format Bug<Product><Number>Fixed for constants, and include a hyperlink to the bug database record in the comments. Product will usually be "Olap4j", but sometimes we are blocked by bugs in other components, such as the JDK or Mondrian.

Cleanup items

The following is a list of cleanup items. They are not bugs per se: functionality is not wrong, just the organization of the code. If they were bugs, they would be in jira. It makes sense to have the list here, so that referenced class, method and variable names show up as uses in code searches.
Split out Test Compatability Kit (TCK)
Factor parts of olap4j test suite that depend on an olap4j implementation (such as mondrian) into a jar that can be invoked by that implementation. Then each implementation is responsible for running the TCK. It can also manage which version of the TCK it implements, so that it does not have to be absolutely up to date. Some parts of the olap4j suite do not stretch the capabilities of the OLAP engine or driver, and will remain part of the olap4j suite, using mondrian as reference implementation.
Since:
Nov 9, 2010
Author:
jhyde