-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[incubator-kie-drools#5776] [new-parser] failed to parse when a metho… #5783
[incubator-kie-drools#5776] [new-parser] failed to parse when a metho… #5783
Conversation
…d name is a drl keyword
; | ||
|
||
// matches any identifiers including acceptable java keywords (defined in JavaParser.g4) and drl keywords | ||
drlIdentifier returns [Token token] |
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.
We need to define this rule to aggregate acceptable tokens.
| i1=IDENTIFIER { helper.emit($i1, DroolsEditorType.IDENTIFIER); } | ||
| i1=drlIdentifier { helper.emit($i1.token, DroolsEditorType.IDENTIFIER); } |
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.
I have fixed only primary
rule to make this PR concise and easy to review. I filed #5784 to review DRL6Expressions.g4
for other possible IDENTIFIER
replacement.
Before PR:
After PR:
|
@yurloc @gitgabrio @mariofusco Please review, thanks! |
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.
…d name is a drl keyword (apache#5783)
…d name is a drl keyword (apache#5783)
…d name is a drl keyword (apache#5783)
…d name is a drl keyword (#5783)
…d name is a drl keyword (apache#5783)
…d name is a drl keyword
Issue:
How to replicate CI configuration locally?
Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.
build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.
How to retest this PR or trigger a specific build:
for pull request and downstream checks
for a full downstream build
run_fdb
for Jenkins PR check only
Build Now
button.