July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5500) Workaround comment exists in kie-pmml/pom.xml file while the related issues are already fixed.

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5500?page=com.atlassian.jira.plug... ] Mario Fusco resolved DROOLS-5500. --------------------------------- Resolution: Done > Workaround comment exists in kie-pmml/pom.xml file while the related issues are already fixed. > ---------------------------------------------------------------------------------------------- > > Key: DROOLS-5500 > URL: https://issues.redhat.com/browse/DROOLS-5500 > Project: Drools > Issue Type: Enhancement > Reporter: Tao Xiao > Assignee: Mario Fusco > Priority: Trivial > > In a research project, we analyzed the build file of repositories looking for comments with ready-to-be-addressed SATDs (self-admitted technical debt) that could be addressed. If the underlying issue is already resolved, the related code or comment can be removed or fixed. As we found an instance of this kind of asynchrony in kie-pmml/pom.xml, we decided to report the issue to contribute community. > A comment in drools-core/pom.xml file claims that it is workaround for > [https://github.com/mojohaus/jaxb2-maven-plugin/issues/43], and this issue has been closed long ago. > {quote} > {quote} > Comment location: [https://github.com/kiegroup/drools/blob/a8507fae382ec5d815cce03792aa18b00...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13662) Weld Conversation Context Logs when not using Conversation Context

by Matěj Novotný (Jira)

