[JBoss JIRA] (DROOLS-5229) DMNValidate mojo fails XMLSchema validation with included models
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5229?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5229:
-----------------------------------
Sprint: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4) (was: 2020 Week 16-18 (from Apr 13))
> DMNValidate mojo fails XMLSchema validation with included models
> ----------------------------------------------------------------
>
> Key: DROOLS-5229
> URL: https://issues.redhat.com/browse/DROOLS-5229
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.34.0.Final
> Reporter: Tracy Hires
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
> Attachments: ValidateDMN Mojo Failure.png, xml_validation_error.zip
>
>
> The attached DMN decision project was built using Business Central 7.34.0.Final. In this project, the dmn model `Math Functions.dmn` invokes business knowledge model `Quotient` from dmn model `Divide.dmn`. Invoking the ValidateDMN mojo (enabled by default) from the kie-maven-plugin fails XML Validation. One can get past this error by disabling DMNValidation with the following configuration in the pom (though disabling DMNValidation for an XML Schema validation also prevents finding FEEL parser errors):
> ```
> <build>
> <plugins>
> <plugin>
> <groupId>org.kie</groupId>
> <artifactId>kie-maven-plugin</artifactId>
> <version>7.34.0.Final</version>
> <extensions>true</extensions>
> <!-- Can get past xml validation error by disabling the ValidateDMN Mojo -->
> <configuration>
> <validateDMN>disabled</validateDMN>
> </configuration>
> </plugin>
> </plugins>
> </build>
> ```
> When one combines the two dmn models into a single model, the XML Validation succeeds (this example is not supplied, but is trivial to re-build).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 12 months
[JBoss JIRA] (DROOLS-5210) BRL Column support for GDST to XLS export
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5210?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5210:
-----------------------------------
Sprint: 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4) (was: 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13))
> BRL Column support for GDST to XLS export
> -----------------------------------------
>
> Key: DROOLS-5210
> URL: https://issues.redhat.com/browse/DROOLS-5210
> Project: Drools
> Issue Type: Feature Request
> Components: Guided Decision Table Editor, XLS Decision Table Editor
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
>
> How good the support will end up being is still open. The goal is to have one column for each variable, but if this is doable or not will depend on the limitations of the XLS table.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 12 months
[JBoss JIRA] (DROOLS-5101) rhdm 7 (v 7.5.1; eap 7.2; Drools 7.26; windows 10) FAIL - OutOfMemoryError
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5101?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5101:
-----------------------------------
Sprint: 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4) (was: 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13))
> rhdm 7 (v 7.5.1; eap 7.2; Drools 7.26; windows 10) FAIL - OutOfMemoryError
> --------------------------------------------------------------------------
>
> Key: DROOLS-5101
> URL: https://issues.redhat.com/browse/DROOLS-5101
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.26.0.Final
> Reporter: Charles Herrick
> Assignee: Toni Rikkola
> Priority: Critical
>
> 09:13:02,818 ERROR [org.kie.workbench.common.services.backend.builder.core.Builder] (default task-95) GC overhead limit exceeded: java.lang.OutOfMemoryError: GC overhead limit exceeded
> 09:13:05,335 ERROR [stderr] (default task-95) java.lang.OutOfMemoryError: GC overhead limit exceeded
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 12 months
[JBoss JIRA] (DROOLS-4865) Add i18n reporting for DMN V&V
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-4865?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-4865:
-----------------------------------
Sprint: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4) (was: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13))
> Add i18n reporting for DMN V&V
> ------------------------------
>
> Key: DROOLS-4865
> URL: https://issues.redhat.com/browse/DROOLS-4865
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
>
> The current reporting from the shared V&V is showing debug messages that are not meant for user to see and the custom DMN V&V is not i18n.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 12 months
[JBoss JIRA] (DROOLS-4575) Test Scenario: unsaved changes warning appears even if file has not been changed
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-4575?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-4575:
-----------------------------------
Sprint: 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4) (was: 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13))
> Test Scenario: unsaved changes warning appears even if file has not been changed
> --------------------------------------------------------------------------------
>
> Key: DROOLS-4575
> URL: https://issues.redhat.com/browse/DROOLS-4575
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Daniele Zonca
> Priority: Major
> Labels: CustomerFocus, drools-tools
>
> If user opens a scesim file and then close it, no confirmation message should be opened
> h2. Manual Acceptance Test
> - Opening and closing without changes
> - Open, change data in cell, close
> - Open, add column, remove column, change column binding, close
> - Open, Change settings on the settings panel (e.g. ruleflow group, kie session), close
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 12 months