The repository issues should be corrected now. Let us know if you still experience it.


On Tue, Jul 30, 2013 at 4:17 PM, Julian Hyde <> wrote:
On Jul 30, 2013, at 1:10 PM, Larry Grill <> wrote:

Hi Julian,
I thought OLAP4J was building ok again?
Is there another build that is having issues? Local dev builds?

I'm working on olap4j 2.0 in a different branch. It's pre-alpha, but I still wanted to get something into the repo. Partly because I was having trouble installing in my local repo in a way that a maven project could see.

I've figured out the right mvn install:install-file incantation so I won't need to deploy to the public repo for a while.

We have these versions in right now: 1.0.1-SNAPSHOT,,, 1.1.0, 1.2.0-SNAPSHOT.

Yeah, I see them now. I've always deployed olap4j to the thirdparty repo in the past, and I see that's gone and the builds are now in the pentaho repo. Maybe you cleaned that up.


Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
olap4j-devel mailing list