Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix olap4j dependency #3

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

pstoellberger
Copy link

we need to keep the olap4j versions in sync

i cant build projects that use mondrian 4 anymore because xmlaserver references olap4j-xmla 1.0.1 - which doesn't exist anymore in a repo

@julianhyde
Copy link
Member

Both olap4j and olap4j-xmlaserver have "olap4j2" branches. These need to be merged into master when appropriate. This pull request is not the right thing to do.

@julianhyde julianhyde closed this Sep 23, 2013
@pstoellberger
Copy link
Author

what does olap4j 2.0 have to do with that?
Thats an issue on the current version - 1.2.0-SNAPSHOT - which should be updated here.... as mondrian 4 and all others use that one as well

@julianhyde
Copy link
Member

You're right that this has nothing to do with olap4j-2.0 development. I think the problem is that olap4j-1.0.1-SNAPSHOT was removed from pentaho's maven repository a couple of months back. The safest thing is to restore that jar file.

Things are about to get stirred up as the olap4j2 work becomes the master for olap4j, olap4j-xmlaserver and lagunitas.

@julianhyde julianhyde reopened this Sep 23, 2013
@pstoellberger
Copy link
Author

yeah, thats exactly the issue. and i see your point
i'd prefer setting this to the 1.2 build, but restoring the artifact would work for me as well
i can work around it with exclusions in the poms anyway

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants