October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11106) Kabir Test(For demo)

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFLY-11106?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFLY-11106: ------------------------------ Component/s: Management > Kabir Test(For demo) > -------------------- > > Key: WFLY-11106 > URL: https://issues.jboss.org/browse/WFLY-11106 > Project: WildFly > Issue Type: Feature Request > Components: Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Priority: Major > > An issue for me to move around the board to test the tooling. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11106) Kabir Test(For demo)

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFLY-11106?page=com.atlassian.jira.plugin... ] Kabir Khan moved EAP7-1125 to WFLY-11106: ----------------------------------------- Project: WildFly (was: EAP 7 Planning Pilot) Key: WFLY-11106 (was: EAP7-1125) Issue Type: Feature Request (was: Requirement) Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0) Jirban PT Pre-Checked (PC): (was: TODO) Jirban PT Community Docs (CD): (was: TODO) Jirban PT Test Dev (TD): (was: TODO) > Kabir Test(For demo) > -------------------- > > Key: WFLY-11106 > URL: https://issues.jboss.org/browse/WFLY-11106 > Project: WildFly > Issue Type: Feature Request > Reporter: Kabir Khan > Assignee: Kabir Khan > Priority: Major > > An issue for me to move around the board to test the tooling. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11105) Upgrade WildFly Core 7.0.0.Alpha2

by Jeff Mesnil (Jira)

Jeff Mesnil created WFLY-11105: ---------------------------------- Summary: Upgrade WildFly Core 7.0.0.Alpha2 Key: WFLY-11105 URL: https://issues.jboss.org/browse/WFLY-11105 Project: WildFly Issue Type: Component Upgrade Components: Management Reporter: Jeff Mesnil Assignee: Jeff Mesnil -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4146) Check if we can remove .setXmlName in JaspiDefinitions

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4146?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4146: -------------------------------- Fix Version/s: 7.0.0.Alpha3 (was: 7.0.0.Alpha2) > Check if we can remove .setXmlName in JaspiDefinitions > ------------------------------------------------------ > > Key: WFCORE-4146 > URL: https://issues.jboss.org/browse/WFCORE-4146 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 7.0.0.Alpha3 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4144) Add support for registering a single JVM / Server wide default SSLContext

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4144?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4144: -------------------------------- Fix Version/s: 7.0.0.Alpha3 (was: 7.0.0.Alpha2) > Add support for registering a single JVM / Server wide default SSLContext > ------------------------------------------------------------------------- > > Key: WFCORE-4144 > URL: https://issues.jboss.org/browse/WFCORE-4144 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 7.0.0.Alpha3 > > > By registering a global SSLContext libraries used within the application server can make use of a managed SSLContext instead of relying on one automatically being created through the standard system properties. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3952) Unable to run -DallTests -Delytron builds

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-3952?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3952: -------------------------------- Fix Version/s: 7.0.0.Alpha3 (was: 7.0.0.Alpha2) > Unable to run -DallTests -Delytron builds > ----------------------------------------- > > Key: WFCORE-3952 > URL: https://issues.jboss.org/browse/WFCORE-3952 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 7.0.0.Alpha3 > > > Attempting to use -DallTests -Delytron results in the following error: - > {noformat} > [ERROR] } > [ERROR] Cannot start embedded Host Controller: WFLYEMB0022: Cannot invoke 'start' on embedded process: WFLYHC0097: Domain base directory does not exist: /home/darranl/src/wildfly13/wildfly-core/testsuite/standalone/target/wildfly-core/domain > {noformat} > I believe this is actually caused by WFCORE-3769 which provisions a standalone server only. > We don't currently run -Delytron jobs for WildFly Core but this bug causes problems with experimental builds where we may want to use -Delytron. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4148) Check and consider to put escaped quotes (\") back to the -Xloggc in standalone.sh

by Radovan Stancel (Jira)

