March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-486) cli echo command should not output the result in columns

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/WFCORE-486?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-486: ------------------------------------------------ Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1173615|https://bugzilla.redhat.com/show_bug.cgi?id=1173615] from NEW to CLOSED > cli echo command should not output the result in columns > -------------------------------------------------------- > > Key: WFCORE-486 > URL: https://issues.jboss.org/browse/WFCORE-486 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > Priority: Major > Fix For: 1.0.0.Alpha15 > > > Current implementation of echo command displays the results in columns. Originally its arguments where limited to variables only. Now it also accepts arbitrary text mixed with expressions. So, the logical and expected output would be now the string with the expressions resolved. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-437) Add config option to fail deployment if private API is used

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/WFCORE-437?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-437: ------------------------------------------------ Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1018260|https://bugzilla.redhat.com/show_bug.cgi?id=1018260] from NEW to CLOSED > Add config option to fail deployment if private API is used > ----------------------------------------------------------- > > Key: WFCORE-437 > URL: https://issues.jboss.org/browse/WFCORE-437 > Project: WildFly Core > Issue Type: Feature Request > Components: Management > Reporter: Pete Muir > Priority: Major > > This would allow users to have continuous integration jobs check if their app uses a private API by mistake, and have the job fail if it does. > Needed to automate the check that quickstarts only use public API. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4235) JDR capture OS version

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/WFLY-4235?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4235: ----------------------------------------------- Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1195516|https://bugzilla.redhat.com/show_bug.cgi?id=1195516] from NEW to CLOSED > JDR capture OS version > ---------------------- > > Key: WFLY-4235 > URL: https://issues.jboss.org/browse/WFLY-4235 > Project: WildFly > Issue Type: Feature Request > Components: JDR > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Priority: Major > > JDR should capture OS version if available -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1073) Replicating JNDI tree to another server

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/WFLY-1073?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1073: ----------------------------------------------- Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 913618|https://bugzilla.redhat.com/show_bug.cgi?id=913618] from NEW to CLOSED > Replicating JNDI tree to another server > ---------------------------------------- > > Key: WFLY-1073 > URL: https://issues.jboss.org/browse/WFLY-1073 > Project: WildFly > Issue Type: Feature Request > Components: Naming > Reporter: Miroslav Novak > Priority: Major > > Description of problem: > This use case is taken from one of our user which we were able to handle using HA-JNDI in EAP 5: > 1. JMS Client will create Context with two URL (node1, node2) (java.naming.provider.url property) > 2. For some reason client is connected to node2 first which will have no JMS admin objects registered in JNDI (this happens when this node is configured as HornetQ backup) > 3. Node2 has replicated JNDI tree from node1. So connection factory will connect client to node1 and queue/topics are deployed on node1. > Can be this functionality provided in EAP 6, please? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4239) WARN if system-property is already set and is being overridden

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/WFCORE-4239?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-4239: ------------------------------------------------- Chao Wang <chaowan(a)redhat.com> changed the Status of [bug 1654454|https://bugzilla.redhat.com/show_bug.cgi?id=1654454] from NEW to ASSIGNED > WARN if system-property is already set and is being overridden > -------------------------------------------------------------- > > Key: WFCORE-4239 > URL: https://issues.jboss.org/browse/WFCORE-4239 > Project: WildFly Core > Issue Type: Enhancement > Components: Management > Reporter: Brad Maxwell > Assignee: Chao Wang > Priority: Major > Fix For: 8.0.0.Beta2, 8.0.0.Final > > > WARN if system-property is already set and is being overridden > If user sets a system property using the java opts or on the command line and the same system property is defined in the standalone.xml, then the standalone.xml value overrides that passed on the commandline/JAVA_OPTS, a warning would be useful as looking at the logs (and ps), it shows value1 passed on the command line and nothing indicating that the value was changed later. > JAVA_OPTS="$JAVA_OPTS -Dmy.system.property=value1" > {code} > <system-properties> > <property name="my.system.property" value="value2"/> > </system-properties> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3659) DMN: UX for documentation reports

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3659?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3659: ---------------------------------------- Thanks [~tdolphine] I missed the "Print" button! :-) > DMN: UX for documentation reports > --------------------------------- > > Key: DROOLS-3659 > URL: https://issues.jboss.org/browse/DROOLS-3659 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: DROOLS-3659-documentation.mp4 > > > User stories: > * As a user I want to generate a PDF or HTML report of the DMN model, with documentation, so that I can hand it off to external team and/or business that needs information about the diagrams and the logic of the decisions being automated. The report can be printed out and used by business teams not involved with the modeling itself, to learn about content of the .dmn file. > * As a user I need a means through the UI to input additional documentation, links and attachments to nodes. > Notes: > - Docs to help with docs formatting. > - Might be able to leverage Case View docs widget. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3659) DMN: UX for documentation reports

