December 2015 - jbosstools-issues

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

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20422?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-20422: --------------------------------------- Fixed in https://bugs.eclipse.org/bugs/show_bug.cgi?id=484113 (available for new workspaces). Otherwise, users can show/hide stopped containers in the Docker Explorer view and in the Docker Containers view. > 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.x > > > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21294) NPE when starting CDK server

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21294?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21294: ------------------------------------- [~mmalina] I don'thave a mac so I can't trace through this. It'd be great if you could tell me which of the following is going wrong somehow if you're able to trace through: (mark all that is wrong) 1) default location is wrong 2) search of path cannot find 3) use of 'which' fails I could of course just put in a dummy null-check but that won't solve the root of the issue. See CommandLocationLookupStrategy line 80. Also, did you happen to double-click the .app file? We know the .app file has issues with inheriting a full path, right? > NPE when starting CDK server > ---------------------------- > > Key: JBIDE-21294 > URL: https://issues.jboss.org/browse/JBIDE-21294 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > > I've been testing the CDK adapter with [1] today and when I tried to start again from scratch (vagrant destroy + new workspace) and added the server again and started, I got a NPE: > {code} > An internal error occurred during: "Starting cdk-v2 CDK Server". > java.lang.NullPointerException > at java.io.File.<init>(File.java:277) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(CDKLaunchController.java:133) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > 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.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > I did add the user credentials in the server editor. > Now I looked in the launch config and the first field at the top is empty - it should contain path to vagrant. I'm not sure why it's missing - I just used runtime detection. But in any case, the NPE should be handled somehow. > [1] https://github.com/redhat-developer-tooling/openshift-vagrant -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

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

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21157?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-21157. --------------------------------- Resolution: Done Basic windows support seems complete > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21187) Fix issues with styled label providers

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21187?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21187: ---------------------------------------- >From jbosstools-dev(a)lists.jboss.org: Max: {quote} Okey, but how about have at startup of the plugin check the SWT version and if it is the broken one disable custom painting and use the default if it is not the broken version ? Then you can build and install against Mars.0 but still work better when users install on Mars.1+ Seems like the simplest/best option ? {quote} Alexey: {quote}+1. I suggested that in JIRA too. I looked at the code and it seems to be easy to implement. Andre, if you are too busy fixing OS/CDK stuff for Beta1, I think we can ask [~snjeza] to help with that.{quote} > Fix issues with styled label providers > -------------------------------------- > > Key: JBIDE-21187 > URL: https://issues.jboss.org/browse/JBIDE-21187 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Snjezana Peco > Assignee: Andre Dietisheim > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta1 > > Attachments: bad-labels-tree.png, correct-labels-tree.png, openshift2-grey-decorations.png, openshift3-grey-decorations.png > > > Since https://bugs.eclipse.org/bugs/show_bug.cgi?id=466499 has been fixed, we can remove the workaround related to styled label providers. > The fix is included in Mars 4.5.1 (Mars.1) and Neon 4.6.0M2. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20916) importing jbosstools-website results in error

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20916?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20916: --------------------------------------------- eh - the error messsage is shown in the logs: {quote} org.eclipse.ui.internal.wizards.datatransfer.CouldNotImportProjectException: Could not import project located at /Users/max/Documents/workspace-centraltest at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.toExistingOrNewProject(EasymportJob.java:365) at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.run(EasymportJob.java:101) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: org.eclipse.core.internal.resources.ResourceException: Invalid project description. at org.eclipse.core.internal.resources.Project.checkDescription(Project.java:168) at org.eclipse.core.internal.resources.Project.assertCreateRequirements(Project.java:52) at org.eclipse.core.internal.resources.Project.create(Project.java:268) at org.eclipse.core.internal.resources.Project.create(Project.java:252) at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.createOrImportProject(EasymportJob.java:401) at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.toExistingOrNewProject(EasymportJob.java:353) ... 2 more {quote} exact stacktrace to locate where the error message is created. what more do you need ? > importing jbosstools-website results in error > --------------------------------------------- > > Key: JBIDE-20916 > URL: https://issues.jboss.org/browse/JBIDE-20916 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > use import nested of jbosstools-website result in progress dialog showing error saying: > {quote} > bin | Could not import project located at /Users/max/code/jbosstools/jbosstools-website/bin > {quote} > No additional info provided. > (note: this happened on second import so it might be when .project already there) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20609: --------------------------------------------- [~nickboldt] not sure I follow you comment to that link - this link seem to be exactly why the "advertise" feature is relevant/good ? > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20609: --------------------------------------------- "Well, I believe that's the core paradigm of this change. In my opinion, and as the change was designed, no-one needs to know whether a connector is EA or not before-hand. People install features, they're just interested in what they will be able to do with it. Whether it's EA or not is IMO secondary and isn't something that should be presented so early to users." which is exactly why I don't like that the new solution since it push Earlyaccess into users lap immediately without explanation/warning/enablement. > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21179) Upgrade Forge Runtime to 3.0.0.Alpha3

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21179?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21179: ---------------------------------------- Desision made on today's PM call: Keep it in Beta1 and revert it later if it does not work or breaks IS or breaks the backwards compatibility. cc: [~pleacu] > Upgrade Forge Runtime to 3.0.0.Alpha3 > ------------------------------------- > > Key: JBIDE-21179 > URL: https://issues.jboss.org/browse/JBIDE-21179 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.3.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21294) NPE when starting CDK server

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21294?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-21294: --------------------------------------- I didn't realize the solution is so simple! Just stop coding bugs :) I will tell Rob :) > NPE when starting CDK server > ---------------------------- > > Key: JBIDE-21294 > URL: https://issues.jboss.org/browse/JBIDE-21294 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > > I've been testing the CDK adapter with [1] today and when I tried to start again from scratch (vagrant destroy + new workspace) and added the server again and started, I got a NPE: > {code} > An internal error occurred during: "Starting cdk-v2 CDK Server". > java.lang.NullPointerException > at java.io.File.<init>(File.java:277) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(CDKLaunchController.java:133) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > 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.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > I did add the user credentials in the server editor. > Now I looked in the launch config and the first field at the top is empty - it should contain path to vagrant. I'm not sure why it's missing - I just used runtime detection. But in any case, the NPE should be handled somehow. > [1] https://github.com/redhat-developer-tooling/openshift-vagrant -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21294) NPE when starting CDK server

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21294?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-21294 at 12/10/15 10:14 AM: ---------------------------------------------------------------- yeah why do we keep coding bugs? That's unacceptable! :-) was (Author: fbricon): yeah why do we keep coding bugs? That's inacceptable! :-) > NPE when starting CDK server > ---------------------------- > > Key: JBIDE-21294 > URL: https://issues.jboss.org/browse/JBIDE-21294 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > > I've been testing the CDK adapter with [1] today and when I tried to start again from scratch (vagrant destroy + new workspace) and added the server again and started, I got a NPE: > {code} > An internal error occurred during: "Starting cdk-v2 CDK Server". > java.lang.NullPointerException > at java.io.File.<init>(File.java:277) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(CDKLaunchController.java:133) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > 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.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > I did add the user credentials in the server editor. > Now I looked in the launch config and the first field at the top is empty - it should contain path to vagrant. I'm not sure why it's missing - I just used runtime detection. But in any case, the NPE should be handled somehow. > [1] https://github.com/redhat-developer-tooling/openshift-vagrant -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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