-
Notifications
You must be signed in to change notification settings - Fork 38
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
[Suggestion] Merge guide/dev into website/developers #185
base: master
Are you sure you want to change the base?
Conversation
@@ -1,14 +1,21 @@ | |||
--- | |||
layout: website-normal | |||
title: Developers | |||
started-pdf-exclude: true |
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.
think this might be required for PDF build?
@@ -65,6 +65,8 @@ JAVA_DEBUG_OPTS='-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=5 | |||
For other options please check your JVM JPDA documentation. | |||
Hotspot JPDA: https://docs.oracle.com/javase/8/docs/technotes/guides/jpda/ | |||
|
|||
## Quick testing |
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.
Either this should have content or next section should be a subsection (###
not ##
)
Do not merge yet. In addition to the comments the case for making this change needs to be made. The reason for the old docs structure is that some of the dev guide content is specific to a given version. We lose that clarity with this PR. I expect @bostko is suggesting that precision is not worth the user-facing complexity, but @bostko it would be helpful to describe how this is simpler and note main places confusion could arise if we don't have the dev guide aligned for released versions. |
One section for all coding related matters.