November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1902) Error messages from CLI batch should be more informative

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1902?page=com.atlassian.jira.plugi... ] Marek Kopecký commented on WFCORE-1902: --------------------------------------- Ok, thank you. I created JBEAP-7319. > Error messages from CLI batch should be more informative > -------------------------------------------------------- > > Key: WFCORE-1902 > URL: https://issues.jboss.org/browse/WFCORE-1902 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Affects Versions: 3.0.0.Alpha10 > Reporter: Marek Kopecký > Assignee: Jean-Francois Denise > Labels: user_experience > > *Description of problem:* > Error messages from CLI batch should be more informative > *Steps to Reproduce:* > {noformat} > cat <<EOF >a > batch > :read-attribute(name=product-version) > :read-attribute(name=product-name) > :read-attribute(name=nonsence) > :read-attribute(name=product-name) > run-batch > EOF > ./jboss-cli.sh -c --file=a > {noformat} > *Actual results:* > {noformat} > The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-3" => "WFLYCTL0201: Unknown attribute 'nonsence'"}} > {noformat} > *Expected results:* > I can imagine content like following could be helpful for troubleshooting: > {noformat} > { > "WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => { > "Operation step-3" => { > "operation" => ":read-attribute(name=nonsence)" > "response" => "WFLYCTL0201: Unknown attribute 'nonsence'" > } > } > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1902) Error messages from CLI batch should be more informative

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1902?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-1902: ---------------------------------------------- This will be implemented in 7.1.0. This is not a big change. > Error messages from CLI batch should be more informative > -------------------------------------------------------- > > Key: WFCORE-1902 > URL: https://issues.jboss.org/browse/WFCORE-1902 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Affects Versions: 3.0.0.Alpha10 > Reporter: Marek Kopecký > Assignee: Jean-Francois Denise > Labels: user_experience > > *Description of problem:* > Error messages from CLI batch should be more informative > *Steps to Reproduce:* > {noformat} > cat <<EOF >a > batch > :read-attribute(name=product-version) > :read-attribute(name=product-name) > :read-attribute(name=nonsence) > :read-attribute(name=product-name) > run-batch > EOF > ./jboss-cli.sh -c --file=a > {noformat} > *Actual results:* > {noformat} > The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-3" => "WFLYCTL0201: Unknown attribute 'nonsence'"}} > {noformat} > *Expected results:* > I can imagine content like following could be helpful for troubleshooting: > {noformat} > { > "WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => { > "Operation step-3" => { > "operation" => ":read-attribute(name=nonsence)" > "response" => "WFLYCTL0201: Unknown attribute 'nonsence'" > } > } > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2129) Schema generation fails on JDK9

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/JGRP-2129?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated JGRP-2129: --------------------------------- Issue Type: Task (was: Component Upgrade) > Schema generation fails on JDK9 > ------------------------------- > > Key: JGRP-2129 > URL: https://issues.jboss.org/browse/JGRP-2129 > Project: JGroups > Issue Type: Task > Reporter: Radoslav Husar > Assignee: Bela Ban > Priority: Minor > Labels: jdk9 > Fix For: 4.1 > > > Not going to be a problem for a while until base is compiled with JDK9 by default, but just in case. > {noformat} > main: > [mkdir] Created dir: /Users/rhusar/git/jgroups/target/schema > [java] java.lang.ExceptionInInitializerError > [java] at org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:194) > [java] at org.apache.tools.ant.taskdefs.Java.run(Java.java:771) > [java] at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:221) > [java] at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:135) > [java] at org.apache.tools.ant.taskdefs.Java.execute(Java.java:108) > [java] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) > [java] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-ea/Native Method) > [java] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@9-ea/NativeMethodAccessorImpl.java:62) > [java] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-ea/DelegatingMethodAccessorImpl.java:43) > [java] at java.lang.reflect.Method.invoke(java.base@9-ea/Method.java:537) > [java] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) > [java] at org.apache.tools.ant.Task.perform(Task.java:348) > [java] at org.apache.tools.ant.Target.execute(Target.java:390) > [java] at org.apache.tools.ant.Target.performTasks(Target.java:411) > [java] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399) > [java] at org.apache.tools.ant.Project.executeTarget(Project.java:1368) > [java] at org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:327) > [java] at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) > [java] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) > [java] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > [java] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > [java] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > [java] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > [java] at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > [java] at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > [java] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > [java] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > [java] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > [java] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) > [java] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) > [java] at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) > [java] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-ea/Native Method) > [java] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@9-ea/NativeMethodAccessorImpl.java:62) > [java] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-ea/DelegatingMethodAccessorImpl.java:43) > [java] at java.lang.reflect.Method.invoke(java.base@9-ea/Method.java:537) > [java] at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > [java] at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > [java] at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > [java] at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > [java] Caused by: java.lang.ExceptionInInitializerError > [java] at org.jgroups.conf.ClassConfigurator.<clinit>(ClassConfigurator.java:56) > [java] at org.jgroups.protocols.ASYM_ENCRYPT.<clinit>(ASYM_ENCRYPT.java:55) > [java] at java.lang.Class.forName0(java.base@9-ea/Native Method) > [java] at java.lang.Class.forName(java.base@9-ea/Class.java:291) > [java] at org.jgroups.util.XMLSchemaGenerator.getClasses(XMLSchemaGenerator.java:127) > [java] at org.jgroups.util.XMLSchemaGenerator.generateProtocolSchema(XMLSchemaGenerator.java:106) > [java] at org.jgroups.util.XMLSchemaGenerator.main(XMLSchemaGenerator.java:80) > [java] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-ea/Native Method) > [java] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@9-ea/NativeMethodAccessorImpl.java:62) > [java] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-ea/DelegatingMethodAccessorImpl.java:43) > [java] at java.lang.reflect.Method.invoke(java.base@9-ea/Method.java:537) > [java] at org.apache.tools.ant.taskdefs.ExecuteJava.run(ExecuteJava.java:217) > [java] at org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:152) > [java] ... 38 more > [java] Caused by: java.lang.NullPointerException > [java] at org.jgroups.conf.ClassConfigurator.init(ClassConfigurator.java:229) > [java] at org.jgroups.conf.ClassConfigurator.<clinit>(ClassConfigurator.java:53) > [java] ... 50 more > [java] Java Result: -1 > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2129) Schema generation fails on JDK9

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/JGRP-2129?page=com.atlassian.jira.plugin.... ] Radoslav Husar closed JGRP-2129. -------------------------------- Resolution: Rejected Actually, this works no problem from ant with "ant make-schema", I was just running "mvn clean install" to hit this. I will close this for now. > Schema generation fails on JDK9 > ------------------------------- > > Key: JGRP-2129 > URL: https://issues.jboss.org/browse/JGRP-2129 > Project: JGroups > Issue Type: Task > Reporter: Radoslav Husar > Assignee: Bela Ban > Priority: Minor > Labels: jdk9 > Fix For: 4.1 > > > Not going to be a problem for a while until base is compiled with JDK9 by default, but just in case. > {noformat} > main: > [mkdir] Created dir: /Users/rhusar/git/jgroups/target/schema > [java] java.lang.ExceptionInInitializerError > [java] at org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:194) > [java] at org.apache.tools.ant.taskdefs.Java.run(Java.java:771) > [java] at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:221) > [java] at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:135) > [java] at org.apache.tools.ant.taskdefs.Java.execute(Java.java:108) > [java] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) > [java] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-ea/Native Method) > [java] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@9-ea/NativeMethodAccessorImpl.java:62) > [java] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-ea/DelegatingMethodAccessorImpl.java:43) > [java] at java.lang.reflect.Method.invoke(java.base@9-ea/Method.java:537) > [java] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) > [java] at org.apache.tools.ant.Task.perform(Task.java:348) > [java] at org.apache.tools.ant.Target.execute(Target.java:390) > [java] at org.apache.tools.ant.Target.performTasks(Target.java:411) > [java] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399) > [java] at org.apache.tools.ant.Project.executeTarget(Project.java:1368) > [java] at org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:327) > [java] at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) > [java] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) > [java] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > [java] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > [java] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > [java] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > [java] at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > [java] at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > [java] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > [java] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > [java] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > [java] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) > [java] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) > [java] at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) > [java] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-ea/Native Method) > [java] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@9-ea/NativeMethodAccessorImpl.java:62) > [java] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-ea/DelegatingMethodAccessorImpl.java:43) > [java] at java.lang.reflect.Method.invoke(java.base@9-ea/Method.java:537) > [java] at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > [java] at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > [java] at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > [java] at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > [java] Caused by: java.lang.ExceptionInInitializerError > [java] at org.jgroups.conf.ClassConfigurator.<clinit>(ClassConfigurator.java:56) > [java] at org.jgroups.protocols.ASYM_ENCRYPT.<clinit>(ASYM_ENCRYPT.java:55) > [java] at java.lang.Class.forName0(java.base@9-ea/Native Method) > [java] at java.lang.Class.forName(java.base@9-ea/Class.java:291) > [java] at org.jgroups.util.XMLSchemaGenerator.getClasses(XMLSchemaGenerator.java:127) > [java] at org.jgroups.util.XMLSchemaGenerator.generateProtocolSchema(XMLSchemaGenerator.java:106) > [java] at org.jgroups.util.XMLSchemaGenerator.main(XMLSchemaGenerator.java:80) > [java] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-ea/Native Method) > [java] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@9-ea/NativeMethodAccessorImpl.java:62) > [java] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-ea/DelegatingMethodAccessorImpl.java:43) > [java] at java.lang.reflect.Method.invoke(java.base@9-ea/Method.java:537) > [java] at org.apache.tools.ant.taskdefs.ExecuteJava.run(ExecuteJava.java:217) > [java] at org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:152) > [java] ... 38 more > [java] Caused by: java.lang.NullPointerException > [java] at org.jgroups.conf.ClassConfigurator.init(ClassConfigurator.java:229) > [java] at org.jgroups.conf.ClassConfigurator.<clinit>(ClassConfigurator.java:53) > [java] ... 50 more > [java] Java Result: -1 > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-731) Coverity static analysis: Missing parent calls in Elytron

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/ELY-731?page=com.atlassian.jira.plugin.sy... ] Ilia Vassilev commented on ELY-731: ----------------------------------- [~jcacek] What is the problem for the 3rd change request [1]? How to access the coverity link? Do I need an account? [1] org.wildfly.security.auth.client.MatchSchemeSpecificPartRule.matches(URI, String, String, String) compare to MatchHostRule class https://scan7.coverity.com/reports.htm#v16159/p11778/fileInstanceId=56224... > Coverity static analysis: Missing parent calls in Elytron > --------------------------------------------------------- > > Key: ELY-731 > URL: https://issues.jboss.org/browse/ELY-731 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Josef Cacek > Assignee: Ilia Vassilev > Priority: Minor > Labels: static_analysis > > Coverity static-analysis scan found missing parent calls in Elytron. They seems to be a simple fixes: > * DisposedCallbackSaslClientFactory should use super.dispose() instead of delegate.dispose() > ** https://scan7.coverity.com/reports.htm#v16159/p11778/fileInstanceId=56219... > * DisposedCallbackSaslServerFactory should use super.dispose() instead of delegate.dispose() > ** https://scan7.coverity.com/reports.htm#v16159/p11778/fileInstanceId=56218... > * org.wildfly.security.auth.client.MatchSchemeSpecificPartRule.matches(URI, String, String, String) > ** compare to {{MatchHostRule}} class > ** https://scan7.coverity.com/reports.htm#v16159/p11778/fileInstanceId=56224... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-759) DirContext with non-simple auth-level should use Elytron SASL

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-759?page=com.atlassian.jira.plugin.sy... ] Jan Kalina updated ELY-759: --------------------------- Issue Type: Enhancement (was: Bug) > DirContext with non-simple auth-level should use Elytron SASL > ------------------------------------------------------------- > > Key: ELY-759 > URL: https://issues.jboss.org/browse/ELY-759 > Project: WildFly Elytron > Issue Type: Enhancement > Reporter: Jan Kalina > Assignee: Darran Lofthouse > Priority: Optional > > DirContext allows to use SASL for LDAP authentication: > {code:java} > <dir-context authentication-level="DIGEST-MD5" name="DirContextInsecure" url="ldap://localhost:11391/"/> > {code} > Would be logical to ensure Elytron SASL clients will be used. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7599) PersistentResourceXMLDescription for parsing/marshaling of Elytron

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7599?page=com.atlassian.jira.plugin.... ] Jan Kalina updated WFLY-7599: ----------------------------- Issue Type: Enhancement (was: Bug) > PersistentResourceXMLDescription for parsing/marshaling of Elytron > ------------------------------------------------------------------ > > Key: WFLY-7599 > URL: https://issues.jboss.org/browse/WFLY-7599 > Project: WildFly > Issue Type: Enhancement > Components: Security > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Optional > > Using PersistentResourceXMLDescription for parsing/marshaling of Elytron subsystem model parts would simplify code of the subsystem. > (as an example can be used https://github.com/wildfly-security/elytron-subsystem/pull/290/files or RealmParser) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-759) DirContext with non-simple auth-level should use Elytron SASL

