September 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBMETA-412) Update schemas to use JavaEE 8 schemas

by ehsavoie Hugonnet (JIRA)

ehsavoie Hugonnet created JBMETA-412: ---------------------------------------- Summary: Update schemas to use JavaEE 8 schemas Key: JBMETA-412 URL: https://issues.jboss.org/browse/JBMETA-412 Project: JBoss Metadata Issue Type: Bug Components: client, common, ear, web Affects Versions: 10.0.2.Final Reporter: ehsavoie Hugonnet Assignee: ehsavoie Hugonnet Schemas are using JavaEE 7 schemas and not JavaEE8. Update schemas to the new JavaEE version. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-438) Bookinfo "Error: ImagePullBackOff"

by Matt Mahoney (JIRA)

Matt Mahoney created SWSQE-438: ---------------------------------- Summary: Bookinfo "Error: ImagePullBackOff" Key: SWSQE-438 URL: https://issues.jboss.org/browse/SWSQE-438 Project: Kiali QE Issue Type: Bug Reporter: Matt Mahoney Assignee: Michael Foley Encountering failures with Bookinfo images ""Error: ImagePullBackOff"" ratings-v1 reviews-v3 This happens when deploying with Maistra Minimal deployer, as well as w/ Bookinfo Jenkins job. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10339) Broadcast/discovery-group resources have ambiguous requirement specs

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-10339?page=com.atlassian.jira.plugin... ] Paul Ferraro commented on WFLY-10339: ------------------------------------- Not sure how I missed this: {quote}CCing ehsavoie Hugonnet who is taking over the messaging subsystem.{quote} Reassigning to [~ehugonnet] (with his consent, of course...) > Broadcast/discovery-group resources have ambiguous requirement specs > -------------------------------------------------------------------- > > Key: WFLY-10339 > URL: https://issues.jboss.org/browse/WFLY-10339 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 12.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > Currently, the broadcast/discovery-group resources have messy requirement specs, as the capabilities that they require are dependent whether or not the jgroups-cluster attribute is defined. > I suggest splitting these resources into 2: > {code}/subsystem=messaging-activemq/server=*/jgroups-broadcast-group=*{code} > {code}/subsystem=messaging-activemq/server=*/jgroups-discovery-group=*{code} > which requires clustering capabilities > and > {code}/subsystem=messaging-activemq/server=*/socket-broadcast-group=*{code} > {code}/subsystem=messaging-activemq/server=*/socket-discovery-group=*{code} > which requires a socket-binding capability. > This results in clearer requirement specs - which helps simplify the introspection of this subsystem for provisioning purposes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10339) Broadcast/discovery-group resources have ambiguous requirement specs

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-10339?page=com.atlassian.jira.plugin... ] Paul Ferraro reassigned WFLY-10339: ----------------------------------- Assignee: ehsavoie Hugonnet (was: Paul Ferraro) > Broadcast/discovery-group resources have ambiguous requirement specs > -------------------------------------------------------------------- > > Key: WFLY-10339 > URL: https://issues.jboss.org/browse/WFLY-10339 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 12.0.0.Final > Reporter: Paul Ferraro > Assignee: ehsavoie Hugonnet > > Currently, the broadcast/discovery-group resources have messy requirement specs, as the capabilities that they require are dependent whether or not the jgroups-cluster attribute is defined. > I suggest splitting these resources into 2: > {code}/subsystem=messaging-activemq/server=*/jgroups-broadcast-group=*{code} > {code}/subsystem=messaging-activemq/server=*/jgroups-discovery-group=*{code} > which requires clustering capabilities > and > {code}/subsystem=messaging-activemq/server=*/socket-broadcast-group=*{code} > {code}/subsystem=messaging-activemq/server=*/socket-discovery-group=*{code} > which requires a socket-binding capability. > This results in clearer requirement specs - which helps simplify the introspection of this subsystem for provisioning purposes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11069) test Hibernate51CompatibilityTransformer transformations for o.h.type.Type and o.h.type.AbstractStandardBasicType

by Martin Simka (JIRA)

