May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21861) Include Docker & Vagrant tooling 2.0.0 in JBT 4.4.x TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21861?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21861: ------------------------------------ [~jjohnstn] this issue is resolved. Please use https://issues.jboss.org/browse/JBIDE-22411 for updates to docker/vagrant tooling in the JBT 4.4.x / RHJBDS 10 target platform. > Include Docker & Vagrant tooling 2.0.0 in JBT 4.4.x TP > ------------------------------------------------------ > > Key: JBIDE-21861 > URL: https://issues.jboss.org/browse/JBIDE-21861 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha2 > > > Include Docker tooling 2.0.0 in Target Platform 4.60.x, targeting JBoss Tools 4.4.x -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22411) update to latest Docker/Vagrant tooling

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22411?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22411: ------------------------------- Description: Latest Docker tooling from Linux Tools can be found at: http://download.eclipse.org/linuxtools/update-neon-docker-rc1 > update to latest Docker/Vagrant tooling > --------------------------------------- > > Key: JBIDE-22411 > URL: https://issues.jboss.org/browse/JBIDE-22411 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Affects Versions: 4.4.0.Alpha2 > Reporter: Nick Boldt > Fix For: 4.4.0.Alpha3 > > > Latest Docker tooling from Linux Tools can be found at: http://download.eclipse.org/linuxtools/update-neon-docker-rc1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22411) update to latest Docker/Vagrant tooling

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-22411: ---------------------------------- Summary: update to latest Docker/Vagrant tooling Key: JBIDE-22411 URL: https://issues.jboss.org/browse/JBIDE-22411 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: docker Affects Versions: 4.4.0.Alpha2 Reporter: Nick Boldt -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-712) Unhandled event loop exception No more handles when trying to download jBPM quickstart

by Josef Ludvicek (JIRA)

[ https://issues.jboss.org/browse/JBTIS-712?page=com.atlassian.jira.plugin.... ] Josef Ludvicek updated JBTIS-712: --------------------------------- Summary: Unhandled event loop exception No more handles when trying to download jBPM quickstart (was: org.eclipse.swt.SWTError: No more handles when trying to download jBPM quickstart) > Unhandled event loop exception No more handles when trying to download jBPM quickstart > -------------------------------------------------------------------------------------- > > Key: JBTIS-712 > URL: https://issues.jboss.org/browse/JBTIS-712 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPMN2 > Reporter: Josef Ludvicek > > Installed JBDS 9.1.0.GA + installed JBoss Business Process and Rules Development > File -> New -> Other -> jBPM Project -> example from online repository -> jBPM Playground at github (droolsjbpm-6.3) > throws org.eclipse.swt.SWTError: No more handles > {code} > org.eclipse.swt.SWTError: No more handles > at org.eclipse.swt.SWT.error(SWT.java:4517) > at org.eclipse.swt.SWT.error(SWT.java:4406) > at org.eclipse.swt.SWT.error(SWT.java:4377) > at org.eclipse.swt.browser.Browser.<init>(Browser.java:103) > at org.kie.eclipse.wizard.project.AbstractKieOnlineExampleProjectWizardPage.createOnlineExampleProjectControls(AbstractKieOnlineExampleProjectWizardPage.java:268) > at org.kie.eclipse.wizard.project.AbstractKieOnlineExampleProjectWizardPage.handleOnlineExampleProjectSelected(AbstractKieOnlineExampleProjectWizardPage.java:342) > at org.kie.eclipse.wizard.project.AbstractKieOnlineExampleProjectWizardPage.access$1(AbstractKieOnlineExampleProjectWizardPage.java:341) > at org.kie.eclipse.wizard.project.AbstractKieOnlineExampleProjectWizardPage$1.widgetSelected(AbstractKieOnlineExampleProjectWizardPage.java:99) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269) > at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343) > at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:160) > at org.eclipse.ui.internal.actions.CommandAction.run(CommandAction.java:175) > at org.eclipse.ui.actions.NewWizardDropDownAction.run(NewWizardDropDownAction.java:188) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) > at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:462) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) > at org.eclipse.equinox.launcher.Main.run(Main.java:1515) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-712) org.eclipse.swt.SWTError: No more handles when trying to download jBPM quickstart

by Josef Ludvicek (JIRA)

Josef Ludvicek created JBTIS-712: ------------------------------------ Summary: org.eclipse.swt.SWTError: No more handles when trying to download jBPM quickstart Key: JBTIS-712 URL: https://issues.jboss.org/browse/JBTIS-712 Project: JBoss Tools Integration Stack Issue Type: Bug Components: BPMN2 Reporter: Josef Ludvicek Installed JBDS 9.1.0.GA + installed JBoss Business Process and Rules Development File -> New -> Other -> jBPM Project -> example from online repository -> jBPM Playground at github (droolsjbpm-6.3) throws org.eclipse.swt.SWTError: No more handles {code} org.eclipse.swt.SWTError: No more handles at org.eclipse.swt.SWT.error(SWT.java:4517) at org.eclipse.swt.SWT.error(SWT.java:4406) at org.eclipse.swt.SWT.error(SWT.java:4377) at org.eclipse.swt.browser.Browser.<init>(Browser.java:103) at org.kie.eclipse.wizard.project.AbstractKieOnlineExampleProjectWizardPage.createOnlineExampleProjectControls(AbstractKieOnlineExampleProjectWizardPage.java:268) at org.kie.eclipse.wizard.project.AbstractKieOnlineExampleProjectWizardPage.handleOnlineExampleProjectSelected(AbstractKieOnlineExampleProjectWizardPage.java:342) at org.kie.eclipse.wizard.project.AbstractKieOnlineExampleProjectWizardPage.access$1(AbstractKieOnlineExampleProjectWizardPage.java:341) at org.kie.eclipse.wizard.project.AbstractKieOnlineExampleProjectWizardPage$1.widgetSelected(AbstractKieOnlineExampleProjectWizardPage.java:99) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) at org.eclipse.jface.window.Window.open(Window.java:803) at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234) at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:160) at org.eclipse.ui.internal.actions.CommandAction.run(CommandAction.java:175) at org.eclipse.ui.actions.NewWizardDropDownAction.run(NewWizardDropDownAction.java:188) at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:462) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) at org.eclipse.equinox.launcher.Main.run(Main.java:1515) at org.eclipse.equinox.launcher.Main.main(Main.java:1488) {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22383) Application Wizard: Selected project combo box is empty

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22383?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22383: --------------------------------------- I know about JBIDE-22380 and this one is different. The JBIDE-22380 happens when opening a New OpenShift Application wizard via OpenShift Explorer view from context menu of a project. This issue happens when opening via shell menu File - New - OpenShift Application and only in particular case = if different project than first one placed under a connection is selected in OpenShift Explorer view. In addition JBIDE-22380 has combo box disabled (as it seems to be disabled according to the screenshot attached in the JIRA. Personally I was not able to reproduce that issue so far). In my case the combo box is enabled and it is possible to select any OpenShift project. The only outstanding problem here is the empty selection in the combo box. > Application Wizard: Selected project combo box is empty > ------------------------------------------------------- > > Key: JBIDE-22383 > URL: https://issues.jboss.org/browse/JBIDE-22383 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Labels: application_wizard, openshift_v3 > > Having a connection with several projects and a different than the first one project selected in OpenShift Explorer view, opening of a New OpenShift Application wizard via shell menu File - New - OpenShift Application leaves combo box for a project empty. If the first project is preselect in OpenShift Explorer view, its ok. Issues is only with selected project different than the first one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21861) Include Docker & Vagrant tooling 2.0.0 in JBT 4.4.x TP

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21861?page=com.atlassian.jira.plugi... ] Jeff Johnston commented on JBIDE-21861: --------------------------------------- Latest Docker tooling from Linux Tools can be found at: http://download.eclipse.org/linuxtools/update-neon-docker-rc1 > Include Docker & Vagrant tooling 2.0.0 in JBT 4.4.x TP > ------------------------------------------------------ > > Key: JBIDE-21861 > URL: https://issues.jboss.org/browse/JBIDE-21861 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha2 > > > Include Docker tooling 2.0.0 in Target Platform 4.60.x, targeting JBoss Tools 4.4.x -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-201) Trying to run an image from DockerExplorerView says image needs pulling for a secondary tag [EBZ#493953]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-201: --------------------------------------- Summary: Trying to run an image from DockerExplorerView says image needs pulling for a secondary tag [EBZ#493953] Key: ERT-201 URL: https://issues.jboss.org/browse/ERT-201 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Fix For: Neon (4.6) Trying to run an image which has multiple tags picks the last tag listed in the DockerExplorerView node. The Run Image Wizard will only show the first in any list and thinks that the image is not pulled so issues a message about it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22403) BrowserSim New and Noteworthy for 4.4.0.Alpha2

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22403?page=com.atlassian.jira.plugi... ] Ilya Buziuk closed JBIDE-22403. ------------------------------- Resolution: Rejected No N&N in that release > BrowserSim New and Noteworthy for 4.4.0.Alpha2 > ---------------------------------------------- > > Key: JBIDE-22403 > URL: https://issues.jboss.org/browse/JBIDE-22403 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: browsersim > Reporter: Alexey Kazakov > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If BrowserSim is not listed here check if there are issues that should be added and add them. > Document the ones relevant for BrowserSim by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22391) Visual Editor New and Noteworthy for 4.4.0.Alpha2

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22391?page=com.atlassian.jira.plugi... ] Ilya Buziuk closed JBIDE-22391. ------------------------------- Release Notes Text: No N&N in that release Resolution: Rejected > Visual Editor New and Noteworthy for 4.4.0.Alpha2 > ------------------------------------------------- > > Key: JBIDE-22391 > URL: https://issues.jboss.org/browse/JBIDE-22391 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: visual-page-editor-core, visual-page-editor-templates > Reporter: Alexey Kazakov > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Visual Editor is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Visual Editor by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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