November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3226) [DMN Designer] Function Header Cell in BKM

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3226?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3226: -------------------------------- Description: Function header cell can be selected, but user can't set its properties in PropertiesPanel if the Function is the top level Expression of the BKM node. See below comparision of Function as the top level Expression. Once in decision node, then in BKM node. h3. Decision node !Screenshot from 2018-11-01 13-25-03.png|thumbnail! h3. BKM node !Screenshot from 2018-11-01 13-25-21.png|thumbnail! was: Function header cell can be selected, but user can't set its properties in PropertiesPanel if the Function is the top level Expression of the BKM node. See below comparision of Function as the top level Expression. Once in decision node, then in BKM node. h3. Decision node !Screenshot from 2018-11-01 13-25-03.png|thumbnail! h3. BKM node !Screenshot from 2018-11-01 13-25-03.png|thumbnail! > [DMN Designer] Function Header Cell in BKM > ------------------------------------------ > > Key: DROOLS-3226 > URL: https://issues.jboss.org/browse/DROOLS-3226 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2018-11-01 13-25-03.png, Screenshot from 2018-11-01 13-25-21.png > > > Function header cell can be selected, but user can't set its properties in PropertiesPanel if the Function is the top level Expression of the BKM node. See below comparision of Function as the top level Expression. Once in decision node, then in BKM node. > h3. Decision node > !Screenshot from 2018-11-01 13-25-03.png|thumbnail! > h3. BKM node > !Screenshot from 2018-11-01 13-25-21.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-477) REST Tests failed in Istio 1.0.3

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-477?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-477: --------------------------------------------- Team: Infrastructure (was: Infrastructure) Assignee: Matt Mahoney (was: Guilherme Baufaker Rêgo) > REST Tests failed in Istio 1.0.3 > -------------------------------- > > Key: SWSQE-477 > URL: https://issues.jboss.org/browse/SWSQE-477 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Matt Mahoney > Priority: Major > > Started happening after B12 installed with Istio 1.0.3. > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/run-kiali-e2e-te... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-126) MP metrics not enabled for HA profiles

by Rostislav Svoboda (Jira)

Rostislav Svoboda created WFWIP-126: --------------------------------------- Summary: MP metrics not enabled for HA profiles Key: WFWIP-126 URL: https://issues.jboss.org/browse/WFWIP-126 Project: WildFly WIP Issue Type: Bug Components: MP Metrics Reporter: Rostislav Svoboda Assignee: Jeff Mesnil MP Metrics not enabled for HA profiles {code} grep 'org.wildfly.extension.microprofile.metrics-smallrye' dist/target/wildfly-15.0.0.Alpha1-SNAPSHOT/standalone/configuration/*.xml {code} MP Metrics enabled in: * standalone-full.xml * standalone.xml MP Metrics NOT enabled in: * standalone-ha.xml * standalone-full-ha.xml -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-126) MP metrics not enabled for HA profiles

by Rostislav Svoboda (Jira)

