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

[service-name] bash start script does not use JVM options from launcher-custom.yml #139

Closed
iamdanfox opened this issue Nov 3, 2016 · 2 comments

Comments

@iamdanfox
Copy link
Contributor

I'd like to run a custom dropwizard command (migrate) to do migrations, that needs the JVM trustStore system property to be set.

Since I can't use init.sh to run migrate, I tried to use the [service-name] bash start script, however, this did not pick up the JVM arguments I'd set in launcher-custom.yml.

  launcherCustom:
    configType: java
    configVersion: 1
    jvmOpts:
      - '-Djavax.net.ssl.trustStore=XXX'

Is this a reasonable approach to take or am I going about this the wrong way?

@uschi2000
Copy link
Contributor

can you run the go-java-launcher binary directly?

@uschi2000
Copy link
Contributor

Don't think we'll fix this.

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