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.

Sign up for GitHub

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

Jump to bottom

RHPAM-4779: Added ProcessDataChangedEvent to ProcessEventSupport #30

Merged
merged 2 commits into from
Aug 7, 2024
Merged

RHPAM-4779: Added ProcessDataChangedEvent to ProcessEventSupport #30

merged 2 commits into from
Aug 7, 2024

Conversation

nmirasch
Copy link

@nmirasch nmirasch commented Feb 27, 2024 •
edited
Loading

JIRA: https://issues.redhat.com/browse/RHPAM-4779

Notify listeners when Process Instance related data changes.

referenced Pull Requests:

depends on kiegroup/droolsjbpm-knowledge#646

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 checks
    Please add comment: Jenkins retest this

  • for a specific pull request check
    Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] tests

  • for a full downstream build

    • for jenkins job: please add comment: Jenkins run fdb
    • for github actions job: add the label run_fdb

  • a compile downstream build please add comment: Jenkins run cdb

  • a full production downstream build please add comment: Jenkins execute product fdb

  • an upstream build please add comment: Jenkins run upstream

  • for quarkus branch checks
    Run checks against Quarkus current used branch
    Please add comment: Jenkins run quarkus-branch

  • for a quarkus branch specific check
    Run checks against Quarkus current used branch
    Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] quarkus-branch

  • for quarkus main checks
    Run checks against Quarkus main branch
    Please add comment: Jenkins run quarkus-main

  • for a specific quarkus main check
    Run checks against Quarkus main branch
    Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] quarkus-main

  • for quarkus lts checks
    Run checks against Quarkus lts branch
    Please add comment: Jenkins run quarkus-lts

  • for a specific quarkus lts check
    Run checks against Quarkus lts branch
    Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] quarkus-lts

  • for native checks
    Run native checks
    Please add comment: Jenkins run native

  • for a specific native check
    Run native checks
    Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] native

  • for native lts checks
    Run native checks against quarkus lts branch
    Please add comment: Jenkins run native-lts

  • for a specific native lts check
    Run native checks against quarkus lts branch
    Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] native-lts

How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-7.67.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.

If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

This was referenced Feb 27, 2024
Closed
Merged
@nmirasch nmirasch requested a review from fjtirado February 27, 2024 19:59
fjtirado
fjtirado reviewed Feb 27, 2024
View reviewed changes
drools-core/src/main/java/org/drools/core/event/rule/impl/ProcessDataChangedEventImpl.java Outdated
}

