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

2.1.0 support #91

Open
cburkey opened this issue Dec 7, 2015 · 7 comments
Open

2.1.0 support #91

cburkey opened this issue Dec 7, 2015 · 7 comments

Comments

@cburkey
Copy link

cburkey commented Dec 7, 2015

Sorry to bother you with this.

Verifying http://xbib.org/repository/org/xbib/elasticsearch/plugin/elasticsearch-knapsack/2.0.0.0/elasticsearch-knapsack-2.0.0.0-plugin.zip checksums if available ...
Downloading .DONE
ERROR: Plugin [knapsack] is incompatible with Elasticsearch [2.1.0]. Was designed for version [2.0.0]

@jprante
Copy link
Owner

jprante commented Dec 7, 2015

Knapsack 2.1.0.0 just released for ES 2.1.0

@celumuser
Copy link

Is there a way to make a release for ES 2.1.2
Knapsack 2.1.1 is not compatible with it.

@jprante
Copy link
Owner

jprante commented Mar 23, 2016

I just pushed out Knapsack plugin version 2.1.2.0 for ES 2.1.2

You can also compile from source, no problem.

@celumuser
Copy link

Thanks a lot!

Actually, I did compile from source few hours before your response. At the beginning, I had some problems with gradle (2.12). Then I had to downgrade to 2.10 to get the build running.
I ended up downgrading to the old release 2.1.1.0 and from there I've built my 2.1.2.0 package.
Some of the unit tests were failing, So I wasn't sure if my build would work.

Any ways, thanks again for the suift response.

@jprante
Copy link
Owner

jprante commented Mar 25, 2016

Would love to see the failed test output. Can you post them as a new Issue maybe?

Here, tests are passing on Mac OS X with Java 8 and gradle 2.12, but Travis builds fail with weird timeouts, so I like to blame Travis because of their resource limits.

@celumuser
Copy link

In my case the build was on Windows, and I strongly think it is the cause of the problem.
Some test files could not be accessed and some URIs are not correctly resolved.

Sorry, I didn't have more time to look into the code and find the exact cause of the failing tests.

I've included the entire build log here:
build.txt

@jprante
Copy link
Owner

jprante commented Mar 25, 2016

Thank you, that's great help. I do not test on Windows.

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

No branches or pull requests

3 participants