by Tiago Dolphine (Jira)

[ https://issues.jboss.org/browse/DROOLS-3659?page=com.atlassian.jira.plugi... ] Tiago Dolphine commented on DROOLS-3659: ---------------------------------------- Hi [~manstis] about downloading the documentation, the way it was decided to be quicker and work on the same way as the jbpm-designer is to have a printable version of the documentation, see the button on the top right, and use the browser to save as a pdf (now this is coupled to the bpmn documentation view page, but it could be extracted to some common component. About the documentation generation, yeah it is based on a given text template (we are using https://mustache.github.io/ engine and the syntax that is pretty simple to use) and a data model that should be generated based on the diagram/graph structure, so it is flexible to generate all that is necessary for DMN documentation requirements. > DMN: UX for documentation reports > --------------------------------- > > Key: DROOLS-3659 > URL: https://issues.jboss.org/browse/DROOLS-3659 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: DROOLS-3659-documentation.mp4 > > > User stories: > * As a user I want to generate a PDF or HTML report of the DMN model, with documentation, so that I can hand it off to external team and/or business that needs information about the diagrams and the logic of the decisions being automated. The report can be printed out and used by business teams not involved with the modeling itself, to learn about content of the .dmn file. > * As a user I need a means through the UI to input additional documentation, links and attachments to nodes. > Notes: > - Docs to help with docs formatting. > - Might be able to leverage Case View docs widget. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

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

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3077?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3077: ---------------------------------------- Personally, I am wondering if [~uxdlc] first [proposal|https://redhat.invisionapp.com/share/WJQMEPWBRE9#/348010399_1] was better? Furthermore whether the _overriding_ Constraint definition (when "Modify" was clicked and the Constraint popover shown) should be applied when the "OK" button on the Constraint popover was clicked and we remove the "OK", "Cancel" buttons from the {{InputClause}} column popover. > 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)

5 years, 10 months

1
0
0 / 0

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

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3077?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3077: ---------------------------------------- [~karreiro] [~uxdlc] On the whole I think it looks good. However; I think with {{Applicant.Age}} set as the input expression and the Data Type {{Age}} the _existing_ constraint of {{[18..24]}} could be overridden *without* needing to select a different or define a new Data Type. Furthermore I wonder whether the User should _set_ the constraint rather than _add_ one (as they can only have one constraint). Also, at the moment, if I change the Name or Data Type the change can be undone. However (currently) changes to the Constraint definition cannot be undone. So we have a mis-match of functionality. However we could change this so that clicking OK performs the actions necessary to change the Name, Data-type and Constraint in such a way as they can be undone. Changes made on the Data Types cannot be undone. Finally, I wonder if adding the "OK", "Cancel" buttons to the {{InputClause}} popover should be replicated to all popovers; otherwise some popovers will continue to apply changes when (a) the "Name" {{TextBox}} looses focus, (b) when a selection is made in the "Data Type" drop-down, (c) when the "OK" button is clicked... just wondering. > 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)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3659) DMN: UX for documentation reports

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3659?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3659: ---------------------------------------- It would appear that the content of the _documentation_ tab cannot be downloaded.. [~tdolphine] did I miss something? > DMN: UX for documentation reports > --------------------------------- > > Key: DROOLS-3659 > URL: https://issues.jboss.org/browse/DROOLS-3659 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: DROOLS-3659-documentation.mp4 > > > User stories: > * As a user I want to generate a PDF or HTML report of the DMN model, with documentation, so that I can hand it off to external team and/or business that needs information about the diagrams and the logic of the decisions being automated. The report can be printed out and used by business teams not involved with the modeling itself, to learn about content of the .dmn file. > * As a user I need a means through the UI to input additional documentation, links and attachments to nodes. > Notes: > - Docs to help with docs formatting. > - Might be able to leverage Case View docs widget. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2019