November 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3412) elytron-tool.* scripts use SEP variable

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3412?page=com.atlassian.jira.plugi... ] Ilia Vassilev reassigned WFCORE-3412: ------------------------------------- Assignee: Ilia Vassilev > elytron-tool.* scripts use SEP variable > --------------------------------------- > > Key: WFCORE-3412 > URL: https://issues.jboss.org/browse/WFCORE-3412 > Project: WildFly Core > Issue Type: Bug > Reporter: Martin Choma > Assignee: Ilia Vassilev > > Customer impact low. Problem occures when environment defines SEP environment variable. If this happens user can unset variable locally or use elytron subsystem for managing credential stores (alternative to elytron-tool script) > SEP for variable name is too general. It can happen running environment uses it for other purpose. Rename variable SEP in elytron-tool.* scripts (bat,ps1,sh) using namespace to ELYTRON_TOOL_SEP, as there are already variables using this namespace; ELYTRON_TOOL_RUNJAR, ELYTRON_TOOL_ADDONS. > Variable SEP is not used in any other script. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-182) support for logging complete MDC map

by Jimmy Praet (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-182?page=com.atlassian.jira.plugin... ] Jimmy Praet updated LOGMGR-182: ------------------------------- Git Pull Request: https://github.com/jboss-logging/jboss-logmanager/pull/152 > support for logging complete MDC map > ------------------------------------ > > Key: LOGMGR-182 > URL: https://issues.jboss.org/browse/LOGMGR-182 > Project: JBoss Log Manager > Issue Type: Feature Request > Components: core > Reporter: Jimmy Praet > > {noformat} > It would be nice if the complete MDC map with all it's entries got logged if you use %X in your log pattern without specifying a key (e.g. %X{key1}). > Similar to logback: https://logback.qos.ch/manual/layouts.html#mdc > where it would be output as: > key1=val1, key2=val2 > Or log4j: https://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/EnhancedPat... > where it would be output as: > {{key1,val1},{key2,val2}} > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-182) support for logging complete MDC map

by Jimmy Praet (JIRA)

Jimmy Praet created LOGMGR-182: ---------------------------------- Summary: support for logging complete MDC map Key: LOGMGR-182 URL: https://issues.jboss.org/browse/LOGMGR-182 Project: JBoss Log Manager Issue Type: Feature Request Components: core Reporter: Jimmy Praet {noformat} It would be nice if the complete MDC map with all it's entries got logged if you use %X in your log pattern without specifying a key (e.g. %X{key1}). Similar to logback: https://logback.qos.ch/manual/layouts.html#mdc where it would be output as: key1=val1, key2=val2 Or log4j: https://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/EnhancedPat... where it would be output as: {{key1,val1},{key2,val2}} {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2122) Error when drl file is opened with in project with runtime classes

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2122?page=com.atlassian.jira.plugi... ] Kris Verlaenen reassigned DROOLS-2122: -------------------------------------- Assignee: Kris Verlaenen > Error when drl file is opened with in project with runtime classes > ------------------------------------------------------------------- > > Key: DROOLS-2122 > URL: https://issues.jboss.org/browse/DROOLS-2122 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Affects Versions: 7.3.0.Final > Environment: DevstudioIS 11.1.0.Beta1 > Brms 6.4.6.GA > Reporter: Tomas David > Assignee: Kris Verlaenen > Priority: Blocker > Fix For: 7.5.0.Final > > Attachments: Screenshot from 2017-11-09 09-55-05.png, devstudiolog.log > > > If new drools project is created with build using Java and Drools classes, error is displayed after drl file is opened. > This blocks also other functions like add a breakpoint or show content assist menu. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2122) Error when drl file is opened with in project with runtime classes

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2122?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2122: ----------------------------------- Fix Version/s: 7.5.0.Final > Error when drl file is opened with in project with runtime classes > ------------------------------------------------------------------- > > Key: DROOLS-2122 > URL: https://issues.jboss.org/browse/DROOLS-2122 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Affects Versions: 7.3.0.Final > Environment: DevstudioIS 11.1.0.Beta1 > Brms 6.4.6.GA > Reporter: Tomas David > Assignee: Kris Verlaenen > Priority: Blocker > Fix For: 7.5.0.Final > > Attachments: Screenshot from 2017-11-09 09-55-05.png, devstudiolog.log > > > If new drools project is created with build using Java and Drools classes, error is displayed after drl file is opened. > This blocks also other functions like add a breakpoint or show content assist menu. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3412) elytron-tool.* scripts use SEP variable

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3412?page=com.atlassian.jira.plugi... ] Martin Choma moved ELY-1441 to WFCORE-3412: ------------------------------------------- Project: WildFly Core (was: WildFly Elytron) Key: WFCORE-3412 (was: ELY-1441) > elytron-tool.* scripts use SEP variable > --------------------------------------- > > Key: WFCORE-3412 > URL: https://issues.jboss.org/browse/WFCORE-3412 > Project: WildFly Core > Issue Type: Bug > Reporter: Martin Choma > Assignee: Darran Lofthouse > > Customer impact low. Problem occures when environment defines SEP environment variable. If this happens user can unset variable locally or use elytron subsystem for managing credential stores (alternative to elytron-tool script) > SEP for variable name is too general. It can happen running environment uses it for other purpose. Rename variable SEP in elytron-tool.* scripts (bat,ps1,sh) using namespace to ELYTRON_TOOL_SEP, as there are already variables using this namespace; ELYTRON_TOOL_RUNJAR, ELYTRON_TOOL_ADDONS. > Variable SEP is not used in any other script. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3412) elytron-tool.* scripts use SEP variable

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3412?page=com.atlassian.jira.plugi... ] Martin Choma reassigned WFCORE-3412: ------------------------------------ Assignee: (was: Darran Lofthouse) > elytron-tool.* scripts use SEP variable > --------------------------------------- > > Key: WFCORE-3412 > URL: https://issues.jboss.org/browse/WFCORE-3412 > Project: WildFly Core > Issue Type: Bug > Reporter: Martin Choma > > Customer impact low. Problem occures when environment defines SEP environment variable. If this happens user can unset variable locally or use elytron subsystem for managing credential stores (alternative to elytron-tool script) > SEP for variable name is too general. It can happen running environment uses it for other purpose. Rename variable SEP in elytron-tool.* scripts (bat,ps1,sh) using namespace to ELYTRON_TOOL_SEP, as there are already variables using this namespace; ELYTRON_TOOL_RUNJAR, ELYTRON_TOOL_ADDONS. > Variable SEP is not used in any other script. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1441) elytron-tool.* scripts use SEP variable

by Martin Choma (JIRA)

Martin Choma created ELY-1441: --------------------------------- Summary: elytron-tool.* scripts use SEP variable Key: ELY-1441 URL: https://issues.jboss.org/browse/ELY-1441 Project: WildFly Elytron Issue Type: Bug Reporter: Martin Choma Assignee: Darran Lofthouse Customer impact low. Problem occures when environment defines SEP environment variable. If this happens user can unset variable locally or use elytron subsystem for managing credential stores (alternative to elytron-tool script) SEP for variable name is too general. It can happen running environment uses it for other purpose. Rename variable SEP in elytron-tool.* scripts (bat,ps1,sh) using namespace to ELYTRON_TOOL_SEP, as there are already variables using this namespace; ELYTRON_TOOL_RUNJAR, ELYTRON_TOOL_ADDONS. Variable SEP is not used in any other script. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2122) Error when drl file is opened with in project with runtime classes

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2122?page=com.atlassian.jira.plugi... ] Andrej Podhradsky updated DROOLS-2122: -------------------------------------- Workaround Description: # Create maven drools project before runtime project is created. # Or add Drools 7.x runtime and create one project with this 7.x version then also 6.x project wil work was:# Create maven drools project before runtime project is created. Workaround: Workaround Exists > Error when drl file is opened with in project with runtime classes > ------------------------------------------------------------------- > > Key: DROOLS-2122 > URL: https://issues.jboss.org/browse/DROOLS-2122 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Affects Versions: 7.3.0.Final > Environment: DevstudioIS 11.1.0.Beta1 > Brms 6.4.6.GA > Reporter: Tomas David > Priority: Blocker > Attachments: Screenshot from 2017-11-09 09-55-05.png, devstudiolog.log > > > If new drools project is created with build using Java and Drools classes, error is displayed after drl file is opened. > This blocks also other functions like add a breakpoint or show content assist menu. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2124) 6.5.x Decision table fails to handle predicate

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2124?page=com.atlassian.jira.plugi... ] Toni Rikkola commented on DROOLS-2124: -------------------------------------- [~mfusco] The only reason was that you were the default assignee. Not sure if DROOLS supports none. > 6.5.x Decision table fails to handle predicate > ---------------------------------------------- > > Key: DROOLS-2124 > URL: https://issues.jboss.org/browse/DROOLS-2124 > Project: Drools > Issue Type: Bug > Components: decision tables > Reporter: Toni Rikkola > Assignee: Mario Fusco > > Create a dtable. > Add Condition. > Create New fact pattern > Select Calculation type: Predicate > Add row ( if you did not already have one ) > Add something into the predicate field. I used "gggggg" > Open source tab > Try to open Editor tab > Can't go back to Editor tab. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 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 November 2017