August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4438) XLS export does not add the cell values for columns that resolve to String, but actually store the data as Date

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4438?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4438: -------------------------------- Labels: drools-tools (was: ) > XLS export does not add the cell values for columns that resolve to String, but actually store the data as Date > --------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4438 > URL: https://issues.jboss.org/browse/DROOLS-4438 > Project: Drools > Issue Type: Sub-task > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > This most likely also applies for any other data type than String. Dates, doubles, ints so on. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4438) XLS export does not add the cell values for columns that resolve to String, but actually store the data as Date

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4438?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4438: -------------------------------- Component/s: Guided Decision Table Editor XLS Decision Table Editor > XLS export does not add the cell values for columns that resolve to String, but actually store the data as Date > --------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4438 > URL: https://issues.jboss.org/browse/DROOLS-4438 > Project: Drools > Issue Type: Sub-task > Components: Guided Decision Table Editor, XLS Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > This most likely also applies for any other data type than String. Dates, doubles, ints so on. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4438) XLS export does not add the cell values for columns that resolve to String, but actually store the data as Date

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4438?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4438: -------------------------------- Tester: Jozef Marko > XLS export does not add the cell values for columns that resolve to String, but actually store the data as Date > --------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4438 > URL: https://issues.jboss.org/browse/DROOLS-4438 > Project: Drools > Issue Type: Sub-task > Components: Guided Decision Table Editor, XLS Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > This most likely also applies for any other data type than String. Dates, doubles, ints so on. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2284) Discovery protocol for members in the same process

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2284?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2284. ---------------------------- Release Notes Text: The new proocol is called {{LOCAL_PING}}. It is similar to Infinispan's {{TEST_PING}}, but doesn't have the need to special handling of {{DISCARD}} protocols. Resolution: Done > Discovery protocol for members in the same process > -------------------------------------------------- > > Key: JGRP-2284 > URL: https://issues.jboss.org/browse/JGRP-2284 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.3 > > > Discovery protocol that works for members in the same process. Something like SHARED_LOOPBACK_PING, but without the requirement for SHARED_LOOPBACK as transport, but it should work over UDP, TCP, TCP_NIO2 etc. > Similar to TEST_PING in Infinispan. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4438) XLS export does not add the cell values for columns that resolve to String, but actually store the data as Date

by Toni Rikkola (Jira)

Toni Rikkola created DROOLS-4438: ------------------------------------ Summary: XLS export does not add the cell values for columns that resolve to String, but actually store the data as Date Key: DROOLS-4438 URL: https://issues.jboss.org/browse/DROOLS-4438 Project: Drools Issue Type: Sub-task Reporter: Toni Rikkola Assignee: Toni Rikkola This most likely also applies for any other data type than String. Dates, doubles, ints so on. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-170) Galleon provisioning does not work when layers defined using provisioning.xml

by Nikoleta Ziakova (Jira)

Nikoleta Ziakova created WFWIP-170: -------------------------------------- Summary: Galleon provisioning does not work when layers defined using provisioning.xml Key: WFWIP-170 URL: https://issues.jboss.org/browse/WFWIP-170 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Nikoleta Ziakova Assignee: Jean Francois Denise S2I build of [helloworld|https://github.com/nziakova/jboss-eap-quickstarts/tree/with_ga...] quickstart fails after adding galleon/[provisioning.xml|https://github.com/wildfly/temp-eap-modules/blo...: {code} Not a valid galleon description /tmp/src/galleon exiting {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-169) Galleon provisioning does not work when layers defined using env vars

by Nikoleta Ziakova (Jira)

