January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3452) Data type constraints: Date/Time

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3452?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3452: -------------------------------- Attachment: (was: range.png) > Data type constraints: Date/Time > -------------------------------- > > Key: DROOLS-3452 > URL: https://issues.jboss.org/browse/DROOLS-3452 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: range.png > > > Background > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.) > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3452) Data type constraints: Date/Time

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3452?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3452: -------------------------------- Attachment: range.png > Data type constraints: Date/Time > -------------------------------- > > Key: DROOLS-3452 > URL: https://issues.jboss.org/browse/DROOLS-3452 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: range.png > > > Background > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.) > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3452) Data type constraints: Date/Time

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3452?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3452: -------------------------------- Attachment: (was: range.png) > Data type constraints: Date/Time > -------------------------------- > > Key: DROOLS-3452 > URL: https://issues.jboss.org/browse/DROOLS-3452 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > > Background > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.) > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11234) Since WildFly 14 i18n ResourceBundle properties file not found if without locale

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11234?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-11234: ----------------------------------------- I reconfirmed that the WFLY-11202 problem is indeed fixed in 15.0.1. The deployment attached to that one deploys. I also tweaked the test app there to prove that the message is indeed resolved correctly, i.e. not just that it doesn't fail. Works. So there must be something different about your use case. > Since WildFly 14 i18n ResourceBundle properties file not found if without locale > -------------------------------------------------------------------------------- > > Key: WFLY-11234 > URL: https://issues.jboss.org/browse/WFLY-11234 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 14.0.1.Final > Environment: Ubuntu 18.04, OpenJDK 8 and 11 > Reporter: Anton Pussep > Assignee: Farah Juma > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > As discussed in this thread > https://developer.jboss.org/message/985930 > my i18n properties have not been resolved on WildFly 14.0.1.Final - it was working fine through WildFly 10-13, however. I could solve the issue by renaming my properties file from messages.properties to messages_en.properties. Since this solved the issue, I suspect that WildFly 14 does not accept filenames without locale anymore. Since I'm not sure if this is by design, I'm posting this as a bug report here. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11234) Since WildFly 14 i18n ResourceBundle properties file not found if without locale

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11234?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-11234: --------------------------------------- Component/s: JSF Assignee: Farah Juma (was: Brian Stansberry) Can you attach a reproducer app? Perhaps there is something different about your use case from WFLY-11202. > Since WildFly 14 i18n ResourceBundle properties file not found if without locale > -------------------------------------------------------------------------------- > > Key: WFLY-11234 > URL: https://issues.jboss.org/browse/WFLY-11234 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 14.0.1.Final > Environment: Ubuntu 18.04, OpenJDK 8 and 11 > Reporter: Anton Pussep > Assignee: Farah Juma > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > As discussed in this thread > https://developer.jboss.org/message/985930 > my i18n properties have not been resolved on WildFly 14.0.1.Final - it was working fine through WildFly 10-13, however. I could solve the issue by renaming my properties file from messages.properties to messages_en.properties. Since this solved the issue, I suspect that WildFly 14 does not accept filenames without locale anymore. Since I'm not sure if this is by design, I'm posting this as a bug report here. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-1743) Release WildFly Elytron 1.8.0.CR1

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1743?page=com.atlassian.jira.plugin.s... ] Farah Juma resolved ELY-1743. ----------------------------- Resolution: Done > Release WildFly Elytron 1.8.0.CR1 > --------------------------------- > > Key: ELY-1743 > URL: https://issues.jboss.org/browse/ELY-1743 > Project: WildFly Elytron > Issue Type: Release > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.8.0.CR1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-1743) Release WildFly Elytron 1.8.0.CR1

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1743?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1743: ---------------------------- Fix Version/s: 1.8.0.CR1 > Release WildFly Elytron 1.8.0.CR1 > --------------------------------- > > Key: ELY-1743 > URL: https://issues.jboss.org/browse/ELY-1743 > Project: WildFly Elytron > Issue Type: Release > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.8.0.CR1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4237) Update KeyStoresTestCase and CertificateAuthoritiesTestCase now that AcmeClientSpi has been updated to use POST-as-GET requests

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFCORE-4237?page=com.atlassian.jira.plugi... ] Farah Juma updated WFCORE-4237: ------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/3605, https://github.com/wildfly/wildfly-core/pull/3646 (was: https://github.com/wildfly/wildfly-core/pull/3605) > Update KeyStoresTestCase and CertificateAuthoritiesTestCase now that AcmeClientSpi has been updated to use POST-as-GET requests > ------------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-4237 > URL: https://issues.jboss.org/browse/WFCORE-4237 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > > Update {{KeyStoresTestCase}} and {{CertificateAuthoritiesTestCase}} now that {{AcmeClientSpi}} has been updated to use POST-as-GET requests (see ELY-1693). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-533) Deprecate all legacy code

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-533?page=com.atlassian.jira.plugin.sy... ] Farah Juma updated ELY-533: --------------------------- Fix Version/s: 1.8.0.CR2 (was: 1.8.0.CR1) > Deprecate all legacy code > ------------------------- > > Key: ELY-533 > URL: https://issues.jboss.org/browse/ELY-533 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.8.0.CR2 > > > In a few places we have legacy behaviour within the project to assist migration from previous JBoss / WildFly releases - this code should be flagged as deprecated to encourage minimal use. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-243) Ensure reference to repository is removed from pom

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-243?page=com.atlassian.jira.plugin.sy... ] Farah Juma updated ELY-243: --------------------------- Fix Version/s: 1.8.0.CR2 (was: 1.8.0.CR1) > Ensure reference to repository is removed from pom > -------------------------------------------------- > > Key: ELY-243 > URL: https://issues.jboss.org/browse/ELY-243 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Priority: Major > Fix For: 1.8.0.CR2 > > > We need to ensure the reference to the JBoss repo is removed from the pom and artefacts are available from Maven Central. > Also at this point probably good to put the steps in place for Elytron to also be available from Maven Central. -- This message was sent by Atlassian Jira (v7.12.1#712002)

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