-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Fix ConditionParser to handle newlines before && operator #12038
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
Open
blaspat
wants to merge
4
commits into
apache:master
Choose a base branch
from
blaspat:fix/maven-11882-condition-parser-multiline
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
4022c80
Fix ConditionParser to handle newlines before && operator
blaspat ad0aa49
Update impl/maven-impl/src/main/java/org/apache/maven/impl/model/prof…
blaspat c39393d
Update impl/maven-impl/src/main/java/org/apache/maven/impl/model/prof…
blaspat f64ecb7
Update impl/maven-impl/src/test/java/org/apache/maven/impl/model/prof…
blaspat File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -262,6 +262,31 @@ void testPropertyAlias() { | |
| assertThrows(RuntimeException.class, () -> parser.parse("${unclosed")); | ||
| } | ||
|
|
||
| @Test | ||
| void testAmpersandAmpersandTokenizerMultiline() { | ||
| // Regression test for https://github.com/apache/maven/issues/11882 | ||
| // The && operator was not being tokenized correctly when a line break appeared before it. | ||
| // Uses ${os.name} and ${os.arch} which are set to 'windows' and 'amd64' in the mock context. | ||
|
|
||
| // Case 1: Basic && without line breaks (baseline - always worked) | ||
| assertTrue((Boolean) parser.parse("${os.arch} == 'amd64' && ${os.name} == 'windows'")); | ||
|
|
||
| // Case 2: Line break BEFORE && - this was the bug from issue #11882 | ||
| // In the issue, CDATA content had a line break before &&: | ||
| // <condition><![CDATA[exists( '.profile-2' )\n&& missing( '.profile-1' )]]></condition> | ||
| assertTrue((Boolean) parser.parse("${os.arch} == 'amd64'\n&& ${os.name} == 'windows'")); | ||
|
|
||
| // Case 3: Line break AFTER && | ||
| assertTrue((Boolean) parser.parse("${os.arch} == 'amd64' &&\n${os.name} == 'windows'")); | ||
|
|
||
| // Case 4: Line breaks on both sides | ||
| assertTrue((Boolean) parser.parse("${os.arch} == 'amd64'\n&&\n${os.name} == 'windows'")); | ||
|
|
||
| // Case 5: Multiple && with line break before first && (like bad-profile-2d in issue) | ||
| assertTrue( | ||
| (Boolean) parser.parse("${os.arch} == 'amd64'\n&& ${os.name} == 'windows' && ${os.name} == 'windows'")); | ||
| } | ||
|
|
||
| @Test | ||
| void testNestedPropertyAlias() { | ||
| functions.put("property", args -> { | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please also add a test for @Test
void testPipePipeTokenizerMultiline() {
// || with newlines should work the same as &&
assertTrue((Boolean) parser.parse("${os.arch} == 'amd64' || ${os.name} == 'linux'"));
assertTrue((Boolean) parser.parse("${os.arch} == 'amd64'\n|| ${os.name} == 'linux'"));
assertTrue((Boolean) parser.parse("${os.arch} == 'amd64' ||\n${os.name} == 'linux'"));
assertTrue((Boolean) parser.parse("${os.arch} == 'amd64'\n||\n${os.name} == 'linux'"));
} |
||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Two issues:
&in theX=group:&was added to the>=/<=/==/!=lookahead, which means&=would be tokenized as a valid two-char operator. But&=is not valid in this language — remove|| c == '&'from this condition.||not handled: The||operator has the exact same tokenization gap that&&had. The|character is not in the operator list, so||only works when surrounded by spaces. Handle it symmetrically with&&.Please also add corresponding test cases for
||with newlines, similar to the&&tests.