November 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9571) Upgrade Weld to 3.0.2.Final

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-9571?page=com.atlassian.jira.plugin.... ] Martin Kouba updated WFLY-9571: ------------------------------- Description: Weld 3.0.2.Final was [released|http://weld.cdi-spec.org/news/2017/11/23/weld-302Final/] so we can update that in master WFLY. Along with this goes Weld API update to 3.0.SP2. Note that WFLY already runs Weld 3.x was: Weld 3.0.2.Final was[ released|http://weld.cdi-spec.org/news/2017/11/23/weld-302Final/] so we can update that in master WFLY. Along with this goes Weld API update to 3.0.SP2. Note that WFLY already runs Weld 3.x > Upgrade Weld to 3.0.2.Final > --------------------------- > > Key: WFLY-9571 > URL: https://issues.jboss.org/browse/WFLY-9571 > Project: WildFly > Issue Type: Component Upgrade > Components: CDI / Weld > Reporter: Matej Novotny > Assignee: Matej Novotny > Fix For: 12.0.0.Alpha1 > > > Weld 3.0.2.Final was [released|http://weld.cdi-spec.org/news/2017/11/23/weld-302Final/] so we can update that in master WFLY. > Along with this goes Weld API update to 3.0.SP2. > Note that WFLY already runs Weld 3.x -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9571) Upgrade Weld to 3.0.2.Final

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/WFLY-9571?page=com.atlassian.jira.plugin.... ] Matej Novotny updated WFLY-9571: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/10672 > Upgrade Weld to 3.0.2.Final > --------------------------- > > Key: WFLY-9571 > URL: https://issues.jboss.org/browse/WFLY-9571 > Project: WildFly > Issue Type: Component Upgrade > Components: CDI / Weld > Reporter: Matej Novotny > Assignee: Matej Novotny > Fix For: 12.0.0.Alpha1 > > > Weld 3.0.2.Final was[ released|http://weld.cdi-spec.org/news/2017/11/23/weld-302Final/] so we can update that in master WFLY. > Along with this goes Weld API update to 3.0.SP2. > Note that WFLY already runs Weld 3.x -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9571) Upgrade Weld to 3.0.2.Final

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/WFLY-9571?page=com.atlassian.jira.plugin.... ] Matej Novotny updated WFLY-9571: -------------------------------- Description: Weld 3.0.2.Final was[ released|http://weld.cdi-spec.org/news/2017/11/23/weld-302Final/] so we can update that in master WFLY. Along with this goes Weld API update to 3.0.SP2. Note that WFLY already runs Weld 3.x was: Weld 3.0.2.Final was[ released|http://weld.cdi-spec.org/news/2017/11/23/weld-302Final/] so we can update that in master WFLY. Note that WFLY already runs Weld 3.0.1.Final. > Upgrade Weld to 3.0.2.Final > --------------------------- > > Key: WFLY-9571 > URL: https://issues.jboss.org/browse/WFLY-9571 > Project: WildFly > Issue Type: Component Upgrade > Components: CDI / Weld > Reporter: Matej Novotny > Assignee: Matej Novotny > Fix For: 12.0.0.Alpha1 > > > Weld 3.0.2.Final was[ released|http://weld.cdi-spec.org/news/2017/11/23/weld-302Final/] so we can update that in master WFLY. > Along with this goes Weld API update to 3.0.SP2. > Note that WFLY already runs Weld 3.x -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9571) Upgrade Weld to 3.0.2.Final

by Matej Novotny (JIRA)

Matej Novotny created WFLY-9571: ----------------------------------- Summary: Upgrade Weld to 3.0.2.Final Key: WFLY-9571 URL: https://issues.jboss.org/browse/WFLY-9571 Project: WildFly Issue Type: Component Upgrade Components: CDI / Weld Reporter: Matej Novotny Assignee: Matej Novotny Fix For: 12.0.0.Alpha1 Weld 3.0.2.Final was[ released|http://weld.cdi-spec.org/news/2017/11/23/weld-302Final/] so we can update that in master WFLY. Note that WFLY already runs Weld 3.0.1.Final. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2122) Error when drl file is opened with in project with runtime classes

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2122?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-2122: -------------------------------- Sprint: 2017 Week 47-48 > Error when drl file is opened with in project with runtime classes > ------------------------------------------------------------------- > > Key: DROOLS-2122 > URL: https://issues.jboss.org/browse/DROOLS-2122 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Affects Versions: 7.3.0.Final > Environment: DevstudioIS 11.1.0.Beta1 > Brms 6.4.6.GA > Reporter: Tomas David > Assignee: Mario Fusco > Priority: Blocker > Fix For: 7.5.0.Final > > Attachments: Screenshot from 2017-11-09 09-55-05.png, devstudiolog.log > > > If new drools project is created with build using Java and Drools classes, error is displayed after drl file is opened. > This blocks also other functions like add a breakpoint or show content assist menu. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9570) ClientCompatibilityUnitTestCase freeze with non-"en_US.UTF-8" locale settings

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-9570?page=com.atlassian.jira.plugin.... ] Lin Gao deleted WFLY-9570: -------------------------- > ClientCompatibilityUnitTestCase freeze with non-"en_US.UTF-8" locale settings > ----------------------------------------------------------------------------- > > Key: WFLY-9570 > URL: https://issues.jboss.org/browse/WFLY-9570 > Project: WildFly > Issue Type: Bug > Reporter: Lin Gao > Assignee: Lin Gao > Original Estimate: 3 days > Remaining Estimate: 3 days > > *Description of problem:* > ClientCompatibilityUnitTestCase freeze with non-"en_US.UTF-8" locale settings. These LANG are affected: > * de_DE.UTF-8 > * es_ES.UTF-8 > * fr_FR.UTF-8 > * ja_JP.UTF-8 > * pt_BR.UTF-8 > * zh_CN.UTF-8 > These test methods are affected: > * testCore100Final > * testCore100FinalHttp > * testCore101Final > * testCore101FinalHttp > Workaround: Add this line to createClient method od ClientCompatibilityUnitTestCase: > {code:java}classLoaderBuilder.addParentFirstClassPattern("org.jboss.as.protocol.logging.ProtocolLogger");{code} > This could relates with JBEAP-12673 or JBEAP-12818 > *How reproducible:* > Always > *Steps to Reproduce:* > # export LANG=de_DE.UTF-8 > # mvn install -B -fae -Dmaven.test.failure.ignore=true -llr -Dts.basic -Djboss.dist=$JBOSS_DIST -Dtest=ClientCompatibilityUnitTestCase -DfailIfNoTests=false -DtestLogToFile=false > *Actual results:* > {noformat} > Exception in thread "Remoting "management-client" task-5" java.lang.NoClassDefFoundError: Could not initialize class org.jboss.as.protocol.logging.ProtocolLogger > at org.jboss.as.protocol.mgmt.ManagementChannelReceiver.handleMessage(ManagementChannelReceiver.java:103) > at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:463) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {noformat} > *Expected results:* > No errors -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9570) ClientCompatibilityUnitTestCase freeze with non-"en_US.UTF-8" locale settings

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-9570?page=com.atlassian.jira.plugin.... ] Lin Gao moved JBEAP-13843 to WFLY-9570: --------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9570 (was: JBEAP-13843) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Test Suite (was: Test Suite) Affects Version/s: (was: 7.1.0.CR1) > ClientCompatibilityUnitTestCase freeze with non-"en_US.UTF-8" locale settings > ----------------------------------------------------------------------------- > > Key: WFLY-9570 > URL: https://issues.jboss.org/browse/WFLY-9570 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Lin Gao > Assignee: Lin Gao > Original Estimate: 3 days > Remaining Estimate: 3 days > > *Description of problem:* > ClientCompatibilityUnitTestCase freeze with non-"en_US.UTF-8" locale settings. These LANG are affected: > * de_DE.UTF-8 > * es_ES.UTF-8 > * fr_FR.UTF-8 > * ja_JP.UTF-8 > * pt_BR.UTF-8 > * zh_CN.UTF-8 > These test methods are affected: > * testCore100Final > * testCore100FinalHttp > * testCore101Final > * testCore101FinalHttp > Workaround: Add this line to createClient method od ClientCompatibilityUnitTestCase: > {code:java}classLoaderBuilder.addParentFirstClassPattern("org.jboss.as.protocol.logging.ProtocolLogger");{code} > This could relates with JBEAP-12673 or JBEAP-12818 > *How reproducible:* > Always > *Steps to Reproduce:* > # export LANG=de_DE.UTF-8 > # mvn install -B -fae -Dmaven.test.failure.ignore=true -llr -Dts.basic -Djboss.dist=$JBOSS_DIST -Dtest=ClientCompatibilityUnitTestCase -DfailIfNoTests=false -DtestLogToFile=false > *Actual results:* > {noformat} > Exception in thread "Remoting "management-client" task-5" java.lang.NoClassDefFoundError: Could not initialize class org.jboss.as.protocol.logging.ProtocolLogger > at org.jboss.as.protocol.mgmt.ManagementChannelReceiver.handleMessage(ManagementChannelReceiver.java:103) > at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:463) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {noformat} > *Expected results:* > No errors -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9563) Integrate KUBE_PING discovery protocol

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9563?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9563: --------------------------------- Fix Version/s: 12.0.0.Alpha1 > Integrate KUBE_PING discovery protocol > -------------------------------------- > > Key: WFLY-9563 > URL: https://issues.jboss.org/browse/WFLY-9563 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 12.0.0.Alpha1 > > > https://github.com/jgroups-extras/jgroups-kubernetes -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2152) JDK9: Upgrade mockito, gwtmockito and powermock

by Petr Široký (JIRA)

Petr Široký created DROOLS-2152: ----------------------------------- Summary: JDK9: Upgrade mockito, gwtmockito and powermock Key: DROOLS-2152 URL: https://issues.jboss.org/browse/DROOLS-2152 Project: Drools Issue Type: Component Upgrade Components: build Affects Versions: 7.4.1.Final Reporter: Petr Široký Assignee: Petr Široký Currently used versions of mockito (1.10.19), gwtmockito (1.1.6) and powermock (1.6.3) are _not_ compatible with Java 9. All of these need to upgraded, ideally all at once as they rely on each other and e.g. mockito 2.x does not work with powermock 1.x and vice versa. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2151) DMN default disable Runtime type-check, provide flag for explicit enablement

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-2151: -------------------------------------- Summary: DMN default disable Runtime type-check, provide flag for explicit enablement Key: DROOLS-2151 URL: https://issues.jboss.org/browse/DROOLS-2151 Project: Drools Issue Type: Bug Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 November 2017