July 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22965) CDK tools should work behind proxy

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-22965?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-22965. --------------------------------- > CDK tools should work behind proxy > ---------------------------------- > > Key: JBIDE-22965 > URL: https://issues.jboss.org/browse/JBIDE-22965 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.12.0.Final > > Attachments: create_proxy-test_env.sh > > > Proxy support has been added in CDK vagrant box and in vagrant-registration plugin. > We should make sure our CDK tooling supports it too. > In order to run CDK behind proxy, we need to set environment variables: https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... > Eclipse Proxy Testing link: https://mojo.redhat.com/docs/DOC-989982 > + to create a proxy test environment: https://gist.github.com/LalatenduMohanty/5062050ac78721eda9676bbc15ecfd25 > Standard unix proxy environmet variable $http_proxy has different purpose then $PROXY that CDK uses. Comments from [~lalatendum]: > {noformat} > lalatenduM: we exepect customers workstation is configured to porixy server > that means when you ping subscription-rhn-redhat-com.edge.prod.ext.phx2.redhat.com it should work > lalatenduM: on a customer worksttaion > lalatenduM: now teh challenge is to make openshift , docker and subscription manager in CDK VM aware of proxy server information > lalatenduM: vagrant-registration uses subscription manager for registraton > lalatenduM: whenyou use https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... it will make openshift, docker and vagrant-registration aware of proxy server info > {noformat} > in a mail on the 26th of October 2017 "Re: [openshift-sme] CDK: Usage behind proxy": > {quote} > The CDK supports a number of methods to apply proxy configuration. > You can specify a few of these at startup using the “minishift start” command. > First, you can set the --http-proxy and/or --https-proxy to apply RHEL environment variables. > For Docker Pulls, you can specify environment variables that are applied to the Docker daemon using the --docker-env flag (HTTP_PROXY, HTTPS_PROXY, NO_PROXY). > There are additional considerations for builds as well that can be applied. Please see the following document on the proxy considerations: > https://docs.openshift.com/container-platform/3.6/install_config/http_pro... > - Andy > {quote} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26671) Switch URLs to https

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26671?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-26671. --------------------------------- > Switch URLs to https > -------------------- > > Key: JBIDE-26671 > URL: https://issues.jboss.org/browse/JBIDE-26671 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.12.0.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.12.0.Final > > > jboss.org will soon support only https. We should update URLs used in our build system to https -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26670) Update 4.12.0.Final Target Platform (Docker tooling, ...) for 2019-06

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26670?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-26670. --------------------------------- > Update 4.12.0.Final Target Platform (Docker tooling, ...) for 2019-06 > --------------------------------------------------------------------- > > Key: JBIDE-26670 > URL: https://issues.jboss.org/browse/JBIDE-26670 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.12.0.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.12.0.Final > > Attachments: p2diff_log_jbosstools_2019-06-20_15-52.txt > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26715) Update 4.13.0.AM1 Target Platform (Docker tooling, ...) for 2019-09.M1

by stephane bouchet (Jira)