Martin Simka created WFLY-11069: ----------------------------------- Summary: test Hibernate51CompatibilityTransformer transformations for o.h.type.Type and o.h.type.AbstractStandardBasicType Key: WFLY-11069 URL: https://issues.jboss.org/browse/WFLY-11069 Project: WildFly Issue Type: Enhancement Components: JPA / Hibernate, Test Suite Reporter: Martin Simka Assignee: Martin Simka There are missing tests for two Hibernate51CompatibilityTransformer transformations: * [org.hibernate.type.AbstractStandardBasicType|https://github.com/wildfly/w...] * [org.hibernate.type.Type|https://github.com/wildfly/wildfly/blob/master/jp...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10339) Broadcast/discovery-group resources have ambiguous requirement specs

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFLY-10339?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet commented on WFLY-10339: ------------------------------------------ Please don't forget that we have now discovery groups out of the broker so it would be 6 discovery group resources :) > Broadcast/discovery-group resources have ambiguous requirement specs > -------------------------------------------------------------------- > > Key: WFLY-10339 > URL: https://issues.jboss.org/browse/WFLY-10339 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 12.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > Currently, the broadcast/discovery-group resources have messy requirement specs, as the capabilities that they require are dependent whether or not the jgroups-cluster attribute is defined. > I suggest splitting these resources into 2: > {code}/subsystem=messaging-activemq/server=*/jgroups-broadcast-group=*{code} > {code}/subsystem=messaging-activemq/server=*/jgroups-discovery-group=*{code} > which requires clustering capabilities > and > {code}/subsystem=messaging-activemq/server=*/socket-broadcast-group=*{code} > {code}/subsystem=messaging-activemq/server=*/socket-discovery-group=*{code} > which requires a socket-binding capability. > This results in clearer requirement specs - which helps simplify the introspection of this subsystem for provisioning purposes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2804) [DMN Designer] Properties Panel to drill-down to DMN component level

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2804?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2804: ---------------------------------------- [~jomarko] I've not forgotten your request.. when I look at this JIRA is more detail I'll fill in the gaps. > [DMN Designer] Properties Panel to drill-down to DMN component level > -------------------------------------------------------------------- > > Key: DROOLS-2804 > URL: https://issues.jboss.org/browse/DROOLS-2804 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > > The Properties Panel currently shows properties for Stunner-level "graph" components. > We need, for DMN, the Properties Panel to show the properties of DMN elements' properties at the "grid" level. For example, when a {{Context}} is selected the Properties Panel should show only the top level properties for the {{Context}} (i.e. not those of its {{ContextEntries}}). Selection of a {{ContextEntry}} should refresh the Properties Panel to show only the top-level properties of the {{ContextEntry}}. Selection of the {{ContextEntry}}'s {{Expression}} should again refresh the Properties Panel to show only the top-level properties of the {{Expression}} and so forth. > h2. Properties on the Grid Level > The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel. > h3. Literal expression > ||Selected item||Properties panel items|| > |Cell|(?)| > h3. Context > ||Selected item||Properties panel items|| > |Row|(?)| > |Column|(?)| > |Cell|(?)| > h3. Decision Table > ||Selected item||Properties panel items|| > |Row|(?)| > |Column|(?)| > |Cell|(?)| > h3. Relation > ||Selected item||Properties panel items|| > |Row|(?)| > |Column|(?)| > |Cell|(?)| > h3. Function > ||Selected item||Properties panel items|| > |Row|(?)| > |Column|(?)| > |Cell|(?)| > h3. Invocation > ||Selected item||Properties panel items|| > |Row|(?)| > |Column|(?)| > |Cell|(?)| > h2. Manual Acceptance Test > - Switching between DRG and Grid editor, check proper fields shown > - Switching between rows, columns, cells in Grid editor, check proper fields > -- In same expression kind > -- Across different expression kinds > - Clear expression kind > - Read only mode - older asset version > - All Grid specific properties saved -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2911) Update Scenario Simulation command to use the new module

by Klara Kufova (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2911?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-2911: --------------------------------- Story Points: 8 (was: 5) > Update Scenario Simulation command to use the new module > -------------------------------------------------------- > > Key: DROOLS-2911 > URL: https://issues.jboss.org/browse/DROOLS-2911 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > > Use new kie-wb-common-command-api for Scenario Simulation commands -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2899) Implement infinite grid scrolling in Scenario Simulation Grid

by Klara Kufova (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2899?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-2899: --------------------------------- Story Points: 5 > Implement infinite grid scrolling in Scenario Simulation Grid > ------------------------------------------------------------- > > Key: DROOLS-2899 > URL: https://issues.jboss.org/browse/DROOLS-2899 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > > Implement infinite canvas scrolling for the Grid using the same/a similar approach of DMN Decision Table -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2899) Implement infinite grid scrolling in Scenario Simulation Grid

by Klara Kufova (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2899?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-2899: --------------------------------- Sprint: 2018 Week 39-41 > Implement infinite grid scrolling in Scenario Simulation Grid > ------------------------------------------------------------- > > Key: DROOLS-2899 > URL: https://issues.jboss.org/browse/DROOLS-2899 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > > Implement infinite canvas scrolling for the Grid using the same/a similar approach of DMN Decision Table -- This message was sent by Atlassian JIRA (v7.5.0#75005)

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 September 2018