[ https://issues.jboss.org/browse/WFCORE-4148?page=com.atlassian.jira.plugi... ] Radovan Stancel reassigned WFCORE-4148: --------------------------------------- Assignee: Radovan Stancel (was: James Perkins) > Check and consider to put escaped quotes (\") back to the -Xloggc in standalone.sh > ---------------------------------------------------------------------------------- > > Key: WFCORE-4148 > URL: https://issues.jboss.org/browse/WFCORE-4148 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Marek Kopecký > Assignee: Radovan Stancel > Priority: Major > > Check and consider to put escaped quotes (\") back to the -Xloggc in standalone.sh > See the discussion [here|https://github.com/wildfly/wildfly-core/pull/3496#discussion_r221509989] -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3022) [DMN Designer] Data Types - Validations - Validate the uniqueness and the presence of a Data Type name

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3022?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3022: -------------------------------- Description: The Data Type name must be unique at the level that it's defined; e.g. - tPerson -- uuid -- name -- city (Structure) --- uuid --- name The Data Type above is valid, because _tPerson.uuid_ and _tPerson.city.uuid_ are in different levels. ---- Prototype: !validation.png|thumbnail! h2. Manaul Acceptance Test - Try to put same name by Typing (/) - Try to put same name by Copy and paste (/) - Do not allow empty name (/) - Allow spaces in name (/) - Allow multibyte chars in name (/) - Allow special characters in name (/) - Allow lower upper case in name (/) - Save when error shown (x) - Cancel edit when error shown (x) - Invoke other edit when error shown (x) was: The Data Type name must be unique at the level that it's defined; e.g. - tPerson -- uuid -- name -- city (Structure) --- uuid --- name The Data Type above is valid, because _tPerson.uuid_ and _tPerson.city.uuid_ are in different levels. ---- Prototype: !validation.png|thumbnail! h2. Manaul Acceptance Test - Try to put same name by Typing - Try to put same name by Copy and paste - Do not allow empty name - Allow spaces in name - Allow multibyte chars in name - Allow special characters in name (?) - Allow lower upper case in name - Save when error shown (x) - Cancel edit when error shown (x) - Invoke other edit when error shown > [DMN Designer] Data Types - Validations - Validate the uniqueness and the presence of a Data Type name > ------------------------------------------------------------------------------------------------------ > > Key: DROOLS-3022 > URL: https://issues.jboss.org/browse/DROOLS-3022 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > Attachments: validation.png > > > The Data Type name must be unique at the level that it's defined; e.g. > - tPerson > -- uuid > -- name > -- city (Structure) > --- uuid > --- name > The Data Type above is valid, because _tPerson.uuid_ and _tPerson.city.uuid_ are in different levels. > ---- > Prototype: > !validation.png|thumbnail! > h2. Manaul Acceptance Test > - Try to put same name by Typing (/) > - Try to put same name by Copy and paste (/) > - Do not allow empty name (/) > - Allow spaces in name (/) > - Allow multibyte chars in name (/) > - Allow special characters in name (/) > - Allow lower upper case in name (/) > - Save when error shown (x) > - Cancel edit when error shown (x) > - Invoke other edit when error shown (x) -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3022) [DMN Designer] Data Types - Validations - Validate the uniqueness and the presence of a Data Type name

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3022?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3022: -------------------------------- Description: The Data Type name must be unique at the level that it's defined; e.g. - tPerson -- uuid -- name -- city (Structure) --- uuid --- name The Data Type above is valid, because _tPerson.uuid_ and _tPerson.city.uuid_ are in different levels. ---- Prototype: !validation.png|thumbnail! h2. Manaul Acceptance Test - Try to put same name by Typing - Try to put same name by Copy and paste - Do not allow empty name - Allow spaces in name - Allow multibyte chars in name - Allow special characters in name (?) - Allow lower upper case in name - Save when error shown (x) - Cancel edit when error shown (x) - Invoke other edit when error shown was: The Data Type name must be unique at the level that it's defined; e.g. - tPerson -- uuid -- name -- city (Structure) --- uuid --- name The Data Type above is valid, because _tPerson.uuid_ and _tPerson.city.uuid_ are in different levels. ---- Prototype: !validation.png|thumbnail! h2. Manaul Acceptance Test - Try to put same name by Typing - Try to put same name by Copy and paste - Do not allow empty name - Allow spaces in name - Allow multibyte chars in name - Allow special characters in name (?) - Allow lower upper case in name - Save when error shown - Cancel edit when error shown (x) - Invoke other edit when error shown > [DMN Designer] Data Types - Validations - Validate the uniqueness and the presence of a Data Type name > ------------------------------------------------------------------------------------------------------ > > Key: DROOLS-3022 > URL: https://issues.jboss.org/browse/DROOLS-3022 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > Attachments: validation.png > > > The Data Type name must be unique at the level that it's defined; e.g. > - tPerson > -- uuid > -- name > -- city (Structure) > --- uuid > --- name > The Data Type above is valid, because _tPerson.uuid_ and _tPerson.city.uuid_ are in different levels. > ---- > Prototype: > !validation.png|thumbnail! > h2. Manaul Acceptance Test > - Try to put same name by Typing > - Try to put same name by Copy and paste > - Do not allow empty name > - Allow spaces in name > - Allow multibyte chars in name > - Allow special characters in name (?) > - Allow lower upper case in name > - Save when error shown (x) > - Cancel edit when error shown (x) > - Invoke other edit when error shown -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3053) Warning popup of column type change in Scenario grid

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3053?page=com.atlassian.jira.plugi... ] Gabriele Cardosi updated DROOLS-3053: ------------------------------------- Description: Implement a warning popup when the user changes the type of a column that has been already populated. To be done/merged *after* DROOLS-3051. *Acceptance criteria* - If the column contains no value, no confirmation is needed - If old and new types are the same the user has to decide if the values should be removed or not - If old and new types are not the same the user has to accept that old values will be removed - All warning popups should contains also a "Cancel" command to abort the edit - If the user try to update the column type with the same column type no warning should be raised and data should stay untouched was: Implement a warning popup when the user changes the type of a column that has been already populated. To be done/merged *after* DROOLS-3051, because in that PR there will be implemented the "empty cell" semantic. *Acceptance criteria* - If the column contains no value, no confirmation is needed - If old and new types are the same the user has to decide if the values should be removed or not - If old and new types are not the same the user has to accept that old values will be removed - All warning popups should contains also a "Cancel" command to abort the edit - If the user try to update the column type with the same column type no warning should be raised and data should stay untouched > Warning popup of column type change in Scenario grid > ---------------------------------------------------- > > Key: DROOLS-3053 > URL: https://issues.jboss.org/browse/DROOLS-3053 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Minor > Labels: UX, UXTeam > > Implement a warning popup when the user changes the type of a column that has been already populated. > To be done/merged *after* DROOLS-3051. > *Acceptance criteria* > - If the column contains no value, no confirmation is needed > - If old and new types are the same the user has to decide if the values should be removed or not > - If old and new types are not the same the user has to accept that old values will be removed > - All warning popups should contains also a "Cancel" command to abort the edit > - If the user try to update the column type with the same column type no warning should be raised and data should stay untouched -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2018