Skip to content

8357862: Java argument file is parsed unexpectedly with trailing comment #25589

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

Closed

Conversation

sormuras
Copy link
Member

@sormuras sormuras commented Jun 2, 2025

Please review this fix to correctly parse tokens in an argument file that contains trailing comments without preceding whitespace characters before the '#' comment marker, the number sign.

The specifaction of the java Command has in section java Command-Line Argument Files:

Use the number sign `#` in the argument file to identify comments.
All characters following the `#` are ignored until the end of line.

There is not requirement specified to prepend a comment in a line with at least one argument with one or more preceding whitespace characters.


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8357862: Java argument file is parsed unexpectedly with trailing comment (Bug - P4)

Reviewers

Contributors

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/25589/head:pull/25589
$ git checkout pull/25589

Update a local copy of the PR:
$ git checkout pull/25589
$ git pull https://git.openjdk.org/jdk.git pull/25589/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 25589

View PR using the GUI difftool:
$ git pr show -t 25589

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25589.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Jun 2, 2025

👋 Welcome back cstein! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Jun 2, 2025

@sormuras 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:

8357862: Java argument file is parsed unexpectedly with trailing comment

Co-authored-by: Stuart Marks <[email protected]>
Reviewed-by: vromero

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 166 new commits pushed to the master branch:

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

@openjdk openjdk bot added the rfr Pull request is ready for review label Jun 2, 2025
@openjdk
Copy link

openjdk bot commented Jun 2, 2025

@sormuras The following labels will be automatically applied to this pull request:

  • core-libs
  • hotspot-runtime

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command.

@mlbridge
Copy link

mlbridge bot commented Jun 2, 2025

Webrevs

@vicente-romero-oracle
Copy link
Contributor

the fact that not including a space between the comment and the previous element created havoc seems to indicate that the scanner is pretty fragile and could break again in the future. We should probably file a follow up to make this code more reliable

@sormuras
Copy link
Member Author

sormuras commented Jun 2, 2025

the fact that not including a space between the comment and the previous element created havoc seems to indicate that the scanner is pretty fragile and could break again in the future. We should probably file a follow up to make this code more reliable

Yes, seems reasonable. My initial solution was to try to make use of the shared CommandLine class, but the parsing of the launcher is too early in the game.

Copy link
Contributor

@vicente-romero-oracle vicente-romero-oracle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Jun 11, 2025
@sormuras
Copy link
Member Author

/contributor add @stuart-marks

@openjdk
Copy link

openjdk bot commented Jun 11, 2025

@sormuras
Contributor Stuart Marks <[email protected]> successfully added.

@sormuras
Copy link
Member Author

/integrate

@openjdk
Copy link

openjdk bot commented Jun 17, 2025

Going to push as commit 21b72de.
Since your change was applied there have been 238 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Jun 17, 2025
@openjdk openjdk bot closed this Jun 17, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Jun 17, 2025
@openjdk
Copy link

openjdk bot commented Jun 17, 2025

@sormuras Pushed as commit 21b72de.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

@sormuras sormuras deleted the 8357862-argfile-nospacecomments branch June 17, 2025 14:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants