October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3191) Add highlight red borders to errors

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3191?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3191: --------------------------------- Tester: Klara Kufova > Add highlight red borders to errors > ----------------------------------- > > Key: DROOLS-3191 > URL: https://issues.jboss.org/browse/DROOLS-3191 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > > Align error reporting in the table as design proposal (add red borders around error cells) > https://issues.jboss.org/browse/DROOLS-3151 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3184) [DMN Designer] Edge source and target WayPoints are same

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-3184?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-3184: ---------------------------------------- {quote}ndefined i.e. null (IDK why, need to raise an issue with the Stunner people{quote} Isn't this what I'm checking here? https://github.com/kiegroup/kie-wb-common/pull/2204/files#diff-165c0c76fc... > [DMN Designer] Edge source and target WayPoints are same > -------------------------------------------------------- > > Key: DROOLS-3184 > URL: https://issues.jboss.org/browse/DROOLS-3184 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Matteo Mortari > Priority: Blocker > Labels: drools-tools > Attachments: Screenshot from 2018-10-25 12-12-20.png, a1.dmn, image (2).png > > > The source of DMN model has same waypoint for edge source and target. If you open the attached [^a1.dmn] model, there will be: > {code:xml} > <dmndi:DMNEdge id="dmnedge-_594C4BE1-52D0-4009-9D4F-9960957539FB" dmnElementRef="_594C4BE1-52D0-4009-9D4F-9960957539FB"> > <di:waypoint xmlns:di="http://www.omg.org/spec/DMN/20180521/DI/" x="50" y="25"/> > <di:waypoint xmlns:di="http://www.omg.org/spec/DMN/20180521/DI/" x="50" y="25"/> > </dmndi:DMNEdge> > {code} > However in our designer the edge has different waypoints: > !Screenshot from 2018-10-25 12-12-20.png|thumbnail! > In the external modeling tools, the edge is rendered according to real waypoints and this the edge is not visible: > !image (2).png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3185) [DMN Designer] Change Literal Expression to Decision Table

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-3185?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-3185: ---------------------------------------- [~manstis] in DMN 1.2 it is without prefix. The marshaller is working correctly to export to 1.2. {quote}This could have quite an impact on the UI as we previously assumed built-in-types were feel:xyz.{quote} Let's discuss this when suitable. I would have expected on DMNv1.1 to have properly separated into prefix and localname; if it's missing some namespace somewhere please point me to where I might have missed in the case? > [DMN Designer] Change Literal Expression to Decision Table > ---------------------------------------------------------- > > Key: DROOLS-3185 > URL: https://issues.jboss.org/browse/DROOLS-3185 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Matteo Mortari > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2018-10-25 14-40-06.png > > > When user changes Decision node top level expression from literal expression to decision table, that decision table misses InputClause columns. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-470) oc cluster up not working on b15

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-470?page=com.atlassian.jira.plugin.... ] Filip Brychta updated SWSQE-470: -------------------------------- Summary: oc cluster up not working on b15 (was: oc cluster op not working on b15) > oc cluster up not working on b15 > -------------------------------- > > Key: SWSQE-470 > URL: https://issues.jboss.org/browse/SWSQE-470 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-470) oc cluster op not working on b15

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-470?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-470. --------------------------------- Resolution: Done I followed https://github.com/openshift/origin/blob/master/docs/cluster_up_down.md and its starting fine now. Problem was probably in iptables. I disabled that and installed firewalld and configured as described. > oc cluster op not working on b15 > -------------------------------- > > Key: SWSQE-470 > URL: https://issues.jboss.org/browse/SWSQE-470 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-470) oc cluster op not working on b15

by Filip Brychta (Jira)

Filip Brychta created SWSQE-470: ----------------------------------- Summary: oc cluster op not working on b15 Key: SWSQE-470 URL: https://issues.jboss.org/browse/SWSQE-470 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3194) Make Drools to run on JDK11

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-3194?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-3194: ------------------------------------- poker: 8 > Make Drools to run on JDK11 > --------------------------- > > Key: DROOLS-3194 > URL: https://issues.jboss.org/browse/DROOLS-3194 > Project: Drools > Issue Type: Task > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > > Justification: https://blog.codefx.org/java/java-11-migration-guide/ > Other good resource: https://winterbe.com/posts/2018/08/29/migrate-maven-projects-to-java-11-j... > Note: our primary build is still JDK 8, we just want to be JDK 11 friendly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3194) Make Drools to run on JDK11

by Mario Fusco (Jira)

