February 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-3579) Fuse archetype catalog cannot be added with JBDS 9

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3579?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3579: ------------------------------------------- this cannot be fixed in Mars.2? > Fuse archetype catalog cannot be added with JBDS 9 > -------------------------------------------------- > > Key: JBDS-3579 > URL: https://issues.jboss.org/browse/JBDS-3579 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: maven > Affects Versions: 9.0.0.GA > Reporter: Keith Babo > Assignee: Fred Bricon > Fix For: 10.0.0.Alpha1 > > > When adding the Fuse Integration Services archetype catalog to JBDS 9, the IDE reports that the catalog is empty. This works in Eclipse and I've heard reports that it also works in earlier versions of JBDS (although I have not confirmed this personally). > Archetype catalog in question: > https://repo.fusesource.com/nexus/content/groups/public/io/fabric8/archet... > Steps to reproduce: > - Preferences -> Maven -> Archetypes -> Add Remote Catalog > - Add URL above for Catalog File > - Click Verify ... and you get the message "Remote catalog is empty" > - Click Finish and try to use the catalog from the New Maven Project wizard and the message is "No archetypes available for this catalog." > Impact here is that Fuse customers looking to use Fuse on OpenShift cannot use JBDS to create new projects using our Maven archetypes (the primary means of getting started). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21645) No build config warning dialog shown when opening Import Application... on OS3 connection

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21645?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21645: --------------------------------------------- I can do File > New > Class on a project in eclipse - why should I need to go to the source folder to do it ? please don't make it so I have to manually navigate the tree to import. File > New > will at least allow me to do this too, right ? Instead of removing this the wizard should allow me to enter or select from the list of apps available. Thus reopening for clarification why this aren't just enabling choosing the app from the opened wizard ? > No build config warning dialog shown when opening Import Application... on OS3 connection > ----------------------------------------------------------------------------------------- > > Key: JBIDE-21645 > URL: https://issues.jboss.org/browse/JBIDE-21645 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Labels: import_wizard, openshift_v3 > Fix For: 4.3.1.CR1 > > Attachments: no_build_config.png > > > When I am trying to import a new application via connection context menu Import Application..., I get following warning dialog > !no_build_config.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21658) Property sheet cells are editable

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21658?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21658: --------------------------------------------- +1 but don't make it so we can't actually copy the values ;) > Property sheet cells are editable > --------------------------------- > > Key: JBIDE-21658 > URL: https://issues.jboss.org/browse/JBIDE-21658 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.x > Environment: Boss Openshift UI Plugin Version: 3.1.0.CR1-v20160202-0335-B166 > Reporter: Steve Speicher > Attachments: Screen Shot 2016-02-06 at 9.03.05 AM.png > > > When I bring up the property sheet, values are editable but I can't really edit them. It would be good if users were disallowed from changing values (like the property name field is restricted) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21658) Property sheet cells are editable

by Steve Speicher (JIRA)

Steve Speicher created JBIDE-21658: -------------------------------------- Summary: Property sheet cells are editable Key: JBIDE-21658 URL: https://issues.jboss.org/browse/JBIDE-21658 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.x Environment: Boss Openshift UI Plugin Version: 3.1.0.CR1-v20160202-0335-B166 Reporter: Steve Speicher Attachments: Screen Shot 2016-02-06 at 9.03.05 AM.png When I bring up the property sheet, values are editable but I can't really edit them. It would be good if users were disallowed from changing values (like the property name field is restricted) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21293) CDK start timed out due to slow image download

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21293?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21293: ------------------------------------- Another alternative is to ask the user if he wants to wait longer > CDK start timed out due to slow image download > ---------------------------------------------- > > Key: JBIDE-21293 > URL: https://issues.jboss.org/browse/JBIDE-21293 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > I set up a CDK server using https://github.com/redhat-developer-tooling/openshift-vagrant . > Then I tried to start the server for the first time. Of course this will take quite long as it needs to download the VM image first. I was on a very fast connection, but it still only went around 1 MB/s. So the startup took longer than the default timeout of 450 s. The result was that the startup timed out in the middle followed by an attempted shutdown by the tooling which failed. So in the end I ended up with the running box, but with two unwanted errors. > I'm not sure what we can do here. Perhaps just increase the timeout to something bigger? Even better would be if could detect that a download is in progress so it will take longer, but I don't think the current mechanism is capable of anything like that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19439) Explorer: Cannot delete v2 applications via "Del"-Key

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19439?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-19439. --------------------------------- Fix Version/s: 4.3.1.CR1 (was: 4.3.x) Assignee: Viacheslav Kabanovich Resolution: Done This was fixed with https://github.com/jbosstools/jbosstools-openshift/commit/09c150b0980d45a... > Explorer: Cannot delete v2 applications via "Del"-Key > ----------------------------------------------------- > > Key: JBIDE-19439 > URL: https://issues.jboss.org/browse/JBIDE-19439 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.3.1.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20364) Connection wizard: all text (not just "retrieve") is clickable

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20364?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-20364. --------------------------------- Fix Version/s: 4.3.1.CR1 (was: 4.3.x) Resolution: Out of Date This was fixed a while ago. > Connection wizard: all text (not just "retrieve") is clickable > -------------------------------------------------------------- > > Key: JBIDE-20364 > URL: https://issues.jboss.org/browse/JBIDE-20364 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Environment: JBDS 9.0.0.Beta2 B81 > Reporter: Marián Labuda > Priority: Minor > Labels: connection_wizard, help_wanted > Fix For: 4.3.1.CR1 > > Attachments: all-text-is-clickable.png > > > The link for OAuth type of authentization for v3 connection "Enter a token or retrieve a new one." is whole clickable. > !all-text-is-clickable.png! > The label (only black text) should not be clickable. Only keyword "retrieve", which is marked as a link (blue, underlined) should be clickable. Now there is a carret on the whole link with label and nothing let user know that also label is clickable, what should not be. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20686) Preferences: No OpenShift Client binary warning dialog is shown upon restoring default preferences

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20686?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20686: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > Preferences: No OpenShift Client binary warning dialog is shown upon restoring default preferences > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-20686 > URL: https://issues.jboss.org/browse/JBIDE-20686 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3, preferences > Fix For: 4.4.x > > > In OpenShift 3 workbench preference page restoring default setting by clicking on a button Restore Defaults pops up a warning dialog with title "No OpenShift Client binary" and text "Could not find the OpenShift binary "oc" on your path". I would expect that choosing default settings would just clear text field with oc binary location and no dialog is shown. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20048) Explorer: No feedback on failed removal of kubernetes services

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20048?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20048: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > Explorer: No feedback on failed removal of kubernetes services > -------------------------------------------------------------- > > Key: JBIDE-20048 > URL: https://issues.jboss.org/browse/JBIDE-20048 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.4.x > > Attachments: kuebernetes-services.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20544) For OpenShift v3, since a default server does not exist, we should remove the default server check box

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20544?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-20544. --------------------------------- Fix Version/s: 4.3.1.CR1 (was: 4.3.x) Resolution: Partially Completed What [~scabanovich] said. The checkbox is disabled for OS3 connections. That should be enough. Resolving as partially complete. > For OpenShift v3, since a default server does not exist, we should remove the default server check box > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20544 > URL: https://issues.jboss.org/browse/JBIDE-20544 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Len DiMaggio > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.3.1.CR1 > > Attachments: OSE3.png > > > See attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 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 February 2016