jBPM

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
JBPM-5897 - Fails to start a process with CorrelationKey which is unique but includes correlation properties of an existing correlation key

JBPM-5897 - Fails to start a process with CorrelationKey which is unique but includes correlation properties of an existing correlation key

JBPM-5886: Replace joda-time with Java 8 time implementation (#809)

JBPM-5891 - Process validation should not trigger on empty package name (#813)

JBPM-4646 - case management - case file data audit trail (#812)

  1. … 55 more files in changeset.
JBPM-5880 - 'async' as a default option for all tasks (#806)

JBPM-5897 Fails to start a process with CorrelationKey which is unique but includes correlation properties of an existing correlation key - Test case

JBPM-5897 Fails to start a process with CorrelationKey which is unique but includes correlation properties of an existing correlation key - Test case

JBPM-5891 - updating tests (#815)

JBPM-5891 - Process validation should not trigger on empty package name (#814)

- added one more folder for case mgmt cleanup

    • -0
    • +1
    /jbpm-installer/src/main/resources/build.xml
- added one more folder for case mgmt cleanup

    • -0
    • +1
    /jbpm-installer/src/main/resources/build.xml
JBPM-5772: Improve jbpm-installer to support case mgmt + auto-provisioning + demo

    • -29
    • +27
    /jbpm-installer/src/main/resources/build.xml
JBPM-5772: Improve jbpm-installer to support case mgmt + auto-provisioning + demo

    • -29
    • +27
    /jbpm-installer/src/main/resources/build.xml
JBPM-4646 - case management - case file data audit trail (#807)

  1. … 55 more files in changeset.
JBPM-5885 - Add new constant for completeCondition on Ad-hoc Subprocesses for autoComplete (#808) (#811)

JBPM-5885 - Add new constant for completeCondition on Ad-hoc Subprocesses for autoComplete (#808)

JBPM-5468 - Enable multiple column sorting on advanced queries (#796)

* JBPM-5468 refactoring to use AdvancedQueryContext for advanced query api.

* JBPM-5468 correction to logic which parses the orderByClause

* JBPM-5468 reset to upstream/master and refactored with suggested changes from code review

Add two additional tests for CleanupExecutionErrorCommand

JBPM-5841 - Round robin assignment strategy (#790)

* Adding RoundRobin assignment strategy

JBPM-5610 - Add tests with groups and excluded owners (#801)

Adds 2 tests methods that test behaviour of excluding user/users

from group that is set as potential owner of the task.

Upgraded to next development version 7.1.0-SNAPSHOT (#799)

  1. … 43 more files in changeset.
JBPM-5869 - Boundary Event Signal does not transalate variables while registring as Signal Event Listener (#800)

    • -0
    • +328
    /jbpm-bpmn2/src/test/resources/BPMN2-SubprocessWithSignalEndEventAndSignalBoundaryEvent.bpmn2
Upgraded versions for release 7.0.0.CR1

  1. … 43 more files in changeset.
avoid NPE when dynamic task parameters are not given (#798)

RHBPMS-1328 - business rule task supports boundary error event (#797)

    • -0
    • +203
    /jbpm-bpmn2/src/test/resources/BPMN2-ErrorBoundaryEventOnBusinessRuleTask.bpmn2
    • -0
    • +26
    /jbpm-bpmn2/src/test/resources/BPMN2-ErrorBoundaryEventOnBusinessRuleTask.drl
    • -0
    • +317
    /jbpm-bpmn2/src/test/resources/BPMN2-MultiErrorBoundaryEventsOnBusinessRuleTask.bpmn2
    • -0
    • +37
    /jbpm-bpmn2/src/test/resources/BPMN2-MultiErrorBoundaryEventsOnBusinessRuleTask.drl
Test with Tomcat 8.0.x instead of Tomcat 8.5.x

Tomcat 8.5.x is not compatible with arquillian-tomcat-remote-7 and there

is no arquillian-tomcat-remote-8 (yet?).

See https://github.com/arquillian/arquillian-container-tomcat/issues/39

Test with WildFly 10.1.0.Final and Tomcat 8.5.13

Run container tests only when container profile is used

The tests in jbpm-remote-ejb-test-suite were executed even if no

container profile was specified. This makes is hard to disable the

tests for specific containers (like Tomcat8, for which it does not

make sense to run the EJB tests).

With the changes:

- mvn clean install -> no tests executed; cargo execs disabled

- mvn clean install -Dcustom-profile -> tests executed, no cargo exec

- mvn clean install -Dcontainer.profile=tomcat8 -> tests executed on

the specified container (which is managed by cargo)

container-tests: fail the build if there are test failures

Gailsafe needs the 'verify' goal as that is when the decision

to fail or not happens.