July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22718) NullPointerException in HIDDEN

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22718?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-22718: ------------------------------------- Assignee: Snjezana Peco > NullPointerException in HIDDEN > ------------------------------ > > Key: JBIDE-22718 > URL: https://issues.jboss.org/browse/JBIDE-22718 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian > Affects Versions: 4.4.x > Reporter: Automated Error Reporting Bot > Assignee: Snjezana Peco > > The following problem was reported via the automated error reporting: > Message: > {noformat} > java.lang.NullPointerException: null > at HIDDEN.HIDDEN(HIDDEN:-1) > at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2) > 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.jboss.tools.arquillian.ui.internal.utils.ArquillianUIUtil.addContainerProperties(ArquillianUIUtil.java:581) > at org.jboss.tools.arquillian.ui.internal.utils.ArquillianUIUtil.getArquillianProperties(ArquillianUIUtil.java:507) > at org.jboss.tools.arquillian.ui.internal.launcher.ArquillianTab.initializeFrom(ArquillianTab.java:644) > at org.eclipse.debug.ui.AbstractLaunchConfigurationTab.activated(AbstractLaunchConfigurationTab.java:411) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.handleTabSelected(LaunchConfigurationTabGroupViewer.java:1365) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$6.widgetSelected(LaunchConfigurationTabGroupViewer.java:377) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > {noformat} > Bundles: > | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 | > | org.eclipse.debug.ui | 3.11.101.v20160203-1230 | 3.11.101.v20160203-1230 | > | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.11.1.v20160128-1644 | > | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 | > | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 | > | org.jboss.tools.arquillian.ui | 1.2.1.Final-v20160331-0142-B69 | 1.2.1.Final-v20160331-0142-B69 | > Operating Systems: > | Windows | 6.3.0 | 6.3.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57344b2ee4b0138d62...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22718) NullPointerException in HIDDEN

by Automated Error Reporting Bot (JIRA)

