December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2164) [DMN Editor] New Expression Columns doesn't respect width of parent column

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2164: ----------------------------------- Summary: [DMN Editor] New Expression Columns doesn't respect width of parent column Key: DROOLS-2164 URL: https://issues.jboss.org/browse/DROOLS-2164 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.5.0.Final Reporter: Jozef Marko Assignee: Michael Anstis New Expression Column doesn't respect the width of the parent column in the context table. It can be seen if the context table contains multiple entries. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3450) CLI - avoid required attributes to be hard to see when using tab completion

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3450?page=com.atlassian.jira.plugi... ] Ingo Weiss commented on WFCORE-3450: ------------------------------------ I agree with this matrix. [~jfdenise], what do you think? > CLI - avoid required attributes to be hard to see when using tab completion > ---------------------------------------------------------------------------- > > Key: WFCORE-3450 > URL: https://issues.jboss.org/browse/WFCORE-3450 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Miroslav Novak > > This is follow up for WFCORE-2283 which marked required attributes by "*" when using tab completion. Still if there are many attributes, it's hard to see all required attributes, for example in: > {code} > [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/cluster-connection=my-cluster:add( > ! check-period connector-name* max-retry-interval notification-interval retry-interval-multiplier > allow-direct-connections-only cluster-connection-address* discovery-group* message-load-balancing-type producer-window-size static-connectors* > call-failover-timeout confirmation-window-size initial-connect-attempts min-large-message-size reconnect-attempts use-duplicate-detection > call-timeout connection-ttl max-hops notification-attempts retry-interval > {code} > it's not clear at the first look how many required attributes there are. > Suggestion is to group required attributes together and then provide list of other attributes, for example on the next line. Another options might be considered as well. For example to show required attributes when double pressing <tab>. > Discussed on https://developer.jboss.org/wiki/CLI-BetterCompletionForArguments?et=watc... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3450) CLI - avoid required attributes to be hard to see when using tab completion

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3450?page=com.atlassian.jira.plugi... ] Rostislav Svoboda commented on WFCORE-3450: ------------------------------------------- For color case we would need it configurable (+1 to make colors enabled) and cover following scenarios: * terminal supports color + CLI color on * terminal supports color + CLI color off * terminal does not support color + CLI color on * terminal does not support color + CLI color off Windows seems to be the fun platform - cmd + powershell. Some people can be using stuff like http://cmder.net/ > CLI - avoid required attributes to be hard to see when using tab completion > ---------------------------------------------------------------------------- > > Key: WFCORE-3450 > URL: https://issues.jboss.org/browse/WFCORE-3450 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Miroslav Novak > > This is follow up for WFCORE-2283 which marked required attributes by "*" when using tab completion. Still if there are many attributes, it's hard to see all required attributes, for example in: > {code} > [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/cluster-connection=my-cluster:add( > ! check-period connector-name* max-retry-interval notification-interval retry-interval-multiplier > allow-direct-connections-only cluster-connection-address* discovery-group* message-load-balancing-type producer-window-size static-connectors* > call-failover-timeout confirmation-window-size initial-connect-attempts min-large-message-size reconnect-attempts use-duplicate-detection > call-timeout connection-ttl max-hops notification-attempts retry-interval > {code} > it's not clear at the first look how many required attributes there are. > Suggestion is to group required attributes together and then provide list of other attributes, for example on the next line. Another options might be considered as well. For example to show required attributes when double pressing <tab>. > Discussed on https://developer.jboss.org/wiki/CLI-BetterCompletionForArguments?et=watc... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3450) CLI - avoid required attributes to be hard to see when using tab completion

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3450?page=com.atlassian.jira.plugi... ] Rostislav Svoboda updated WFCORE-3450: -------------------------------------- Forum Reference: https://developer.jboss.org/wiki/CLI-BetterCompletionForArguments?et=watc... > CLI - avoid required attributes to be hard to see when using tab completion > ---------------------------------------------------------------------------- > > Key: WFCORE-3450 > URL: https://issues.jboss.org/browse/WFCORE-3450 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Miroslav Novak > > This is follow up for WFCORE-2283 which marked required attributes by "*" when using tab completion. Still if there are many attributes, it's hard to see all required attributes, for example in: > {code} > [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/cluster-connection=my-cluster:add( > ! check-period connector-name* max-retry-interval notification-interval retry-interval-multiplier > allow-direct-connections-only cluster-connection-address* discovery-group* message-load-balancing-type producer-window-size static-connectors* > call-failover-timeout confirmation-window-size initial-connect-attempts min-large-message-size reconnect-attempts use-duplicate-detection > call-timeout connection-ttl max-hops notification-attempts retry-interval > {code} > it's not clear at the first look how many required attributes there are. > Suggestion is to group required attributes together and then provide list of other attributes, for example on the next line. Another options might be considered as well. For example to show required attributes when double pressing <tab>. > Discussed on https://developer.jboss.org/wiki/CLI-BetterCompletionForArguments?et=watc... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3450) CLI - avoid required attributes to be hard to see when using tab completion

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3450?page=com.atlassian.jira.plugi... ] Rostislav Svoboda updated WFCORE-3450: -------------------------------------- Description: This is follow up for WFCORE-2283 which marked required attributes by "*" when using tab completion. Still if there are many attributes, it's hard to see all required attributes, for example in: {code} [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/cluster-connection=my-cluster:add( ! check-period connector-name* max-retry-interval notification-interval retry-interval-multiplier allow-direct-connections-only cluster-connection-address* discovery-group* message-load-balancing-type producer-window-size static-connectors* call-failover-timeout confirmation-window-size initial-connect-attempts min-large-message-size reconnect-attempts use-duplicate-detection call-timeout connection-ttl max-hops notification-attempts retry-interval {code} it's not clear at the first look how many required attributes there are. Suggestion is to group required attributes together and then provide list of other attributes, for example on the next line. Another options might be considered as well. For example to show required attributes when double pressing <tab>. Discussed on https://developer.jboss.org/wiki/CLI-BetterCompletionForArguments?et=watc... was: This is follow up for WFCORE-2283 which marked required attributes by "*" when using tab completion. Still if there are many attributes, it's hard to see all required attributes, for example in: {code} [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/cluster-connection=my-cluster:add( ! check-period connector-name* max-retry-interval notification-interval retry-interval-multiplier allow-direct-connections-only cluster-connection-address* discovery-group* message-load-balancing-type producer-window-size static-connectors* call-failover-timeout confirmation-window-size initial-connect-attempts min-large-message-size reconnect-attempts use-duplicate-detection call-timeout connection-ttl max-hops notification-attempts retry-interval {code} it's not clear at the first look how many required attributes there are. Suggestion is to group required attributes together and then provide list of other attributes, for example on the next line. Another options might be considered as well. For example to show required attributes when double pressing <tab>. > CLI - avoid required attributes to be hard to see when using tab completion > ---------------------------------------------------------------------------- > > Key: WFCORE-3450 > URL: https://issues.jboss.org/browse/WFCORE-3450 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Miroslav Novak > > This is follow up for WFCORE-2283 which marked required attributes by "*" when using tab completion. Still if there are many attributes, it's hard to see all required attributes, for example in: > {code} > [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/cluster-connection=my-cluster:add( > ! check-period connector-name* max-retry-interval notification-interval retry-interval-multiplier > allow-direct-connections-only cluster-connection-address* discovery-group* message-load-balancing-type producer-window-size static-connectors* > call-failover-timeout confirmation-window-size initial-connect-attempts min-large-message-size reconnect-attempts use-duplicate-detection > call-timeout connection-ttl max-hops notification-attempts retry-interval > {code} > it's not clear at the first look how many required attributes there are. > Suggestion is to group required attributes together and then provide list of other attributes, for example on the next line. Another options might be considered as well. For example to show required attributes when double pressing <tab>. > Discussed on https://developer.jboss.org/wiki/CLI-BetterCompletionForArguments?et=watc... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3450) CLI - avoid required attributes to be hard to see when using tab completion

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3450?page=com.atlassian.jira.plugi... ] Ingo Weiss commented on WFCORE-3450: ------------------------------------ As mentioned, I think colours + '*' would be best suited. If the terminal doesn't support colours, then the '*' should suffice. Maybe we can add a note mentioning that '*' attributes are required ones? > CLI - avoid required attributes to be hard to see when using tab completion > ---------------------------------------------------------------------------- > > Key: WFCORE-3450 > URL: https://issues.jboss.org/browse/WFCORE-3450 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Miroslav Novak > > This is follow up for WFCORE-2283 which marked required attributes by "*" when using tab completion. Still if there are many attributes, it's hard to see all required attributes, for example in: > {code} > [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/cluster-connection=my-cluster:add( > ! check-period connector-name* max-retry-interval notification-interval retry-interval-multiplier > allow-direct-connections-only cluster-connection-address* discovery-group* message-load-balancing-type producer-window-size static-connectors* > call-failover-timeout confirmation-window-size initial-connect-attempts min-large-message-size reconnect-attempts use-duplicate-detection > call-timeout connection-ttl max-hops notification-attempts retry-interval > {code} > it's not clear at the first look how many required attributes there are. > Suggestion is to group required attributes together and then provide list of other attributes, for example on the next line. Another options might be considered as well. For example to show required attributes when double pressing <tab>. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2122) Error when drl file is opened with in project with runtime classes

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2122?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-2122: ------------------------------------- Fixed by https://github.com/kiegroup/droolsjbpm-knowledge/commit/aedd33f85b4fa73bd... and https://github.com/kiegroup/droolsjbpm-tools/commit/b8dc98591075b7f050d96... > Error when drl file is opened with in project with runtime classes > ------------------------------------------------------------------- > > Key: DROOLS-2122 > URL: https://issues.jboss.org/browse/DROOLS-2122 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Affects Versions: 7.3.0.Final > Environment: DevstudioIS 11.1.0.Beta1 > Brms 6.4.6.GA > Reporter: Tomas David > Assignee: Mario Fusco > Priority: Blocker > Fix For: 7.5.0.Final > > Attachments: Screenshot from 2017-11-09 09-55-05.png, devstudiolog.log > > > If new drools project is created with build using Java and Drools classes, error is displayed after drl file is opened. > This blocks also other functions like add a breakpoint or show content assist menu. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2122) Error when drl file is opened with in project with runtime classes

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2122?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-2122: ---------------------------------------- Also requires 2 commits, on droolsjbpm-knowledge and a new one on droolsjbpm-tools: https://github.com/kiegroup/droolsjbpm-knowledge/commit/aedd33f85b4fa73bd... https://github.com/kiegroup/droolsjbpm-tools/commit/b8dc98591075b7f050d96... > Error when drl file is opened with in project with runtime classes > ------------------------------------------------------------------- > > Key: DROOLS-2122 > URL: https://issues.jboss.org/browse/DROOLS-2122 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Affects Versions: 7.3.0.Final > Environment: DevstudioIS 11.1.0.Beta1 > Brms 6.4.6.GA > Reporter: Tomas David > Assignee: Mario Fusco > Priority: Blocker > Fix For: 7.5.0.Final > > Attachments: Screenshot from 2017-11-09 09-55-05.png, devstudiolog.log > > > If new drools project is created with build using Java and Drools classes, error is displayed after drl file is opened. > This blocks also other functions like add a breakpoint or show content assist menu. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3450) CLI - avoid required attributes to be hard to see when using tab completion

by Miroslav Novak (JIRA)

Miroslav Novak created WFCORE-3450: -------------------------------------- Summary: CLI - avoid required attributes to be hard to see when using tab completion Key: WFCORE-3450 URL: https://issues.jboss.org/browse/WFCORE-3450 Project: WildFly Core Issue Type: Feature Request Components: CLI Reporter: Miroslav Novak This is follow up for WFCORE-2283 which marked required attributes by "*" when using tab completion. Still if there are many attributes, it's hard to see all required attributes, for example in: {code} [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/cluster-connection=my-cluster:add( ! check-period connector-name* max-retry-interval notification-interval retry-interval-multiplier allow-direct-connections-only cluster-connection-address* discovery-group* message-load-balancing-type producer-window-size static-connectors* call-failover-timeout confirmation-window-size initial-connect-attempts min-large-message-size reconnect-attempts use-duplicate-detection call-timeout connection-ttl max-hops notification-attempts retry-interval {code} it's not clear at the first look how many required attributes there are. Suggestion is to group required attributes together and then provide list of other attributes, for example on the next line. Another options might be considered as well. For example to show required attributes when double pressing <tab>. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2163) [DMN Editor] Context table doesn't show entry type label if table is scrolled

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2163: ----------------------------------- Summary: [DMN Editor] Context table doesn't show entry type label if table is scrolled Key: DROOLS-2163 URL: https://issues.jboss.org/browse/DROOLS-2163 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.5.0.Final Reporter: Jozef Marko Assignee: Michael Anstis Context table offers 5 types of entries while each entry has label of its own type (Literal Expression, Function Relation etc.) However this label is not shown if the user scroll the table. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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 December 2017