June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22658) Infinite or very long hang in CDI builder with Payara embedded maven dep

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22658?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22658: ---------------------------------------- If this dependency is huge (and it looks like this is the case) then it can take a long time to build the project the very first time. But one hour seems to be too long anyway. [~scabanovich] could you please take a look? > Infinite or very long hang in CDI builder with Payara embedded maven dep > ------------------------------------------------------------------------ > > Key: JBIDE-22658 > URL: https://issues.jboss.org/browse/JBIDE-22658 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Reporter: arjan tijms > Fix For: 4.4.x > > > In the latest JBoss Tools for Eclipse Mars .2 (would be great if it was easy to see the main version easily, but I guess it's 4.3.1), the CDI builder either infinitely hangs or takes an enormous amount of time (an hour at least on a core M laptop) when payara embedded is present as (test) dependency in a maven project. > During this hang I took a stack trace, which looks as follows: > {noformat} > "Worker-20" #96 prio=5 os_prio=31 tid=0x0000000101512000 nid=0x14803 runnable [0x0000700003fde000] > java.lang.Thread.State: RUNNABLE > at java.util.zip.ZipFile.open(Native Method) > at java.util.zip.ZipFile.<init>(ZipFile.java:219) > at java.util.zip.ZipFile.<init>(ZipFile.java:149) > at java.util.zip.ZipFile.<init>(ZipFile.java:163) > at org.eclipse.jdt.internal.core.JavaModelManager.getZipFile(JavaModelManager.java:2678) > at org.eclipse.jdt.internal.core.JavaModelManager.getZipFile(JavaModelManager.java:2644) > at org.eclipse.jdt.internal.core.JarPackageFragmentRoot.getJar(JarPackageFragmentRoot.java:156) > at org.eclipse.jdt.internal.core.ClassFile.getJarBinaryTypeInfo(ClassFile.java:355) > at org.eclipse.jdt.internal.core.ClassFile.getBinaryTypeInfo(ClassFile.java:290) > at org.eclipse.jdt.internal.core.ClassFile.getBinaryTypeInfo(ClassFile.java:284) > at org.eclipse.jdt.internal.core.ClassFile.buildStructure(ClassFile.java:93) > at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:259) > at org.eclipse.jdt.internal.core.SourceRefElement.generateInfos(SourceRefElement.java:107) > at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579) > at org.eclipse.jdt.internal.core.BinaryType.getElementInfo(BinaryType.java:287) > at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302) > at org.eclipse.jdt.internal.core.JavaElement.exists(JavaElement.java:220) > at org.jboss.tools.cdi.internal.core.scanner.ImplementationCollector.process(ImplementationCollector.java:41) > at org.jboss.tools.cdi.internal.core.scanner.ImplementationCollector.<init>(ImplementationCollector.java:32) > at org.jboss.tools.cdi.internal.core.impl.CDIProject.rebuildBeans(CDIProject.java:1309) > at org.jboss.tools.cdi.internal.core.impl.CDIProject.update(CDIProject.java:1216) > - locked <0x000000078ecd93d8> (a org.jboss.tools.cdi.internal.core.impl.CDICache) > at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.applyWorkingCopy(DefinitionContext.java:442) > at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:267) > at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245) > at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303) > at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359) > at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382) > at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144) > at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > I debugged Eclipse with a second Eclipse, and it appeared that the code is repeatedly opening {{.m2/repository/fish/payara/extras/payara-embedded-all/4.1.1.162/payara-embedded-all-4.1.1.162.jar}} from {{CDIProject#rebuildBeans}}. > The specific line of code is: > {code:java} > ImplementationCollector ic = new ImplementationCollector(typeDefinitions); > {code} > The number of type definitions it seems to go through in {{ImplementationCollector#process}} is *33009* and the loop looks to be making progress, so it's more likely just incredibly slow and not an infinite hang. > The dependency in pom.xml looks as follows: > {code:xml} > <dependency> > <groupId>fish.payara.extras</groupId> > <artifactId>payara-embedded-all</artifactId> > <version>4.1.1.162</version> > <scope>test</scope> > </dependency> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22658) Infinite or very long hang in CDI builder with Payara embedded maven dep

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22658?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22658: ----------------------------------- Fix Version/s: 4.4.x > Infinite or very long hang in CDI builder with Payara embedded maven dep > ------------------------------------------------------------------------ > > Key: JBIDE-22658 > URL: https://issues.jboss.org/browse/JBIDE-22658 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Reporter: arjan tijms > Fix For: 4.4.x > > > In the latest JBoss Tools for Eclipse Mars .2 (would be great if it was easy to see the main version easily, but I guess it's 4.3.1), the CDI builder either infinitely hangs or takes an enormous amount of time (an hour at least on a core M laptop) when payara embedded is present as (test) dependency in a maven project. > During this hang I took a stack trace, which looks as follows: > {noformat} > "Worker-20" #96 prio=5 os_prio=31 tid=0x0000000101512000 nid=0x14803 runnable [0x0000700003fde000] > java.lang.Thread.State: RUNNABLE > at java.util.zip.ZipFile.open(Native Method) > at java.util.zip.ZipFile.<init>(ZipFile.java:219) > at java.util.zip.ZipFile.<init>(ZipFile.java:149) > at java.util.zip.ZipFile.<init>(ZipFile.java:163) > at org.eclipse.jdt.internal.core.JavaModelManager.getZipFile(JavaModelManager.java:2678) > at org.eclipse.jdt.internal.core.JavaModelManager.getZipFile(JavaModelManager.java:2644) > at org.eclipse.jdt.internal.core.JarPackageFragmentRoot.getJar(JarPackageFragmentRoot.java:156) > at org.eclipse.jdt.internal.core.ClassFile.getJarBinaryTypeInfo(ClassFile.java:355) > at org.eclipse.jdt.internal.core.ClassFile.getBinaryTypeInfo(ClassFile.java:290) > at org.eclipse.jdt.internal.core.ClassFile.getBinaryTypeInfo(ClassFile.java:284) > at org.eclipse.jdt.internal.core.ClassFile.buildStructure(ClassFile.java:93) > at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:259) > at org.eclipse.jdt.internal.core.SourceRefElement.generateInfos(SourceRefElement.java:107) > at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579) > at org.eclipse.jdt.internal.core.BinaryType.getElementInfo(BinaryType.java:287) > at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302) > at org.eclipse.jdt.internal.core.JavaElement.exists(JavaElement.java:220) > at org.jboss.tools.cdi.internal.core.scanner.ImplementationCollector.process(ImplementationCollector.java:41) > at org.jboss.tools.cdi.internal.core.scanner.ImplementationCollector.<init>(ImplementationCollector.java:32) > at org.jboss.tools.cdi.internal.core.impl.CDIProject.rebuildBeans(CDIProject.java:1309) > at org.jboss.tools.cdi.internal.core.impl.CDIProject.update(CDIProject.java:1216) > - locked <0x000000078ecd93d8> (a org.jboss.tools.cdi.internal.core.impl.CDICache) > at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.applyWorkingCopy(DefinitionContext.java:442) > at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:267) > at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245) > at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303) > at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359) > at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382) > at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144) > at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > I debugged Eclipse with a second Eclipse, and it appeared that the code is repeatedly opening {{.m2/repository/fish/payara/extras/payara-embedded-all/4.1.1.162/payara-embedded-all-4.1.1.162.jar}} from {{CDIProject#rebuildBeans}}. > The specific line of code is: > {code:java} > ImplementationCollector ic = new ImplementationCollector(typeDefinitions); > {code} > The number of type definitions it seems to go through in {{ImplementationCollector#process}} is *33009* and the loop looks to be making progress, so it's more likely just incredibly slow and not an infinite hang. > The dependency in pom.xml looks as follows: > {code:xml} > <dependency> > <groupId>fish.payara.extras</groupId> > <artifactId>payara-embedded-all</artifactId> > <version>4.1.1.162</version> > <scope>test</scope> > </dependency> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22658) Infinite or very long hang in CDI builder with Payara embedded maven dep

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22658?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22658: -------------------------------------- Assignee: Viacheslav Kabanovich > Infinite or very long hang in CDI builder with Payara embedded maven dep > ------------------------------------------------------------------------ > > Key: JBIDE-22658 > URL: https://issues.jboss.org/browse/JBIDE-22658 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Reporter: arjan tijms > Assignee: Viacheslav Kabanovich > Fix For: 4.4.x > > > In the latest JBoss Tools for Eclipse Mars .2 (would be great if it was easy to see the main version easily, but I guess it's 4.3.1), the CDI builder either infinitely hangs or takes an enormous amount of time (an hour at least on a core M laptop) when payara embedded is present as (test) dependency in a maven project. > During this hang I took a stack trace, which looks as follows: > {noformat} > "Worker-20" #96 prio=5 os_prio=31 tid=0x0000000101512000 nid=0x14803 runnable [0x0000700003fde000] > java.lang.Thread.State: RUNNABLE > at java.util.zip.ZipFile.open(Native Method) > at java.util.zip.ZipFile.<init>(ZipFile.java:219) > at java.util.zip.ZipFile.<init>(ZipFile.java:149) > at java.util.zip.ZipFile.<init>(ZipFile.java:163) > at org.eclipse.jdt.internal.core.JavaModelManager.getZipFile(JavaModelManager.java:2678) > at org.eclipse.jdt.internal.core.JavaModelManager.getZipFile(JavaModelManager.java:2644) > at org.eclipse.jdt.internal.core.JarPackageFragmentRoot.getJar(JarPackageFragmentRoot.java:156) > at org.eclipse.jdt.internal.core.ClassFile.getJarBinaryTypeInfo(ClassFile.java:355) > at org.eclipse.jdt.internal.core.ClassFile.getBinaryTypeInfo(ClassFile.java:290) > at org.eclipse.jdt.internal.core.ClassFile.getBinaryTypeInfo(ClassFile.java:284) > at org.eclipse.jdt.internal.core.ClassFile.buildStructure(ClassFile.java:93) > at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:259) > at org.eclipse.jdt.internal.core.SourceRefElement.generateInfos(SourceRefElement.java:107) > at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579) > at org.eclipse.jdt.internal.core.BinaryType.getElementInfo(BinaryType.java:287) > at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302) > at org.eclipse.jdt.internal.core.JavaElement.exists(JavaElement.java:220) > at org.jboss.tools.cdi.internal.core.scanner.ImplementationCollector.process(ImplementationCollector.java:41) > at org.jboss.tools.cdi.internal.core.scanner.ImplementationCollector.<init>(ImplementationCollector.java:32) > at org.jboss.tools.cdi.internal.core.impl.CDIProject.rebuildBeans(CDIProject.java:1309) > at org.jboss.tools.cdi.internal.core.impl.CDIProject.update(CDIProject.java:1216) > - locked <0x000000078ecd93d8> (a org.jboss.tools.cdi.internal.core.impl.CDICache) > at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.applyWorkingCopy(DefinitionContext.java:442) > at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:267) > at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245) > at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303) > at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359) > at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382) > at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144) > at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > I debugged Eclipse with a second Eclipse, and it appeared that the code is repeatedly opening {{.m2/repository/fish/payara/extras/payara-embedded-all/4.1.1.162/payara-embedded-all-4.1.1.162.jar}} from {{CDIProject#rebuildBeans}}. > The specific line of code is: > {code:java} > ImplementationCollector ic = new ImplementationCollector(typeDefinitions); > {code} > The number of type definitions it seems to go through in {{ImplementationCollector#process}} is *33009* and the loop looks to be making progress, so it's more likely just incredibly slow and not an infinite hang. > The dependency in pom.xml looks as follows: > {code:xml} > <dependency> > <groupId>fish.payara.extras</groupId> > <artifactId>payara-embedded-all</artifactId> > <version>4.1.1.162</version> > <scope>test</scope> > </dependency> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22669) SelectionBar widget returns incorrect visibility

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22669?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22669: -------------------------------------- Assignee: Viacheslav Kabanovich [~scabanovich] could you please review this PR? > SelectionBar widget returns incorrect visibility > ------------------------------------------------ > > Key: JBIDE-22669 > URL: https://issues.jboss.org/browse/JBIDE-22669 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.4.0.Final > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.4.1.M1 > > > setVisible method doesnt call super.setVisible thus always returns true when called isVisible() -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22670) tools.jboss.org/downloads refers to devstudio 9.1.0 even after 10.0 GA release

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22670?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22670: ---------------------------------------- [~xcoulon] I applied https://github.com/jbosstools/jbosstools-website/pull/595 because it's kinda urgent. Please reopen this issue if you believe there is a better solution. > tools.jboss.org/downloads refers to devstudio 9.1.0 even after 10.0 GA release > ------------------------------------------------------------------------------ > > Key: JBIDE-22670 > URL: https://issues.jboss.org/browse/JBIDE-22670 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.4.0.Final > Reporter: Alexey Kazakov > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.4.0.Final > > > 10.0.0.GA (Neon) is available - http://tools.jboss.org/downloads/devstudio/neon/10.0.0.GA.html > but http://tools.jboss.org/downloads/ still refers to 9.1.0.GA (Mars) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22670) tools.jboss.org/downloads refers to devstudio 9.1.0 even after 10.0 GA release

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-22670: -------------------------------------- Summary: tools.jboss.org/downloads refers to devstudio 9.1.0 even after 10.0 GA release Key: JBIDE-22670 URL: https://issues.jboss.org/browse/JBIDE-22670 Project: Tools (JBoss Tools) Issue Type: Bug Components: website Affects Versions: 4.4.0.Final Reporter: Alexey Kazakov Assignee: Xavier Coulon Priority: Critical Fix For: 4.4.0.Final 10.0.0.GA (Neon) is available - http://tools.jboss.org/downloads/devstudio/neon/10.0.0.GA.html but http://tools.jboss.org/downloads/ still refers to 9.1.0.GA (Mars) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22595) Deploy Docker image wizard: One gets 2 authentication dialogs if you're using a non-conected connection without store pw

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22595?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22595 at 6/27/16 2:57 PM: ------------------------------------------------------------------- i merged [#1236|https://github.com/jbosstools/jbosstools-openshift/pull/1236] into master. Will test the additional usecase in [~jeffmaury]'s comment and see if there's more to be done for this. was (Author: adietish): i merged https://github.com/jbosstools/jbosstools-openshift/pull/1236 into master. Will test the additional usecase in [~jeffmaury]'s comment and see if there's more to be done for this. > Deploy Docker image wizard: One gets 2 authentication dialogs if you're using a non-conected connection without store pw > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22595 > URL: https://issues.jboss.org/browse/JBIDE-22595 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: connection_wizard, openshift_v3 > Fix For: 4.4.1.M1 > > Attachments: 2-password-dialogs.png, screenshot-1.png, screenshot-2.png > > Original Estimate: 1 day > Time Spent: 2 days, 1 hour > Remaining Estimate: 0 minutes > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22595) Deploy Docker image wizard: One gets 2 authentication dialogs if you're using a non-conected connection without store pw

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22595?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22595: ------------------------------------------ i merged https://github.com/jbosstools/jbosstools-openshift/pull/1236 into master. Will test the additional usecase in [~jeffmaury]'s comment and see if there's more to be done for this. > Deploy Docker image wizard: One gets 2 authentication dialogs if you're using a non-conected connection without store pw > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22595 > URL: https://issues.jboss.org/browse/JBIDE-22595 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: connection_wizard, openshift_v3 > Fix For: 4.4.1.M1 > > Attachments: 2-password-dialogs.png, screenshot-1.png, screenshot-2.png > > Original Estimate: 1 day > Time Spent: 2 days, 1 hour > Remaining Estimate: 0 minutes > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-154) Allow for specifying labels when running a container [EBZ#485913]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-154?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston updated ERT-154: ------------------------------ Sprint: devex #116 June 2016 > Allow for specifying labels when running a container [EBZ#485913] > ----------------------------------------------------------------- > > Key: ERT-154 > URL: https://issues.jboss.org/browse/ERT-154 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: Docker, bzira > Fix For: Neon (4.6) > > > Labels can be specified on the container when it is created. The wizard/launcher could also provide this feature in the UI. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22645) Pre-select OpenShift 3 in New OpenShift Connection wizard

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22645?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22645: ----------------------------------------------- This seems a duplicate of JBIDE-20026. > Pre-select OpenShift 3 in New OpenShift Connection wizard > --------------------------------------------------------- > > Key: JBIDE-22645 > URL: https://issues.jboss.org/browse/JBIDE-22645 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Alexey Kazakov > > Currently OS 2 is selected by default. We should pre-select OS 3 instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 June 2016