July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10698) [EAT] : When using versioning, exclude the tests if the current version is a SNAPSHOT

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/WFLY-10698?page=com.atlassian.jira.plugin... ] Panagiotis Sotiropoulos updated WFLY-10698: ------------------------------------------- Component/s: Test Suite > [EAT] : When using versioning, exclude the tests if the current version is a SNAPSHOT > ------------------------------------------------------------------------------------- > > Key: WFLY-10698 > URL: https://issues.jboss.org/browse/WFLY-10698 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > > When using versioning, exclude the tests, if the current version is a SNAPSHOT, for the tests that are introduced in this version for the first time. > Proposed in https://github.com/jboss-set/eap-additional-testsuite/pull/43 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10698) [EAT] : When using versioning, exclude the tests if the current version is a SNAPSHOT

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/WFLY-10698?page=com.atlassian.jira.plugin... ] Panagiotis Sotiropoulos moved JBEAP-15049 to WFLY-10698: -------------------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-10698 (was: JBEAP-15049) Issue Type: Task (was: Bug) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Fix Version/s: (was: 7.1.5.GA) > [EAT] : When using versioning, exclude the tests if the current version is a SNAPSHOT > ------------------------------------------------------------------------------------- > > Key: WFLY-10698 > URL: https://issues.jboss.org/browse/WFLY-10698 > Project: WildFly > Issue Type: Task > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > > When using versioning, exclude the tests, if the current version is a SNAPSHOT, for the tests that are introduced in this version for the first time. > Proposed in https://github.com/jboss-set/eap-additional-testsuite/pull/43 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10688) Bad unit conversion of jdbc-network-timeout attribute

by Erich Duda (JIRA)

[ https://issues.jboss.org/browse/WFLY-10688?page=com.atlassian.jira.plugin... ] Erich Duda commented on WFLY-10688: ----------------------------------- I tried to build WF from your PR branch but I still see following warning message in the log. {code} jdbc-network-timeout isn't properly configured: the recommended value is <= jdbc-lock-expiration {code} I think that problem is here \[1\]. The {{ActiveMQDefaultConfiguration.getDefaultJdbcNetworkTimeout()}} returns value in milliseconds but measurement unit is set to seconds. In Artemis upgrade branch, you fixed this issue by this change \[2\]. \[1\] https://github.com/wildfly/wildfly/pull/11355/files#diff-ad6d616ebe61ee6d... \[2\] https://github.com/jmesnil/wildfly/commit/be3af696141c9a6755583a5d1ab82f8... > Bad unit conversion of jdbc-network-timeout attribute > ----------------------------------------------------- > > Key: WFLY-10688 > URL: https://issues.jboss.org/browse/WFLY-10688 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 13.0.0.Final > Reporter: Erich Duda > Assignee: Jeff Mesnil > Priority: Blocker > > In the messaging subsystem there is an attribute {{jdbc-network-timeout}} with default value 20 seconds. However this parameter is passed to ActiveMQ Artemis as 20 000 000 milliseconds (20 000 seconds). > For reproducing the issue just configure JDBC persistence store and attach debugger with breakpoint on {{AbstractJDBCDriver::connect}}. > *Blocker* priority was set because it is regression against Wildfly 12. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2656) PNGs for the toolbox icons for the different connector types.

by Matthew Stevens (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2656?page=com.atlassian.jira.plugi... ] Matthew Stevens commented on DROOLS-2656: ----------------------------------------- My apologies [~manstis] for not seeing that and confusing things. > PNGs for the toolbox icons for the different connector types. > ------------------------------------------------------------- > > Key: DROOLS-2656 > URL: https://issues.jboss.org/browse/DROOLS-2656 > Project: Drools > Issue Type: Sub-task > Reporter: Liz Clayton > Assignee: Brian Dellascio > Labels: IconRequest, UX, UXTeam, VisualDesign, drools-tools > Attachments: DROOLS-2652 (Stunner, hover).png.png, DROOLS-2652 (Stunner, no-hover).png, DROOLS-2656 (hover).png, DROOLS-2656 (toolbox icons).png, DROOLS-2656.png, association_toolbox.png, association_toolbox.svg, authority_requirement_toolbox.png, authority_requirement_toolbox.svg, businessknowledgemodel_toolbox.png, businessknowledgemodel_toolbox.svg, edit.svg, info_requirement_toolbox.png, info_requirement_toolbox.svg, inputdata_toolbox.png, inputdata_toolbox.svg, knowledge_requirement_toolbox.png, knowledge_requirement_toolbox.svg, knowledgesource_toolbox.png, knowledgesource_toolbox.svg, stunner-2656.png, task_toolbox.png, task_toolbox.svg, textannotation_toolbox.png, textannotation_toolbox.svg, toolbox_icons.png > > > PNGs for the toolbox icons for the different connector types. > Their appearance can be seen in https://www.omg.org/spec/DMN/1.1/PDF (page 30, "Association", "Information Requirement", "Knowledge Requirement" and "Authority Requirement"). They'll only be used as icons on the toolbox (see screenshot attached). Could you please also remind me of the BAPL for the new "Node" SVGs (I'll need to make PNGs of those too for the same "toolbox" purpose.. unless UX have a tool to convert SVG to PNG?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3885) XNIO prints WARNING with JDK10+ if CLI connects to server

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3885?page=com.atlassian.jira.plugi... ] Miroslav Novak commented on WFCORE-3885: ---------------------------------------- [~dmlloyd] Any update on this? Was the fix already merged? > XNIO prints WARNING with JDK10+ if CLI connects to server > --------------------------------------------------------- > > Key: WFCORE-3885 > URL: https://issues.jboss.org/browse/WFCORE-3885 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Scripts > Reporter: Marek Kopecký > Assignee: Jean-Francois Denise > Labels: blocker-WF14 > > CLI prints WARNING with JDK10+ if CLI connects to server > {noformat} > [mkopecky@dhcp-10-40-5-52 bin]$ java -version > java version "10" 2018-03-20 > Java(TM) SE Runtime Environment 18.3 (build 10+46) > Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10+46, mixed mode) > [mkopecky@dhcp-10-40-5-52 bin]$ ./jboss-cli.sh "echo test" > test > [mkopecky@dhcp-10-40-5-52 bin]$ ./jboss-cli.sh -c "echo test" > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by org.xnio.nio.NioXnio$2 (jar:file:/home/mkopecky/playground/eap/7.2.0.CD13.1/jboss-eap-7.2/modules/system/layers/base/org/jboss/xnio/nio/main/xnio-nio-3.6.3.Final.jar!/) to constructor sun.nio.ch.EPollSelectorProvider() > WARNING: Please consider reporting this to the maintainers of org.xnio.nio.NioXnio$2 > WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations > WARNING: All illegal access operations will be denied in a future release > test > [mkopecky@dhcp-10-40-5-52 bin]$ > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1379) service.bat points user to wrong directory

