-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
JDK-8290845: Consider an alternative item separator for multi-item option values #11178
JDK-8290845: Consider an alternative item separator for multi-item option values #11178
Conversation
👋 Welcome back jjg! A progress list of the required criteria for merging this PR into |
@jonathan-gibbons The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
src/jdk.javadoc/share/classes/jdk/javadoc/internal/doclets/toolkit/BaseConfiguration.java
Outdated
Show resolved
Hide resolved
…parator # Please enter a commit message to explain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.
*/ | ||
private List<String> tokenize(String s, char separator, int maxTokens) { | ||
private List<String> tokenize(String s, int maxTokens) { |
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.
Not saying that we should do anything about it, but I would be surprised if there were no such tokenization functionality in the JDK API.
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.
None of the JDK simple tokenizers supports handling of escape characters.
But a Pattern/Matcher could be used.
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.
Looks good to me.
@jonathan-gibbons This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 4 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
/integrate |
Going to push as commit 52494df.
Your commit was automatically rebased without conflicts. |
@jonathan-gibbons Pushed as commit 52494df. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Please review a medium simple update to prefer the use of comma (
,
) instead of colon (:
) in certain options taking a list of values. Options taking a search path (like--class-path
,--source-path
, etc) are not affected.Progress
Issues
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/11178/head:pull/11178
$ git checkout pull/11178
Update a local copy of the PR:
$ git checkout pull/11178
$ git pull https://git.openjdk.org/jdk pull/11178/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 11178
View PR using the GUI difftool:
$ git pr show -t 11178
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/11178.diff