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

Jump to bottom

service.bat should handle JRE not just JDK for starting Elasticsearch #3739

Closed
costin opened this issue Sep 19, 2013 · 0 comments
Closed

service.bat should handle JRE not just JDK for starting Elasticsearch #3739

costin opened this issue Sep 19, 2013 · 0 comments
Assignees
@costin
Labels
>bug v0.90.6 v1.0.0.Beta1

Comments

@costin
Copy link
Member

costin commented Sep 19, 2013

Currently service.bat assumes a JDK is used but there are plenty of cases where a JRE Is used instead (the default Java installation).
Instead of failing, service.bat should use that instead and give a proper warning.
@ghost ghost assigned costin Sep 19, 2013
@costin costin closed this as completed in 9fe99aa Sep 19, 2013
costin added a commit that referenced this issue Sep 19, 2013
@costin
detect JRE (vs JDK) and invalid JAVA_HOME
3ff6570 
fixes #3739

(cherry picked from commit 9fe99aa)
@stijnherreman stijnherreman mentioned this issue Oct 17, 2013
Closed
mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
@costin
detect JRE (vs JDK) and invalid JAVA_HOME
ce3351b 
fixes elastic#3739

(cherry picked from commit 9fe99aa)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@costin costin

Labels
>bug v0.90.6 v1.0.0.Beta1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@costin