April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (LOGMGR-250) Upgrade the maven-compiler-plugin from 3.7.0-jboss-1 to 3.8.0-jboss-2

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-250?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-250: --------------------------------- Git Pull Request: https://github.com/jboss-logging/jboss-logmanager/pull/244 (was: https://github.com/jboss-logging/jboss-logmanager/pull/243) > Upgrade the maven-compiler-plugin from 3.7.0-jboss-1 to 3.8.0-jboss-2 > --------------------------------------------------------------------- > > Key: LOGMGR-250 > URL: https://issues.jboss.org/browse/LOGMGR-250 > Project: JBoss Log Manager > Issue Type: Component Upgrade > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Fix For: 2.1.9.Final > > > Upgrade the maven-compiler-plugin from 3.7.0-jboss-1 to 3.8.0-jboss-2 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-249) Upgrade byteman from 4.0.4 to 4.0.6

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-249?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-249: --------------------------------- Git Pull Request: https://github.com/jboss-logging/jboss-logmanager/pull/244 (was: https://github.com/jboss-logging/jboss-logmanager/pull/243) > Upgrade byteman from 4.0.4 to 4.0.6 > ----------------------------------- > > Key: LOGMGR-249 > URL: https://issues.jboss.org/browse/LOGMGR-249 > Project: JBoss Log Manager > Issue Type: Component Upgrade > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Fix For: 2.1.9.Final > > > Upgrade byteman 4.0.4 to 4.0.6 which is used for tests only. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-250) Upgrade the maven-compiler-plugin from 3.7.0-jboss-1 to 3.8.0-jboss-2

by James Perkins (Jira)

James Perkins created LOGMGR-250: ------------------------------------ Summary: Upgrade the maven-compiler-plugin from 3.7.0-jboss-1 to 3.8.0-jboss-2 Key: LOGMGR-250 URL: https://issues.jboss.org/browse/LOGMGR-250 Project: JBoss Log Manager Issue Type: Component Upgrade Reporter: James Perkins Assignee: James Perkins Upgrade the maven-compiler-plugin from 3.7.0-jboss-1 to 3.8.0-jboss-2 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-249) Upgrade byteman from 4.0.4 to 4.0.6

by James Perkins (Jira)

James Perkins created LOGMGR-249: ------------------------------------ Summary: Upgrade byteman from 4.0.4 to 4.0.6 Key: LOGMGR-249 URL: https://issues.jboss.org/browse/LOGMGR-249 Project: JBoss Log Manager Issue Type: Component Upgrade Reporter: James Perkins Assignee: James Perkins Upgrade byteman 4.0.4 to 4.0.6 which is used for tests only. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-248) Upgrade jboss-modules from 1.7.0.Final to 1.9.0.Final

by James Perkins (Jira)

James Perkins created LOGMGR-248: ------------------------------------ Summary: Upgrade jboss-modules from 1.7.0.Final to 1.9.0.Final Key: LOGMGR-248 URL: https://issues.jboss.org/browse/LOGMGR-248 Project: JBoss Log Manager Issue Type: Component Upgrade Reporter: James Perkins Assignee: James Perkins Upgrade {{org.jboss.modules:jboss-modules}} from 1.7.0.Final to 1.9.0.Final. This kind of upgrade is not usually done in a micro release, however this should be safe. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4419) Remove deprecated ParseUtil methods

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4419?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-4419: ------------------------------------- Description: Remove methods deprecated in WFCORE-4418. When this is done the WFLYCTL0107 message method it calls should also be commented out. was:Remove methods deprecated in WFCORE-4418. > Remove deprecated ParseUtil methods > ----------------------------------- > > Key: WFCORE-4419 > URL: https://issues.jboss.org/browse/WFCORE-4419 > Project: WildFly Core > Issue Type: Task > Components: Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 11.0.0.Beta1 > > > Remove methods deprecated in WFCORE-4418. > When this is done the WFLYCTL0107 message method it calls should also be commented out. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4420) ParseUtil.readProperty incorrectly checks for XMLConstants.NULL_NS_URI

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4420: ---------------------------------------- Summary: ParseUtil.readProperty incorrectly checks for XMLConstants.NULL_NS_URI Key: WFCORE-4420 URL: https://issues.jboss.org/browse/WFCORE-4420 Project: WildFly Core Issue Type: Bug Components: Management Reporter: Brian Stansberry Assignee: Brian Stansberry This will always return false: if (uri != null&&!"".equals(XMLConstants.NULL_NS_URI)) The second test should use 'uri', not '""'. (The value of XMLConstants.NULL_NS_URI is '""'). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3887) Smarter range validation error messages

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-3887?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-3887: ------------------------------------------ [~michpetrov] +1. Thanks. WFLYCTL0107 is still used by ParseUtil.parseBoundedIntegerAttribute, but that method is unused, and I'm going to deprecate it (WFCORE-4418) and later remove it (WFCORE-4419). > Smarter range validation error messages > --------------------------------------- > > Key: WFCORE-3887 > URL: https://issues.jboss.org/browse/WFCORE-3887 > Project: WildFly Core > Issue Type: Enhancement > Components: Management > Reporter: Brian Stansberry > Assignee: Michal Petrov > Priority: Minor > > A message like this is kind of silly: "Value must be between 0 and 9007199254740991". > Smarter would be the ParameterValidator code that detects the message checking if the range max is Integer.MAX_INT (for an int) or Long.MAX_LONG (for a long) and if the bad value is below the max, just saying the equivalent of "Value must be greater than %d". -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4419) Remove deprecated ParseUtil methods

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4419: ---------------------------------------- Summary: Remove deprecated ParseUtil methods Key: WFCORE-4419 URL: https://issues.jboss.org/browse/WFCORE-4419 Project: WildFly Core Issue Type: Task Components: Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 11.0.0.Beta1 Remove methods deprecated in WFCORE-4418. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4418) Deprecate unused ParseUtil methods

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4418: ---------------------------------------- Summary: Deprecate unused ParseUtil methods Key: WFCORE-4418 URL: https://issues.jboss.org/browse/WFCORE-4418 Project: WildFly Core Issue Type: Task Components: Management Reporter: Brian Stansberry Assignee: Brian Stansberry The ParseUtil class has a few unused static methods that date back to the days when there was a lot more custom parsing vs using AttributeDefinition. Deprecate these so we can clean them out -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 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 April 2019