Automated Error Reporting Bot created JBIDE-22718: ----------------------------------------------------- Summary: NullPointerException in HIDDEN Key: JBIDE-22718 URL: https://issues.jboss.org/browse/JBIDE-22718 Project: Tools (JBoss Tools) Issue Type: Bug Components: arquillian Affects Versions: 4.4.x Reporter: Automated Error Reporting Bot The following problem was reported via the automated error reporting: Message: {noformat} java.lang.NullPointerException: null at HIDDEN.HIDDEN(HIDDEN:-1) at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2) 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.jboss.tools.arquillian.ui.internal.utils.ArquillianUIUtil.addContainerProperties(ArquillianUIUtil.java:581) at org.jboss.tools.arquillian.ui.internal.utils.ArquillianUIUtil.getArquillianProperties(ArquillianUIUtil.java:507) at org.jboss.tools.arquillian.ui.internal.launcher.ArquillianTab.initializeFrom(ArquillianTab.java:644) at org.eclipse.debug.ui.AbstractLaunchConfigurationTab.activated(AbstractLaunchConfigurationTab.java:411) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.handleTabSelected(LaunchConfigurationTabGroupViewer.java:1365) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$6.widgetSelected(LaunchConfigurationTabGroupViewer.java:377) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) {noformat} Bundles: | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 | | org.eclipse.debug.ui | 3.11.101.v20160203-1230 | 3.11.101.v20160203-1230 | | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.11.1.v20160128-1644 | | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 | | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 | | org.jboss.tools.arquillian.ui | 1.2.1.Final-v20160331-0142-B69 | 1.2.1.Final-v20160331-0142-B69 | Operating Systems: | Windows | 6.3.0 | 6.3.0 | The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57344b2ee4b0138d62...] for the latest data. Thank you for your assistance. Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22635) Deprecate the Server Log View

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22635?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22635: ----------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.4.1.AM1) > Deprecate the Server Log View > ----------------------------- > > Key: JBIDE-22635 > URL: https://issues.jboss.org/browse/JBIDE-22635 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.4.1.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.1.AM2 > > > Deprecate and remove the Server Log View. > The Server Log View was originally designed to allow a custom "Error Log" to be filled with information that wasn't just "errors" but more like tracing what the server adapter was doing. > In it's original form, it held all status warnings and errors, and users never saw them. Eventually, we started also sending the status objects to the official Error Log, so users may see them. Once that happened, the Server Log view became completely redundant. It's only benefits were that it occasionally over-logged stuff that wasn't appropriate to send to the main error log... but it's API / extension points were kinda ugly, and it overall isn't very useful any longer. > Also, other server adapters have requested we remove the action at least, for their server types, since they never use the Server Log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22695) Environment Variables of application deployment should have different workflow

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22695?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22695: ----------------------------------------------- 'Manage Environment Variables' dialog just edits one part of a selected resource. If a dialog modifying a resource results in creating a new copy of the resource with readjusting the project to it, it will look as a bad implementation of the version control system. Resetting to original state may seem good for a project that has a short story of changes. If it had a lot of modifications, then some intermediate state may be more preferred than the original. Does Openshift keeps the history of changes for each resource? If it does, we might have a feature button 'Restore from History' to show versions and their differences from the current state. I would leave button 'Reset All' to do what it does now - handle diffs of current input from the last saved state. If Openshift does not keep the history, any hard-wired solution will have its limitations. > Environment Variables of application deployment should have different workflow > ------------------------------------------------------------------------------ > > Key: JBIDE-22695 > URL: https://issues.jboss.org/browse/JBIDE-22695 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v3 > > Reset All button in Environment Var wizard dialog should get application to default state. At the moment it reset environment variables in the table just to the values at the point of opening the wizard. If I would delete some environment variables and confirm changes, but I would find out I broke something and I would like to rollback it to original state, I would try to reset it with Reset All button. But it won't work for me. This is causing the more serious issue: > Because we edit same deployment configuration and start deployments from it and in the same time we set number of replicas in other deployment configs to zero. So we don't have the original deployment config and thus we cannot rollback easily (well there is a way but nasty one - edit replication controller, copy and paste environment variables to the deployment config, save it and deploy latest). > There are 2 options: > a) Create a new deployment configuration for a new (modified) set of environment variables and create a new replication controller (deployment) from this deployment configuration. There is one con - it can lead to many deployment configurations and replication controllers (for each deployment configuration there would be one replication controller). > b) Just edit current replication controller (deployment) of an application or create a new one from an existing but with modified env. vars and with correct amount of replicas and set replicas in the previous to 0. And then let respin pods with correct setup. One of those approaches (create/edit RC) would be, I think, more satisfying. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22702) Decorators are shifted after selecting an element in combo which displays a submessage

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22702?page=com.atlassian.jira.plugi... ] George Gastaldi resolved JBIDE-22702. ------------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.4.x) Assignee: George Gastaldi Resolution: Done > Decorators are shifted after selecting an element in combo which displays a submessage > -------------------------------------------------------------------------------------- > > Key: JBIDE-22702 > URL: https://issues.jboss.org/browse/JBIDE-22702 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.4.0.Final > Environment: Windows 10 > Reporter: Aurélien Pupier > Assignee: George Gastaldi > Fix For: 4.4.1.AM2 > > Attachments: after.png, before.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22702) Decorators are shifted after selecting an element in combo which displays a submessage

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22702?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-22702: ----------------------------------------- Fixed. Please test with the code in master > Decorators are shifted after selecting an element in combo which displays a submessage > -------------------------------------------------------------------------------------- > > Key: JBIDE-22702 > URL: https://issues.jboss.org/browse/JBIDE-22702 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.4.0.Final > Environment: Windows 10 > Reporter: Aurélien Pupier > Assignee: George Gastaldi > Fix For: 4.4.1.AM2 > > Attachments: after.png, before.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22608) Support scenario when cdk is stopped from cli and then in devstudio

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22608?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-22608. --------------------------------- Fix Version/s: 4.4.1.AM1 Resolution: Done Sometimes the server actions don't update their enablement right away, and you might have to click off your selection and re-click it again to get an accurate menu with accurate enablement. I can't replicate this at this time, so I'm closing it. It seems the issue where cdk is stopped from cmd line has been fixed, and the tools handle this properly now. > Support scenario when cdk is stopped from cli and then in devstudio > ------------------------------------------------------------------- > > Key: JBIDE-22608 > URL: https://issues.jboss.org/browse/JBIDE-22608 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.1.AM1 > > > Assume your cdk is started and it's shown as started in devstudio, now what if you stop cdk from cli for whatever reason? Currently the tooling can't handle such situation. > If you then try to stop cdk in devstudio, you get an error pop-up: > Server Container Development Environment failed to stop. > And the console will just say: > ==> default: VM not created. Moving on... > But most importantly, the server adapter will stay in the Started state. > We should probably support this scenario - it's quite likely that it will happen to users. > Right now there are several ways out of this situation: > a) Start cdk from cli again and everything will probably work as expected > b) Restart your IDE > So I suggest we improve the tooling in such a way that when you stop cdk, it will be able to detect that it's actually not running and just change the state to Stopped. It may be still ok to pop up the error saying it failed to stop. But at least you can now start it again from the IDE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22717) Remove all server log view code

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22717?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22717: -------------------------------- Fix Version/s: 4.5.0.AM1 > Remove all server log view code > ------------------------------- > > Key: JBIDE-22717 > URL: https://issues.jboss.org/browse/JBIDE-22717 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.4.0.Final > Reporter: Rob Stryker > Fix For: 4.5.0.AM1 > > > Follow up on: https://issues.jboss.org/browse/JBIDE-22635 > Remove the deprecated classes and extension points. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22717) Remove all server log view code

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22717?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-22717: ----------------------------------- Assignee: Rob Stryker > Remove all server log view code > ------------------------------- > > Key: JBIDE-22717 > URL: https://issues.jboss.org/browse/JBIDE-22717 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.4.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > Follow up on: https://issues.jboss.org/browse/JBIDE-22635 > Remove the deprecated classes and extension points. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22635) Deprecate the Server Log View

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22635?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22635: -------------------------------- Fix Version/s: 4.4.1.AM1 > Deprecate the Server Log View > ----------------------------- > > Key: JBIDE-22635 > URL: https://issues.jboss.org/browse/JBIDE-22635 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.4.1.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.1.AM1 > > > Deprecate and remove the Server Log View. > The Server Log View was originally designed to allow a custom "Error Log" to be filled with information that wasn't just "errors" but more like tracing what the server adapter was doing. > In it's original form, it held all status warnings and errors, and users never saw them. Eventually, we started also sending the status objects to the official Error Log, so users may see them. Once that happened, the Server Log view became completely redundant. It's only benefits were that it occasionally over-logged stuff that wasn't appropriate to send to the main error log... but it's API / extension points were kinda ugly, and it overall isn't very useful any longer. > Also, other server adapters have requested we remove the action at least, for their server types, since they never use the Server Log. -- 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 July 2016