by Jan Kalina (JIRA)

Jan Kalina created ELY-759: ------------------------------ Summary: DirContext with non-simple auth-level should use Elytron SASL Key: ELY-759 URL: https://issues.jboss.org/browse/ELY-759 Project: WildFly Elytron Issue Type: Bug Reporter: Jan Kalina Assignee: Darran Lofthouse DirContext allows to use SASL for LDAP authentication: {code:java} <dir-context authentication-level="DIGEST-MD5" name="DirContextInsecure" url="ldap://localhost:11391/"/> {code} Would be logical to ensure Elytron SASL clients will be used. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-759) DirContext with non-simple auth-level should use Elytron SASL

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-759?page=com.atlassian.jira.plugin.sy... ] Jan Kalina updated ELY-759: --------------------------- Priority: Optional (was: Major) > DirContext with non-simple auth-level should use Elytron SASL > ------------------------------------------------------------- > > Key: ELY-759 > URL: https://issues.jboss.org/browse/ELY-759 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Jan Kalina > Assignee: Darran Lofthouse > Priority: Optional > > DirContext allows to use SASL for LDAP authentication: > {code:java} > <dir-context authentication-level="DIGEST-MD5" name="DirContextInsecure" url="ldap://localhost:11391/"/> > {code} > Would be logical to ensure Elytron SASL clients will be used. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7599) PersistentResourceXMLDescription for parsing/marshaling of Elytron

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7599?page=com.atlassian.jira.plugin.... ] Jan Kalina updated WFLY-7599: ----------------------------- Description: Using PersistentResourceXMLDescription for parsing/marshaling of Elytron subsystem model parts would simplify code of the subsystem. (as an example can be used https://github.com/wildfly-security/elytron-subsystem/pull/290/files or RealmParser) was:Using PersistentResourceXMLDescription for parsing/marshaling of Elytron subsystem model parts would simplify code of the subsystem. > PersistentResourceXMLDescription for parsing/marshaling of Elytron > ------------------------------------------------------------------ > > Key: WFLY-7599 > URL: https://issues.jboss.org/browse/WFLY-7599 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Optional > > Using PersistentResourceXMLDescription for parsing/marshaling of Elytron subsystem model parts would simplify code of the subsystem. > (as an example can be used https://github.com/wildfly-security/elytron-subsystem/pull/290/files or RealmParser) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 November 2016