August 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9255) Upgrade Migration Tool to 1.0.1.Final

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9255?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-9255: ----------------------------------- Git Pull Request: (was: https://github.com/jbossas/jboss-eap7/pull/2311) > Upgrade Migration Tool to 1.0.1.Final > ------------------------------------- > > Key: WFLY-9255 > URL: https://issues.jboss.org/browse/WFLY-9255 > Project: WildFly > Issue Type: Component Upgrade > Components: Server > Reporter: Kabir Khan > Assignee: Eduardo Martins > Priority: Blocker > Fix For: 11.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9255) Upgrade Migration Tool to 1.0.1.Final

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9255?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-9255: ----------------------------------- Fix Version/s: 11.0.0.CR1 > Upgrade Migration Tool to 1.0.1.Final > ------------------------------------- > > Key: WFLY-9255 > URL: https://issues.jboss.org/browse/WFLY-9255 > Project: WildFly > Issue Type: Component Upgrade > Components: Server > Reporter: Kabir Khan > Assignee: Eduardo Martins > Priority: Blocker > Fix For: 11.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9255) Upgrade Migration Tool to 1.0.1.Final

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9255?page=com.atlassian.jira.plugin.... ] Brian Stansberry moved JBEAP-12833 to WFLY-9255: ------------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9255 (was: JBEAP-12833) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Server (was: Migration) > Upgrade Migration Tool to 1.0.1.Final > ------------------------------------- > > Key: WFLY-9255 > URL: https://issues.jboss.org/browse/WFLY-9255 > Project: WildFly > Issue Type: Component Upgrade > Components: Server > Reporter: Kabir Khan > Assignee: Eduardo Martins > Priority: Blocker > Fix For: 11.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9252) Redundant config restore before quorum configuration

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/WFLY-9252?page=com.atlassian.jira.plugin.... ] Sande Gilda commented on WFLY-9252: ----------------------------------- [~rhusar]: I believe I added that step because I ran into an issue after playing around with other election policies, not just the one in this quickstart, and was not able to get your CLI command to work. > Redundant config restore before quorum configuration > ---------------------------------------------------- > > Key: WFLY-9252 > URL: https://issues.jboss.org/browse/WFLY-9252 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 11.0.0.Beta1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Labels: eap7.1-ok-for-CR1 > > In ER3 there is a new instruction in {{Configure a Quorum for the Singleton Policy}} to restore the singleton election policy to default configuration: > {{If you have tested other election policies that configured the singleton subsystem, see Restoring the Default Singleton Subsystem Configuration for instructions to restore the singleton election policy to the default configuration.}} > I think this step should be either removed or reworded to avoid confusion. The reasons are: > * Quorum can be specified for any election policy, not only for the default one. > * Wording {{If you have tested other election policies}} suggests that this section configures another election policy, which is not true - it only adds quorum to existing election policy. > [~rhusar], what do you think? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9254) Upgrade wildfly-arquillian to 2.1.0.Final

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-9254?page=com.atlassian.jira.plugin.... ] James Perkins moved JBEAP-12832 to WFLY-9254: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9254 (was: JBEAP-12832) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Test Suite (was: Test Suite) > Upgrade wildfly-arquillian to 2.1.0.Final > ----------------------------------------- > > Key: WFLY-9254 > URL: https://issues.jboss.org/browse/WFLY-9254 > Project: WildFly > Issue Type: Component Upgrade > Components: Test Suite > Reporter: James Perkins > Assignee: James Perkins > Priority: Blocker > > Upgrade {{wildfly-arquillian}} to 2.1.0.Final. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9253) Upgrade the wildfly-maven-plugin to 1.2.0.Final

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-9253?page=com.atlassian.jira.plugin.... ] James Perkins moved JBEAP-12831 to WFLY-9253: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9253 (was: JBEAP-12831) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Test Suite (was: Test Suite) > Upgrade the wildfly-maven-plugin to 1.2.0.Final > ----------------------------------------------- > > Key: WFLY-9253 > URL: https://issues.jboss.org/browse/WFLY-9253 > Project: WildFly > Issue Type: Component Upgrade > Components: Test Suite > Reporter: James Perkins > Assignee: James Perkins > Priority: Blocker > Fix For: 11.0.0.CR1 > > > Upgrade the {{wildfly-maven-plugin}} to version 1.2.0.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9253) Upgrade the wildfly-maven-plugin to 1.2.0.Final

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-9253?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-9253: -------------------------------- Fix Version/s: 11.0.0.CR1 > Upgrade the wildfly-maven-plugin to 1.2.0.Final > ----------------------------------------------- > > Key: WFLY-9253 > URL: https://issues.jboss.org/browse/WFLY-9253 > Project: WildFly > Issue Type: Component Upgrade > Components: Test Suite > Reporter: James Perkins > Assignee: James Perkins > Priority: Blocker > Fix For: 11.0.0.CR1 > > > Upgrade the {{wildfly-maven-plugin}} to version 1.2.0.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1344) Comment out unused logger methods

by James Perkins (JIRA)

James Perkins created ELY-1344: ---------------------------------- Summary: Comment out unused logger methods Key: ELY-1344 URL: https://issues.jboss.org/browse/ELY-1344 Project: WildFly Elytron Issue Type: Task Reporter: James Perkins Assignee: James Perkins Unused logger methods should be commented out to save on the metaspace used when the classes are loaded. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-85) Support GSS-Proxy

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-85?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse updated ELY-85: -------------------------------- Fix Version/s: 1.2.0.Beta3 (was: 1.2.0.Beta1) > Support GSS-Proxy > ----------------- > > Key: ELY-85 > URL: https://issues.jboss.org/browse/ELY-85 > Project: WildFly Elytron > Issue Type: Feature Request > Components: SASL > Reporter: Darran Lofthouse > Fix For: 1.2.0.Beta3 > > > GSS Proxy is something we should consider being able to support when running on an OS that supports it: - > https://fedorahosted.org/gss-proxy/ > The big first step will be to identify what is required to achieve this, is this something that can be solved with a custom login module or does this also impact on the Java supplied GSSAPI implementation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-63) Pluggable nonce handling strategy

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-63?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse updated ELY-63: -------------------------------- Fix Version/s: 1.2.0.Beta3 (was: 1.2.0.Beta1) > Pluggable nonce handling strategy > --------------------------------- > > Key: ELY-63 > URL: https://issues.jboss.org/browse/ELY-63 > Project: WildFly Elytron > Issue Type: Task > Reporter: Darran Lofthouse > Fix For: 1.2.0.Beta3 > > > Implement a pluggable nonce handling strategy. > At the very least we need to be able to switch to using a SecureRandom instead of Random. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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