April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5248) DMN utility method for inspecting "root" leafs DRGElements

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5248?page=com.atlassian.jira.plug... ] Matteo Mortari deleted DROOLS-5248: ----------------------------------- > DMN utility method for inspecting "root" leafs DRGElements > ---------------------------------------------------------- > > Key: DROOLS-5248 > URL: https://issues.redhat.com/browse/DROOLS-5248 > Project: Drools > Issue Type: Task > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1123) 3Scale tests backport to 1.1

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1123?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan moved OSSM-181 to SWSQE-1123: -------------------------------------------- Project: Kiali QE (was: OpenShift Service Mesh) Key: SWSQE-1123 (was: OSSM-181) Workflow: classic default workflow (was: OpenShift Service Mesh - GitHub Workflow) > 3Scale tests backport to 1.1 > ---------------------------- > > Key: SWSQE-1123 > URL: https://issues.redhat.com/browse/SWSQE-1123 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-268) Upgrade jboss-modules to 1.10.1.Final

by James Perkins (Jira)

James Perkins created LOGMGR-268: ------------------------------------ Summary: Upgrade jboss-modules to 1.10.1.Final Key: LOGMGR-268 URL: https://issues.redhat.com/browse/LOGMGR-268 Project: JBoss Log Manager Issue Type: Component Upgrade Components: core Reporter: James Perkins Assignee: James Perkins Upgrade {{org.jboss.modules:jboss-modules}} to 1.10.1.Final. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-269) Upgrade JSON-P to Jakarta JSON-P

by James Perkins (Jira)

James Perkins created LOGMGR-269: ------------------------------------ Summary: Upgrade JSON-P to Jakarta JSON-P Key: LOGMGR-269 URL: https://issues.redhat.com/browse/LOGMGR-269 Project: JBoss Log Manager Issue Type: Component Upgrade Components: ext Reporter: James Perkins Assignee: James Perkins Migrate the JSON-P API and implementation over to Jakarta. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13380) Upgrade dom4j from 2.1.1 to 2.1.3

by Scott Marlow (Jira)