by Swaroop Kulkarni (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1379?page=com.atlassian.jira.plugi... ] Swaroop Kulkarni commented on WFCORE-1379: ------------------------------------------ In my case adding JAVA_HOME system variable solved the issue. I am now able to start the service without any error! > service.bat points user to wrong directory > ------------------------------------------ > > Key: WFCORE-1379 > URL: https://issues.jboss.org/browse/WFCORE-1379 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 2.0.10.Final > Reporter: Nicklas Karlsson > Assignee: Tomaz Cerar > Priority: Trivial > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > > Running service.bat from the docs/contrib/scripts/service dir tells user to run the script under bin/service*s* but the binary paths to the services expects bin/service, resulting in service install failure with file not found -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10688) Bad unit conversion of jdbc-network-timeout attribute

by Erich Duda (JIRA)

[ https://issues.jboss.org/browse/WFLY-10688?page=com.atlassian.jira.plugin... ] Erich Duda updated WFLY-10688: ------------------------------ Labels: (was: feature-branch-blocker) > Bad unit conversion of jdbc-network-timeout attribute > ----------------------------------------------------- > > Key: WFLY-10688 > URL: https://issues.jboss.org/browse/WFLY-10688 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 13.0.0.Final > Reporter: Erich Duda > Assignee: Jeff Mesnil > Priority: Blocker > > In the messaging subsystem there is an attribute {{jdbc-network-timeout}} with default value 20 seconds. However this parameter is passed to ActiveMQ Artemis as 20 000 000 milliseconds (20 000 seconds). > For reproducing the issue just configure JDBC persistence store and attach debugger with breakpoint on {{AbstractJDBCDriver::connect}}. > *Blocker* priority was set because it is regression against Wildfly 12. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2735) [DMN Editor] Function change breaks column layout

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2735?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2735: -------------------------------- Priority: Minor (was: Major) > [DMN Editor] Function change breaks column layout > ------------------------------------------------- > > Key: DROOLS-2735 > URL: https://issues.jboss.org/browse/DROOLS-2735 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.9.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > Attachments: Screenshot from 2018-07-13 10-21-15.png, Screenshot from 2018-07-13 10-21-28.png > > > If user changes function definition in the context entry, while context grid contains multiple entries, then the layout of the context grid is broken. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2735) [DMN Editor] Function change breaks column layout

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2735: ----------------------------------- Summary: [DMN Editor] Function change breaks column layout Key: DROOLS-2735 URL: https://issues.jboss.org/browse/DROOLS-2735 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.9.0.Final Reporter: Jozef Marko Assignee: Michael Anstis Attachments: Screenshot from 2018-07-13 10-21-15.png, Screenshot from 2018-07-13 10-21-28.png If user changes function definition in the context entry, while context grid contains multiple entries, then the layout of the context grid is broken. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2735) [DMN Editor] Function change breaks column layout

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2735?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2735: -------------------------------- Labels: drools-tools (was: ) > [DMN Editor] Function change breaks column layout > ------------------------------------------------- > > Key: DROOLS-2735 > URL: https://issues.jboss.org/browse/DROOLS-2735 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.9.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: drools-tools > Attachments: Screenshot from 2018-07-13 10-21-15.png, Screenshot from 2018-07-13 10-21-28.png > > > If user changes function definition in the context entry, while context grid contains multiple entries, then the layout of the context grid is broken. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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 July 2018