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

Allow overriding gradle version to hardcode a specific version #1

Closed
dakrone opened this issue Sep 1, 2016 · 5 comments
Closed

Allow overriding gradle version to hardcode a specific version #1

dakrone opened this issue Sep 1, 2016 · 5 comments

Comments

@dakrone
Copy link

dakrone commented Sep 1, 2016

I work on a project that requires gradle 2.13 due to bugs introduced in later gradle versions, however, when I try to run the server I get:

Caused by: org.gradle.api.GradleException: Gradle 2.13 is required to build elasticsearch
    at build_da97v8nh3ew8kq4jfh1zxmavb.run(/home/hinmanm/es/elasticsearch/buildSrc/build.gradle:33)
    at org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:90)
    ... 83 more

Because it uses gradle 3.0 from the wrapper.

It would be great if there were a way to tell meghanada to use gradle from the $PATH rather than the gradle from the wrapper, so the version I need to use explicitly will work.

@mopemope
Copy link
Owner

mopemope commented Sep 2, 2016

This is elasticsearch side problem.
Server support multi gradle version and detect your project gradle wrapper ./gradlew.
But elasticsearch does not provide gradle wrapper.
(see elastic/elasticsearch#13744 )

mopemope added a commit that referenced this issue Sep 2, 2016
@mopemope
Copy link
Owner

mopemope commented Sep 2, 2016

Supported override gradle version.

$ export MEGHANADA_GRADLE_VERSION=2.13

OR

$ java -jar path/to//meghanada.jar --gradle-version 2.13 

@mopemope mopemope closed this as completed Sep 2, 2016
@dakrone
Copy link
Author

dakrone commented Sep 2, 2016

@mopemope thanks for adding that option! It looks like the jar from https://dl.bintray.com/mopemope/meghanada/meghanada.jar is the older version that doesn't support that yet, any idea when it will be updated?

@mopemope
Copy link
Owner

mopemope commented Sep 2, 2016

@dakrone already uploaded!

@dakrone
Copy link
Author

dakrone commented Sep 2, 2016

Thanks, I am able to use meghanada now!

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

2 participants