September 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2957) Need plugin for Intellij Community

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2957?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-2957. --------------------------------- Resolution: Rejected The plugin already exists, see https://stackoverflow.com/questions/39534153/drools-support-in-intellij-idea > Need plugin for Intellij Community > ---------------------------------- > > Key: DROOLS-2957 > URL: https://issues.jboss.org/browse/DROOLS-2957 > Project: Drools > Issue Type: Feature Request > Environment: I am using Intellij Community 2017.2. > I would like to have a drools project in it. > There is no available plugin. > Reporter: Ayala r > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11054) Port JGroups subsystem to use generic parser/writer from wildfly-core

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-11054: ----------------------------------- Summary: Port JGroups subsystem to use generic parser/writer from wildfly-core Key: WFLY-11054 URL: https://issues.jboss.org/browse/WFLY-11054 Project: WildFly Issue Type: Task Components: Clustering Affects Versions: 14.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Port JGroups subsystem to use generic parser/writer from wildfly-core. Without WFCORE-3939, a new schema will need to be created that conforms to the limitations of PersistentResourceXMLParser. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11053) Port singleton subsystem to use generic parser/writer from wildfly-core

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-11053: ----------------------------------- Summary: Port singleton subsystem to use generic parser/writer from wildfly-core Key: WFLY-11053 URL: https://issues.jboss.org/browse/WFLY-11053 Project: WildFly Issue Type: Task Components: Clustering Affects Versions: 14.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Port singleton subsystem to use generic parser/writer from wildfly-core. Without WFCORE-3939, a new schema will need to be created that conforms to the limitations of PersistentResourceXMLParser. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11052) Set journal-pool-files default value to 10

by ehsavoie Hugonnet (JIRA)

ehsavoie Hugonnet created WFLY-11052: ---------------------------------------- Summary: Set journal-pool-files default value to 10 Key: WFLY-11052 URL: https://issues.jboss.org/browse/WFLY-11052 Project: WildFly Issue Type: Enhancement Components: JMS Affects Versions: 14.0.0.Final Reporter: ehsavoie Hugonnet Assignee: ehsavoie Hugonnet Update the default value to 10 as -1 creates a warning with Artemis 2.6.x -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4120) It is possible add modules as extensions when they are not really an extension

by Yeray Borges (JIRA)

Yeray Borges created WFCORE-4120: ------------------------------------ Summary: It is possible add modules as extensions when they are not really an extension Key: WFCORE-4120 URL: https://issues.jboss.org/browse/WFCORE-4120 Project: WildFly Core Issue Type: Bug Components: Management Affects Versions: 7.0.0.Alpha1 Reporter: Yeray Borges Assignee: Yeray Borges Priority: Minor The {{ExtensionAddHandler}} is not checking that the module that is being added as extension really has an Extension service. That means we can do odd things like: {{domain@localhost:9990 /] /extension=io.netty:add}} This operation completes successfully and io.netty is added to the extensions section in the configuration files, which is incorrect. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4049) Deactivate modular jdk properties we used in the past for workarounds.

by Martin Švehla (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4049?page=com.atlassian.jira.plugi... ] Martin Švehla updated WFCORE-4049: ---------------------------------- Labels: Java11 jdk11 (was: jdk11) > Deactivate modular jdk properties we used in the past for workarounds. > ---------------------------------------------------------------------- > > Key: WFCORE-4049 > URL: https://issues.jboss.org/browse/WFCORE-4049 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Reporter: Richard Opalka > Assignee: Richard Opalka > Labels: Java11, jdk11 > Fix For: 6.0.0.Final > > > In the past we used the following properties: > -Dsun.util.logging.disableCallerCheck=true > -Djdk.attach.allowAttachSelf=true > to activate some workarounds on modular JDKs. > These workarounds are not needed anymore. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4000) Domain tests fail on JDK11 because of missing java.se module