[ https://issues.redhat.com/browse/WFLY-13380?page=com.atlassian.jira.plugi... ] Scott Marlow commented on WFLY-13380: ------------------------------------- Updated relationship of link to HHH-13953, from blocked by, to is related to. The dom4j upgrade is upstream now in Hibernate master + 5.3 branches, that should be enough. > Upgrade dom4j from 2.1.1 to 2.1.3 > --------------------------------- > > Key: WFLY-13380 > URL: https://issues.redhat.com/browse/WFLY-13380 > Project: WildFly > Issue Type: Component Upgrade > Components: JPA / Hibernate > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Labels: downstream_dependency > Fix For: 19.0.1.Final, 20.0.0.Beta1 > > > https://github.com/dom4j/dom4j/compare/version-2.1.1...version-2.1.3 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3737) JavaEE appclient "Main" replace "System.in"

by Wolfgang Knauf (Jira)

[ https://issues.redhat.com/browse/WFLY-3737?page=com.atlassian.jira.plugin... ] Wolfgang Knauf commented on WFLY-3737: -------------------------------------- Same for WildFly 19 > JavaEE appclient "Main" replace "System.in" > ------------------------------------------- > > Key: WFLY-3737 > URL: https://issues.redhat.com/browse/WFLY-3737 > Project: WildFly > Issue Type: Bug > Components: Application Client > Affects Versions: 8.1.0.Final, 11.0.0.CR1, 19.0.0.Final > Reporter: Wolfgang Knauf > Assignee: James Perkins > Priority: Major > > "org.jboss.as.appclient.subsystem.Main.main" replaces System.in with a "NullInputStream" and thus you cannot use it to read user inputs. > I don't whether this is intentional, but it sounds like a bug to me -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3737) JavaEE appclient "Main" replace "System.in"

by Wolfgang Knauf (Jira)

[ https://issues.redhat.com/browse/WFLY-3737?page=com.atlassian.jira.plugin... ] Wolfgang Knauf updated WFLY-3737: --------------------------------- Affects Version/s: 19.0.0.Final > JavaEE appclient "Main" replace "System.in" > ------------------------------------------- > > Key: WFLY-3737 > URL: https://issues.redhat.com/browse/WFLY-3737 > Project: WildFly > Issue Type: Bug > Components: Application Client > Affects Versions: 8.1.0.Final, 11.0.0.CR1, 19.0.0.Final > Reporter: Wolfgang Knauf > Assignee: James Perkins > Priority: Major > > "org.jboss.as.appclient.subsystem.Main.main" replaces System.in with a "NullInputStream" and thus you cannot use it to read user inputs. > I don't whether this is intentional, but it sounds like a bug to me -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5248) wildfly-ejb-multi-server-app-one-ejb quickstart fails to validate in eclipse

by Ranabir Chakraborty (Jira)

[ https://issues.redhat.com/browse/WFLY-5248?page=com.atlassian.jira.plugin... ] Ranabir Chakraborty commented on WFLY-5248: ------------------------------------------- [~rob.stryker] is this issue still there? > wildfly-ejb-multi-server-app-one-ejb quickstart fails to validate in eclipse > ---------------------------------------------------------------------------- > > Key: WFLY-5248 > URL: https://issues.redhat.com/browse/WFLY-5248 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Rob Stryker > Priority: Major > > The quickstart wildfly-ejb-multi-server-app-one-ejb quickstart fails to validate. The reason seems to be as follows: > 1) jboss-ejb3.xml imports the xmlns:ci ="urn:container-interceptors:1.0" namespace. > 2) boss-ejb-container-interceptors_1_0.xsd imports jboss-ejb3-spec-2_0.xsd namespace as follows: > {code} > <xs:import namespace="http://java.sun.com/xml/ns/javaee" schemaLocation="http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd > {code} > 3) jboss-ejb3-spec-2_0.xsd imports jboss-ejb3-2_0.xsd as follows: > {code} > <xs:import namespace="http://www.jboss.com/xml/ns/javaee" schemaLocation="jboss-ejb3-2_0.xsd"/> > {code} > The use of a relative path in step 3 breaks the eclipse validator. It would be best to use full urls that point to the actual xsd file. > This fix will most likely require: > 1) Changes to jboss-ejb3-spec-2_0.xsd in whatever repository it lives in > 2) Changes to jboss-ejb3-spec-2_0.xsd on http://www.jboss.org/schema/jbossas/ > 3) Changes to jboss-ejb3-spec-2_0.xsd inside jbosstools, which typically clones all updated files living at http://www.jboss.org/schema/jbossas/ -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4806) Upgrade jboss-logmanager from 2.1.15.Final to 2.2.0.Final

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-4806?page=com.atlassian.jira.plug... ] James Perkins updated WFCORE-4806: ---------------------------------- Summary: Upgrade jboss-logmanager from 2.1.15.Final to 2.2.0.Final (was: Upgrade jboss-logmanager from 2.1.14.Final to 2.2.0.Final) > Upgrade jboss-logmanager from 2.1.15.Final to 2.2.0.Final > --------------------------------------------------------- > > Key: WFCORE-4806 > URL: https://issues.redhat.com/browse/WFCORE-4806 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > Upgrade the {{org.jboss.logmanager:jboss-logmanager}} to 2.2.0.Final. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4930) Upgrade jboss-logmanager from 2.1.14.Final to 2.1.15.Final

by James Perkins (Jira)

James Perkins created WFCORE-4930: ------------------------------------- Summary: Upgrade jboss-logmanager from 2.1.14.Final to 2.1.15.Final Key: WFCORE-4930 URL: https://issues.redhat.com/browse/WFCORE-4930 Project: WildFly Core Issue Type: Component Upgrade Components: Logging Reporter: James Perkins Assignee: James Perkins Upgrade {{org.jboss.logmanager:jboss-logmanager}} to 2.1.15.Final. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 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