January 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26456) Provision Rhel 8 image with JBDS labels and add it to jenkins

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26456?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26456: ------------------------------- Sprint: devex #157 November 2019, devex #159 December 2018, devex #161 January 2019 (was: devex #157 November 2019, devex #159 December 2018) > Provision Rhel 8 image with JBDS labels and add it to jenkins > ------------------------------------------------------------- > > Key: JBIDE-26456 > URL: https://issues.jboss.org/browse/JBIDE-26456 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.10.0.AM1 > Environment: Linux > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Labels: jenkins, openstack > Fix For: 4.11.0.AM1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26454) Proxy usage within QE teams, needs and requirements for deploying

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26454?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26454: ------------------------------- Sprint: devex #159 December 2018, devex #161 January 2019 (was: devex #159 December 2018) > Proxy usage within QE teams, needs and requirements for deploying > ----------------------------------------------------------------- > > Key: JBIDE-26454 > URL: https://issues.jboss.org/browse/JBIDE-26454 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.10.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Labels: quality > Fix For: 4.11.0.AM1 > > > Find out: > * existing solutions within RH > * needs of other teams > * usability of open source proxy technologies/solutions > * usage among different OS -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26478) Errors during import Spring Starter Project

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26478?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26478: ------------------------------- Component/s: central (was: build) > Errors during import Spring Starter Project > ------------------------------------------- > > Key: JBIDE-26478 > URL: https://issues.jboss.org/browse/JBIDE-26478 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.10.0.AM1 > Environment: F29 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Priority: Minor > Fix For: 4.11.0.AM1 > > > During import of Spring Starter project there are some errors in error log; > {code:java} > eclipse.buildId=12.10.0.AM1-v20181129-0845-B3670 > java.version=1.8.0_191 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -data file:/home/jkopriva/devstudio_B3670_2/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.springframework.ide.eclipse.beans.core > Error > Fri Nov 30 10:37:18 CET 2018 > Problems occurred when invoking code from plug-in: "org.springframework.ide.eclipse.beans.core". > java.lang.NoSuchMethodError: org.springframework.beans.factory.support.BeanDefinitionBuilder.genericBeanDefinition(Ljava/lang/Class;Ljava/util/function/Supplier;)Lorg/springframework/beans/factory/support/BeanDefinitionBuilder; > at org.springframework.boot.autoconfigure.condition.BeanTypeRegistry.get(BeanTypeRegistry.java:363) > at org.springframework.boot.autoconfigure.condition.OnBeanCondition.collectBeanNamesForType(OnBeanCondition.java:297) > at org.springframework.boot.autoconfigure.condition.OnBeanCondition.getBeanNamesForType(OnBeanCondition.java:289) > at org.springframework.boot.autoconfigure.condition.OnBeanCondition.getBeanNamesForType(OnBeanCondition.java:278) > at org.springframework.boot.autoconfigure.condition.OnBeanCondition.getMatchingBeans(OnBeanCondition.java:189) > at org.springframework.boot.autoconfigure.condition.OnBeanCondition.getMatchOutcome(OnBeanCondition.java:125) > at org.springframework.boot.autoconfigure.condition.SpringBootCondition.matches(SpringBootCondition.java:47) > at org.springframework.context.annotation.ConditionEvaluator.shouldSkip(ConditionEvaluator.java:102) > at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader$TrackedConditionEvaluator.shouldSkip(ConfigurationClassBeanDefinitionReader.java:443) > at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader$TrackedConditionEvaluator.shouldSkip(ConfigurationClassBeanDefinitionReader.java:432) > at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitionsForConfigurationClass(ConfigurationClassBeanDefinitionReader.java:127) > at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitions(ConfigurationClassBeanDefinitionReader.java:116) > at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:320) > at org.springframework.ide.eclipse.metadata.process.JdtConfigurationClassPostProcessor.postProcess(JdtConfigurationClassPostProcessor.java:88) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$3.run(BeansJavaConfig.java:332) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig.executePostProcessor(BeansJavaConfig.java:321) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig.access$5(BeansJavaConfig.java:319) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$2.call(BeansJavaConfig.java:233) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$2.call(BeansJavaConfig.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > {code} > {code:java} > eclipse.buildId=12.10.0.AM1-v20181129-0845-B3670 > java.version=1.8.0_191 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -data file:/home/jkopriva/devstudio_B3670_2/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.springframework.ide.eclipse.beans.core > Warning > Fri Nov 30 10:37:18 CET 2018 > Error occured while running bean post processors > java.lang.NoSuchMethodError: org.springframework.beans.factory.support.BeanDefinitionBuilder.genericBeanDefinition(Ljava/lang/Class;Ljava/util/function/Supplier;)Lorg/springframework/beans/factory/support/BeanDefinitionBuilder; > at org.springframework.boot.autoconfigure.condition.BeanTypeRegistry.get(BeanTypeRegistry.java:363) > at org.springframework.boot.autoconfigure.condition.OnBeanCondition.collectBeanNamesForType(OnBeanCondition.java:297) > at org.springframework.boot.autoconfigure.condition.OnBeanCondition.getBeanNamesForType(OnBeanCondition.java:289) > at org.springframework.boot.autoconfigure.condition.OnBeanCondition.getBeanNamesForType(OnBeanCondition.java:278) > at org.springframework.boot.autoconfigure.condition.OnBeanCondition.getMatchingBeans(OnBeanCondition.java:189) > at org.springframework.boot.autoconfigure.condition.OnBeanCondition.getMatchOutcome(OnBeanCondition.java:125) > at org.springframework.boot.autoconfigure.condition.SpringBootCondition.matches(SpringBootCondition.java:47) > at org.springframework.context.annotation.ConditionEvaluator.shouldSkip(ConditionEvaluator.java:102) > at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader$TrackedConditionEvaluator.shouldSkip(ConfigurationClassBeanDefinitionReader.java:443) > at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader$TrackedConditionEvaluator.shouldSkip(ConfigurationClassBeanDefinitionReader.java:432) > at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitionsForConfigurationClass(ConfigurationClassBeanDefinitionReader.java:127) > at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitions(ConfigurationClassBeanDefinitionReader.java:116) > at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:320) > at org.springframework.ide.eclipse.metadata.process.JdtConfigurationClassPostProcessor.postProcess(JdtConfigurationClassPostProcessor.java:88) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$3.run(BeansJavaConfig.java:332) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig.executePostProcessor(BeansJavaConfig.java:321) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig.access$5(BeansJavaConfig.java:319) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$2.call(BeansJavaConfig.java:233) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$2.call(BeansJavaConfig.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26477) Update 4.11.0.AM1 TP (Docker tooling, ...)

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26477?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-26477: ------------------------------------ Updated CentralTP with: - SpringIDE 3.9.7 - EclipseCS 8.7.0 - SonarLint 4.0.0 See [^jbtcentraltarget.p2diff.txt] > Update 4.11.0.AM1 TP (Docker tooling, ...) > ------------------------------------------ > > Key: JBIDE-26477 > URL: https://issues.jboss.org/browse/JBIDE-26477 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, target-platform > Affects Versions: 4.10.0.AM1 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.11.0.AM1 > > Attachments: jbtcentraltarget.p2diff.txt, p2diff_4.11.0.AM1-4.10.0.AM1.txt, p2diff_4.11.0.AM1-4.11.0.AM1-previous.txt, p2diff_4.11.0.AM1-cameltooling-1.0.0.201812030843.txt, p2diff_4.11.0.AM1-m2e-1.10.txt > > > We should update docker tooling on TP, there is a fix for JDK 11: https://bugs.eclipse.org/bugs/show_bug.cgi?id=539483 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26477) Update 4.11.0.AM1 TP (Docker tooling, ...)

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26477?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26477: ------------------------------- Attachment: jbtcentraltarget.p2diff.txt > Update 4.11.0.AM1 TP (Docker tooling, ...) > ------------------------------------------ > > Key: JBIDE-26477 > URL: https://issues.jboss.org/browse/JBIDE-26477 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, target-platform > Affects Versions: 4.10.0.AM1 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.11.0.AM1 > > Attachments: jbtcentraltarget.p2diff.txt, p2diff_4.11.0.AM1-4.10.0.AM1.txt, p2diff_4.11.0.AM1-4.11.0.AM1-previous.txt, p2diff_4.11.0.AM1-cameltooling-1.0.0.201812030843.txt, p2diff_4.11.0.AM1-m2e-1.10.txt > > > We should update docker tooling on TP, there is a fix for JDK 11: https://bugs.eclipse.org/bugs/show_bug.cgi?id=539483 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26500) central compilation errors on Java11+

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26500?page=com.atlassian.jira.plugi... ] Zbyněk Červinka closed JBIDE-26500. ----------------------------------- Resolution: Done > central compilation errors on Java11+ > ------------------------------------- > > Key: JBIDE-26500 > URL: https://issues.jboss.org/browse/JBIDE-26500 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.10.0.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.11.0.AM1 > > > central does not compile on Java11+ because of missing dependencies (javax.xml.bind, ...) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26500) central compilation errors on Java11+

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26500?page=com.atlassian.jira.plugi... ] Zbyněk Červinka edited comment on JBIDE-26500 at 1/15/19 9:22 AM: ------------------------------------------------------------------ Tested on localhost with "mvn clean install -DskipTests=true", build successful under JAVA 11.0.1. was (Author: zcervink): Tested on localhost with "mvn clean install -DkipTests=true", build successfull under JAVA 11.0.1. > central compilation errors on Java11+ > ------------------------------------- > > Key: JBIDE-26500 > URL: https://issues.jboss.org/browse/JBIDE-26500 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.10.0.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.11.0.AM1 > > > central does not compile on Java11+ because of missing dependencies (javax.xml.bind, ...) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26500) central compilation errors on Java11+

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26500?page=com.atlassian.jira.plugi... ] Zbyněk Červinka closed JBIDE-26500. ----------------------------------- Tested on localhost with "mvn clean install -DkipTests=true", build successfull under JAVA 11.0.1. > central compilation errors on Java11+ > ------------------------------------- > > Key: JBIDE-26500 > URL: https://issues.jboss.org/browse/JBIDE-26500 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.10.0.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.11.0.AM1 > > > central does not compile on Java11+ because of missing dependencies (javax.xml.bind, ...) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26515) Job jbosstools-livereload_master is Red

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26515?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26515. --------------------------------- Job is back to green. > Job jbosstools-livereload_master is Red > --------------------------------------- > > Key: JBIDE-26515 > URL: https://issues.jboss.org/browse/JBIDE-26515 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, livereload > Affects Versions: 4.11.0.AM1 > Environment: Jenkins > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.11.0.AM1 > > > Livereload build on jenkins started failing in middle of December 2018: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > with errors like: > {code:java} > !SESSION 2019-01-02 02:58:25.265 ----------------------------------------------- > eclipse.buildId=unknown > java.version=1.8.0_191 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -application org.eclipse.tycho.surefire.osgibooter.headlesstest -testproperties /mnt/hudson_workspace/workspace/jbosstools-livereload_master/sources/tests/org.jboss.tools.livereload.test/target/surefire.properties -testApplication org.eclipse.ui.ide.workbench -product org.eclipse.platform.ide > Command-line arguments: -data /mnt/hudson_workspace/workspace/jbosstools-livereload_master/sources/tests/org.jboss.tools.livereload.test/target/work/data -application org.eclipse.tycho.surefire.osgibooter.headlesstest -testproperties /mnt/hudson_workspace/workspace/jbosstools-livereload_master/sources/tests/org.jboss.tools.livereload.test/target/surefire.properties -testApplication org.eclipse.ui.ide.workbench -product org.eclipse.platform.ide > !ENTRY org.jboss.tools.livereload.core 4 0 2019-01-02 02:58:41.425 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.core [286] > Unresolved requirement: Require-Bundle: org.apache.aries.spifly.dynamic.bundle; bundle-version="1.0.10" > -> Bundle-SymbolicName: org.apache.aries.spifly.dynamic.bundle; bundle-version="1.0.10" > org.apache.aries.spifly.dynamic.bundle [16] > Unresolved requirement: Import-Package: org.objectweb.asm.commons; version="[5.0.0,7.0.0)" > -> Export-Package: org.objectweb.asm.commons; bundle-symbolic-name="org.objectweb.asm.commons"; bundle-version="6.2.1.v20180823-1831"; version="6.2.1"; uses:="org.objectweb.asm,org.objectweb.asm.signature,org.objectweb.asm.tree" > org.objectweb.asm.commons [18] > No resolution report for the bundle. Bundle was not resolved because of a uses constraint violation. > org.apache.felix.resolver.reason.ReasonException: Uses constraint violation. Unable to resolve resource org.apache.aries.spifly.dynamic.bundle [osgi.identity; osgi.identity="org.apache.aries.spifly.dynamic.bundle"; type="osgi.bundle"; version:Version="1.0.10"] because it is exposed to package 'org.objectweb.asm' from resources org.objectweb.asm [osgi.identity; osgi.identity="org.objectweb.asm"; type="osgi.bundle"; version:Version="6.2.1.v20180823-1831"] and org.objectweb.asm [osgi.identity; osgi.identity="org.objectweb.asm"; type="osgi.bundle"; version:Version="7.0.0.v20181030-2244"] via two dependency chains. > Chain 1: > org.apache.aries.spifly.dynamic.bundle [osgi.identity; osgi.identity="org.apache.aries.spifly.dynamic.bundle"; type="osgi.bundle"; version:Version="1.0.10"] > import: (&(osgi.wiring.package=org.objectweb.asm)(&(version>=5.0.0)(!(version>=7.0.0)))) > | > export: osgi.wiring.package: org.objectweb.asm > org.objectweb.asm [osgi.identity; osgi.identity="org.objectweb.asm"; type="osgi.bundle"; version:Version="6.2.1.v20180823-1831"] > Chain 2: > org.apache.aries.spifly.dynamic.bundle [osgi.identity; osgi.identity="org.apache.aries.spifly.dynamic.bundle"; type="osgi.bundle"; version:Version="1.0.10"] > import: (&(osgi.wiring.package=org.objectweb.asm.commons)(&(version>=5.0.0)(!(version>=7.0.0)))) > | > export: osgi.wiring.package=org.objectweb.asm.commons; uses:=org.objectweb.asm > org.objectweb.asm.commons [osgi.identity; osgi.identity="org.objectweb.asm.commons"; type="osgi.bundle"; version:Version="6.2.1.v20180823-1831"] > import: (&(osgi.wiring.package=org.objectweb.asm)(version>=6.2.1)) > | > export: osgi.wiring.package: org.objectweb.asm > org.objectweb.asm [osgi.identity; osgi.identity="org.objectweb.asm"; type="osgi.bundle"; version:Version="7.0.0.v20181030-2244"] > at org.eclipse.osgi.container.Module.start(Module.java:451) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1749) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1728) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1691) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1622) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:233) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:343) > {code} > Similar issues are in: > https://issues.jboss.org/browse/JBIDE-26027 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26517) Upgrade to JBoss Forge 3.9.2.Final

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26517?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26517. --------------------------------- Forge is updated and can be started. Verified in: Red Hat Developer Studio Version: 12.11.0.AM1 Build id: AM1-v20190109-0423-B3781 Build date: 20190109-0423 > Upgrade to JBoss Forge 3.9.2.Final > ---------------------------------- > > Key: JBIDE-26517 > URL: https://issues.jboss.org/browse/JBIDE-26517 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.10.0.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.11.0.AM1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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

jbosstools-issues January 2019