Skip to content
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

Conversation

tkobayas
Copy link
Contributor

…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

    • Push a new commit to the PR. An empty commit would be enough.
  • for a full downstream build

    • for github actions job: add the label run_fdb
  • for Jenkins PR check only

;

// matches any identifiers including acceptable java keywords (defined in JavaParser.g4) and drl keywords
drlIdentifier returns [Token token]
Copy link
Contributor Author

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.

Comment on lines -611 to +681
| i1=IDENTIFIER { helper.emit($i1, DroolsEditorType.IDENTIFIER); }
| i1=drlIdentifier { helper.emit($i1.token, DroolsEditorType.IDENTIFIER); }
Copy link
Contributor Author

@tkobayas tkobayas Mar 14, 2024

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.

@tkobayas
Copy link
Contributor Author

NullSafeDereferencingTest.testNullSafeDereferencingPredicateMethod has fixed.

Before PR:
drools-model-codegen

[ERROR] Tests run: 2433, Failures: 430, Errors: 2, Skipped: 9

After PR:
drools-model-codegen

[ERROR] Tests run: 2433, Failures: 419, Errors: 2, Skipped: 9

@tkobayas
Copy link
Contributor Author

@yurloc @gitgabrio @mariofusco Please review, thanks!

Copy link
Contributor

@yurloc yurloc left a comment

Choose a reason for hiding this comment

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

LGTM.

@tkobayas tkobayas merged commit 3796779 into apache:dev-new-parser Mar 18, 2024
0 of 3 checks passed
tkobayas added a commit to tkobayas/drools that referenced this pull request Jun 11, 2024
tkobayas added a commit to tkobayas/drools that referenced this pull request Oct 2, 2024
tkobayas added a commit to tkobayas/drools that referenced this pull request Oct 11, 2024
tkobayas added a commit that referenced this pull request Oct 11, 2024
rgdoliveira pushed a commit to rgdoliveira/drools that referenced this pull request Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants