June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBFORUMS-109) BBCode support for standalone version

by Ryszard Kozmik (JIRA)

BBCode support for standalone version ------------------------------------- Key: JBFORUMS-109 URL: http://jira.jboss.com/jira/browse/JBFORUMS-109 Project: JBoss Forums Issue Type: Task Components: Forum Enhancements Reporter: Ryszard Kozmik Fix For: 1.0.0 Alpha BBCode parser is now working only in portal environment. We need make it work as a standalone too. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

4 days, 21 hours

3
3
0 / 0

[JBoss JIRA] (DROOLS-3330) DMN Properties panel - Style menu

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3330?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3330: -------------------------------- Description: Request to combine the three current style related menus (Background details, Font settings, Dimensions) into a single menu. Rationale: * As the context of these items is very different from the other properties, it might be beneficial to the user to group them together thereby distinguishing them from the rest. * The extra menu headers required for these additional menus takes up valuable screen real estate, that could otherwise be used by higher priority properties. * If the user does want to use the style settings, we're creating additional work to make them both scroll down and open the additional related menus. was: Creating this jira to investigate if it would be possible to combine the three current style related menus (Background details, Font settings, Dimensions) into a single menu. Rationale: * As the context of these items is very different from the other properties, it might be beneficial to the user to group them together thereby distinguishing them from the rest. * The extra menu headers required for these additional menus takes up valuable screen real estate, that could otherwise be used by higher priority properties. * If the user does want to use the style settings, we're creating additional work to make them both scroll down and open the additional related menus. > DMN Properties panel - Style menu > --------------------------------- > > Key: DROOLS-3330 > URL: https://issues.jboss.org/browse/DROOLS-3330 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Michael Anstis > Priority: Optional > Labels: UX, UXTeam, drools-tools > Attachments: styles.png > > > Request to combine the three current style related menus (Background details, Font settings, Dimensions) into a single menu. > Rationale: > * As the context of these items is very different from the other properties, it might be beneficial to the user to group them together thereby distinguishing them from the rest. > * The extra menu headers required for these additional menus takes up valuable screen real estate, that could otherwise be used by higher priority properties. > * If the user does want to use the style settings, we're creating additional work to make them both scroll down and open the additional related menus. -- This message was sent by Atlassian Jira (v7.12.1#712002)

1 week

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-457) Optimization: make threads return immediately if NAKACK has another active thread for the same sender

by Bela Ban (JIRA)

Optimization: make threads return immediately if NAKACK has another active thread for the same sender ----------------------------------------------------------------------------------------------------- Key: JGRP-457 URL: http://jira.jboss.com/jira/browse/JGRP-457 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.5 In NAKACK, when a thread places a message for sender S into the NakReceiverWindow NRW, it subsequently acquires a lock on NRW (lock by sender) and removes as many messages as possible and passes them up. If many threads do this at the same time, all threads but one are blocked, and - when finally unblocked - usually return. This causes context switches and possibly cache flushing, so a better way would be to have the threads check whether another thread is already removing messages using a CAS operation *before* acquiring the lock. The effect should be that no threads will wait on the lock unnecessarily, and thus fewer context switches, and more threads available to the pool. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 month, 1 week

2
3
0 / 0

[JBoss JIRA] (WFLY-10796) Warning about JSF version 'NONE' is shown in logs

by Jan Kašík (JIRA)

[ https://issues.jboss.org/browse/WFLY-10796?page=com.atlassian.jira.plugin... ] Jan Kašík updated WFLY-10796: ----------------------------- Description: Following warning is shown in log upon server start: {code} 2018-08-02 16:13:28,487 WARN [org.jboss.as.jsf] (MSC service thread 1-3) WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be used instead. {code} Seems like, that 'NONE' constant from WildFly code is somehow used instead of default 'main' value. Version 'NONE' is not specified anywhere, so this warning should not be present. From my point of view, it seems like I am trying set slot 'NONE' to be the default. But nothing like that is happening. was: Following warning is shown in log upon server start: {code} 2018-08-02 16:13:28,487 WARN [org.jboss.as.jsf] (MSC service thread 1-3) WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be used instead. {code} Seems like, that 'NONE' constant from WildFly code is somehow used instead of default 'main' value. Version 'NONE' is not specified anywhere, so this warning should not be present. > Warning about JSF version 'NONE' is shown in logs > -------------------------------------------------- > > Key: WFLY-10796 > URL: https://issues.jboss.org/browse/WFLY-10796 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 14.0.0.Beta2 > Reporter: Jan Kašík > Assignee: Dmitrii Tikhomirov > > Following warning is shown in log upon server start: > {code} > 2018-08-02 16:13:28,487 WARN [org.jboss.as.jsf] (MSC service thread 1-3) WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be used instead. > {code} > Seems like, that 'NONE' constant from WildFly code is somehow used instead of default 'main' value. Version 'NONE' is not specified anywhere, so this warning should not be present. From my point of view, it seems like I am trying set slot 'NONE' to be the default. But nothing like that is happening. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

2 months

2
1
0 / 0

[JBoss JIRA] (ELY-776) Eliminate reference to "slot" from module configurations

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-776?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reassigned ELY-776: ------------------------------------ Assignee: Darran Lofthouse > Eliminate reference to "slot" from module configurations > -------------------------------------------------------- > > Key: ELY-776 > URL: https://issues.jboss.org/browse/ELY-776 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: David Lloyd > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta15 > > > The final version of our client XSD should accept a name for modules but no slot. Instead, either the new name-only APIs should be used or a ModuleIdentifier created via that class's "fromString" method. Module slots are deprecated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

2 months

2
1
0 / 0

[JBoss JIRA] (JBRULES-3445) DSL expander expands lines in /* */comment block

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3445: ------------------------------------ Summary: DSL expander expands lines in /* */comment block Key: JBRULES-3445 URL: https://issues.jboss.org/browse/JBRULES-3445 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco When you comment some code in dslr file, the expander still tries to expand it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

7 months

3
10
0 / 0

[JBoss JIRA] (DROOLS-3944) DMN Editor: Data type usability study

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3944?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-3944: -------------------------------------- Sprint: 2019 Week 23-25 > DMN Editor: Data type usability study > ------------------------------------- > > Key: DROOLS-3944 > URL: https://issues.jboss.org/browse/DROOLS-3944 > Project: Drools > Issue Type: Task > Components: DMN Editor > Environment: Version 7.4 > Reporter: Elizabeth Clayton > Assignee: Sarahjane Clark > Priority: Major > Labels: UX, UXTeam, Usability, drools-tools > > Lightweight usability study to test the ease of use in viewing, creating, editing and deleting data types, particularly structured data types. > GOALS: Access the Data Type editor in terms of productivity and usability. > * Ease of use when creating a complex type (concern: minimizing the mouse usage.) > * Ease of use when saving a basic data type (e.g. age: number) > * Discoverability of actions in the kebab menu, especially, insert nested, delete. > * Ease of use/accuracy: Type-ahead of the data type selector. -- This message was sent by Atlassian Jira (v7.12.1#712002)

1 year, 3 months

2
1
0 / 0

[JBoss JIRA] (WFLY-12262) Tasks-rf quickstart has no pre-requisite of tasks quickstart

by Eduardo Martins (Jira)

Eduardo Martins created WFLY-12262: -------------------------------------- Summary: Tasks-rf quickstart has no pre-requisite of tasks quickstart Key: WFLY-12262 URL: https://issues.jboss.org/browse/WFLY-12262 Project: WildFly Issue Type: Bug Components: Quickstarts Affects Versions: 17.0.0.Final Reporter: Eduardo Martins Assignee: Eduardo Martins The README.adoc of tasks-rf quickstart refers tasks QuickStart as pre-requisite, this is outdated and should be fixed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12261) Incorrect ImageandTemplateImportURL in CD QS

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-12261?page=com.atlassian.jira.plugin... ] Eduardo Martins moved JBEAP-17122 to WFLY-12261: ------------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-12261 (was: JBEAP-17122) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Documentation Quickstarts (was: Documentation) (was: Quickstarts) Affects Version/s: 17.0.0.Final (was: 7.3.0.CD16) > Incorrect ImageandTemplateImportURL in CD QS > -------------------------------------------- > > Key: WFLY-12261 > URL: https://issues.jboss.org/browse/WFLY-12261 > Project: WildFly > Issue Type: Bug > Components: Documentation, Quickstarts > Affects Versions: 17.0.0.Final > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Critical > Labels: Doc_prio_2 > > The readmes in CD16 QS use this incorrect imange and template import url: > [https://raw.githubusercontent.com/jboss-container-images/jboss-eap-7-open...] > Defined at: > https://github.com/wildfly/quickstart/blob/master/shared-doc/attributes.a... > Which resolves to: > https://raw.githubusercontent.com/jboss-container-images/jboss-eap-7-open... > There's no CD7.3 tag or branch in the repo: > https://github.com/jboss-container-images/jboss-eap-7-openshift-image > It should probably be CD16. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12260) Deploy to openshift command cannot be copied from the readme because of redundant characters

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-12260?page=com.atlassian.jira.plugin... ] Eduardo Martins moved JBEAP-17121 to WFLY-12260: ------------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-12260 (was: JBEAP-17121) Issue Type: Enhancement (was: Bug) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Quickstarts (was: Quickstarts) Affects Version/s: 17.0.0.Final (was: 7.3.0.CD16) > Deploy to openshift command cannot be copied from the readme because of redundant characters > -------------------------------------------------------------------------------------------- > > Key: WFLY-12260 > URL: https://issues.jboss.org/browse/WFLY-12260 > Project: WildFly > Issue Type: Enhancement > Components: Quickstarts > Affects Versions: 17.0.0.Final > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Minor > > The {{Deploy the JBoss EAP Source-to-Image (S2I) Quickstart to OpenShift}} section of readme for CD QS contains this command: > {code} > oc new-app --template=eap-cd-basic-s2i \(1) > -p IMAGE_STREAM_NAMESPACE="helloworld-project" \(2) > -p SOURCE_REPOSITORY_URL="https://github.com/jboss-developer/jboss-eap-quickstarts" \(3) > -p SOURCE_REPOSITORY_REF="openshift" \(4) > -p CONTEXT_DIR="helloworld"(5) > {code} > It cannot be copied and pasted in a single step because of the references at the end of each line - (1)..(5). It would be nice if the command didn't contain the redundant characters. > For example, the notes below the command could be updated in following way without the need for the references (1)...(5) in the command itself: > {code} > --template - The template to use. > -p IMAGE_STREAM_NAMESPACE - The latest images streams and templates were imported into the project's namespace, so you must specify the namespace of where to find the image stream. This is usually the OpenShift project's name. > -p SOURCE_REPOSITORY_URL - URL to the repository containing the application source code. > -p SOURCE_REPOSITORY_REF - The Git repository reference to use for the source code. This can be a Git branch or tag reference. > -p CONTEXT_DIR - The directory within the source repository to build. > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

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