December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20422) Docker explorer - Stopping a container removes it from the explorer display

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20422?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20422. --------------------------------- Verified in JBDS 9.0.0.Beta1 B197 > Docker explorer - Stopping a container removes it from the explorer display > --------------------------------------------------------------------------- > > Key: JBIDE-20422 > URL: https://issues.jboss.org/browse/JBIDE-20422 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: docker, upstream > Affects Versions: 4.3.0.Beta2 > Environment: RHEL 7 > Java 8 > Reporter: Len DiMaggio > Assignee: Xavier Coulon > Fix For: 4.3.1.Beta1 > > > Once the container is removed from the Docker explorer, the user must go to the CLI to restart it and have it appear again in the explorer. > Why not leave it visible in the Docker explorer and mark it as stopped? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20741) JVM Navigator "Link with Editor" toggle button force current selection to be current and visible

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20741?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20741. --------------------------------- Verified in jboss-devstudio-9.1.0.Beta1-v20151216-2040-B197-installer-standalone.jar > JVM Navigator "Link with Editor" toggle button force current selection to be current and visible > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-20741 > URL: https://issues.jboss.org/browse/JBIDE-20741 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.3.0.CR1 > Reporter: Denis Golovin > Assignee: Rob Stryker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > Attachments: viewer-linking.mp4 > > > Watch attached [^viewer-linking.mp4] to see actual behavior. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21352) OpenShift Server Adapter: New server adapter could use preselected project from project explorer

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21352?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21352: ------------------------------------------ [~scabanovich] dare to review https://github.com/jbosstools/jbosstools-openshift/pull/864? > OpenShift Server Adapter: New server adapter could use preselected project from project explorer > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-21352 > URL: https://issues.jboss.org/browse/JBIDE-21352 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.3.1.Beta2 > > > It would be nice if wizard to create a new OpenShift 3 server adapter would use preselected project from Project explorer, if it is opened and selected. Currently it uses first eclipse project. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-695) Review: 9.1.0 Beta1 Release Notes

by Supriya Bharadwaj (JIRA)

