April 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10310) Incorrect license link for LGPL v2.1 or later

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-10310: --------------------------------------- Summary: Incorrect license link for LGPL v2.1 or later Key: WFLY-10310 URL: https://issues.jboss.org/browse/WFLY-10310 Project: WildFly Issue Type: Bug Components: Build System Reporter: Brian Stansberry Assignee: Brian Stansberry The links on the licenses.html file point to a .html file for the license, but the actual file is .txt so the link is broken. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2198) Reduce log level for RequestCorrelator "channel is not connected" error during shutdown

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-2198?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JGRP-2198: ----------------------------------------------- Jiří Bílek <jbilek(a)redhat.com> changed the Status of [bug 1463387|https://bugzilla.redhat.com/show_bug.cgi?id=1463387] from ON_QA to VERIFIED > Reduce log level for RequestCorrelator "channel is not connected" error during shutdown > --------------------------------------------------------------------------------------- > > Key: JGRP-2198 > URL: https://issues.jboss.org/browse/JGRP-2198 > Project: JGroups > Issue Type: Bug > Reporter: Peter Palaga > Assignee: Peter Palaga > > This is a followup of JGRP-1958. > While the fix for JGRP-1958 https://github.com/belaban/JGroups/commit/03d7c93145f6a9314c2380f5ad66bdc... > removed the stack trace, the error message is still logged as SEVERE. > [~shay1680], [~jbilek] and [~dereed] all agree that the log level should be reduced to WARN. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3775) Legacy feature pack template for host-slave.xml using outdated http-interface http-upgrade-enabled config

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3775: ---------------------------------------- Summary: Legacy feature pack template for host-slave.xml using outdated http-interface http-upgrade-enabled config Key: WFCORE-3775 URL: https://issues.jboss.org/browse/WFCORE-3775 Project: WildFly Core Issue Type: Bug Components: Management Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor The template should use the child resource instead of the attribute. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-192) Include Openshift Module in Ansible Slaves

by Guilherme Baufaker Rêgo (JIRA)

Guilherme Baufaker Rêgo created SWSQE-192: --------------------------------------------- Summary: Include Openshift Module in Ansible Slaves Key: SWSQE-192 URL: https://issues.jboss.org/browse/SWSQE-192 Project: Kiali QE Issue Type: Task Reporter: Guilherme Baufaker Rêgo Assignee: Guilherme Baufaker Rêgo - New Test Mesh Stage [SWSQE-166] will require openshift pip module -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10309) Legacy feature pack host-master xml templates should put the 'host' element attributes in the correct order

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10309?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFCORE-3774 to WFLY-10309: ------------------------------------------------- Project: WildFly (was: WildFly Core) Key: WFLY-10309 (was: WFCORE-3774) Component/s: Management (was: Management) > Legacy feature pack host-master xml templates should put the 'host' element attributes in the correct order > ----------------------------------------------------------------------------------------------------------- > > Key: WFLY-10309 > URL: https://issues.jboss.org/browse/WFLY-10309 > Project: WildFly > Issue Type: Bug > Components: Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > > The 'name="master" attribute should come after the xmlns as that is the way it will be persisted. It's also the way the Galleon build will generate it, as the Galleon build is based on xml persistence by the management layer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3774) Legacy feature pack host-master xml templates should put the 'host' element attributes in the correct order

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3774: ---------------------------------------- Summary: Legacy feature pack host-master xml templates should put the 'host' element attributes in the correct order Key: WFCORE-3774 URL: https://issues.jboss.org/browse/WFCORE-3774 Project: WildFly Core Issue Type: Bug Components: Management Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor The 'name="master" attribute should come after the xmlns as that is the way it will be persisted. It's also the way the Galleon build will generate it, as the Galleon build is based on xml persistence by the management layer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3773) Legacy feature pack host-master xml template should put the 'host' element attributes in the correct order

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3773: ---------------------------------------- Summary: Legacy feature pack host-master xml template should put the 'host' element attributes in the correct order Key: WFCORE-3773 URL: https://issues.jboss.org/browse/WFCORE-3773 Project: WildFly Core Issue Type: Bug Components: Management Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor The 'name="master" attribute should come after the xmlns as that is the way it will be persisted. It's also the way the Galleon build will generate it, as the Galleon build is based on xml persistence by the management layer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3772) Elytron legacy feature pack subsystem template uses wrong attribute order for http-authentication-factory

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3772: ---------------------------------------- Summary: Elytron legacy feature pack subsystem template uses wrong attribute order for http-authentication-factory Key: WFCORE-3772 URL: https://issues.jboss.org/browse/WFCORE-3772 Project: WildFly Core Issue Type: Bug Components: Security Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Right: <http-authentication-factory name="management-http-authentication" security-domain="ManagementDomain" http-server-mechanism-factory="global"> Wrong: <http-authentication-factory name="management-http-authentication" http-server-mechanism-factory="global" security-domain="ManagementDomain"> The xsd and the persistence logic does it right; the template does it wrong so our standard config is wrong. Galleon will do it right so fixing this is basically about eliminating spurious differences between the WFCORE-3769 galleon output and the legacy output. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3771) Eliminate comments from the WildFly Core xml config files

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3771?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-3771: ---------------------------------------- Assignee: Brian Stansberry (was: Jeff Mesnil) > Eliminate comments from the WildFly Core xml config files > --------------------------------------------------------- > > Key: WFCORE-3771 > URL: https://issues.jboss.org/browse/WFCORE-3771 > Project: WildFly Core > Issue Type: Task > Components: Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > > Comments in our standard xml config files have always been frowned upon because when the user does anything to cause config persistence the comments will be lost. > Now, with Galleon the build won't generate those comments anyway. So get rid of them in the legacy stuff; they were always wrong and having them is not a meaningful build diff of legacy vs galleon. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3771) Eliminate comments from the WildFly Core xml config files

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3771: ---------------------------------------- Summary: Eliminate comments from the WildFly Core xml config files Key: WFCORE-3771 URL: https://issues.jboss.org/browse/WFCORE-3771 Project: WildFly Core Issue Type: Task Components: Management Reporter: Brian Stansberry Assignee: Jeff Mesnil Priority: Minor Comments in our standard xml config files have always been frowned upon because when the user does anything to cause config persistence the comments will be lost. Now, with Galleon the build won't generate those comments anyway. So get rid of them in the legacy stuff; they were always wrong and having them is not a meaningful build diff of legacy vs galleon. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2018