February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBLOGGING-130) Choose and define an Automatic-Module-Name manifest entry

by Sanne Grinovero (JIRA)

Sanne Grinovero created JBLOGGING-130: ----------------------------------------- Summary: Choose and define an Automatic-Module-Name manifest entry Key: JBLOGGING-130 URL: https://issues.jboss.org/browse/JBLOGGING-130 Project: JBoss Logging Issue Type: Enhancement Reporter: Sanne Grinovero Assignee: James Perkins Fix For: 3.3.2.Final Would be great for JBoss Logging to define an {{Automatic-Module-Name}}, as many other projects depend on it, so that some can start releasing proper Jigsaw modules. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9815) Remove configadmin subsystem

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9815?page=com.atlassian.jira.plugin.... ] Tomaz Cerar closed WFLY-9815. ----------------------------- Assignee: (was: Tomaz Cerar) Resolution: Won't Do > Remove configadmin subsystem > ---------------------------- > > Key: WFLY-9815 > URL: https://issues.jboss.org/browse/WFLY-9815 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Tomaz Cerar > > ConfigAdmin subsystem was part of OSGi subsystem at the time. > It has no usage outside of osgi and we forgot to remove it when we removed OSGi -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9815) Remove configadmin subsystem

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9815?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-9815: ---------------------------------------- We neglected to remove the extension from our standard EAP 6.4 configs, so we cannot remove this extension until we drop support for 6.4 > Remove configadmin subsystem > ---------------------------- > > Key: WFLY-9815 > URL: https://issues.jboss.org/browse/WFLY-9815 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > > ConfigAdmin subsystem was part of OSGi subsystem at the time. > It has no usage outside of osgi and we forgot to remove it when we removed OSGi -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9819) Upgrade Infinispan to 9.1.6.Final

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-9819: ---------------------------------- Summary: Upgrade Infinispan to 9.1.6.Final Key: WFLY-9819 URL: https://issues.jboss.org/browse/WFLY-9819 Project: WildFly Issue Type: Component Upgrade Components: Clustering Affects Versions: 11.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9815) Remove configadmin subsystem

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFLY-9815?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda commented on WFLY-9815: ----------------------------------------- OK, sounds good, I have no objections to removal now. > Remove configadmin subsystem > ---------------------------- > > Key: WFLY-9815 > URL: https://issues.jboss.org/browse/WFLY-9815 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > > ConfigAdmin subsystem was part of OSGi subsystem at the time. > It has no usage outside of osgi and we forgot to remove it when we removed OSGi -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9815) Remove configadmin subsystem

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9815?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-9815: ----------------------------------- we removed OSGI completely quite some time ago, no mixed-domain support for it or anything. ConfigAdmin cannot exist without osgi, and has no use beyond it. We should have removed it at same time as OSGI, but we missed it. > Remove configadmin subsystem > ---------------------------- > > Key: WFLY-9815 > URL: https://issues.jboss.org/browse/WFLY-9815 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > > ConfigAdmin subsystem was part of OSGi subsystem at the time. > It has no usage outside of osgi and we forgot to remove it when we removed OSGi -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3556) Unexpected output with grep '^no\(fork\|group\)'

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3556?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-3556: ---------------------------------------------- In order for bash grep command to accept echo nofork | grep '^no(fork|group)' you need to add the -E option, so : echo nofork | grep -E '^no(fork|group)' Escaping the parenthesis is a syntax item to advertise that this is a group when not using the extended pattern. I think that we should keep it as it is, there is no need to escape characters that we don't want to see escaped to comply with a behaviour of grep. > Unexpected output with grep '^no\(fork\|group\)' > ------------------------------------------------ > > Key: WFCORE-3556 > URL: https://issues.jboss.org/browse/WFCORE-3556 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Katerina Novotna > Assignee: Jean-Francois Denise > > *Description of problem:* > Aesh grep command doesn't return expected result. The same command with bash grep gives 'nofork' result. > *Actual results:* > [standalone@embedded /] echo nofork | grep '^no\(fork\|group\)' > [standalone@embedded /] > *Expected results:* > [standalone@embedded /] echo nofork | grep '^no\(fork\|group\)' > [standalone@embedded /] nofork -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9815) Remove configadmin subsystem

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFLY-9815?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda edited comment on WFLY-9815 at 2/13/18 9:25 AM: ------------------------------------------------------------------ So no problem to mixed domain etc ? Also question about deprecation of this thing. Can be deprecation of OSGi considered as enough for deprecation and removal of configadmin? [~kabirkhan] wdyt? was (Author: rsvoboda): So no problem to mixed domain etc ? > Remove configadmin subsystem > ---------------------------- > > Key: WFLY-9815 > URL: https://issues.jboss.org/browse/WFLY-9815 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > > ConfigAdmin subsystem was part of OSGi subsystem at the time. > It has no usage outside of osgi and we forgot to remove it when we removed OSGi -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9815) Remove configadmin subsystem

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFLY-9815?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda commented on WFLY-9815: ----------------------------------------- So no problem to mixed domain etc ? > Remove configadmin subsystem > ---------------------------- > > Key: WFLY-9815 > URL: https://issues.jboss.org/browse/WFLY-9815 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > > ConfigAdmin subsystem was part of OSGi subsystem at the time. > It has no usage outside of osgi and we forgot to remove it when we removed OSGi -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1496) Test PKCS12 KeystoreCredentialStore on non-Oracle JDKs

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1496?page=com.atlassian.jira.plugin.s... ] Jan Kalina updated ELY-1496: ---------------------------- Description: As part of ELY-1494 was disabled testing with PKCS12 KeyStore on non-oracle JDKs, because following problems: * IBM and HP (and some older Oracle too) requires provider in signed JAR, which fails on directory of classes used by surefire/junit elytron tests (see ELY-1494) * * IBM does not allow storing custom objects in PKCS12 KeyStore - allows predefined set of specs/algorithms - this cannot be workarounded currently (see discussion in ELY-1295) This testing should be re-enabled if this will be fixed in mentioned JDKs. The first problem can be solved on our side: * rework junit testing to operate on generated (and possibly signed) elytron JAR * test this from different module, outside of elytron - when elytron is dependency, it is packed in JAR was: As part of ELY-1494 was disabled testing with PKCS12 KeyStore on non-oracle JDKs, because following problems: * IBM and HP (and some older Oracle too) requires provider in signed JAR, which fails on directory of classes used by surefire/junit elytron tests (see ELY-1494) * * IBM does not allow storing custom objects in PKCS12 KeyStore - allows predefined set of specs/algorithms - this cannot be workarounded currently (see discussion in ELY-1295) This testing should be re-enabled if this will be fixed in mentioned JDKs. The first problem can be solved on our side too: * rework junit testing to operate on generated (and possibly signed) elytron JAR * test this from different module, outside of elytron - when elytron is dependency, it is packed in JAR > Test PKCS12 KeystoreCredentialStore on non-Oracle JDKs > ------------------------------------------------------ > > Key: ELY-1496 > URL: https://issues.jboss.org/browse/ELY-1496 > Project: WildFly Elytron > Issue Type: Task > Components: Credential Store > Affects Versions: 1.2.0.Beta11 > Reporter: Jan Kalina > Priority: Minor > > As part of ELY-1494 was disabled testing with PKCS12 KeyStore on non-oracle JDKs, because following problems: > * IBM and HP (and some older Oracle too) requires provider in signed JAR, which fails on directory of classes used by surefire/junit elytron tests (see ELY-1494) > * * IBM does not allow storing custom objects in PKCS12 KeyStore - allows predefined set of specs/algorithms - this cannot be workarounded currently (see discussion in ELY-1295) > This testing should be re-enabled if this will be fixed in mentioned JDKs. > The first problem can be solved on our side: > * rework junit testing to operate on generated (and possibly signed) elytron JAR > * test this from different module, outside of elytron - when elytron is dependency, it is packed in JAR -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 February 2018