public String toString() {
return "==>[ProcessDataChanged(name=" + getProcessInstance().getProcessName() + "; id=" + getProcessInstance().getProcessId() + ")]";
Copy link

Choose a reason for hiding this comment

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

Curious tostring implementation

@nmirasch nmirasch requested a review from gmunozfe February 28, 2024 08:15
@fjtirado fjtirado added backport-7.67.x Generate backport PR for 7.67.x branch backport-7.67.x-blue Generate backport PR for 7.67.x-blue branch labels Feb 28, 2024
gmunozfe
gmunozfe approved these changes Mar 11, 2024
View reviewed changes
Copy link
Member

@gmunozfe gmunozfe left a comment

Choose a reason for hiding this comment

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

Code looks good to me, well done @nmirasch !
Only cdb is failing same as in droolsjbpm-knowledge (seems unrelated)

drools-core/src/main/java/org/drools/core/event/rule/impl/ProcessDataChangedEventImpl.java Outdated
@@ -0,0 +1,36 @@
/*
* Copyright 2023 Red Hat, Inc. and/or its affiliates.
Copy link
Member

Choose a reason for hiding this comment

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

2024

@nmirasch nmirasch mentioned this pull request Mar 12, 2024
Merged
@nmirasch nmirasch added backport-7.67.x-blue Generate backport PR for 7.67.x-blue branch and removed backport-7.67.x-blue Generate backport PR for 7.67.x-blue branch labels Mar 28, 2024
@gmunozfe gmunozfe mentioned this pull request Apr 25, 2024
Closed
@nmirasch nmirasch mentioned this pull request Apr 26, 2024
Merged
@akumar074 akumar074 removed the backport-7.67.x-blue Generate backport PR for 7.67.x-blue branch label Jul 16, 2024
This was referenced Aug 5, 2024
Merged
Merged
@fjtirado fjtirado merged commit 5bf0775 into kiegroup:7.x Aug 7, 2024
7 of 8 checks passed
github-actions bot pushed a commit that referenced this pull request Aug 7, 2024
@fjtirado
Merge pull request #30 from nmirasch/RHPAM-4779_7.x
9f4457e 
RHPAM-4779: Added ProcessDataChangedEvent to ProcessEventSupport
@github-actions github-actions bot mentioned this pull request Aug 7, 2024
Merged
rgdoliveira pushed a commit that referenced this pull request Oct 25, 2024
@tkobayas @mariofusco
@gitgabrio @lbenc135 @yurloc @rgdoliveira
[DROOLS-7591] Experiment branch : migrate a new drools-lsp parser int… (
d577bd6 
apache#5682)

* add antlr4 based drl parser

* bump to drools 8.16.0.Beta

* improve node position discovery

* first c3 integration

* Module reorganization (#2)

* WIP

* Ignore directories

* Add debug. Minor modifications

* WIP

* Fix tests - add comments

* manage null ast nodes and fix failing test

* improve drl parser

* Fix basic completion (#4)

* Add Java grammar, fix DRL grammar, simplify token index calculation, remove template code

* Add ignored tokens to completion

Co-authored-by: livio <[email protected]>

* add constraints parsing

* - Added DRLParserWrapper to store errors using DRLErrorListener (#5)

- Added MiscDRLParserTest which is being ported from RuleParserTest to enhance coverage.

* Enhance test/grammar coverage. function import, global, exists, not (#6)

* Enhance test/grammar coverage. and, or, listExpression (#7)

* Enhance test/grammar coverage. matches, single quoted string, escape (#9)

- Introduced drlExpression, drlPrimary, drlLiteral, DRL_STRING_LITERAL

* Enhance test/grammar coverage. dialect, invalid lhs (#10)

* Enhance test/grammar coverage. keyword collision (#11)

- Add "DRL_" prefix for DRL keywords for clarification

* Enhance test/grammar coverage. function, attributes, consequence (#12)

* Enhance test/grammar coverage. function, attributes, consequence
- better getText preserving whitespaces
- resolving WARNs because of overlapping keywords

* - No need to declare duplicate keywords

* Enhance test/grammar coverage. OR, inline map (#13)

* OpenRewrite applied for junit5 and assertj (#14)

* Enhance test/grammar coverage. label, consequenceLocation, test refac… (#15)

* Enhance test/grammar coverage. label, consequenceLocation, test refactoring, assertj best practice

* - better test method names

* [DROOLS-7253] Review and improve drools-lsp parser Visitor design (#16)

* [DROOLS-7253] Review and improve drools-lsp parser Visitor design
- Remove currentConstructStack. Utilize return object instead.

* - Remove instance fields. Utilize return objects instead.

* [DROOLS-7270] Enhance test/grammar coverage : andRestriction, orRestriction (#4)

- Removed some unused cast

* [DROOLS-7271] Fully port RuleParserTest as MiscDRLParserTest with @disabled and priority comment (#10)

* [DROOLS-7285] Failed to parse and/or with parentheses in LHS (#15)

* [DROOLS-7286] Failed to parse binding with || (#21)

* [DROOLS-7287] Failed to parse comments in RHS (#23)

* [DROOLS-7287] Failed to parse comments in RHS

* - add rhs string check

* [DROOLS-7515] Parser : Accept plain text in RHS (#26)

* [DROOLS-7515] Parser : Accept plain text in RHS

* - Handle keyword token in RHS

* - Removed sysout

* - Revert statementKeywords. Instead, define DRL_END with newline or EOF

* - fix method name

* [DROOLS-7288] Failed to parse complex parentheses (#27)

* [DROOLS-7288] Failed to parse complex parentheses
- bump to 8.43.0.Final

* additional tests

* [DROOLS-7289] Implement accumulate (#28)

* [DROOLS-7296] Implement from entry-point (#30)

* [DROOLS-7297] Implement import accumulate (#29)

* [DROOLS-7290] Implement BigInteger literal, BigDecimal literal (#31)

* [DROOLS-7292] Implement eval (#32)

* [DROOLS-7293] Implement extends (#33)

* [DROOLS-7294] Implement forall (#34)

* [DROOLS-7298] Implement memberOf (#35)

* [DROOLS-7300] Implement positional constraint (#36)

* [DROOLS-7304] Implement temporal operators (#38)

- Also covers [DROOLS-7303] Implement sliding window

* [DROOLS-7301] Implement query (#37)

- Also partially fixes [DROOLS-7302] Implement semicolon delimiter

* [DROOLS-7295] Implement from collect (#39)

* [DROOLS-7305] Implement type declaration (#40)

- also covers [DROOLS-7291] Implement entry-point declaration
- also covers window declaration

* [DROOLS-7306] Implement unification (#41)

* [DROOLS-7306] Implement unification
- Also [DROOLS-7307] Parse attribute agenda-group

* [DROOLS-7308] Parse attribute without value
- Also [DROOLS-7309] Parse attribute with parentheses

* [DROOLS-7310] parse nested parentheses (#42)

* [DROOLS-7310] parse nested parentheses

* - Adding code commentes and explanations
- Adding more nested level tests

* [DROOLS-7577] drools-lsp : Add comments and explanations for drools-p… (#43)

* [DROOLS-7577] drools-lsp : Add comments and explanations for drools-parser

* removed syntax examples

* [DROOLS-7591] Experiment branch : migrate a new drools-lsp parser into drools (#44)

- Add some methods to call from drools code base

* Move necessary files without any additional modifications

* Update DRL6Expressions.g4 to ANTLR 4 (#47)

* Add DescrDumperTest and fix the expression parser grammar (#48)

* Add DescrDumperTest

* Fix it

* [DROOLS-7591] Experiment branch : migrate a new drools-lsp parser into drools
- New parser is migrated in drools-drl/drools-drl-parser with org.drools.drl10.parser package
- To enable the new parser, run `mvn test -PDRL10`
- At the moment, we get lots of test failures especially in drools-model/drools-model-codegen and drools-test-coverage/test-compiler-integration

* - License header
- Revert an inappropriate test edit
- Removed unnecessary profile
- Clarify unsupported methods
- Removed unnecessary bom dependency

---------

Co-authored-by: mariofusco <[email protected]>
Co-authored-by: Gabriele Cardosi <[email protected]>
Co-authored-by: Livio Benčik <[email protected]>
Co-authored-by: livio <[email protected]>
Co-authored-by: Jiří Locker <[email protected]>
rgdoliveira pushed a commit that referenced this pull request Oct 25, 2024
@tkobayas @rgdoliveira
[DROOLS-7296] Implement from entry-point (#30)
cee921d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@fjtirado fjtirado fjtirado approved these changes

@gmunozfe gmunozfe gmunozfe approved these changes

@tkobayas tkobayas tkobayas approved these changes

@mariofusco mariofusco mariofusco approved these changes

Assignees
No one assigned
Labels
backport-7.67.x Generate backport PR for 7.67.x branch
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
6 participants
@nmirasch @mariofusco @tkobayas @gmunozfe @fjtirado @akumar074