[ https://issues.jboss.org/browse/WFWIP-169?page=com.atlassian.jira.plugin.... ] Nikoleta Ziakova updated WFWIP-169: ----------------------------------- Description: When running s2i build using the builder image at docker-registry.engineering.redhat.com/kwills/eap-cd-openshift:EAP7-891 and [kitchensink|https://github.com/jboss-developer/jboss-eap-quickstarts/tree...] quickstart using {{cloud-profile-h2}}, h2 is not installed: {code} oc new-app --template=eap-cd-basic-s2i \ -p IMAGE_STREAM_NAMESPACE=eap-demo \ -p SOURCE_REPOSITORY_URL=https://github.com/nziakova/jboss-eap-quickstarts \ -p SOURCE_REPOSITORY_REF=test \ -p CONTEXT_DIR=kitchensink \ -p APPLICATION_NAME=kitchensink \ -e GALLEON_PROVISION_DEFAULT_CONFIG_LAYERS=h2-datasource # OR: -e GALLEON_PROVISION_SERVER=cloud-profile-h2 {code} {code} WFLYCTL0184: New missing/unsatisfied dependencies: service jboss.jdbc-driver.h2 (missing) dependents: [service jboss.data-source."jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS"] {code} When running the same build with [helloworld|https://github.com/jboss-developer/jboss-eap-quickstarts/tree/...] quickstart (which does not use h2), the build passes and the app is successfully deployed. The issue is, the server is not provisioned as requested. This blocks our testing. was: When running s2i build using the builder [image|docker-registry.engineering.redhat.com/kwills/eap-cd-openshift:EAP7...] and [kitchensink|https://github.com/jboss-developer/jboss-eap-quickstarts/tree...] quickstart using {{cloud-profile-h2}}, h2 is not installed: {code} oc new-app --template=eap-cd-basic-s2i \ -p IMAGE_STREAM_NAMESPACE=eap-demo \ -p SOURCE_REPOSITORY_URL=https://github.com/nziakova/jboss-eap-quickstarts \ -p SOURCE_REPOSITORY_REF=test \ -p CONTEXT_DIR=kitchensink \ -p APPLICATION_NAME=kitchensink \ -e GALLEON_PROVISION_DEFAULT_CONFIG_LAYERS=h2-datasource # OR: -e GALLEON_PROVISION_SERVER=cloud-profile-h2 {code} {code} WFLYCTL0184: New missing/unsatisfied dependencies: service jboss.jdbc-driver.h2 (missing) dependents: [service jboss.data-source."jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS"] {code} When running the same build with [helloworld|https://github.com/jboss-developer/jboss-eap-quickstarts/tree/...] quickstart (which does not use h2), the build passes and the app is successfully deployed. The issue is, the server is not provisioned as requested. This blocks our testing. > Galleon provisioning does not work when layers defined using env vars > --------------------------------------------------------------------- > > Key: WFWIP-169 > URL: https://issues.jboss.org/browse/WFWIP-169 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Nikoleta Ziakova > Assignee: Jean Francois Denise > Priority: Critical > > When running s2i build using the builder image at docker-registry.engineering.redhat.com/kwills/eap-cd-openshift:EAP7-891 and [kitchensink|https://github.com/jboss-developer/jboss-eap-quickstarts/tree...] quickstart using {{cloud-profile-h2}}, h2 is not installed: > {code} > oc new-app --template=eap-cd-basic-s2i \ > -p IMAGE_STREAM_NAMESPACE=eap-demo \ > -p SOURCE_REPOSITORY_URL=https://github.com/nziakova/jboss-eap-quickstarts \ > -p SOURCE_REPOSITORY_REF=test \ > -p CONTEXT_DIR=kitchensink \ > -p APPLICATION_NAME=kitchensink \ > -e GALLEON_PROVISION_DEFAULT_CONFIG_LAYERS=h2-datasource > # OR: -e GALLEON_PROVISION_SERVER=cloud-profile-h2 > {code} > {code} > WFLYCTL0184: New missing/unsatisfied dependencies: > service jboss.jdbc-driver.h2 (missing) dependents: [service jboss.data-source."jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS"] > {code} > When running the same build with [helloworld|https://github.com/jboss-developer/jboss-eap-quickstarts/tree/...] quickstart (which does not use h2), the build passes and the app is successfully deployed. The issue is, the server is not provisioned as requested. > This blocks our testing. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBEE-209) Port PicketBox integration changes to JBoss / Jakarta JACC Form

by Darran Lofthouse (Jira)

Darran Lofthouse created JBEE-209: ------------------------------------- Summary: Port PicketBox integration changes to JBoss / Jakarta JACC Form Key: JBEE-209 URL: https://issues.jboss.org/browse/JBEE-209 Project: JBoss Enterprise Spec APIs Issue Type: Task Components: jboss-jacc-api Reporter: Darran Lofthouse Assignee: Darran Lofthouse -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10145) mvn versions:set -DnewVersion=xxxx does not replace component-matrix/pom.xml

by Michal Petrov (Jira)

[ https://issues.jboss.org/browse/WFLY-10145?page=com.atlassian.jira.plugin... ] Michal Petrov resolved WFLY-10145. ---------------------------------- Resolution: Out of Date This seems to be out of date, at the moment the maven command sets all versions correctly. > mvn versions:set -DnewVersion=xxxx does not replace component-matrix/pom.xml > ---------------------------------------------------------------------------- > > Key: WFLY-10145 > URL: https://issues.jboss.org/browse/WFLY-10145 > Project: WildFly > Issue Type: Bug > Components: Build System > Reporter: Kabir Khan > Assignee: Tomaž Cerar > Priority: Major > > Similar to WFCORE-3718, using mvn versions:set -DnewVersion=12.0.0.Beta1, leaves component-matrix/pom.xml untouched. > {code} > $git grep "\-SNAPSHOT" > component-matrix/pom.xml: <version>13.0.0.Alpha1-SNAPSHOT</version> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4437) [DMN Designer] Nested Structure update causes field addition

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4437?page=com.atlassian.jira.plugi... ] Guilherme Gomes reassigned DROOLS-4437: --------------------------------------- Assignee: Guilherme Gomes (was: Michael Anstis) > [DMN Designer] Nested Structure update causes field addition > ------------------------------------------------------------ > > Key: DROOLS-4437 > URL: https://issues.jboss.org/browse/DROOLS-4437 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.26.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: edit-nested-structure.webm > > > There is an issue when user decides to edit an non-top level data structure. In such case during saving also new nested field is added into structure, for steps to reproduce see the attached video. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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 August 2019