April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13302) Add ARM64 versions for libartemis-native.so and libwfssl.so

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13302?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFLY-13302: --------------------------------------- Assignee: Farah Juma (was: Brian Stansberry) > Add ARM64 versions for libartemis-native.so and libwfssl.so > ----------------------------------------------------------- > > Key: WFLY-13302 > URL: https://issues.redhat.com/browse/WFLY-13302 > Project: WildFly > Issue Type: Feature Request > Components: Build System > Affects Versions: 19.0.0.Final > Reporter: Martin Grigorov > Assignee: Farah Juma > Priority: Major > > Hello WildFly team, > I'd like to ask you to add arm64/aarch64 versions of the libartemis-native.so and libwfssl.so binaries to the release distribution. > The TGZ download from https://wildfly.org/downloads/ has the following .so files: > {code} > wildfly-19.0.0.Final $ find ./ -name "*.so" > ./modules/system/layers/base/org/apache/activemq/artemis/journal/main/lib/linux-i686/libartemis-native-32.so > ./modules/system/layers/base/org/apache/activemq/artemis/journal/main/lib/linux-x86_64/libartemis-native-64.so > ./modules/system/layers/base/org/wildfly/openssl/main/lib/linux-x86_64/libwfssl.so > ./modules/system/layers/base/org/wildfly/openssl/main/lib/linux-i386/libwfssl.so > ./modules/system/layers/base/org/wildfly/openssl/main/lib/solaris-x86_64/libwfssl.so > {code} > Since recently there is a TeamCity agent running on Ubuntu 18.04.4 ARM64: https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxArm64OpenJ911 > I guess it could be used to build those binaries too -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13302) Add ARM64 versions for libartemis-native.so and libwfssl.so

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13302?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFLY-13302: ----------------------------------------- [~fjuma] [~ehugonnet] FYI. If something can be done for both of these, please split the issue. If the basic thing to do is to direct [~martin.grigorov1] to the appropriate issue tracker for adding a new native to Artemis and WF OpenSSL please do so. WildFly itself shouldn't be producing new natives; we only package ones provided by our components. > Add ARM64 versions for libartemis-native.so and libwfssl.so > ----------------------------------------------------------- > > Key: WFLY-13302 > URL: https://issues.redhat.com/browse/WFLY-13302 > Project: WildFly > Issue Type: Feature Request > Components: Build System > Affects Versions: 19.0.0.Final > Reporter: Martin Grigorov > Assignee: Brian Stansberry > Priority: Major > > Hello WildFly team, > I'd like to ask you to add arm64/aarch64 versions of the libartemis-native.so and libwfssl.so binaries to the release distribution. > The TGZ download from https://wildfly.org/downloads/ has the following .so files: > {code} > wildfly-19.0.0.Final $ find ./ -name "*.so" > ./modules/system/layers/base/org/apache/activemq/artemis/journal/main/lib/linux-i686/libartemis-native-32.so > ./modules/system/layers/base/org/apache/activemq/artemis/journal/main/lib/linux-x86_64/libartemis-native-64.so > ./modules/system/layers/base/org/wildfly/openssl/main/lib/linux-x86_64/libwfssl.so > ./modules/system/layers/base/org/wildfly/openssl/main/lib/linux-i386/libwfssl.so > ./modules/system/layers/base/org/wildfly/openssl/main/lib/solaris-x86_64/libwfssl.so > {code} > Since recently there is a TeamCity agent running on Ubuntu 18.04.4 ARM64: https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxArm64OpenJ911 > I guess it could be used to build those binaries too -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4746) UX for DMN "quick test" tool

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-4746?page=com.atlassian.jira.plug... ] Elizabeth Clayton updated DROOLS-4746: -------------------------------------- Attachment: Screen Shot 2020-04-08 at 5.01.51 PM.png > UX for DMN "quick test" tool > ---------------------------- > > Key: DROOLS-4746 > URL: https://issues.redhat.com/browse/DROOLS-4746 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2020-04-08 at 4.34.49 PM.png, Screen Shot 2020-04-08 at 5.01.51 PM.png, decision-logic-2-2.png, decision-logic-3-2.png > > > As a DMN author, I'd like to probe the DMN model during the authoring phase without leaving the DMN Editor. Actually, it's really important to explore the DMN model to understand with values are required by the test. > When the user run the test he can get back the results of the DMN execution. > Moreover, it would be handy to add those input/output to an existing (or new) test scenario. > *Acceptance criteria* > Users are able to: > * Execute a single node boxed expression by providing node inputs (within the DMN editor.) > * Explore the DMN model and provide inputs necessary to run a scenario test. > * Obtain results (Expected) within the DMN editor once the test is run. > Notes: > * Try to dissociate this feature from the "test scenario" concept and think of this more as a partial execution. When we're thinking about the concept of a "test scenario", we think about input values and expected outputs... however, in this new component, users will be able to provide inputs and just check the current output. > * Out of scope: Saving or exporting the "quick test." -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13288) Upgrade Mojarra to 2.3.9.SP08

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFLY-13288?page=com.atlassian.jira.plugi... ] Farah Juma updated WFLY-13288: ------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/13141, https://github.com/wildfly/wildfly/pull/13194 (was: https://github.com/wildfly/wildfly/pull/13141) > Upgrade Mojarra to 2.3.9.SP08 > ----------------------------- > > Key: WFLY-13288 > URL: https://issues.redhat.com/browse/WFLY-13288 > Project: WildFly > Issue Type: Component Upgrade > Components: JSF > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 20.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12870) Upgrade JBoss JSF API from 3.0.0.SP01 to 3.0.0.SP02

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFLY-12870?page=com.atlassian.jira.plugi... ] Farah Juma updated WFLY-12870: ------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/13106, https://github.com/wildfly/wildfly/pull/13194 (was: https://github.com/wildfly/wildfly/pull/13106) > Upgrade JBoss JSF API from 3.0.0.SP01 to 3.0.0.SP02 > --------------------------------------------------- > > Key: WFLY-12870 > URL: https://issues.redhat.com/browse/WFLY-12870 > Project: WildFly > Issue Type: Component Upgrade > Components: JSF > Reporter: Ilia Vassilev > Assignee: Farah Juma > Priority: Major > Labels: downstream_dependency > Fix For: 20.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13225) Upgrade JSF based on Mojarra 2.3.9.SP06 to 2.3.9.SP07

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFLY-13225?page=com.atlassian.jira.plugi... ] Farah Juma updated WFLY-13225: ------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/13106, https://github.com/wildfly/wildfly/pull/13194 (was: https://github.com/wildfly/wildfly/pull/13106) > Upgrade JSF based on Mojarra 2.3.9.SP06 to 2.3.9.SP07 > ----------------------------------------------------- > > Key: WFLY-13225 > URL: https://issues.redhat.com/browse/WFLY-13225 > Project: WildFly > Issue Type: Component Upgrade > Components: JSF > Reporter: Bartosz Spyrko > Assignee: Farah Juma > Priority: Major > Fix For: 20.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13225) Upgrade JSF based on Mojarra 2.3.9.SP06 to 2.3.9.SP07

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFLY-13225?page=com.atlassian.jira.plugi... ] Farah Juma commented on WFLY-13225: ----------------------------------- I've created the following PR to get this included in 19.0.1: https://github.com/wildfly/wildfly/pull/13194 > Upgrade JSF based on Mojarra 2.3.9.SP06 to 2.3.9.SP07 > ----------------------------------------------------- > > Key: WFLY-13225 > URL: https://issues.redhat.com/browse/WFLY-13225 > Project: WildFly > Issue Type: Component Upgrade > Components: JSF > Reporter: Bartosz Spyrko > Assignee: Farah Juma > Priority: Major > Fix For: 20.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13252) JSF IdMapper can create repeated ids in clustered environments causing: IllegalStateException with postback

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFLY-13252?page=com.atlassian.jira.plugi... ] Farah Juma resolved WFLY-13252. ------------------------------- Resolution: Done > JSF IdMapper can create repeated ids in clustered environments causing: IllegalStateException with postback > ----------------------------------------------------------------------------------------------------------- > > Key: WFLY-13252 > URL: https://issues.redhat.com/browse/WFLY-13252 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 19.0.0.Beta3 > Reporter: Ricardo Martin Camarero > Assignee: Ricardo Martin Camarero > Priority: Major > Labels: downstream_dependency > Fix For: 20.0.0.Beta1 > > > In the round-robin load-balancing environment, IllegalStateException occurs with postback action. > This issue seems to occur notably when set javax.faces.PARTIAL_STATE_SAVING=false. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13252) JSF IdMapper can create repeated ids in clustered environments causing: IllegalStateException with postback

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFLY-13252?page=com.atlassian.jira.plugi... ] Farah Juma updated WFLY-13252: ------------------------------ Fix Version/s: 20.0.0.Beta1 > JSF IdMapper can create repeated ids in clustered environments causing: IllegalStateException with postback > ----------------------------------------------------------------------------------------------------------- > > Key: WFLY-13252 > URL: https://issues.redhat.com/browse/WFLY-13252 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 19.0.0.Beta3 > Reporter: Ricardo Martin Camarero > Assignee: Ricardo Martin Camarero > Priority: Major > Labels: downstream_dependency > Fix For: 20.0.0.Beta1 > > > In the round-robin load-balancing environment, IllegalStateException occurs with postback action. > This issue seems to occur notably when set javax.faces.PARTIAL_STATE_SAVING=false. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4746) UX for DMN "quick test" tool

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-4746?page=com.atlassian.jira.plug... ] Elizabeth Clayton commented on DROOLS-4746: ------------------------------------------- Thanks [~karreiro]. The output for Fine is points and $$, so would I add these fields: !Screen Shot 2020-04-08 at 4.34.49 PM.png|thumbnail! > UX for DMN "quick test" tool > ---------------------------- > > Key: DROOLS-4746 > URL: https://issues.redhat.com/browse/DROOLS-4746 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2020-04-08 at 4.34.49 PM.png, decision-logic-2-2.png, decision-logic-3-2.png > > > As a DMN author, I'd like to probe the DMN model during the authoring phase without leaving the DMN Editor. Actually, it's really important to explore the DMN model to understand with values are required by the test. > When the user run the test he can get back the results of the DMN execution. > Moreover, it would be handy to add those input/output to an existing (or new) test scenario. > *Acceptance criteria* > Users are able to: > * Execute a single node boxed expression by providing node inputs (within the DMN editor.) > * Explore the DMN model and provide inputs necessary to run a scenario test. > * Obtain results (Expected) within the DMN editor once the test is run. > Notes: > * Try to dissociate this feature from the "test scenario" concept and think of this more as a partial execution. When we're thinking about the concept of a "test scenario", we think about input values and expected outputs... however, in this new component, users will be able to provide inputs and just check the current output. > * Out of scope: Saving or exporting the "quick test." -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 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 April 2020