January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12913) Rationalize com.sum.xml.bind module dependencies

by Lin Gao (Jira)

[ https://issues.redhat.com/browse/WFLY-12913?page=com.atlassian.jira.plugi... ] Lin Gao commented on WFLY-12913: -------------------------------- Refer to: https://github.com/wildfly/wildfly/pull/12856 for the context about this issue. > Rationalize com.sum.xml.bind module dependencies > ------------------------------------------------ > > Key: WFLY-12913 > URL: https://issues.redhat.com/browse/WFLY-12913 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate, REST, Web Services > Reporter: Brian Stansberry > Priority: Minor > > The com.sun.xml.bind module depends on and exports four other modules, and those modules in turn are private and have no other dependents: > {code} > <module name="com.github.relaxng" export="true" /> > <module name="com.sun.istack" export="true" /> > <module name="com.sun.xml.txw2" export="true" /> > <module name="com.sun.xsom" export="true" /> > {code} > Task is to: > 1) Write to wildfly-dev mail list to check for any projects that layer on WildFly that directly use these modules. > 2) Write to jboss-layered-products (internal Red Hat) mail list to check for any products based on WF/EAP that directly use these modules. > 3) Assuming no positive responses, make the artifacts from the above four modules direct artifacts of the com.sun.xml.bind module, add any needed module dependencies to con.sum.xml.bind, and get rid of those four modules. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2427) UDP: change methods deprecated in Java 14

by Bela Ban (Jira)

Bela Ban created JGRP-2427: ------------------------------ Summary: UDP: change methods deprecated in Java 14 Key: JGRP-2427 URL: https://issues.redhat.com/browse/JGRP-2427 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 5.0 Several methods in UDP will get deprecated in Java 14, e.g. {{MulticastSocket.joinGroup()/leaveGroup()/setInterface()}} etc. They can be replaced with their suggested alternatives, even in Java 11 (these methods are already present). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4879) [DMN Designer] unification of import flash messages

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4879?page=com.atlassian.jira.plug... ] Jozef Marko commented on DROOLS-4879: ------------------------------------- [~uxdlc] thank you for finding the proper solution. [~dadossan] ok, I reassigned the jira to you as I guess you will implement it, am I right? > [DMN Designer] unification of import flash messages > --------------------------------------------------- > > Key: DROOLS-4879 > URL: https://issues.redhat.com/browse/DROOLS-4879 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > We should unify the flash messages related to import data types. See the github comment here https://github.com/kiegroup/kie-wb-common/pull/3071#issuecomment-566436373 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4879) [DMN Designer] unification of import flash messages

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4879?page=com.atlassian.jira.plug... ] Jozef Marko reassigned DROOLS-4879: ----------------------------------- Assignee: Daniel José dos Santos (was: Elizabeth Clayton) > [DMN Designer] unification of import flash messages > --------------------------------------------------- > > Key: DROOLS-4879 > URL: https://issues.redhat.com/browse/DROOLS-4879 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > We should unify the flash messages related to import data types. See the github comment here https://github.com/kiegroup/kie-wb-common/pull/3071#issuecomment-566436373 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4879) [DMN Designer] unification of import flash messages

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4879?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-4879: -------------------------------- Summary: [DMN Designer] unification of import flash messages (was: [UX] [DMN Designer] unification of import flash messages) > [DMN Designer] unification of import flash messages > --------------------------------------------------- > > Key: DROOLS-4879 > URL: https://issues.redhat.com/browse/DROOLS-4879 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Elizabeth Clayton > Priority: Major > Labels: drools-tools > > We should unify the flash messages related to import data types. See the github comment here https://github.com/kiegroup/kie-wb-common/pull/3071#issuecomment-566436373 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4879) [UX] [DMN Designer] unification of import flash messages

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4879?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-4879: -------------------------------- Component/s: DMN Editor > [UX] [DMN Designer] unification of import flash messages > -------------------------------------------------------- > > Key: DROOLS-4879 > URL: https://issues.redhat.com/browse/DROOLS-4879 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Elizabeth Clayton > Priority: Major > Labels: drools-tools > > We should unify the flash messages related to import data types. See the github comment here https://github.com/kiegroup/kie-wb-common/pull/3071#issuecomment-566436373 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-290) Response Content-Type is 'application/json' even when HTTP request defines 'application/json-patch+json' "Accept" header