[ https://issues.redhat.com/browse/WFLY-13662?page=com.atlassian.jira.plugi... ] Matěj Novotný commented on WFLY-13662: -------------------------------------- Hi [~clerum], it looks like something is using conversation context, could even be some added internal module perhaps. Could you provide a bigger segment of the stacktrace? Or, better still, would you be able to provide a reproducer? FTR, WFLY 18 is Weld 3.1.2.Final while WFLY 20 is Weld 3.1.4.Final. Possible problematic issue could be WELD-2612, however it is hard to tell without reproducer. I am not seeing these failures in any tests weld or wfly have. > Weld Conversation Context Logs when not using Conversation Context > ------------------------------------------------------------------ > > Key: WFLY-13662 > URL: https://issues.redhat.com/browse/WFLY-13662 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, JSF > Affects Versions: 20.0.1.Final > Reporter: Cody Lerum > Assignee: Matěj Novotný > Priority: Major > > After upgrading to Widfly 20.0.1 from 18.0.1 I'm starting to receive show log errors regarding the CDI conversation context even though it is not used anywhere in the application. > These did not present in the same application in 18.0.1.Final > {code:java} > 020-07-10 15:42:47,561 ERROR [io.undertow.request] (default task-273) UT005023: Exception handling request to /s/c/voice/fax/view.xhtml: java.lang.NullPointerException2020-07-10 15:42:47,562 WARN [org.jboss.weld.Servlet] (default task-273) WELD-000717: Unable to deactivate context org.jboss.weld.module.web.context.http.LazyHttpConversationContextImpl@25333df0 when destroying request HttpServletRequestImpl [ GET /s/c/voice/fax/view.xhtml ] > 2020-07-10 15:42:48,165 WARN [org.jboss.weld.Conversation] (default task-273) WELD-000335: Conversation context is already active, most likely it was not cleaned up properly during previous request processing: HttpServletRequestImpl [ GET /i/ticket/46893 ] {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5500) Workaround comment exists in kie-pmml/pom.xml file while the related issues are already fixed.

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5500?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-5500: -------------------------------- Sprint: 2020 Week 28-30 (from Jul 6) > Workaround comment exists in kie-pmml/pom.xml file while the related issues are already fixed. > ---------------------------------------------------------------------------------------------- > > Key: DROOLS-5500 > URL: https://issues.redhat.com/browse/DROOLS-5500 > Project: Drools > Issue Type: Enhancement > Reporter: Tao Xiao > Assignee: Mario Fusco > Priority: Trivial > > In a research project, we analyzed the build file of repositories looking for comments with ready-to-be-addressed SATDs (self-admitted technical debt) that could be addressed. If the underlying issue is already resolved, the related code or comment can be removed or fixed. As we found an instance of this kind of asynchrony in kie-pmml/pom.xml, we decided to report the issue to contribute community. > A comment in drools-core/pom.xml file claims that it is workaround for > [https://github.com/mojohaus/jaxb2-maven-plugin/issues/43], and this issue has been closed long ago. > {quote} > {quote} > Comment location: [https://github.com/kiegroup/drools/blob/a8507fae382ec5d815cce03792aa18b00...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5500) Workaround comment exists in kie-pmml/pom.xml file while the related issues are already fixed.

by Tao Xiao (Jira)

Tao Xiao created DROOLS-5500: -------------------------------- Summary: Workaround comment exists in kie-pmml/pom.xml file while the related issues are already fixed. Key: DROOLS-5500 URL: https://issues.redhat.com/browse/DROOLS-5500 Project: Drools Issue Type: Enhancement Reporter: Tao Xiao Assignee: Mario Fusco In a research project, we analyzed the build file of repositories looking for comments with ready-to-be-addressed SATDs (self-admitted technical debt) that could be addressed. If the underlying issue is already resolved, the related code or comment can be removed or fixed. As we found an instance of this kind of asynchrony in kie-pmml/pom.xml, we decided to report the issue to contribute community. A comment in drools-core/pom.xml file claims that it is workaround for [https://github.com/mojohaus/jaxb2-maven-plugin/issues/43], and this issue has been closed long ago. {quote} {quote} Comment location: [https://github.com/kiegroup/drools/blob/a8507fae382ec5d815cce03792aa18b00...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-5046) ElytronToolScriptTestCase fails if environment defines _JAVA_OPTIONS environment variable

by Paul Ferraro (Jira)

Paul Ferraro created WFCORE-5046: ------------------------------------ Summary: ElytronToolScriptTestCase fails if environment defines _JAVA_OPTIONS environment variable Key: WFCORE-5046 URL: https://issues.redhat.com/browse/WFCORE-5046 Project: WildFly Core Issue Type: Bug Components: Test Suite Reporter: Paul Ferraro Assignee: Paul Ferraro If the runtime environment defines a _JAVA_OPTIONS environment variable, java likes to output: "Picked up _JAVA_OPTIONS: ..." to the console. Because this test reads the console output verbatim, it fails if the JVM outputs noise on startup. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-5045) CliScriptTestCase fails if environment defines _JAVA_OPTIONS environment variable

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFCORE-5045?page=com.atlassian.jira.plug... ] Paul Ferraro updated WFCORE-5045: --------------------------------- Description: If the runtime environment defines a _JAVA_OPTIONS environment variable, java likes to output: "Picked up _JAVA_OPTIONS: ..." to the console. Because this test reads the console output verbatim, it fails if the JVM outputs noise on startup. was: If the runtime environment defines a _JAVA_OPTIONS environment variable, java likes to output: "Picked up _JAVA_OPTIONS: ..." to the console. Because thus test reads the console output verbatim, it fails if the JVM outputs noise on startup. > CliScriptTestCase fails if environment defines _JAVA_OPTIONS environment variable > --------------------------------------------------------------------------------- > > Key: WFCORE-5045 > URL: https://issues.redhat.com/browse/WFCORE-5045 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > If the runtime environment defines a _JAVA_OPTIONS environment variable, java likes to output: "Picked up _JAVA_OPTIONS: ..." to the console. > Because this test reads the console output verbatim, it fails if the JVM outputs noise on startup. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-5045) CliScriptTestCase fails if environment defines _JAVA_OPTIONS environment variable

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFCORE-5045?page=com.atlassian.jira.plug... ] Paul Ferraro updated WFCORE-5045: --------------------------------- Description: If the runtime environment defines a _JAVA_OPTIONS environment variable, java likes to output: "Picked up _JAVA_OPTIONS: ..." to the console. Because thus test reads the console output verbatim, it fails if the JVM outputs noise on startup. was: If the runtime environment defines a _JAVA_OPTIONS environment variable, java likes to output: "Picked up _JAVA_OPTIONS: ..." to the console. Because the longCommand test reads the console output verbatim, it fails if the JVM outputs noise on startup. > CliScriptTestCase fails if environment defines _JAVA_OPTIONS environment variable > --------------------------------------------------------------------------------- > > Key: WFCORE-5045 > URL: https://issues.redhat.com/browse/WFCORE-5045 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > If the runtime environment defines a _JAVA_OPTIONS environment variable, java likes to output: "Picked up _JAVA_OPTIONS: ..." to the console. > Because thus test reads the console output verbatim, it fails if the JVM outputs noise on startup. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-5045) CliScriptTestCase fails if environment defines _JAVA_OPTIONS environment variable

by Paul Ferraro (Jira)

Paul Ferraro created WFCORE-5045: ------------------------------------ Summary: CliScriptTestCase fails if environment defines _JAVA_OPTIONS environment variable Key: WFCORE-5045 URL: https://issues.redhat.com/browse/WFCORE-5045 Project: WildFly Core Issue Type: Bug Components: Test Suite Reporter: Paul Ferraro Assignee: Paul Ferraro If the runtime environment defines a _JAVA_OPTIONS environment variable, java likes to output: "Picked up _JAVA_OPTIONS: ..." to the console. Because the longCommand test reads the console output verbatim, it fails if the JVM outputs noise on startup. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

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.13.0.CR3 (was: 1.13.0.CR2) > 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.13.0.CR3 > > > 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

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.13.0.CR3 (was: 1.13.0.CR2) > 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.13.0.CR3 > > > 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

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 2020