August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4432) DMN data type editor enhancements based on usability findings

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4432?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4432: -------------------------------------- Attachment: (was: Screen Shot 2019-08-23 at 3.24.20 PM.png) > DMN data type editor enhancements based on usability findings > ------------------------------------------------------------- > > Key: DROOLS-4432 > URL: https://issues.jboss.org/browse/DROOLS-4432 > Project: Drools > Issue Type: Task > Components: DMN Editor > Environment: Version 7.4 > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, Usability, drools-tools > Attachments: Screen Shot 2019-08-23 at 3.28.48 PM.png > > > Description: > Outline findings related to a followup usability study. The study tests redesign proposals and prototypes documented at: https://issues.jboss.org/browse/DROOLS-4372. Focus on findings particularly as they relate to resolving any issues in the current proposal. > Verification conditions > * Google document with high-level findings and summary of possible design enhancements. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4432) DMN data type editor enhancements based on usability findings

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4432?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4432: -------------------------------------- Attachment: Screen Shot 2019-08-23 at 3.28.48 PM.png > DMN data type editor enhancements based on usability findings > ------------------------------------------------------------- > > Key: DROOLS-4432 > URL: https://issues.jboss.org/browse/DROOLS-4432 > Project: Drools > Issue Type: Task > Components: DMN Editor > Environment: Version 7.4 > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, Usability, drools-tools > Attachments: Screen Shot 2019-08-23 at 3.28.48 PM.png > > > Description: > Outline findings related to a followup usability study. The study tests redesign proposals and prototypes documented at: https://issues.jboss.org/browse/DROOLS-4372. Focus on findings particularly as they relate to resolving any issues in the current proposal. > Verification conditions > * Google document with high-level findings and summary of possible design enhancements. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4432) DMN data type editor enhancements based on usability findings

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4432?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4432: -------------------------------------- Attachment: Screen Shot 2019-08-23 at 3.24.20 PM.png > DMN data type editor enhancements based on usability findings > ------------------------------------------------------------- > > Key: DROOLS-4432 > URL: https://issues.jboss.org/browse/DROOLS-4432 > Project: Drools > Issue Type: Task > Components: DMN Editor > Environment: Version 7.4 > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, Usability, drools-tools > Attachments: Screen Shot 2019-08-23 at 3.24.20 PM.png > > > Description: > Outline findings related to a followup usability study. The study tests redesign proposals and prototypes documented at: https://issues.jboss.org/browse/DROOLS-4372. Focus on findings particularly as they relate to resolving any issues in the current proposal. > Verification conditions > * Google document with high-level findings and summary of possible design enhancements. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4432) DMN data type editor enhancements based on usability findings

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4432?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4432: -------------------------------------- Attachment: (was: Screen Shot 2019-08-23 at 12.55.21 PM.png) > DMN data type editor enhancements based on usability findings > ------------------------------------------------------------- > > Key: DROOLS-4432 > URL: https://issues.jboss.org/browse/DROOLS-4432 > Project: Drools > Issue Type: Task > Components: DMN Editor > Environment: Version 7.4 > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, Usability, drools-tools > > Description: > Outline findings related to a followup usability study. The study tests redesign proposals and prototypes documented at: https://issues.jboss.org/browse/DROOLS-4372. Focus on findings particularly as they relate to resolving any issues in the current proposal. > Verification conditions > * Google document with high-level findings and summary of possible design enhancements. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12418) Move to jakarta.security.enterprise:jakarta.security.enterprise-api and org.glassfish.soteria:jakarta.security.enterprise

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12418?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12418: ----------------------------------------- [~dvilkola] [~dlofthouse] Please make any related changes to the boms are completed. > Move to jakarta.security.enterprise:jakarta.security.enterprise-api and org.glassfish.soteria:jakarta.security.enterprise > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12418 > URL: https://issues.jboss.org/browse/WFLY-12418 > Project: WildFly > Issue Type: Sub-task > Components: EE, Security > Reporter: Diana Vilkolakova > Assignee: Diana Vilkolakova > Priority: Major > > This is simple component upgrade to jakarta since we will not be forking EE security for now. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12426) Move to Jakarta approved version of jakarta.security.enterprise:jakarta.security.enterprise-api

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12426?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12426: ------------------------------------ Priority: Blocker (was: Major) > Move to Jakarta approved version of jakarta.security.enterprise:jakarta.security.enterprise-api > ----------------------------------------------------------------------------------------------- > > Key: WFLY-12426 > URL: https://issues.jboss.org/browse/WFLY-12426 > Project: WildFly > Issue Type: Sub-task > Components: Security > Reporter: Brian Stansberry > Assignee: Darran Lofthouse > Priority: Blocker > > WFLY-12418 moves us to jakarta.security.enterprise:jakarta.security.enterprise-api but the version has not been approved by Jakarta as the official release for use in Jakarta EE 8. It's fine to do that upgrade; this issue is just to make sure we move to the approved version if it is different. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12426) Move to Jakarta approved version of jakarta.security.enterprise:jakarta.security.enterprise-api

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-12426: --------------------------------------- Summary: Move to Jakarta approved version of jakarta.security.enterprise:jakarta.security.enterprise-api Key: WFLY-12426 URL: https://issues.jboss.org/browse/WFLY-12426 Project: WildFly Issue Type: Sub-task Components: Security Reporter: Brian Stansberry Assignee: Darran Lofthouse WFLY-12418 moves us to jakarta.security.enterprise:jakarta.security.enterprise-api but the version has not been approved by Jakarta as the official release for use in Jakarta EE 8. It's fine to do that upgrade; this issue is just to make sure we move to the approved version if it is different. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4621) Create a service to install a dynamic 'wildflyee.api' module

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4621?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-4621: ------------------------------------------ [~jamezp] [~yersan] fyi > Create a service to install a dynamic 'wildflyee.api' module > ------------------------------------------------------------ > > Key: WFCORE-4621 > URL: https://issues.jboss.org/browse/WFCORE-4621 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Reporter: Brian Stansberry > Priority: Minor > > Follow up on WFCORE-4612 by removing the list of detailed optional dependencies added there and instead have a service that installs a dynamic 'wildflyee.api' module that optional depends on all those. Then ExternalModuleDependencySpecService would add a dependency on that 'wildflyee.api' module. > Then the next step is the javaee.api module in full WildFly would become an alias to wildflyee.api. > The benefit to this is the content set for this 'ee.api' convenience module > a) gets set in one place (vs the two places that WFCORE-4612 introduces) > b) is defined in core, which makes some sense as core utilizes the module for the ExternalModuleDependencySpecService use case. > c) External uses of 'javaee.api' can benefit from the WFCORE-4612 improvement; i.e. if they have slimmed the server such that some APIs are not present, javaee.api can still be used. They just can't be using any APIs that they slimmed away. > A downside is maintaining an 'ee.api' modules is not a great fit for core. > The reason to use a dynamic module is a static module would be visible to Galleon, and with the standard passive+[1] provisioning scheme we use that would lead to Galleon provisioning the packages for all the EE APIs, regardless of whether the server config required them. > [1] https://docs.wildfly.org/galleon/#_effective_package_set > This is somewhat me brainstorming, so needs harder thought. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4621) Create a service to install a dynamic 'wildflyee.api' module

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4621: ---------------------------------------- Summary: Create a service to install a dynamic 'wildflyee.api' module Key: WFCORE-4621 URL: https://issues.jboss.org/browse/WFCORE-4621 Project: WildFly Core Issue Type: Enhancement Components: Server Reporter: Brian Stansberry Assignee: Jeff Mesnil Follow up on WFCORE-4612 by removing the list of detailed optional dependencies added there and instead have a service that installs a dynamic 'wildflyee.api' module that optional depends on all those. Then ExternalModuleDependencySpecService would add a dependency on that 'wildflyee.api' module. Then the next step is the javaee.api module in full WildFly would become an alias to wildflyee.api. The benefit to this is the content set for this 'ee.api' convenience module a) gets set in one place (vs the two places that WFCORE-4612 introduces) b) is defined in core, which makes some sense as core utilizes the module for the ExternalModuleDependencySpecService use case. c) External uses of 'javaee.api' can benefit from the WFCORE-4612 improvement; i.e. if they have slimmed the server such that some APIs are not present, javaee.api can still be used. They just can't be using any APIs that they slimmed away. A downside is maintaining an 'ee.api' modules is not a great fit for core. The reason to use a dynamic module is a static module would be visible to Galleon, and with the standard passive+[1] provisioning scheme we use that would lead to Galleon provisioning the packages for all the EE APIs, regardless of whether the server config required them. [1] https://docs.wildfly.org/galleon/#_effective_package_set This is somewhat me brainstorming, so needs harder thought. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4621) Create a service to install a dynamic 'wildflyee.api' module

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4621?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-4621: ---------------------------------------- Assignee: (was: Jeff Mesnil) > Create a service to install a dynamic 'wildflyee.api' module > ------------------------------------------------------------ > > Key: WFCORE-4621 > URL: https://issues.jboss.org/browse/WFCORE-4621 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Reporter: Brian Stansberry > Priority: Minor > > Follow up on WFCORE-4612 by removing the list of detailed optional dependencies added there and instead have a service that installs a dynamic 'wildflyee.api' module that optional depends on all those. Then ExternalModuleDependencySpecService would add a dependency on that 'wildflyee.api' module. > Then the next step is the javaee.api module in full WildFly would become an alias to wildflyee.api. > The benefit to this is the content set for this 'ee.api' convenience module > a) gets set in one place (vs the two places that WFCORE-4612 introduces) > b) is defined in core, which makes some sense as core utilizes the module for the ExternalModuleDependencySpecService use case. > c) External uses of 'javaee.api' can benefit from the WFCORE-4612 improvement; i.e. if they have slimmed the server such that some APIs are not present, javaee.api can still be used. They just can't be using any APIs that they slimmed away. > A downside is maintaining an 'ee.api' modules is not a great fit for core. > The reason to use a dynamic module is a static module would be visible to Galleon, and with the standard passive+[1] provisioning scheme we use that would lead to Galleon provisioning the packages for all the EE APIs, regardless of whether the server config required them. > [1] https://docs.wildfly.org/galleon/#_effective_package_set > This is somewhat me brainstorming, so needs harder thought. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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 August 2019