by Fabio Burzigotti (Jira)

[ https://issues.redhat.com/browse/WFWIP-290?page=com.atlassian.jira.plugin... ] Fabio Burzigotti updated WFWIP-290: ----------------------------------- Steps to Reproduce: The issue can be reproduced following the steps: * execute Wildfly instance build from feature branch * provide a deployment to register `openapi` endpoint * send HTTP GET request to `openapi` defining the Accept header, e.g.: {code} curl --location --request GET 'http://127.0.0.1:8080/openapi' \ --header 'Accept: application/json-patch+json' {code} * the response "Content-Type" header is set to "application/json". Used feature branch is: https://github.com/pferraro/wildfly/tree/WFLY-12313 was: The issue can be reproduced following the steps: * execute Wildfly instance build from feature branch * provide a deployment to register `openapi` endpoint * send HTTP GET request to `openapi` defining the Accept header, e.g.: `curl --location --request GET 'http://127.0.0.1:8080/openapi' \ --header 'Accept: application/json-patch+json'` * the response "Content-Type" header is set to "application/json". Used feature branch is: https://github.com/pferraro/wildfly/tree/WFLY-12313 > Response Content-Type is 'application/json' even when HTTP request defines 'application/json-patch+json' "Accept" header > ------------------------------------------------------------------------------------------------------------------------ > > Key: WFWIP-290 > URL: https://issues.redhat.com/browse/WFWIP-290 > Project: WildFly WIP > Issue Type: Bug > Components: MP OpenAPI > Reporter: Fabio Burzigotti > Assignee: Paul Ferraro > Priority: Major > > When sending HTTP request header "Accept: application/json-patch+json", "Content-Type: application/json" response is returned. > This behavior seems to be less strict compared to what is defined by the spec, as it states "application/json" is specifically needed in order to get the same value back from server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-290) Response Content-Type is 'application/json' even when HTTP request defines 'application/json-patch+json' "Accept" header

by Fabio Burzigotti (Jira)

Fabio Burzigotti created WFWIP-290: -------------------------------------- Summary: Response Content-Type is 'application/json' even when HTTP request defines 'application/json-patch+json' "Accept" header Key: WFWIP-290 URL: https://issues.redhat.com/browse/WFWIP-290 Project: WildFly WIP Issue Type: Bug Components: MP OpenAPI Reporter: Fabio Burzigotti Assignee: Paul Ferraro When sending HTTP request header "Accept: application/json-patch+json", "Content-Type: application/json" response is returned. This behavior seems to be less strict compared to what is defined by the spec, as it states "application/json" is specifically needed in order to get the same value back from server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-243) Ensure reference to repository is removed from pom

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-243?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-243: --------------------------- Fix Version/s: 1.11.0.CR5 (was: 1.11.0.CR4) > Ensure reference to repository is removed from pom > -------------------------------------------------- > > Key: ELY-243 > URL: https://issues.redhat.com/browse/ELY-243 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Priority: Major > Fix For: 1.11.0.CR5 > > > We need to ensure the reference to the JBoss repo is removed from the pom and artefacts are available from Maven Central. > Also at this point probably good to put the steps in place for Elytron to also be available from Maven Central. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-533) Deprecate all legacy code

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-533?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-533: --------------------------- Fix Version/s: 1.11.0.CR5 (was: 1.11.0.CR4) > Deprecate all legacy code > ------------------------- > > Key: ELY-533 > URL: https://issues.redhat.com/browse/ELY-533 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.11.0.CR5 > > > In a few places we have legacy behaviour within the project to assist migration from previous JBoss / WildFly releases - this code should be flagged as deprecated to encourage minimal use. -- This message was sent by Atlassian Jira (v7.13.8#713008)

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