by Martin Švehla (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4000?page=com.atlassian.jira.plugi... ] Martin Švehla updated WFCORE-4000: ---------------------------------- Labels: Java11 blocker-WF14 jdk11 (was: blocker-WF14 jdk11) > Domain tests fail on JDK11 because of missing java.se module > ------------------------------------------------------------ > > Key: WFCORE-4000 > URL: https://issues.jboss.org/browse/WFCORE-4000 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 6.0.0.Alpha5 > Reporter: Richard Opalka > Assignee: Richard Opalka > Labels: Java11, blocker-WF14, jdk11 > Fix For: 6.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4039) Fix JvmOptionsBuilderFactory JDK decision logic

by Martin Švehla (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4039?page=com.atlassian.jira.plugi... ] Martin Švehla updated WFCORE-4039: ---------------------------------- Labels: Java11 blocker-WF14 jdk11 (was: blocker-WF14 jdk11) > Fix JvmOptionsBuilderFactory JDK decision logic > ----------------------------------------------- > > Key: WFCORE-4039 > URL: https://issues.jboss.org/browse/WFCORE-4039 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Richard Opalka > Assignee: Richard Opalka > Labels: Java11, blocker-WF14, jdk11 > Fix For: 6.0.0.Final > > > JvmOptionsBuilderFactory uses wrong JDK to detect if server is going to be running on JDK8 or above. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4002) JDK11 Some security tests fail on closed channel exception

by Martin Švehla (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4002?page=com.atlassian.jira.plugi... ] Martin Švehla updated WFCORE-4002: ---------------------------------- Labels: Java11 jdk11 (was: jdk11) > JDK11 Some security tests fail on closed channel exception > ---------------------------------------------------------- > > Key: WFCORE-4002 > URL: https://issues.jboss.org/browse/WFCORE-4002 > Project: WildFly Core > Issue Type: Bug > Components: Security, Test Suite > Affects Versions: 6.0.0.Alpha5 > Reporter: Richard Opalka > Assignee: Jan Kalina > Priority: Blocker > Labels: Java11, jdk11 > Fix For: 7.0.0.Alpha2 > > > With latest JDK11 (build 11-ea+25) the following tests fail due to closed channel exception: > * domain-management/src/test/java/org/jboss/as/domain/management/security/auditlog/AuditLogHandlerBootEnabledTestCase.java > * testsuite/domain/src/test/java/org/jboss/as/test/integration/domain/HTTPSManagementInterfaceTestCase.java > * testsuite/elytron/src/test/java/org/wildfly/test/integration/elytron/sasl/mgmt/KerberosNativeMgmtSaslTestCase.java > * testsuite/elytron/src/test/java/org/wildfly/test/integration/elytron/sasl/mgmt/ScramPlusMgmtSaslTestCase.java > * testsuite/manualmode/src/test/java/org/wildfly/core/test/standalone/mgmt/HTTPSManagementInterfaceTestCase.java > Is there a known SSL issue in JDK11? Could somebody from our security team investigate this issue? > When these tests will start passing WFCORE test suite will be passing 100% of tests on JDK11. > Potential investigator from our security team may want to include this PR: > https://github.com/wildfly/wildfly-core/pull/3420 > to fix known JDK11 issues. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4001) Eliminate --illegal-access option from WildFly

by Martin Švehla (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4001?page=com.atlassian.jira.plugi... ] Martin Švehla updated WFCORE-4001: ---------------------------------- Labels: Java11 blocker-WF14 jdk11 (was: blocker-WF14 jdk11) > Eliminate --illegal-access option from WildFly > ---------------------------------------------- > > Key: WFCORE-4001 > URL: https://issues.jboss.org/browse/WFCORE-4001 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 6.0.0.Alpha5 > Reporter: Richard Opalka > Assignee: Richard Opalka > Labels: Java11, blocker-WF14, jdk11 > Fix For: 6.0.0.CR2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 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 September 2018