April 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20570) OpenShift Explorer: needs an "Expand All" button

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20570?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20570: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > OpenShift Explorer: needs an "Expand All" button > ------------------------------------------------ > > Key: JBIDE-20570 > URL: https://issues.jboss.org/browse/JBIDE-20570 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Priority: Minor > Labels: explorer, openshift_v3 > Fix For: 4.6.x > > > OpenShift Explorer displays collapsed resources by default. Having to expand resources manually one by one is annoying, as reported by [~sspeiche]. It'd be better to have an Expand All button next to the Collapse All one in the explorer. > Or it might make sense to be able to expand all from a particular node -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22266) Use a SessionFactory in a debugged program as a "Console Configuration"

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22266?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22266: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Use a SessionFactory in a debugged program as a "Console Configuration" > ----------------------------------------------------------------------- > > Key: JBIDE-22266 > URL: https://issues.jboss.org/browse/JBIDE-22266 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Reporter: Koen Aers > Fix For: 4.6.x > > > clicking on a sessionfactory/session in the debug view and run queries/visualization directly against it....no configuration needed (except having a running app) > => copied from HBX-563 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19283) Unnecessary dialog displayed when LiveReload is enabled/disabled for BrowserSim

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19283?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-19283: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Unnecessary dialog displayed when LiveReload is enabled/disabled for BrowserSim > ------------------------------------------------------------------------------- > > Key: JBIDE-19283 > URL: https://issues.jboss.org/browse/JBIDE-19283 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.0.Alpha1 > Environment: JBDS 9.0.0.Alpha1-v20150216-1042-B11 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Priority: Minor > Fix For: 4.6.x > > > 1. Open BrowserSim > 2. Select skin which doesn't fit to screen > ASSERT: Dialog asking to choose Truncate or Show actual size is displayed > 3. Select one from those options > 4. Enable or disable LiveReload for BrowserSim > ERROR: Dialog asking to choose Truncate or Show actual size is displayed -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19466) Improve the usability of the dropdown component

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19466?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-19466: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Improve the usability of the dropdown component > ----------------------------------------------- > > Key: JBIDE-19466 > URL: https://issues.jboss.org/browse/JBIDE-19466 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.6.x > > > Currently if the dropdown has too many items, it is painful to select the one you want. The problem is especially present/painful on OSX. It would be good if a text field can be used to narrow down the items in the list. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19181) correct naming of internal packages so that they're consistent across all openshift plugins

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19181?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-19181: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > correct naming of internal packages so that they're consistent across all openshift plugins > ------------------------------------------------------------------------------------------- > > Key: JBIDE-19181 > URL: https://issues.jboss.org/browse/JBIDE-19181 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Andre Dietisheim > Fix For: 4.6.x > > > Internal packages across the openshift plugins are non-consistent: > ex. > org.jboss.tools.openshift.client: org.jboss.tools.openshift.client.internal > org.jboss.tools.openshift.express.client: org.jboss.tools.openshift.express.client.internal > the base is imho org.jboss.tools.openshift and thus internal packages should always be at org.jboss.tools.openshift.internal across plugins. > For reference, here's the official Eclipse documentation on the topic: http://wiki.eclipse.org/index.php/Naming_Conventions#Java_Packages > {quote} > org.eclipse.jdt.internal.core.compiler - Correct usage > org.eclipse.jdt.core.internal.compiler - Incorrect. internal should immediately follow subproject name. > org.eclipse.core.internal.resources - Correct usage > org.eclipse.internal.core.resources - Incorrect. internal should never immediately follow org.eclipse. > org.eclipse.core.resources.internal - Incorrect. internal should immediately follow Eclipse Platform component name. > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25207) Integration Tests: PortForwardingTest, Win10: Eclipse is missing required privileges

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25207?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25207: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Integration Tests: PortForwardingTest, Win10: Eclipse is missing required privileges > ------------------------------------------------------------------------------------ > > Key: JBIDE-25207 > URL: https://issues.jboss.org/browse/JBIDE-25207 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Environment: Windows 10 > Reporter: Andre Dietisheim > Labels: integration_tests > Fix For: 4.6.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24177) Command to tune storage

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24177?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24177: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Command to tune storage > ----------------------- > > Key: JBIDE-24177 > URL: https://issues.jboss.org/browse/JBIDE-24177 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.6.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22950) ClassNotFoundException below ExternalProcessLauncher.launch (thrown in BundleLoader.findClassInternal)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22950?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22950: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > ClassNotFoundException below ExternalProcessLauncher.launch (thrown in BundleLoader.findClassInternal) > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22950 > URL: https://issues.jboss.org/browse/JBIDE-22950 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Reporter: Automated Error Reporting Bot > Assignee: Ilya Buziuk > Fix For: 4.6.x > > > The following problem was reported via the automated error reporting: > Message: Error logged from Debug UI: > {noformat} > java.lang.ClassNotFoundException: org.jboss.ide.eclipse.freemarker.linetracker.ConsoleLineTracker cannot be found by org.jboss.ide.eclipse.freemarker_1.5.101.v20160718-0829 > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:448) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:361) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:353) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:564) > at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174) > at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905) > at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) > at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) > at org.eclipse.debug.internal.ui.views.console.ProcessConsoleManager.getLineTrackers(ProcessConsoleManager.java:281) > at org.eclipse.debug.internal.ui.views.console.ConsoleLineNotifier.connect(ConsoleLineNotifier.java:54) > at org.eclipse.ui.internal.console.ConsolePatternMatcher.addPatternMatchListener(ConsolePatternMatcher.java:232) > at org.eclipse.ui.console.TextConsole.addPatternMatchListener(TextConsole.java:409) > at org.eclipse.debug.internal.ui.views.console.ProcessConsole.<init>(ProcessConsole.java:228) > at org.eclipse.debug.internal.ui.views.console.ProcessConsoleManager.launchChanged(ProcessConsoleManager.java:149) > at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.run(LaunchManager.java:453) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.notify(LaunchManager.java:433) > at org.eclipse.debug.internal.core.LaunchManager.fireUpdate(LaunchManager.java:1043) > at org.eclipse.debug.core.Launch.fireChanged(Launch.java:393) > at org.eclipse.debug.core.Launch.addProcess(Launch.java:355) > at org.eclipse.debug.core.model.RuntimeProcess.<init>(RuntimeProcess.java:126) > at org.eclipse.debug.core.DebugPlugin.newProcess(DebugPlugin.java:787) > at org.eclipse.jdt.launching.AbstractVMRunner.newProcess(AbstractVMRunner.java:170) > at org.eclipse.jdt.internal.launching.StandardVMRunner.run(StandardVMRunner.java:424) > at org.eclipse.jdt.launching.JavaLaunchDelegate.launch(JavaLaunchDelegate.java:102) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.jboss.tools.browsersim.eclipse.launcher.ExternalProcessLauncher.launch(ExternalProcessLauncher.java:250) > at org.jboss.tools.browsersim.eclipse.launcher.ExternalProcessLauncher.launchAsExternalProcess(ExternalProcessLauncher.java:81) > at org.jboss.tools.browsersim.eclipse.launcher.BrowserSimLauncher.launchBrowserSim(BrowserSimLauncher.java:70) > at org.jboss.tools.browsersim.eclipse.actions.RunBrowserSimAction.run(RunBrowserSimAction.java:29) > at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:247) > at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:228) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565) > at org.eclipse.jface.action.ActionContributionItem.lambda$5(ActionContributionItem.java:436) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > {noformat} > Bundles: > | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 | > | org.eclipse.debug.core | 3.10.100.v20160419-1720 | 3.10.100.v20160419-1720 | > | org.eclipse.debug.ui | 3.11.200.v20160518-1858 | 3.11.200.v20160518-1858 | > | org.eclipse.jdt.launching | 3.8.100.v20160505-0636 | 3.8.100.v20160505-0636 | > | org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.0.v20160518-1929 | > | org.eclipse.osgi | 3.11.0.v20160603-1336 | 3.11.0.v20160603-1336 | > | org.eclipse.swt | 3.105.0.v20160603-0902 | 3.105.0.v20160603-0902 | > | org.eclipse.ui | 3.108.0.v20160518-1929 | 3.108.0.v20160518-1929 | > | org.eclipse.ui.console | 3.6.200.v20160518-1858 | 3.6.200.v20160518-1858 | > | org.jboss.tools.browsersim.eclipse | 3.8.1.v20160610-2137 | 3.8.1.v20160610-2137 | > Operating Systems: > | MacOSX | 10.11.5 | 10.11.5 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/579206b7e4b0024f7d...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23051) CoreException below ChainTextHover.getHoverInfo2 (thrown in FaceletTagRegistry.initialize)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23051?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23051: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > CoreException below ChainTextHover.getHoverInfo2 (thrown in FaceletTagRegistry.initialize) > ------------------------------------------------------------------------------------------ > > Key: JBIDE-23051 > URL: https://issues.jboss.org/browse/JBIDE-23051 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.3.0.Final > Reporter: Automated Error Reporting Bot > Assignee: Viacheslav Kabanovich > Fix For: 4.6.x > > > The following problem was reported via the automated error reporting: > Message: Problem during initialization > {noformat} > org.eclipse.core.runtime.CoreException: Project either does not exists or is not a java project: P/pcc.pom > at org.eclipse.jst.jsf.facelet.core.internal.registry.FaceletTagRegistry.initialize(FaceletTagRegistry.java:159) > at org.eclipse.jst.jsf.facelet.core.internal.registry.FaceletTagRegistry.getAllTagLibraries(FaceletTagRegistry.java:129) > at org.eclipse.jst.jsf.facelet.core.internal.registry.FaceletTagRegistry.getTagLibrary(FaceletTagRegistry.java:230) > at org.eclipse.jst.jsf.facelet.core.internal.cm.FaceletDocumentFactory.getOrCreateCMDocument(FaceletDocumentFactory.java:160) > at org.eclipse.jst.jsf.facelet.core.internal.cm.FaceletDocumentFactory.createCMDocumentForContext(FaceletDocumentFactory.java:56) > at org.eclipse.jst.jsf.facelet.core.internal.cm.FaceletDocumentFactory.createCMElementDeclaration(FaceletDocumentFactory.java:78) > at org.eclipse.jst.jsf.facelet.ui.internal.hover.FaceletHover$MyHTMLTagInfoHoverProcessor.getCMElementDeclaration(FaceletHover.java:132) > at org.eclipse.wst.xml.ui.internal.taginfo.XMLTagInfoHoverProcessor.computeTagAttValueHelp(XMLTagInfoHoverProcessor.java:131) > at org.eclipse.wst.xml.ui.internal.taginfo.XMLTagInfoHoverProcessor.computeRegionHelp(XMLTagInfoHoverProcessor.java:111) > at org.eclipse.wst.xml.ui.internal.taginfo.XMLTagInfoHoverProcessor.computeHoverHelp(XMLTagInfoHoverProcessor.java:86) > at org.eclipse.wst.xml.ui.internal.taginfo.XMLTagInfoHoverProcessor.getHoverInfo(XMLTagInfoHoverProcessor.java:257) > at org.eclipse.jst.jsf.facelet.ui.internal.hover.FaceletHover.getHoverInfo(FaceletHover.java:58) > at org.jboss.tools.common.text.xml.info.ChainTextHover.getHoverInfo2(ChainTextHover.java:145) > at org.jboss.tools.common.text.xml.info.ChainTextHover.getHoverInfo2(ChainTextHover.java:132) > at org.eclipse.jface.text.TextViewerHoverManager$4.run(TextViewerHoverManager.java:165) > {noformat} > Bundles: > | org.eclipse.jface.text | 3.10.0.v20150603-1752 | 3.11.0.v20160505-1301 | > | org.eclipse.jst.jsf.facelet.core | 1.3.100.v201504071708 | 1.3.110.v201603071844 | > | org.eclipse.jst.jsf.facelet.ui | 1.3.100.v201505112336 | 1.3.110.v201603071844 | > | org.eclipse.wst.xml.ui | 1.1.501.v201501212057 | 1.1.700.v201604272318 | > | org.jboss.tools.common.text.xml | 3.7.1.Final-v20160408-2358-B112 | 3.8.0.Final-v20160610-1533-B7 | > Operating Systems: > | Linux | 3.2.0 | 4.6.4.fc23 | > | MacOSX | 10.11.3 | 10.11.5 | > | Windows | 6.1.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57052ef8e4b08ccb7b...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13546) Fix matrix param url generated from jaxrs explorer

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13546?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-13546: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Fix matrix param url generated from jaxrs explorer > -------------------------------------------------- > > Key: JBIDE-13546 > URL: https://issues.jboss.org/browse/JBIDE-13546 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.0.Alpha1 > Reporter: Jaroslav Jankovič > Assignee: Xavier Coulon > Labels: jax-rs > Fix For: 4.6.x > > Attachments: JBIDE-13546.jpg > > > There is difference when generating url from JAX RS explorer with parameters (matrix, query). This can cause issue when entering values in "WS Tester: URL Parameters" dialog. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 April 2018