November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3286) [DMN Designer] FunctionGrid: Move F, J, P selector to header

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3286?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3286: ----------------------------------- Sprint: 2018 Week 48-50 > [DMN Designer] FunctionGrid: Move F, J, P selector to header > ------------------------------------------------------------- > > Key: DROOLS-3286 > URL: https://issues.jboss.org/browse/DROOLS-3286 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Michael Anstis > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > The {{FunctionGrid}} allows switching between FEEL, Java and PMML function definitions using the context menu. [~tirelli] has requested this be changed to a selector in the header. A new column needs to be added with the F, J, P selector in the new column header. The header should display F, J or P accordingly. Do not include row numbers (i.e. don't just add a {{RowNumberColumn}}! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3329) [DMN Designer] Memory leak in DataTypeList

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3329?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3329: ----------------------------------- Sprint: 2018 Week 48-50 > [DMN Designer] Memory leak in DataTypeList > ------------------------------------------ > > Key: DROOLS-3329 > URL: https://issues.jboss.org/browse/DROOLS-3329 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.15.0.Final > Reporter: Daniel José dos Santos > Assignee: Daniel José dos Santos > Priority: Minor > Labels: drools-tools > > In the "Manage Custom Data Types", if you add and remove an type, the type is not removed from memory in "DataTypeList" after you remove it, causing a leak. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3155) [DMN Designer] Data Type Selectbox remains shown

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3155?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3155: ----------------------------------- Story Points: 2 > [DMN Designer] Data Type Selectbox remains shown > ------------------------------------------------ > > Key: DROOLS-3155 > URL: https://issues.jboss.org/browse/DROOLS-3155 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final, 7.15.0.Final > Environment: eap-7.2 > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > Attachments: Screenshot from 2018-10-17 13-38-40.png, Screenshot from 2018-10-17 13-38-52.png > > > List of available data types remain shown if no data type was selected and user clicks to the canvas. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3243) [DMN Designer] Move the Data Type dialog to a tab in the DMN editor

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3243?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3243: --------------------------------------- Story Points: 1 (was: 2) > [DMN Designer] Move the Data Type dialog to a tab in the DMN editor > ------------------------------------------------------------------- > > Key: DROOLS-3243 > URL: https://issues.jboss.org/browse/DROOLS-3243 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > https://issues.jboss.org/browse/DROOLS-3156 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3243) [DMN Designer] Move the Data Type dialog to a tab in the DMN editor

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3243?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3243: --------------------------------------- Story Points: 2 (was: 1) > [DMN Designer] Move the Data Type dialog to a tab in the DMN editor > ------------------------------------------------------------------- > > Key: DROOLS-3243 > URL: https://issues.jboss.org/browse/DROOLS-3243 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > https://issues.jboss.org/browse/DROOLS-3156 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2883) [DMN Designer] Add a Search bar in the Data Type dialog for search top level custom Data Types

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-2883?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-2883: --------------------------------------- Story Points: 3 (was: 2) > [DMN Designer] Add a Search bar in the Data Type dialog for search top level custom Data Types > ---------------------------------------------------------------------------------------------- > > Key: DROOLS-2883 > URL: https://issues.jboss.org/browse/DROOLS-2883 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.11.0.Final > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > h3. Acceptance test > - Find data type with > -- special characters > -- whitespaces > -- same text but different upper/lower case > - Search is cancelled by *escape* > - Search is confirmed by *enter* > - Navigate in results by *tab* -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3039) [DMN Designer] Item definition change doesn't make designer dirty

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3039?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3039: --------------------------------------- Sprint: 2018 Week 48-50 > [DMN Designer] Item definition change doesn't make designer dirty > ----------------------------------------------------------------- > > Key: DROOLS-3039 > URL: https://issues.jboss.org/browse/DROOLS-3039 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Minor > Labels: drools-tools > > Changes in item definition definitions don't make the designer dirty. User can then can easily overlook he should save changes before closing the designer. > h2. Acceptance test > Check editor is dirty: > - Definitions moved > - Definitions declared > - Definitions removed > - Definitions edited -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3039) [DMN Designer] Item definition change doesn't make designer dirty

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3039?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3039: --------------------------------------- Story Points: 3 > [DMN Designer] Item definition change doesn't make designer dirty > ----------------------------------------------------------------- > > Key: DROOLS-3039 > URL: https://issues.jboss.org/browse/DROOLS-3039 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Minor > Labels: drools-tools > > Changes in item definition definitions don't make the designer dirty. User can then can easily overlook he should save changes before closing the designer. > h2. Acceptance test > Check editor is dirty: > - Definitions moved > - Definitions declared > - Definitions removed > - Definitions edited -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5966) Validate requirement for modules previously exported by javax.ejb.api

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFLY-5966?page=com.atlassian.jira.plugin.... ] Yeray Borges updated WFLY-5966: ------------------------------- Description: The WFLY-5922 fix removed the exporting of a number of modules from javax.ejb.api. That introduced some problems with modules that depended on those exported packages no longer having visibility to needed classes, so to prevent problems I blindly added a commit to the module.xml for each module that depended upon javax.ejb.api to add a dependency set like this: {code}  <module name="javax.api"/> <module name="javax.transaction.api"/> <module name="javax.xml.rpc.api"/> <module name="javax.rmi.api"/> <module name="org.omg.api"/> {code} If a module already had a dep on one of those, it's not in the block. This task is to check each of these modules and replace that block with normal dependency declarations for any that are truly needed. Affected modules: feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/javax/management/j2ee/api/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/ejb3/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jsr77/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/webservices/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/weld/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/xts/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb-client/main/module.xml feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb3/main/module.xml feature-pack/src/main/resources/modules/system/layers/base/org/jboss/iiop-client/main/module.xml feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/appclient/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/ejb/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/compensations/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/rts/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/txframework/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/weld/core/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ws/common/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/xts/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/extension/rts/main/module.xml- The following modules were indirectly affected via their dependency on javaee.api, which in turn exports javax.ejb.api: feature-pack/src/main/resources/modules/system/layers/base/com/sun/jsf-impl/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/jberet/main/module.xml jsf/multi-jsf-installer/src/main/resources/mojarra-impl-module.xml jsf/multi-jsf-installer/src/main/resources/myfaces-impl-module.xml The following modules were fixed or verified as correct (moved from the first list): feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/main/module.xml feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/main/module.xml was: The WFLY-5922 fix removed the exporting of a number of modules from javax.ejb.api. That introduced some problems with modules that depended on those exported packages no longer having visibility to needed classes, so to prevent problems I blindly added a commit to the module.xml for each module that depended upon javax.ejb.api to add a dependency set like this: {code}  <module name="javax.api"/> <module name="javax.transaction.api"/> <module name="javax.xml.rpc.api"/> <module name="javax.rmi.api"/> <module name="org.omg.api"/> {code} If a module already had a dep on one of those, it's not in the block. This task is to check each of these modules and replace that block with normal dependency declarations for any that are truly needed. Affected modules: feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/javax/management/j2ee/api/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/ejb3/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jsr77/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/webservices/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/weld/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/xts/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb-client/main/module.xml feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb3/main/module.xml feature-pack/src/main/resources/modules/system/layers/base/org/jboss/iiop-client/main/module.xml feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/appclient/main/module.xml feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/ejb/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/compensations/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/rts/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/txframework/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/weld/core/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ws/common/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/xts/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/extension/rts/main/module.xml- The following modules were indirectly affected via their dependency on javaee.api, which in turn exports javax.ejb.api: feature-pack/src/main/resources/modules/system/layers/base/com/sun/jsf-impl/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/jberet/main/module.xml jsf/multi-jsf-installer/src/main/resources/mojarra-impl-module.xml jsf/multi-jsf-installer/src/main/resources/myfaces-impl-module.xml The following modules were fixed or verified as correct (moved from the first list): feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/main/module.xml feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/main/module.xml > Validate requirement for modules previously exported by javax.ejb.api > --------------------------------------------------------------------- > > Key: WFLY-5966 > URL: https://issues.jboss.org/browse/WFLY-5966 > Project: WildFly > Issue Type: Task > Components: Server > Reporter: Brian Stansberry > Assignee: Yeray Borges > Priority: Major > > The WFLY-5922 fix removed the exporting of a number of modules from javax.ejb.api. That introduced some problems with modules that depended on those exported packages no longer having visibility to needed classes, so to prevent problems I blindly added a commit to the module.xml for each module that depended upon javax.ejb.api to add a dependency set like this: > {code} >  > <module name="javax.api"/> > <module name="javax.transaction.api"/> > <module name="javax.xml.rpc.api"/> > <module name="javax.rmi.api"/> > <module name="org.omg.api"/> > {code} > If a module already had a dep on one of those, it's not in the block. > This task is to check each of these modules and replace that block with normal dependency declarations for any that are truly needed. > Affected modules: > feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml > -feature-pack/src/main/resources/modules/system/layers/base/javax/management/j2ee/api/main/module.xml- > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/ejb3/main/module.xml > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jsr77/main/module.xml- > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/webservices/main/module.xml > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/weld/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/xts/main/module.xml- > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb-client/main/module.xml > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb3/main/module.xml > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/iiop-client/main/module.xml > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/appclient/main/module.xml > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/ejb/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/compensations/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/rts/main/module.xml- > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/txframework/main/module.xml > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/weld/core/main/module.xml- > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ws/common/main/module.xml > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/xts/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/extension/rts/main/module.xml- > The following modules were indirectly affected via their dependency on javaee.api, which in turn exports javax.ejb.api: > feature-pack/src/main/resources/modules/system/layers/base/com/sun/jsf-impl/main/module.xml > -feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml- > feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/jberet/main/module.xml > jsf/multi-jsf-installer/src/main/resources/mojarra-impl-module.xml > jsf/multi-jsf-installer/src/main/resources/myfaces-impl-module.xml > The following modules were fixed or verified as correct (moved from the first list): > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/main/module.xml > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/main/module.xml -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3349) Make drools-integration to run on JDK11

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-3349?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-3349: -------------------------------- Story Points: 8 > Make drools-integration to run on JDK11 > --------------------------------------- > > Key: DROOLS-3349 > URL: https://issues.jboss.org/browse/DROOLS-3349 > Project: Drools > Issue Type: Task > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > -- 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 November 2018