[ https://issues.jboss.org/browse/JBIDE-26715?page=com.atlassian.jira.plugi... ] stephane bouchet updated JBIDE-26715: ------------------------------------- Attachment: p2diff_log_jbosstools_2019-07-30_11-20.txt > Update 4.13.0.AM1 Target Platform (Docker tooling, ...) for 2019-09.M1 > ---------------------------------------------------------------------- > > Key: JBIDE-26715 > URL: https://issues.jboss.org/browse/JBIDE-26715 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.12.0.Final > Reporter: Jeff MAURY > Assignee: stephane bouchet > Priority: Major > Fix For: 4.13.0.AM1 > > Attachments: p2diff_log_jbosstools_2019-07-30_11-20.txt > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26715) Update 4.13.0.AM1 Target Platform (Docker tooling, ...) for 2019-09.M1

by stephane bouchet (Jira)

[ https://issues.jboss.org/browse/JBIDE-26715?page=com.atlassian.jira.plugi... ] stephane bouchet commented on JBIDE-26715: ------------------------------------------ first round with following updates : cameltooling;1.0.0.201907261207 lsp4e;0.11.0.201907261639 webtools;S-3.15.0.M1-20190717080107 mylyn;3.25.0.v20190328-1711 orbit;S20190709113129 simrel;20190719-1000-Simrel.2019-09.M1 > Update 4.13.0.AM1 Target Platform (Docker tooling, ...) for 2019-09.M1 > ---------------------------------------------------------------------- > > Key: JBIDE-26715 > URL: https://issues.jboss.org/browse/JBIDE-26715 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.12.0.Final > Reporter: Jeff MAURY > Assignee: stephane bouchet > Priority: Major > Fix For: 4.13.0.AM1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4756) Cannot start devstudio on mac os with jdk 11

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBDS-4756?page=com.atlassian.jira.plugin.... ] Ondrej Dockal closed JBDS-4756. ------------------------------- > Cannot start devstudio on mac os with jdk 11 > -------------------------------------------- > > Key: JBDS-4756 > URL: https://issues.jboss.org/browse/JBDS-4756 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 12.11.0.AM1 > Environment: CentralCI > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Fix For: 12.12.0.AM1 > > Attachments: Screenshot_20190204_115602.png > > > I can easily install devstudio on mac os with default jdk 11 (from /qa/tools/opt/osx/jdk11_last) but I cannot make it start. No other errors or warnings except the one here: > !Screenshot_20190204_115602.png|thumbnail! > More info links [here|https://support.apple.com/kb/DL1572?locale=en_US]. > I can also see installer [tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] failures on mac os 10.12 and 10.13 with this tack trace: > {code} > java.awt.HeadlessException > at java.desktop/sun.awt.HeadlessToolkit.getScreenSize(HeadlessToolkit.java:186) > at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:244) > at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:237) > at com.jboss.jbds.installer.test.InstallerTest.testInstall(InstallerTest.java:49) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) > at com.sun.proxy.$Proxy0.invoke(Unknown Source) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) > {code} > It might be possible to at least to try the installation and run on some bare metal to verify this error. Could someone possibly assist here, please? I have a suspicion that it might be performance related as the time needed to even open the jdk folder on the shared drive takes quite some time. Thanks! -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26704) Central throws error: no repository found

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26704?page=com.atlassian.jira.plugi... ] Zbyněk Červinka closed JBIDE-26704. ----------------------------------- No issue appears during installation of plugins. I am closing this issue. > Central throws error: no repository found > ----------------------------------------- > > Key: JBIDE-26704 > URL: https://issues.jboss.org/browse/JBIDE-26704 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.12.0.Final > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.12.0.Final > > > This happens during installation of plugins: > {code:java} > eclipse.buildId=12.12.0.GA-v20190628-0434-B4598 > java.version=11.0.2 > java.vendor=Oracle Corporation > BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_GB > Framework arguments: -product com.jboss.devstudio.core.product -product com.jboss.devstudio.core.product -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring > Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product com.jboss.devstudio.core.product -product com.jboss.devstudio.core.product -data file:/Users/jkopriva/workspace_B4598_spring/ -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring > org.eclipse.equinox.p2.core > Error > Sat Jun 29 11:05:35 CEST 2019 > Provisioning exception > org.eclipse.equinox.p2.core.ProvisionException: No repository found at https://devstudio.redhat.com/static/12/stable/updates/central/12.11.0.Final/. > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:394) > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:684) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:110) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:105) > at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.addChild(CompositeMetadataRepository.java:168) > at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.<init>(CompositeMetadataRepository.java:110) > at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.load(CompositeMetadataRepositoryFactory.java:124) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:63) > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:759) > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:660) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:110) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:105) > at org.eclipse.equinox.internal.p2.updatechecker.UpdateChecker.getAvailableRepositories(UpdateChecker.java:152) > at org.eclipse.equinox.internal.p2.updatechecker.UpdateChecker.checkForUpdates(UpdateChecker.java:130) > at org.eclipse.equinox.internal.p2.updatechecker.UpdateChecker$UpdateCheckThread.run(UpdateChecker.java:78) > {code} > {code:java} > eclipse.buildId=12.12.0.GA-v20190628-0434-B4598 > java.version=11.0.2 > java.vendor=Oracle Corporation > BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_GB > Framework arguments: -product com.jboss.devstudio.core.product -product com.jboss.devstudio.core.product -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring > Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product com.jboss.devstudio.core.product -product com.jboss.devstudio.core.product -data file:/Users/jkopriva/workspace_B4598_spring/ -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring > org.eclipse.equinox.p2.metadata.repository > Error > Sat Jun 29 11:05:35 CEST 2019 > No repository found at https://devstudio.redhat.com/static/12/stable/updates/central/12.11.0.Final/. > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4756) Cannot start devstudio on mac os with jdk 11

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBDS-4756?page=com.atlassian.jira.plugin.... ] Ondrej Dockal commented on JBDS-4756: ------------------------------------- We need to set system property java.awt.headless to false and change way to capture the screen in order to make itests run on mac os. Picture capturing was done using org.netbeans.jemmy.util.PNGEncoder, now it is changed to javax.imageio.ImageIO package. Tests are passing on all platforms again. > Cannot start devstudio on mac os with jdk 11 > -------------------------------------------- > > Key: JBDS-4756 > URL: https://issues.jboss.org/browse/JBDS-4756 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 12.11.0.AM1 > Environment: CentralCI > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Fix For: 12.12.0.AM1 > > Attachments: Screenshot_20190204_115602.png > > > I can easily install devstudio on mac os with default jdk 11 (from /qa/tools/opt/osx/jdk11_last) but I cannot make it start. No other errors or warnings except the one here: > !Screenshot_20190204_115602.png|thumbnail! > More info links [here|https://support.apple.com/kb/DL1572?locale=en_US]. > I can also see installer [tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] failures on mac os 10.12 and 10.13 with this tack trace: > {code} > java.awt.HeadlessException > at java.desktop/sun.awt.HeadlessToolkit.getScreenSize(HeadlessToolkit.java:186) > at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:244) > at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:237) > at com.jboss.jbds.installer.test.InstallerTest.testInstall(InstallerTest.java:49) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) > at com.sun.proxy.$Proxy0.invoke(Unknown Source) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) > {code} > It might be possible to at least to try the installation and run on some bare metal to verify this error. Could someone possibly assist here, please? I have a suspicion that it might be performance related as the time needed to even open the jdk folder on the shared drive takes quite some time. Thanks! -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26736) Reduce amount of image used on PSI openstack

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26736?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-26736: --------------------------------------- Request approved, closing. > Reduce amount of image used on PSI openstack > -------------------------------------------- > > Key: JBIDE-26736 > URL: https://issues.jboss.org/browse/JBIDE-26736 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.13.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Fix For: 4.13.0.AM1 > > > According to PSI openstack forum docs [1] we should decrease amount of images we use. We should make it to soft/hard limit - 15/20. > [1]: https://docs.google.com/document/d/1w0RsqqdcGYf-9A-wp8fdRa21TJYsK59rEuEBu... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26736) Reduce amount of image used on PSI openstack

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26736?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-26736. --------------------------------- > Reduce amount of image used on PSI openstack > -------------------------------------------- > > Key: JBIDE-26736 > URL: https://issues.jboss.org/browse/JBIDE-26736 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.13.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Fix For: 4.13.0.AM1 > > > According to PSI openstack forum docs [1] we should decrease amount of images we use. We should make it to soft/hard limit - 15/20. > [1]: https://docs.google.com/document/d/1w0RsqqdcGYf-9A-wp8fdRa21TJYsK59rEuEBu... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2019