September 2017 - jboss-jira - Jboss List Archives

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

by James Perkins (JIRA)

James Perkins created WFLY-9306: ----------------------------------- Summary: Upgrade the wildfly-maven-plugin to 1.2.0.Final Key: WFLY-9306 URL: https://issues.jboss.org/browse/WFLY-9306 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, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3252) provide better filtering of host-exclude for prior releases

by Ken Wills (JIRA)

Ken Wills created WFCORE-3252: --------------------------------- Summary: provide better filtering of host-exclude for prior releases Key: WFCORE-3252 URL: https://issues.jboss.org/browse/WFCORE-3252 Project: WildFly Core Issue Type: Enhancement Reporter: Ken Wills Assignee: Ken Wills Fix For: 4.0.0.Alpha1 Currently a new domain controller connecting to a legacy slave will pass host-exclude values that the HostExcludeResourceDefinition enum on the slave doesn't understand. WFCORE-3226 provided a simple workaround fix to allow this to work via a transformer, but we should have a better mechanism to only send =< the slave version values from the enum, or something similar perhaps. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8990) Add unit test for CLI Capability completion

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFLY-8990?page=com.atlassian.jira.plugin.... ] Jean-Francois Denise closed WFLY-8990. -------------------------------------- Resolution: Rejected Unit test will be added in wildfly core repository. > Add unit test for CLI Capability completion > ------------------------------------------- > > Key: WFLY-8990 > URL: https://issues.jboss.org/browse/WFLY-8990 > Project: WildFly > Issue Type: Task > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > That is a follow up for WFCORE-2993. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBVFS-204) File system operations require both java.io.FilePermission and VirtualFilePermission

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBVFS-204?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBVFS-204: ----------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1464254|https://bugzilla.redhat.com/show_bug.cgi?id=1464254] from VERIFIED to CLOSED > File system operations require both java.io.FilePermission and VirtualFilePermission > ------------------------------------------------------------------------------------ > > Key: JBVFS-204 > URL: https://issues.jboss.org/browse/JBVFS-204 > Project: JBoss VFS > Issue Type: Bug > Affects Versions: 3.2.11.Final, 3.5.0.Alpha1 > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 3.2.12.Final, 3.5.0.Alpha1 > > > File system operations in org.jboss.vfs.VirtualFile check for VirtualFilePermission and then execute the particular io operation which needs java.io.FilePermission if Security Manager is enabled. Because of this a user has to duplicate each permission on a deployment for both VirtualFilePermission and FilePermission. > It should be enough to check for VirtualFilePermission and execute the io operation inside of the privileged block afterwards. > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3074) CapabilityRegistry should not use java.nio.files.Paths to manipulate capabilities

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3074?page=com.atlassian.jira.plugi... ] Jean-Francois Denise reassigned WFCORE-3074: -------------------------------------------- Assignee: Jean-Francois Denise > CapabilityRegistry should not use java.nio.files.Paths to manipulate capabilities > --------------------------------------------------------------------------------- > > Key: WFCORE-3074 > URL: https://issues.jboss.org/browse/WFCORE-3074 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Jean-Francois Denise > > Using filesystem manipulation code for things that are not related to filesystems can lead to things like WFCORE-3072. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-178) Added Shutdown Domain Option - Sprint-68

by Matt Mahoney (JIRA)

Matt Mahoney created HAWKULARQE-178: --------------------------------------- Summary: Added Shutdown Domain Option - Sprint-68 Key: HAWKULARQE-178 URL: https://issues.jboss.org/browse/HAWKULARQE-178 Project: Hawkular QE Issue Type: Task Reporter: Matt Mahoney Assignee: Michael Foley -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-173) UX Improvement - When adding a datasource - MIQ Sprint-67

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-173?page=com.atlassian.jira.pl... ] Guilherme Baufaker Rêgo resolved HAWKULARQE-173. ------------------------------------------------ Resolution: Done > UX Improvement - When adding a datasource - MIQ Sprint-67 > --------------------------------------------------------- > > Key: HAWKULARQE-173 > URL: https://issues.jboss.org/browse/HAWKULARQE-173 > Project: Hawkular QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Sunil kondkar > Attachments: Error Screen.png, Error Screen.png > > > From MIQ Sprint-67 Demo: > UX Improvement - When adding a datasource, there is a need to fetch available jdbc drivers from middleware server. If a provider is not running, do not display an exception when fetching jdbc drivers, but show a descriptive warning message and allow the user to close the wizard. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2216) IllegalFormatException in DefaultDNSResolver#getDnsContext()

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2216?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2216. ---------------------------- Resolution: Done Fixed, thanks! > IllegalFormatException in DefaultDNSResolver#getDnsContext() > ------------------------------------------------------------- > > Key: JGRP-2216 > URL: https://issues.jboss.org/browse/JGRP-2216 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.10, 4.0.5 > Reporter: Johan Vogelzang > Assignee: Bela Ban > Fix For: 4.0.7 > > > An IllegalFormatException is thrown at: > DefaultDNSResolver#getDnsContext() > {code} > log.trace("Initializing DNS Context with factory: %s and url: %s" + dnsContextFactory, dnsAddress); > {code} > should be: > {code} > log.trace("Initializing DNS Context with factory: %s and url: %s", dnsContextFactory, dnsAddress); > {code} > plus sign changed in to comma. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2216) IllegalFormatException in DefaultDNSResolver#getDnsContext()

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2216?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2216: --------------------------- Fix Version/s: (was: 3.6.14) Fixed in 4.0.7: {{DNS_PING}} does not exist in the 3.6 branch > IllegalFormatException in DefaultDNSResolver#getDnsContext() > ------------------------------------------------------------- > > Key: JGRP-2216 > URL: https://issues.jboss.org/browse/JGRP-2216 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.10, 4.0.5 > Reporter: Johan Vogelzang > Assignee: Bela Ban > Fix For: 4.0.7 > > > An IllegalFormatException is thrown at: > DefaultDNSResolver#getDnsContext() > {code} > log.trace("Initializing DNS Context with factory: %s and url: %s" + dnsContextFactory, dnsAddress); > {code} > should be: > {code} > log.trace("Initializing DNS Context with factory: %s and url: %s", dnsContextFactory, dnsAddress); > {code} > plus sign changed in to comma. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2216) IllegalFormatException in DefaultDNSResolver#getDnsContext()

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2216?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2216: --------------------------- Fix Version/s: 3.6.14 4.0.7 > IllegalFormatException in DefaultDNSResolver#getDnsContext() > ------------------------------------------------------------- > > Key: JGRP-2216 > URL: https://issues.jboss.org/browse/JGRP-2216 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.10, 4.0.5 > Reporter: Johan Vogelzang > Assignee: Bela Ban > Fix For: 3.6.14, 4.0.7 > > > An IllegalFormatException is thrown at: > DefaultDNSResolver#getDnsContext() > {code} > log.trace("Initializing DNS Context with factory: %s and url: %s" + dnsContextFactory, dnsAddress); > {code} > should be: > {code} > log.trace("Initializing DNS Context with factory: %s and url: %s", dnsContextFactory, dnsAddress); > {code} > plus sign changed in to comma. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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