Mario Fusco created DROOLS-3194: ----------------------------------- Summary: Make Drools to run on JDK11 Key: DROOLS-3194 URL: https://issues.jboss.org/browse/DROOLS-3194 Project: Drools Issue Type: Task Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco Justification: https://blog.codefx.org/java/java-11-migration-guide/ Other good resource: https://winterbe.com/posts/2018/08/29/migrate-maven-projects-to-java-11-j... Note: our primary build is still JDK 8, we just want to be JDK 11 friendly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3154) Minor UI improvements/bugfixes for Scenario

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3154?page=com.atlassian.jira.plugi... ] Gabriele Cardosi edited comment on DROOLS-3154 at 10/26/18 3:21 AM: -------------------------------------------------------------------- [~uxdlc] About Index/Description header: Maybe it is possible, but surely it is not just a "delete one line" operation; so, for the moment being I would keep them there. /----/ About this header menu: Liz, please, *I'm* asking you what to do. I just underlined to you what (from my point of view) could be a little un-consistence. Please tell me, without keeping asking, what do you prefer the interaction to be, I'm not in love with any of those menu, I can live without. If you want them to be removed, I remove. If you want them to be renamed, I rename. If you want a different interaction, I'll implement. About that document you keep referring to, it can not be considered final by any mean. It is only using the real software while is developed that you may understand what is actually needed, what needs to be changed, and so on and so forth. I'm using it all the day, and whatever doubt or objection I raise is due to the actual usage, being myself not only a "developer" but also a "user". And that drive to my last consideration: if you were able to use a real instance of the scenario is *great*, but now we need a way so that you may look at what I'm currently doing: my last PR (3095), the multi-instance, has a huge impact and implications, and it is taking a lot of time: to wait for you to see it until is merged in master would be a big waste of time, because surely I'm doing things with "developer" eye, that has never matched, in historical reports, UX one :). was (Author: gabriolo): [~uxdlc] About Index/Description header: Maybe it is possible, but surely it is not just a "delete one line" operation; so, for the moment being I would keep them there. /----/ About this header menu: Liz, please, *I'm* asking you what to do. I just underlined to you what (from my point of you) could be a little un-consistence. Please tell me, without keeping asking, what do you prefer the interaction to be, I'm not in love with any of those menu, I can live without. If you want them to be removed, I remove. If you want them to be renamed, I rename. If you want a different interaction, I'll implement. About that document you keep referring to, it can not be considered final by any mean. It is only using the real software while is developed that you may understand what is actually needed, what needs to be changed, and so on and so forth. I'm using it all the day, and whatever doubt or objection I raise is due to the actual usage, being myself not only a "developer" but also a "user". And that drive to my last consideration: if you were able to use a real instance of the scenario is *great*, but now we need a way so that you may look at what I'm currently doing: my last PR (3095), the multi-instance, has a huge impact and implications, and it is taking a lot of time: to wait for you to see it until is merged in master would be a big waste of time, because surely I'm doing things with "developer" eye, that has never matched, in historical reports, UX one :). > Minor UI improvements/bugfixes for Scenario > ------------------------------------------- > > Key: DROOLS-3154 > URL: https://issues.jboss.org/browse/DROOLS-3154 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Major > Labels: UX-CSS > Attachments: Screen Shot 2018-10-25 at 9.53.57 PM.png, test-editor-margin.png > > > This item contains a list of general UI bugs to be fixed: > -Use grey borders for all the grid and not only for the header- Fixed in DROOLS-2684 > -Add some padding to the cells of the grid- Fixed in DROOLS-2684 > Add some padding to right panel the tab titles > -Remove scrolling bar from right panel- Fixed in DROOLS-3170 > Review expression editor component HTML/CSS (paddings, indents, etc) > Review right panel padding (now it is hardcoded) > Use text area inputs instead of text box for inline editing > -Reduce the width of Index column- Fixed in DROOLS-3167 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3154) Minor UI improvements/bugfixes for Scenario

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3154?page=com.atlassian.jira.plugi... ] Gabriele Cardosi commented on DROOLS-3154: ------------------------------------------ [~uxdlc] About Index/Description header: Maybe it is possible, but surely it is not just a "delete one line" operation; so, for the moment being I would keep them there. /----/ About this header menu: Liz, please, *I'm* asking you what to do. I just underlined to you what (from my point of you) could be a little un-consistence. Please tell me, without keeping asking, what do you prefer the interaction to be, I'm not in love with any of those menu, I can live without. If you want them to be removed, I remove. If you want them to be renamed, I rename. If you want a different interaction, I'll implement. About that document you keep referring to, it can not be considered final by any mean. It is only using the real software while is developed that you may understand what is actually needed, what needs to be changed, and so on and so forth. I'm using it all the day, and whatever doubt or objection I raise is due to the actual usage, being myself not only a "developer" but also a "user". And that drive to my last consideration: if you were able to use a real instance of the scenario is *great*, but now we need a way so that you may look at what I'm currently doing: my last PR (3095), the multi-instance, has a huge impact and implications, and it is taking a lot of time: to wait for you to see it until is merged in master would be a big waste of time, because surely I'm doing things with "developer" eye, that has never matched, in historical reports, UX one :). > Minor UI improvements/bugfixes for Scenario > ------------------------------------------- > > Key: DROOLS-3154 > URL: https://issues.jboss.org/browse/DROOLS-3154 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Major > Labels: UX-CSS > Attachments: Screen Shot 2018-10-25 at 9.53.57 PM.png, test-editor-margin.png > > > This item contains a list of general UI bugs to be fixed: > -Use grey borders for all the grid and not only for the header- Fixed in DROOLS-2684 > -Add some padding to the cells of the grid- Fixed in DROOLS-2684 > Add some padding to right panel the tab titles > -Remove scrolling bar from right panel- Fixed in DROOLS-3170 > Review expression editor component HTML/CSS (paddings, indents, etc) > Review right panel padding (now it is hardcoded) > Use text area inputs instead of text box for inline editing > -Reduce the width of Index column- Fixed in DROOLS-3167 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2018