-
Notifications
You must be signed in to change notification settings - Fork 447
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 the -jvm-debug and -h flags in the ash template #1630
Conversation
At least one commit author ([email protected], [email protected]) is not linked to a user. See https://help.github.com/en/articles/why-are-my-commits-linked-to-the-wrong-user#commits-are-not-linked-to-any-user |
At least one commit author ([email protected], [email protected]) is not linked to a user. See https://help.github.com/en/articles/why-are-my-commits-linked-to-the-wrong-user#commits-are-not-linked-to-any-user |
Hi @qwe2, Thank you for your contribution! We really value the time you've taken to put this together. Before we proceed with reviewing this pull request, please sign the Lightbend Contributors License Agreement: |
Interestingly the |
Thanks for tackling this 💪 I'll be on vacation . Maybe @dwickern can take a look 😊 |
I've been a bit busy and wasn't sure what to do about Java 8 compat, but I ended up adding some checks so that |
Hi @qwe2 Sorry for the waiting - I'll try to find some time to take a deeper look! |
Re: Java 8 compatibility, I found the relevant change in the JDK 9 release notes (bold mine)
IMO we should keep the secure defaults and let users decide what address to bind to: That means we can remove all the Java version detection. We should also revert #1546 to keep bash and ash consistent. |
Sounds good, but this would be a breaking change then:
This currently means |
I'm with @dwickern on the secure setting by default and also reflecting what the JVM does. If you are not using sbt-native-packager and you use After all, upgrading a major version of the JVM must be tested and I think it's better if sbt-native-packager doesn't try to magically add a migration path. |
I've reverted #1546 and removed the major version checks. Note that this would be a breaking change for anyone currently using |
Thanks for you patience @qwe2 and thanks for stating the explicit breaking change.
I have never used this flag before. My assumption would be, that this is only used in testing environments and not in production, right? |
Yeah, I think that nobody should be using this flag in production. (Unfortunately that doesn't necessarily mean that nobody does 😞 ) |
Thanks for clarifying 😄 . Then I'm willing to accept than change that some cowboy devops folks may not be able to start there instance when upgrading sbt-native-packager and need to do a small change to their |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dwickern do you have any remarks? Otherwise I would merge and release this change 🎉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🎉
This should fix issues like #1523