June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19654) Application wizard: Opening the wizard on an account without SSH key opens broken wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19654?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19654: ------------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > Application wizard: Opening the wizard on an account without SSH key opens broken wizard > ---------------------------------------------------------------------------------------- > > Key: JBIDE-19654 > URL: https://issues.jboss.org/browse/JBIDE-19654 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: application_wizard > Fix For: 4.3.0.CR1 > > Attachments: new_app_wizard.png, prompt-to-upload-keys.png > > > If user is opening a New application wizard from domain (context menu on domain item in OpenShift explorer) or shell menu (File - New - OpenShift Application) and there is no SSH key related to v2 account, the wizard is opened directly and cartridge/quickstart selection is empty > !new_app_wizard.png! > There should be at first opened SSH Key wizard/dialog to let the user add a SSH key to the account and then it should proceed to New application wizard (this is how it worked. Currently it's working like this only on New application wizard opened via context menu of a connection). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19181?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19181: ------------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > 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: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.CR1 > > > 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 (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19939) Validate basic auth prompt with initial eclipse session an expired token

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19939?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19939: ------------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > Validate basic auth prompt with initial eclipse session an expired token > ------------------------------------------------------------------------ > > Key: JBIDE-19939 > URL: https://issues.jboss.org/browse/JBIDE-19939 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Fix For: 4.3.0.CR1 > > > Validate that a user is properly prompted for credentials when the server is configured for Basic Auth and the user opens a new eclipse session and has an expired/invalid token loaded from storage. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20106) OpenShift v2 plugin is installed even though I selected only OpenShift v3 plugin

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20106?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20106: ------------------------------------------ For my own documentation purposes: I see this being caused by the following in {code:title=org.jboss.tools.openshift.core/MANIFEST.MF} Import-Package: com.openshift.client {code} This seems to have been added in JBIDE-19829 but doesnt seem required (I can remove it without harm). > OpenShift v2 plugin is installed even though I selected only OpenShift v3 plugin > -------------------------------------------------------------------------------- > > Key: JBIDE-20106 > URL: https://issues.jboss.org/browse/JBIDE-20106 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.0.Beta2 > > > While I am installing JBT and I select only OpenShift v3, I expect that only v3 is going to be installed. Unfortunately v2 is installed too and it is possible to create v2 connection, domain, application... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20106) OpenShift v2 plugin is installed even though I selected only OpenShift v3 plugin

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20106?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20106: ------------------------------------------ [~mlabuda] That^s very unfortunate. We verified this and solved it quite a few times. It looks like this sneaked in again. > OpenShift v2 plugin is installed even though I selected only OpenShift v3 plugin > -------------------------------------------------------------------------------- > > Key: JBIDE-20106 > URL: https://issues.jboss.org/browse/JBIDE-20106 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.0.Beta2 > > > While I am installing JBT and I select only OpenShift v3, I expect that only v3 is going to be installed. Unfortunately v2 is installed too and it is possible to create v2 connection, domain, application... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19850) As a user I want to easily set up port forwarding for my application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19850?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19850: ------------------------------------------ This means that there's no reusing of what we have in v2, this looks like something we'd have to implement in the client- or an additional library > As a user I want to easily set up port forwarding for my application > -------------------------------------------------------------------- > > Key: JBIDE-19850 > URL: https://issues.jboss.org/browse/JBIDE-19850 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Priority: Blocker > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.3.0.Beta2 > > > As a user I want to be able to easily set up port forwarding to my application -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19850) As a user I want to easily set up port forwarding for my application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19850?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19850: ------------------------------------------ Port forwarding in OpenShift v3 is a completely different thing than it is in v2. In v2 this was ssh based, in v3 this is a custom solution implemented in kubectl that's based on SPDY. See here: https://github.com/GoogleCloudPlatform/kubernetes/issues/3253 > As a user I want to easily set up port forwarding for my application > -------------------------------------------------------------------- > > Key: JBIDE-19850 > URL: https://issues.jboss.org/browse/JBIDE-19850 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Priority: Blocker > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.3.0.Beta2 > > > As a user I want to be able to easily set up port forwarding to my application -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20068) Show in Web Browser via Livereload Server doesn't work

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20068?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-20068. ------------------------------- Verified for 4.3.0.Beta1b, closing. > Show in Web Browser via Livereload Server doesn't work > ------------------------------------------------------ > > Key: JBIDE-20068 > URL: https://issues.jboss.org/browse/JBIDE-20068 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.0.Beta1 > Environment: JBDS 9.0.0.Beta1-v20150614-0409-B50, Fedora 21, Oracle Java 1.8, JBoss AS 7.1.1.Final > Reporter: Vlado Pakan > Assignee: Xavier Coulon > Priority: Critical > Labels: respin-b > Fix For: 4.3.0.Beta1 > > > 1. Create HTML5 project via JBoss Central > 2. Run it on JBossAS 7.1.1.Final > 3. Select this server in Server View > 4. Expand server and select HTML5 project > 5. Click on context menu Show In > Web Browser via Livereload Server > ERROR: Browser displays HTML error 500. Ur in Web Browser is: http://localhost:54437/jboss-as-kitchensink-html5-mobile > App is working when Web Browser is pointed to http://localhost:8080/jboss-as-kitchensink-html5-mobile/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3408) installer is trying to reach download.jboss.org for content

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3408?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3408. ----------------------------- Verified in 9.0.0.Beta1b, closing. > installer is trying to reach download.jboss.org for content > ----------------------------------------------------------- > > Key: JBDS-3408 > URL: https://issues.jboss.org/browse/JBDS-3408 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Labels: respin-b > Fix For: 9.0.0.Beta1 > > Attachments: JBDS3408.install.jboss-devstudio-9.0.0.Beta1-v20150430-1113-B3095-installer-standalone.jar.log.txt > > > Running latest devstudio 9 installer I caught it in reaching out to download.jboss.org which it should have *zero* links/dependency on. > My guess is there is an updatesite that have bad reference to download.jboss.org that we need fixing. > See screenshot at https://www.dropbox.com/s/wkr30jlvdc7d8wu/Screenshot%202015-04-15%2013.11... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18556) battery status is not reflected in browsersim's status bar

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18556?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-18556: -------------------------------- Priority: Minor (was: Major) > battery status is not reflected in browsersim's status bar > ---------------------------------------------------------- > > Key: JBIDE-18556 > URL: https://issues.jboss.org/browse/JBIDE-18556 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cordovasim > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Priority: Minor > Fix For: 4.3.x > > Attachments: log.png > > > create basic cordova app. > run in cordova sim. > changing the battery level and is-plugged does not take effect in the simulator. > Should it not be able to detect these ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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