October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11109) Fix PatterFormatter documentation for host name pattern

by James Perkins (Jira)

James Perkins created WFLY-11109: ------------------------------------ Summary: Fix PatterFormatter documentation for host name pattern Key: WFLY-11109 URL: https://issues.jboss.org/browse/WFLY-11109 Project: WildFly Issue Type: Task Components: Documentation Reporter: James Perkins Assignee: James Perkins Currently the short host name pattern, {{%h}}, is documented as allowing the a precision argument to be added. This should not be allowed and the short host should only be the first segment of the host. The qualified host name pattern, {{%H}}, indicates the precision is done left to right just like a log category or class name. However in general a host name is the opposite direction and thus should be segmented from right to left instead. For example given the host name {{developer.jboss.org}} and a pattern of {{%H\{1\}}}: {code:title=Current Output} org {code} {code:title=Expected Output} developer {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-206) Qualified host name should use right based precision instead of left

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-206?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-206: --------------------------------- Fix Version/s: 2.1.5.Final > Qualified host name should use right based precision instead of left > -------------------------------------------------------------------- > > Key: LOGMGR-206 > URL: https://issues.jboss.org/browse/LOGMGR-206 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Fix For: 2.1.5.Final > > > Currently if precision is used to remove segments from a qualified host name the names are removed from left to right as they are with the category or class name. However host names are generally reversed and should be truncated from right to left. For example given the host name {{logmanager.jboss.org}} and the pattern {{%H\{1\}}} the resulting host name should be {{logmanager}} not {{org}}. > This does in a sense break compatibility however it feels it was a bug that it even trimmed from the left. If desired there is a workaround too with a pattern like {{%.-3H}} if you wanted the {{org}} part of the host name. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-206) Qualified host name should use right based precision instead of left

by James Perkins (Jira)

James Perkins created LOGMGR-206: ------------------------------------ Summary: Qualified host name should use right based precision instead of left Key: LOGMGR-206 URL: https://issues.jboss.org/browse/LOGMGR-206 Project: JBoss Log Manager Issue Type: Bug Reporter: James Perkins Assignee: James Perkins Currently if precision is used to remove segments from a qualified host name the names are removed from left to right as they are with the category or class name. However host names are generally reversed and should be truncated from right to left. For example given the host name {{logmanager.jboss.org}} and the pattern {{%H\{1\}}} the resulting host name should be {{logmanager}} not {{org}}. This does in a sense break compatibility however it feels it was a bug that it even trimmed from the left. If desired there is a workaround too with a pattern like {{%.-3H}} if you wanted the {{org}} part of the host name. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4151) Upgrade jboss-logmanager from 2.1.4.Final to 2.1.5.Final

by James Perkins (Jira)

James Perkins created WFCORE-4151: ------------------------------------- Summary: Upgrade jboss-logmanager from 2.1.4.Final to 2.1.5.Final Key: WFCORE-4151 URL: https://issues.jboss.org/browse/WFCORE-4151 Project: WildFly Core Issue Type: Component Upgrade Components: Logging Reporter: James Perkins Assignee: James Perkins Upgrade {{org.jboss.logmanager:jboss-logmanager}} from 2.1.4.Final to 2.1.5.Final. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3000) Enhance data type restrictions UX in DT dialog

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3000?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3000: ------------------------------------- [~karreiro] I broke-apart this jira as we discussed, to move the Decision table work into another jira because of it's dependency with Michael's property panel jira. And I'll work on the other enumeration constraints. Have you had a chance to look at [~cristiano.nicolai]'s uberfire component? > Enhance data type restrictions UX in DT dialog > ---------------------------------------------- > > Key: DROOLS-3000 > URL: https://issues.jboss.org/browse/DROOLS-3000 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 AM.png, Screen Shot 2018-09-28 at 2.44.59 PM.png, date-time.png, date.png, enumration-widget.png, pop-overc.png, pop-overcSpecs.png, read-mode.png, select.png, time.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 dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E... > 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)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3077) Enhance data type restrictions UX - Decision Table/properties

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3077?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3077: -------------------------------- Sprint: 2018 Week 33-35, 2018 Week 42-44 (was: 2018 Week 33-35, 2018 Week 39-41) > Enhance data type restrictions UX - Decision Table/properties > ------------------------------------------------------------- > > Key: DROOLS-3077 > URL: https://issues.jboss.org/browse/DROOLS-3077 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 AM.png, Screen Shot 2018-09-28 at 2.44.59 PM.png, date-time.png, date.png, enumration-widget.png, pop-overc.png, pop-overcSpecs.png, read-mode.png, select.png, time.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 dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E... > 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)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3077) Enhance data type restrictions UX - Decision Table/properties

by Liz Clayton (Jira)

Liz Clayton created DROOLS-3077: ----------------------------------- Summary: Enhance data type restrictions UX - Decision Table/properties Key: DROOLS-3077 URL: https://issues.jboss.org/browse/DROOLS-3077 Project: Drools Issue Type: Story Components: DMN Editor Reporter: Liz Clayton Assignee: Liz Clayton Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 AM.png, Screen Shot 2018-09-28 at 2.44.59 PM.png, date-time.png, date.png, enumration-widget.png, pop-overc.png, pop-overcSpecs.png, read-mode.png, select.png, time.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 dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E... 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)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3000) Enhance data type restrictions UX in DT dialog

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3000?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3000: -------------------------------- Story Points: 3 (was: 5) > Enhance data type restrictions UX in DT dialog > ---------------------------------------------- > > Key: DROOLS-3000 > URL: https://issues.jboss.org/browse/DROOLS-3000 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 AM.png, Screen Shot 2018-09-28 at 2.44.59 PM.png, date-time.png, date.png, enumration-widget.png, pop-overc.png, pop-overcSpecs.png, read-mode.png, select.png, time.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 dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E... > 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)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3000) Enhance data type restrictions UX in DT dialog

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3000?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3000: -------------------------------- Summary: Enhance data type restrictions UX in DT dialog (was: Enhance data type restrictions UX (decision tables & DT dialog)) > Enhance data type restrictions UX in DT dialog > ---------------------------------------------- > > Key: DROOLS-3000 > URL: https://issues.jboss.org/browse/DROOLS-3000 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 AM.png, Screen Shot 2018-09-28 at 2.44.59 PM.png, date-time.png, date.png, enumration-widget.png, pop-overc.png, pop-overcSpecs.png, read-mode.png, select.png, time.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 dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E... > 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)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4150) Support automatically adding / updating credentials in the CredentialStore

by Darran Lofthouse (Jira)

Darran Lofthouse created WFCORE-4150: ---------------------------------------- Summary: Support automatically adding / updating credentials in the CredentialStore Key: WFCORE-4150 URL: https://issues.jboss.org/browse/WFCORE-4150 Project: WildFly Core Issue Type: Feature Request Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2018