[ https://issues.jboss.org/browse/WFWIP-126?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda updated WFWIP-126: ------------------------------------ Priority: Blocker (was: Major) > MP metrics not enabled for HA profiles > -------------------------------------- > > Key: WFWIP-126 > URL: https://issues.jboss.org/browse/WFWIP-126 > Project: WildFly WIP > Issue Type: Bug > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Blocker > > MP Metrics not enabled for HA profiles > {code} > grep 'org.wildfly.extension.microprofile.metrics-smallrye' dist/target/wildfly-15.0.0.Alpha1-SNAPSHOT/standalone/configuration/*.xml > {code} > MP Metrics enabled in: > * standalone-full.xml > * standalone.xml > MP Metrics NOT enabled in: > * standalone-ha.xml > * standalone-full-ha.xml -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-891) jboss-deployment-structure.xml resource root allows references outside the deployment

by Jiri Ondrusek (Jira)

[ https://issues.jboss.org/browse/WFCORE-891?page=com.atlassian.jira.plugin... ] Jiri Ondrusek reassigned WFCORE-891: ------------------------------------ Assignee: Jiri Ondrusek (was: JBoss SET) > jboss-deployment-structure.xml resource root allows references outside the deployment > ------------------------------------------------------------------------------------- > > Key: WFCORE-891 > URL: https://issues.jboss.org/browse/WFCORE-891 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Enrique González Martínez > Assignee: Jiri Ondrusek > Priority: Major > > The current code allows making references outside the deployment. This leads to misuse during deployment if users try to share the same library (outside the archive). > See WFCORE-700 > Add a validation for resource-root. It must not allow references outside the deployment. > https://github.com/wildfly/wildfly-core/blob/2.0.0.Beta2/server/src/main/... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2890) [DMN Designer] DMNDiagram properties

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-2890?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2890: -------------------------------- Description: The {{DMNDiagram}} node needs to expose the following properties (from [~tirelli] on DROOLS-[2870|https://issues.jboss.org/browse/DROOLS-2870?focusedCommentId...) {quote} The Definitions properties that I think we need to expose are: * Id (probably read only) * name (needs to be editable; can default to the file name but should remain editable) * namespace * Also, the "description" element should probably be exposed somehow, although with lower priority. If you want just the minimal set, then the above. {quote} h2. Manual acceptance test - B&D new model, non default namespace (/) - Import model with namespace (/) - Import model without namespace (/) was: The {{DMNDiagram}} node needs to expose the following properties (from [~tirelli] on DROOLS-[2870|https://issues.jboss.org/browse/DROOLS-2870?focusedCommentId...) {quote} The Definitions properties that I think we need to expose are: * Id (probably read only) * name (needs to be editable; can default to the file name but should remain editable) * namespace * Also, the "description" element should probably be exposed somehow, although with lower priority. If you want just the minimal set, then the above. {quote} h2. Manual acceptance test - B&D new model, non default namespace - Import model with namespace (/) - Import model without namespace (/) > [DMN Designer] DMNDiagram properties > ------------------------------------ > > Key: DROOLS-2890 > URL: https://issues.jboss.org/browse/DROOLS-2890 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > Fix For: 7.10.0.Final > > > The {{DMNDiagram}} node needs to expose the following properties (from [~tirelli] on DROOLS-[2870|https://issues.jboss.org/browse/DROOLS-2870?focusedCommentId...) > {quote} > The Definitions properties that I think we need to expose are: > * Id (probably read only) > * name (needs to be editable; can default to the file name but should remain editable) > * namespace > * Also, the "description" element should probably be exposed somehow, although with lower priority. If you want just the minimal set, then the above. > {quote} > h2. Manual acceptance test > - B&D new model, non default namespace (/) > - Import model with namespace (/) > - Import model without namespace (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2890) [DMN Designer] DMNDiagram properties

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-2890?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2890: -------------------------------- Description: The {{DMNDiagram}} node needs to expose the following properties (from [~tirelli] on DROOLS-[2870|https://issues.jboss.org/browse/DROOLS-2870?focusedCommentId...) {quote} The Definitions properties that I think we need to expose are: * Id (probably read only) * name (needs to be editable; can default to the file name but should remain editable) * namespace * Also, the "description" element should probably be exposed somehow, although with lower priority. If you want just the minimal set, then the above. {quote} h2. Manual acceptance test - B&D new model, non default namespace - Import model with namespace (/) - Import model without namespace (/) was: The {{DMNDiagram}} node needs to expose the following properties (from [~tirelli] on DROOLS-[2870|https://issues.jboss.org/browse/DROOLS-2870?focusedCommentId...) {quote} The Definitions properties that I think we need to expose are: * Id (probably read only) * name (needs to be editable; can default to the file name but should remain editable) * namespace * Also, the "description" element should probably be exposed somehow, although with lower priority. If you want just the minimal set, then the above. {quote} h2. Manual acceptance test - B&D new model, non default namespace - Import model with namespace - Import model without namespace > [DMN Designer] DMNDiagram properties > ------------------------------------ > > Key: DROOLS-2890 > URL: https://issues.jboss.org/browse/DROOLS-2890 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > Fix For: 7.10.0.Final > > > The {{DMNDiagram}} node needs to expose the following properties (from [~tirelli] on DROOLS-[2870|https://issues.jboss.org/browse/DROOLS-2870?focusedCommentId...) > {quote} > The Definitions properties that I think we need to expose are: > * Id (probably read only) > * name (needs to be editable; can default to the file name but should remain editable) > * namespace > * Also, the "description" element should probably be exposed somehow, although with lower priority. If you want just the minimal set, then the above. > {quote} > h2. Manual acceptance test > - B&D new model, non default namespace > - Import model with namespace (/) > - Import model without namespace (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11266) JAXWS Client BOM

by Eduardo Martins (Jira)

Eduardo Martins created WFLY-11266: -------------------------------------- Summary: JAXWS Client BOM Key: WFLY-11266 URL: https://issues.jboss.org/browse/WFLY-11266 Project: WildFly Issue Type: Enhancement Components: Quickstarts Reporter: Eduardo Martins Assignee: Eduardo Martins The dependency management defined on WildFly, for JAXWS/CXF client, is over 1000 SLoC due to exclusions applied, which is a nightmare to manage on client apps projects, such as the jaxws-* quickstarts. To hide the dependency management complexity on apps a new client BOM should be added wrt JAXWS, which apps can just depend on it, and should includes all dependencies excluded on WildFly dependency management. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4194) Eliminate ServiceBuilder's addDependencies() usages

by Richard Opalka (Jira)

Richard Opalka created WFCORE-4194: -------------------------------------- Summary: Eliminate ServiceBuilder's addDependencies() usages Key: WFCORE-4194 URL: https://issues.jboss.org/browse/WFCORE-4194 Project: WildFly Core Issue Type: Sub-task Components: Security, Server Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 7.0.0.Alpha5 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3220) [DMN Designer] [Edge] Unable to edit context cell

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3220?page=com.atlassian.jira.plugi... ] Michael Anstis reassigned DROOLS-3220: -------------------------------------- Assignee: Daniel José dos Santos (was: Michael Anstis) > [DMN Designer] [Edge] Unable to edit context cell > ------------------------------------------------- > > Key: DROOLS-3220 > URL: https://issues.jboss.org/browse/DROOLS-3220 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Environment: Windows, Edge browser > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Blocker > Labels: drools-tools > > User is unable to invoke edit mode for context cells. Other expression types seems to work fine. > Spotted during DROOLS-3214 review, however don't think it is related. > h2. Acceptance test > Invoke edit mode of regular cell > - Literal > - Dec. Table > - Function > - Relation > - Invocation > - Context > Invoke edit mode of header cell - where applicable > - Literal > - Dec. Table > - Function > - Relation > - Invocation > - Context -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 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