October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4522) Add an "expression" property for every complex type in Scenario Testing

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4522?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-4522: ---------------------------------- Fix Version/s: (was: 7.6.0.Final) > Add an "expression" property for every complex type in Scenario Testing > ----------------------------------------------------------------------- > > Key: DROOLS-4522 > URL: https://issues.jboss.org/browse/DROOLS-4522 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Attachments: can-be-suspended-expression.webm > > > Basically, with the changes introduced in this PR, every complex type object in Scenario has an additional property ("expression") where it will be possible to add expression logic to the referred object (fact). At the moment, the changes involve only front-end side. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12615) Upgrade jboss-ejb-client to 4.0.24.Final

by Ivo Studensky (Jira)

[ https://issues.jboss.org/browse/WFLY-12615?page=com.atlassian.jira.plugin... ] Ivo Studensky updated WFLY-12615: --------------------------------- Labels: downstream_dependency (was: ) > Upgrade jboss-ejb-client to 4.0.24.Final > ---------------------------------------- > > Key: WFLY-12615 > URL: https://issues.jboss.org/browse/WFLY-12615 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12615) Upgrade jboss-ejb-client to 4.0.24.Final

by Ivo Studensky (Jira)

[ https://issues.jboss.org/browse/WFLY-12615?page=com.atlassian.jira.plugin... ] Ivo Studensky moved JBEAP-17677 to WFLY-12615: ---------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-12615 (was: JBEAP-17677) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Build System (was: Build System) Affects Version/s: (was: 7.2.0.GA) Fix Version/s: (was: 7.2.5.GA) > Upgrade jboss-ejb-client to 4.0.24.Final > ---------------------------------------- > > Key: WFLY-12615 > URL: https://issues.jboss.org/browse/WFLY-12615 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4574) Scenario test: UX to add an expression-based value.

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4574?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-4574: --------------------------------------- [~uxdlc] Yes you are right. What do you mean with "more explicit"? > Scenario test: UX to add an expression-based value. > ---------------------------------------------------- > > Key: DROOLS-4574 > URL: https://issues.jboss.org/browse/DROOLS-4574 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam > > As a technical/advanced user (Cameron), I want to be able to input expression-based values in scenario given/expect row cells, so that I can define inputs for complex objects and logic. > Note: Syntax highlighting and etc., are out of scope. Refer to: https://issues.jboss.org/browse/DROOLS-3514 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-216) Providing own ./configuration/settings.xml to S2I build doesn't work with galleon image

by Jean Francois Denise (Jira)

[ https://issues.jboss.org/browse/WFWIP-216?page=com.atlassian.jira.plugin.... ] Jean Francois Denise reassigned WFWIP-216: ------------------------------------------ Assignee: Jean Francois Denise (was: Brian Stansberry) > Providing own ./configuration/settings.xml to S2I build doesn't work with galleon image > --------------------------------------------------------------------------------------- > > Key: WFWIP-216 > URL: https://issues.jboss.org/browse/WFWIP-216 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Jan Blizňák > Assignee: Jean Francois Denise > Priority: Blocker > Attachments: sti-custom-settings-galleon-image.log, sti-custom-settings-standard-cd-image.log > > > According to https://access.redhat.com/documentation/en-us/red_hat_jboss_middleware_fo... the user is able to provide its own settings.xml located in <app_dir>/configuration/settings.xml - this settings file then should be used for mvn build. > This clearly conflicts with galleon settings.xml. However, this is broken backward compatibility and should be somehow addressed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-217) Customizing settings.xml via ENV variables doesn't work on galleon image

by Jean Francois Denise (Jira)

[ https://issues.jboss.org/browse/WFWIP-217?page=com.atlassian.jira.plugin.... ] Jean Francois Denise reassigned WFWIP-217: ------------------------------------------ Assignee: Jean Francois Denise (was: Brian Stansberry) > Customizing settings.xml via ENV variables doesn't work on galleon image > ------------------------------------------------------------------------ > > Key: WFWIP-217 > URL: https://issues.jboss.org/browse/WFWIP-217 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Jan Blizňák > Assignee: Jean Francois Denise > Priority: Blocker > > With released images it is possible to configure settings.xml used for S2I build via ENV variables, eg: https://github.com/jboss-openshift/cct_module/blob/1ff1d96/jboss/containe... > If I understood correctly this was introduced/changed by CLOUD-2911. But with galleon hooked into S2I the settings.xml is replaced with the one needed for slim server so this mechanism no longer works. > This is a backward compatibility issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4691) Upgrade XNIO to 3.7.4.Final

by Ivo Studensky (Jira)

[ https://issues.jboss.org/browse/WFCORE-4691?page=com.atlassian.jira.plugi... ] Ivo Studensky updated WFCORE-4691: ---------------------------------- Labels: downstream_dependency (was: ) > Upgrade XNIO to 3.7.4.Final > --------------------------- > > Key: WFCORE-4691 > URL: https://issues.jboss.org/browse/WFCORE-4691 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Build System > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4691) Upgrade XNIO to 3.7.4.Final

by Ivo Studensky (Jira)

[ https://issues.jboss.org/browse/WFCORE-4691?page=com.atlassian.jira.plugi... ] Ivo Studensky updated WFCORE-4691: ---------------------------------- Description: (was: Tag: Hash: Diff: https://github.com/xnio/xnio/compare/3.7.3.Final...3.7) > Upgrade XNIO to 3.7.4.Final > --------------------------- > > Key: WFCORE-4691 > URL: https://issues.jboss.org/browse/WFCORE-4691 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Build System > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4691) Upgrade XNIO to 3.7.4.Final

by Ivo Studensky (Jira)

[ https://issues.jboss.org/browse/WFCORE-4691?page=com.atlassian.jira.plugi... ] Ivo Studensky moved JBEAP-17676 to WFCORE-4691: ----------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-4691 (was: JBEAP-17676) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Build System (was: Build System) Fix Version/s: (was: 7.2.5.GA) > Upgrade XNIO to 3.7.4.Final > --------------------------- > > Key: WFCORE-4691 > URL: https://issues.jboss.org/browse/WFCORE-4691 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Build System > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Priority: Major > > Tag: > Hash: > Diff: https://github.com/xnio/xnio/compare/3.7.3.Final...3.7 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-215) Operator headless service labeled with wildfly.org/operated-by-loadbalancer=active

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/WFWIP-215?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka commented on WFWIP-215: ---------------------------------------- [~mchoma] thank you for pointing that out. This error happened because of the code refactoring which occured last week. The fix is part of the PR https://github.com/wildfly/wildfly-operator/pull/90 > Operator headless service labeled with wildfly.org/operated-by-loadbalancer=active > ---------------------------------------------------------------------------------- > > Key: WFWIP-215 > URL: https://issues.jboss.org/browse/WFWIP-215 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Ondrej Chaloupka > Priority: Blocker > > # create the WildflyServer CR > {code:yaml} > apiVersion: wildfly.org/v1alpha1 > kind: WildFlyServer > metadata: > name: eap-cd > namespace: mchoma > spec: > applicationImage: >- > image-registry.openshift-image-registry.svc:5000/eapcd-suite-builds/eap-cd-openshift-rhel8:17.0-4 > env: [] > envFrom: [] > size: 1 > {code} > # Both services {{eap-cd-headless}} and {{eap-cd-loadbalancer}} created by Operator have same labels. We used to select service based on label wildfly.org/operated-by-loadbalancer. > {code} > eap-cd-headless > app.kubernetes.io/managed-by=eap-operator > app.kubernetes.io/name=eap-cd > app.openshift.io/runtime=eap > wildfly.org/operated-by-loadbalancer=active > eap-cd-loadbalancer > app.kubernetes.io/managed-by=eap-operator > app.kubernetes.io/name=eap-cd > app.openshift.io/runtime=eap > wildfly.org/operated-by-loadbalancer=active > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2019