July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3865) Platform installer should warn about known bad versions of Vagrant.

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3865?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3865: -------------------------------- Sprint: devex #118 July 2016 > Platform installer should warn about known bad versions of Vagrant. > ------------------------------------------------------------------- > > Key: JBDS-3865 > URL: https://issues.jboss.org/browse/JBDS-3865 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta1 > Environment: Windows 7/64 bit. > Vagrant 1.8.1 installed > Reporter: Robert Terzi > Assignee: Denis Golovin > Priority: Minor > Fix For: 10.1.0.AM3 > > > The platform installer should flag versions of Vagrant (and possibly other software) that are known to be bad. There should possibly be a black list. > Vagrant 1.8.0 and 1.8.1 have a bunch of bugs, so they aren't recommended for CDK. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3962) Blog post about DevSuite installer on developers.redhat.com

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3962?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3962: -------------------------------- Sprint: devex #118 July 2016 > Blog post about DevSuite installer on developers.redhat.com > ----------------------------------------------------------- > > Key: JBDS-3962 > URL: https://issues.jboss.org/browse/JBDS-3962 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.1.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: marketing > Fix For: 10.1.0.AM2 > > > We should draw more attention to DevSuite Installer and put more content about it on http://developers.redhat.com/blog/. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3956) Installer should let to update detected oracle vurtualbox and vagrant

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3956?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3956: -------------------------------- Sprint: devex #118 July 2016 > Installer should let to update detected oracle vurtualbox and vagrant > --------------------------------------------------------------------- > > Key: JBDS-3956 > URL: https://issues.jboss.org/browse/JBDS-3956 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.1.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.1.0.AM3 > > > It should also work for OpenJDK installed from .msi file. Detection should read installation information from registry using vbs scripts (see https://msdn.microsoft.com/en-us/library/aa369767(v=vs.85).aspx for details). > Reading install information form registry would work better than detection based on environment variables. It would let rerun detection on installer windows activation and detect changes in configuration without restarting installer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-604) OpenShift: Document creating a deployment from a template

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-604?page=com.atlassian.jira.plug... ] Misha Ali closed TOOLSDOC-604. ------------------------------ Resolution: Out of Date > OpenShift: Document creating a deployment from a template > --------------------------------------------------------- > > Key: TOOLSDOC-604 > URL: https://issues.jboss.org/browse/TOOLSDOC-604 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Reporter: Misha Ali > Assignee: Misha Ali > Fix For: 4.3.0.Final > > > Document this use case: Use Case #3 > Create Deployment from Template > a) Assume OpenShift is started remotely and provides an entrypoint URL > b) Assume end-user is logged in (ignore auth for now) > c) Eclipse user will open a dialog and enter the URL from step a > d) Eclipse user will then be presented with a list of templates from the template library > (initially a set of files on the local filesystem until openshift has a real template library api) > e) The template list should allow sorting so that higher priority items are at the top > We will likely need some form of categorization for templates also > f) The template list should be searchable by keyword > g) Eclipse user will select a particular template and > h) Create a new openshift deployment based on selected template > i) follow steps JBDS-3297 f through j (clone, import, project facets, etc) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22810) OpenShift Explorer: empty at start

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22810?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-22810: ------------------------------------------ Attachment: EmptyViewAtStart.png > OpenShift Explorer: empty at start > ---------------------------------- > > Key: JBIDE-22810 > URL: https://issues.jboss.org/browse/JBIDE-22810 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Viacheslav Kabanovich > Fix For: 4.4.1.AM3 > > Attachments: EmptyViewAtStart.png > > > When I close Eclipse with OpenShift Explorer not visible (by selecting another view in the same area of the workbench, or by switching another perspective), after I reopen Eclipse, and select OpenShift Explorer. I push 'Connect' button and can select for authenticating any available connection, it happens successfully, but the view remains empty. After I close/reopen OpenShift Explorer, it is opened populated with connections. > I have to add that it is not 100% reproducible. What is interesting, when starting it in the debugger, I reproduce it around 80%, while in normal run the probability is very low if do it leisurely, but can be increased to 50% if take the task with some dedication and find the right moment (very soon after the window opens) to select the explorer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22810) OpenShift Explorer: empty at start

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22810?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-22810: ------------------------------------------ Description: When I close Eclipse with OpenShift Explorer not visible (by selecting another view in the same area of the workbench, or by switching another perspective), after I reopen Eclipse, and select OpenShift Explorer. I push 'Connect' button and can select for authenticating any available connection, it happens successfully, but the view remains empty. After I close/reopen OpenShift Explorer, it is opened populated with connections. I have to add that it is not 100% reproducible. What is interesting, when starting it in the debugger, I reproduce it around 80%, while in normal run the probability is very low if do it leisurely, but can be increased to 50% if take the task with some dedication and find the right moment (very soon after the window opens) to select the explorer. was:When I close Eclipse with OpenShift Explorer not visible (by selecting another view in the same area of the workbench, or by switching another perspective), after I reopen Eclipse, and select OpenShift Explorer. I push 'Connect' button and can select for authenticating any available connection, it happens successfully, but the view remains empty. After I close/reopen OpenShift Explorer, it is opened populated with connections. > OpenShift Explorer: empty at start > ---------------------------------- > > Key: JBIDE-22810 > URL: https://issues.jboss.org/browse/JBIDE-22810 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Viacheslav Kabanovich > Fix For: 4.4.1.AM3 > > > When I close Eclipse with OpenShift Explorer not visible (by selecting another view in the same area of the workbench, or by switching another perspective), after I reopen Eclipse, and select OpenShift Explorer. I push 'Connect' button and can select for authenticating any available connection, it happens successfully, but the view remains empty. After I close/reopen OpenShift Explorer, it is opened populated with connections. > I have to add that it is not 100% reproducible. What is interesting, when starting it in the debugger, I reproduce it around 80%, while in normal run the probability is very low if do it leisurely, but can be increased to 50% if take the task with some dedication and find the right moment (very soon after the window opens) to select the explorer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22446) Release process can include snapshots artifacts

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22446?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22446: ----------------------------------- Component/s: build (was: openshift) > Release process can include snapshots artifacts > ----------------------------------------------- > > Key: JBIDE-22446 > URL: https://issues.jboss.org/browse/JBIDE-22446 > Project: Tools (JBoss Tools) > Issue Type: Release > Components: build > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Fix For: 4.4.x > > > 4.4.0.Alpha2 was generated with a SNAPSHOT dependency. This should be avoided in future releases even for Alpha ones > Update: This issues is for adding some automated test/check to detect situation when our release includes a snapshot dependency. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22806) Connection wizard: "Finish" is enabled even though I didnt oauth authenticate to pick a token

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22806?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22806: ----------------------------------------------- [~adietish], I took the liberty of changing in step 3 of description, 'enabled' to 'disabled'. If I am wrong, sorry, please roll it back. > Connection wizard: "Finish" is enabled even though I didnt oauth authenticate to pick a token > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22806 > URL: https://issues.jboss.org/browse/JBIDE-22806 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Priority: Minor > Fix For: 4.4.1.AM3 > > Attachments: connection-page-finish-enabled.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22806) Connection wizard: "Finish" is enabled even though I didnt oauth authenticate to pick a token

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22806?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-22806: ------------------------------------------ Steps to Reproduce: # ASSERT: have a server that lets you log in via oauth (ex. https://console.engint.openshift.com) # EXEC: launch connection wizard, choose openshift 3 type, provide server url and ensure "OAuth" is selected as authentication means # ASSERT: "Finish" is disabled # EXEC: hit the "retrieve" link and wait for the oauth dialog to appear # EXEC: close auth dialog (do NOT log in nor retrieve any token) Result: "Finish" is enabled, "Token" has no required marker !connection-page-finish-enabled.png! was: # ASSERT: have a server that lets you log in via oauth (ex. https://console.engint.openshift.com) # EXEC: launch connection wizard, choose openshift 3 type, provide server url and ensure "OAuth" is selected as authentication means # ASSERT: "Finish" is enabled # EXEC: hit the "retrieve" link and wait for the oauth dialog to appear # EXEC: close auth dialog (do NOT log in nor retrieve any token) Result: "Finish" is enabled, "Token" has no required marker !connection-page-finish-enabled.png! > Connection wizard: "Finish" is enabled even though I didnt oauth authenticate to pick a token > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22806 > URL: https://issues.jboss.org/browse/JBIDE-22806 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Priority: Minor > Fix For: 4.4.1.AM3 > > Attachments: connection-page-finish-enabled.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22810) OpenShift Explorer: empty at start

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-22810: --------------------------------------------- Summary: OpenShift Explorer: empty at start Key: JBIDE-22810 URL: https://issues.jboss.org/browse/JBIDE-22810 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.1.AM1 Reporter: Viacheslav Kabanovich Fix For: 4.4.1.AM3 When I close Eclipse with OpenShift Explorer not visible (by selecting another view in the same area of the workbench, or by switching another perspective), after I reopen Eclipse, and select OpenShift Explorer. I push 'Connect' button and can select for authenticating any available connection, it happens successfully, but the view remains empty. After I close/reopen OpenShift Explorer, it is opened populated with connections. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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