[JBoss JIRA] (DROOLS-3000) Design data type constraints UX
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3000?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3000:
--------------------------------
Sprint: 2018 Week 33-35, 2018 Week 48-50 (was: 2018 Week 33-35, 2018 Week 48-50, 2018 Week 51-01)
Epic Name: Data Type Constraints UX
> Design data type constraints UX
> --------------------------------
>
> Key: DROOLS-3000
> URL: https://issues.jboss.org/browse/DROOLS-3000
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 AM.png, Screen Shot 2018-09-28 at 2.44.59 PM.png, date-time.png, date.png, enumration-widget.png, pop-overc.png, pop-overcSpecs.png, read-mode.png, select.png, time.png
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E...
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (DROOLS-3445) Date-related data type constraints
by Liz Clayton (Jira)
Liz Clayton created DROOLS-3445:
-----------------------------------
Summary: Date-related data type constraints
Key: DROOLS-3445
URL: https://issues.jboss.org/browse/DROOLS-3445
Project: Drools
Issue Type: Story
Components: DMN Editor
Reporter: Liz Clayton
Assignee: Liz Clayton
Background
Persona: Business analyst or Rules practitioner
Use Cases:
* From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
* From the Data Types tab - as a user I want the ability to define constraints for the following types: Date
Functional considerations/ pre conditions:
* Consider interaction in light of Property panel and consistency.
* Underscore the notion of one-off constraints.
Verification conditions:
* Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (WFLY-11535) Cluster fails to merge if instances started simultaneously
by Ian Rodgers (Jira)
Ian Rodgers created WFLY-11535:
----------------------------------
Summary: Cluster fails to merge if instances started simultaneously
Key: WFLY-11535
URL: https://issues.jboss.org/browse/WFLY-11535
Project: WildFly
Issue Type: Bug
Affects Versions: 14.0.0.Final
Environment: Keycloak 4.6.0 official docker image, AWS ECS cluster
Reporter: Ian Rodgers
Assignee: Jason Greene
Our Keycloak docker cluster has four instances, clustered using Jgroups/Infinispan as per the standalone-ha.xml. If you start them all simultaneously the "Receive new cluster" logs indicate four separate clusters, each with a single member. They never get merged into the proper single cluster of four members. It seems to be the merging that has changed. The application then fails (we are not using sticky sessions, and each member is ignorant of the sessions on the other members).
We can only start the cluster by first starting one instance, then when it is running, starting the other three. The logs then indicate the creation of a single cluster which subsequent instances join.
This is consistent behaviour, and when we revert back to v.4.5.0, the issue goes away, Unfortunately we need 4.6.0 for an important fix.
On 4.5.0 we get the message "Received new, MERGED cluster view for channel ejb: MergeView::" when it detects a number of subgroups to merge. This never appears in 4.6.0.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (DROOLS-1781) Investigate possible replacement of findbugs-maven-plugin with spotbugs-maven-plugin
by Geoffrey De Smet (Jira)
[ https://issues.jboss.org/browse/DROOLS-1781?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet commented on DROOLS-1781:
------------------------------------------
Error message:
14:58:39 [ERROR] Failed to execute goal org.codehaus.mojo:findbugs-maven-plugin:3.0.5:check (findbugs-check) on project kie-api: failed with 7 bugs and 0 errors -> [Help 1]
Looks like findbugs in still active. Do "mvn help:effective-pom | grep findbugs". Then figure it where the findbugs activation comes from (from which parent pom).
> Investigate possible replacement of findbugs-maven-plugin with spotbugs-maven-plugin
> ------------------------------------------------------------------------------------
>
> Key: DROOLS-1781
> URL: https://issues.jboss.org/browse/DROOLS-1781
> Project: Drools
> Issue Type: Task
> Components: build
> Affects Versions: 7.4.1.Final
> Reporter: Petr Široký
> Assignee: Michael Biarnes Kiefer
> Priority: Major
> Labels: java9
>
> SpotBugs is a successor of FingBugs and as such uses different groupId + artifactId for maven plugin. It should also be compatible with Java 9 (at least in the latest versions). We need to investigate it the switch is painless and if so, do it. Otherwise we need to figure out what the blockers are and slowly start to fix them as FindBugs itself won't bet any more updates it seems and so won't be Java 9 compatible.
> *How to migrate*
> * Replace
> {code}
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>findbugs-maven-plugin</artifactId>
> {code}
> by
> {code}
> <groupId>com.github.spotbugs</groupId>
> <artifactId>spotbugs-maven-plugin</artifactId>
> {code}
> * Look for all "findbugs" and replace it by "spotbugs"
> ** Except for anything related to the findbugs annotations dependency that some dependencies drag in or exclude. Leave that one alone!
> ** For example, change findbugs-check -> spotbugs-check, ...
> * Merge this PR if it hasn't been merged already: https://github.com/kiegroup/optaplanner-wb/pull/320
> * Then you only need to adjust the following repo's: build-boostrap, drools, optaplanner and kie-wb-distributions.
> ** See https://github.com/search?q=org%3Akiegroup+findbugs-maven-plugin&type=Code
> ** Ignore contributed experiments, that repo is dead
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months