Supriya Bharadwaj created TOOLSDOC-695: ------------------------------------------ Summary: Review: 9.1.0 Beta1 Release Notes Key: TOOLSDOC-695 URL: https://issues.jboss.org/browse/TOOLSDOC-695 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Feature Request Reporter: Supriya Bharadwaj Assignee: Martin Malina Please review the RNs located at: http://docbuilder.usersys.redhat.com/23115/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20966) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Central]

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20966?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20966. --------------------------------- Done. > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Central] > --------------------------------------------------------- > > Key: JBIDE-20966 > URL: https://issues.jboss.org/browse/JBIDE-20966 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central, maven, project-examples > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Central]: Please perform the following tasks: > If you expect to be doing 4.3.x maintenance work in your component: > 1a. In your *{color:blue}4.3.x branch{color}*, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1 (if planning minor changes). > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT > {code} > 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.) > 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta1-SNAPSHOT</version> > </parent> > {code} > 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above. > 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*; > {code} > mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21157) CDK Server adapter - Windows support

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21157?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21157. --------------------------------- Subtasks closed. Closing this. > CDK Server adapter - Windows support > ------------------------------------ > > Key: JBIDE-21157 > URL: https://issues.jboss.org/browse/JBIDE-21157 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Ensure CDK Server adapter is suitable for use on windows and works OOTB to the best of our ability. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21196) [cdk] Ensure VAGRANT_DETECTED_OS is set to cygwin when in windows

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21196?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21196. --------------------------------- I saw this set when I tested on Windows 2 days ago. Closing. > [cdk] Ensure VAGRANT_DETECTED_OS is set to cygwin when in windows > ------------------------------------------------------------------ > > Key: JBIDE-21196 > URL: https://issues.jboss.org/browse/JBIDE-21196 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift, server > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > This requires other changes. Once cygwin is set, output will include color codes, so the --no-color flag must also be set. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21194) Result from adbinfo on windows has different syntax

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21194?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21194. --------------------------------- This is done and working the way Rob described. If you want it to be done differently, please create a new JIRA. > Result from adbinfo on windows has different syntax > --------------------------------------------------- > > Key: JBIDE-21194 > URL: https://issues.jboss.org/browse/JBIDE-21194 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift, server > Affects Versions: 4.3.0.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > The result from adbinfo on linux is: > {code} > export key=value > {code} > The result on Windows is: > {code} > setx key value > {code} > The adbinfo runner needs to be aware of this difference and react accordingly when creating the openshift connection. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21175) [CDK] Require better logic to find vagrant.exe / vagrant command

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21175?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21175. --------------------------------- This works properly on Windows now. There is an open JIRA for mac though. > [CDK] Require better logic to find vagrant.exe / vagrant command > ---------------------------------------------------------------- > > Key: JBIDE-21175 > URL: https://issues.jboss.org/browse/JBIDE-21175 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift, server > Affects Versions: 4.3.1.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > First step to support for windows is properly locating vagrant.exe. This isn't a windows-only issue, though, as [~mmalina] has already commented that his vagrant was in /usr/local/bin/vagrant rather than /usr/bin/vagrant > So this is a concern on all OSes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20738) JMX Navigator Refresh Command is running in main UI Thread

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20738?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-20738: --------------------------------------- [~rob.stryker], is there an easy way to verify? I never had a problem with this. And is this refresh in the JMX navigator view, or properties of a connected JVM process? > JMX Navigator Refresh Command is running in main UI Thread > ---------------------------------------------------------- > > Key: JBIDE-20738 > URL: https://issues.jboss.org/browse/JBIDE-20738 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.3.0.CR1 > Reporter: Denis Golovin > Assignee: Rob Stryker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Refresh in JMX Navigator freezes UI because executed in main UI thread: > {code}Thread [main] (Suspended (breakpoint at line 435 in org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm)) > owns: org.jboss.tools.jmx.local.internal.JvmConnectionWrapper (id=162) > org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.initialize(javax.management.remote.JMXServiceURL) line: 435 > org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.initialize(java.lang.String, int) line: 465 > org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.initialize() line: 445 > org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.connect(int, boolean) line: 233 > org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.connect(int) line: 213 > org.jboss.tools.jmx.local.internal.JvmConnectionWrapper.connect() line: 121 > org.jboss.tools.jmx.ui.internal.actions.RefreshAction.refreshObjectNode(java.lang.Object) line: 107 > org.jboss.tools.jmx.ui.internal.actions.RefreshAction.run() line: 153 > org.jboss.tools.jmx.ui.internal.actions.RefreshAction(org.eclipse.jface.action.Action).runWithEvent(org.eclipse.swt.widgets.Event) line: 473 > org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(org.eclipse.swt.widgets.Event, boolean) line: 595 > org.eclipse.jface.action.ActionContributionItem.access$2(org.eclipse.jface.action.ActionContributionItem, org.eclipse.swt.widgets.Event, boolean) line: 511 > org.eclipse.jface.action.ActionContributionItem$5.handleEvent(org.eclipse.swt.widgets.Event) line: 420 > org.eclipse.swt.widgets.EventTable.sendEvent(org.eclipse.swt.widgets.Event) line: 84 > org.eclipse.swt.widgets.Display.sendEvent(org.eclipse.swt.widgets.EventTable, org.eclipse.swt.widgets.Event) line: 4481 > org.eclipse.swt.widgets.MenuItem(org.eclipse.swt.widgets.Widget).sendEvent(org.eclipse.swt.widgets.Event) line: 1327 > org.eclipse.swt.widgets.Display.runDeferredEvents() line: 3819 > org.eclipse.swt.widgets.Display.readAndDispatch() line: 3430 > org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run() line: 1127 > org.eclipse.core.databinding.observable.Realm.runWithDefault(org.eclipse.core.databinding.observable.Realm, java.lang.Runnable) line: 337 > org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(org.eclipse.e4.ui.model.application.MApplicationElement, org.eclipse.e4.core.contexts.IEclipseContext) line: 1018 > org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(org.eclipse.e4.ui.model.application.MApplicationElement) line: 156 > org.eclipse.ui.internal.Workbench$5.run() line: 654 > org.eclipse.core.databinding.observable.Realm.runWithDefault(org.eclipse.core.databinding.observable.Realm, java.lang.Runnable) line: 337 > org.eclipse.ui.internal.Workbench.createAndRunWorkbench(org.eclipse.swt.widgets.Display, org.eclipse.ui.application.WorkbenchAdvisor) line: 598 > org.eclipse.ui.PlatformUI.createAndRunWorkbench(org.eclipse.swt.widgets.Display, org.eclipse.ui.application.WorkbenchAdvisor) line: 150 > org.eclipse.ui.internal.ide.application.IDEApplication.start(org.eclipse.equinox.app.IApplicationContext) line: 139 > org.eclipse.equinox.internal.app.EclipseAppHandle.run(java.lang.Object) line: 196 > org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(java.lang.Object) line: 134 > org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(java.lang.Object) line: 104 > org.eclipse.core.runtime.adaptor.EclipseStarter.run(java.lang.Object) line: 380 > org.eclipse.core.runtime.adaptor.EclipseStarter.run(java.lang.String[], java.lang.Runnable) line: 235 > sun.reflect.NativeMethodAccessorImpl.invoke0(java.lang.reflect.Method, java.lang.Object, java.lang.Object[]) line: not available [native method] > sun.reflect.NativeMethodAccessorImpl.invoke(java.lang.Object, java.lang.Object[]) line: 62 > sun.reflect.DelegatingMethodAccessorImpl.invoke(java.lang.Object, java.lang.Object[]) line: 43 > java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object...) line: 497 > org.eclipse.equinox.launcher.Main.invokeFramework(java.lang.String[], java.net.URL[]) line: 669 > org.eclipse.equinox.launcher.Main.basicRun(java.lang.String[]) line: 608 > org.eclipse.equinox.launcher.Main.run(java.lang.String[]) line: 1515 > org.eclipse.equinox.launcher.Main.main(java.lang.String[]) line: 1488 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 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 December 2015