June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13922) OpenShift "Secure Storage" dialog in infinite loop of prompting

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13922?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-13922. --------------------------------- Resolution: Won't Fix Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER. > OpenShift "Secure Storage" dialog in infinite loop of prompting > --------------------------------------------------------------- > > Key: JBIDE-13922 > URL: https://issues.jboss.org/browse/JBIDE-13922 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Environment: Fedora 18 > Reporter: R Searls > Priority: Minor > Fix For: LATER > > > Running : JBoss Developer Studio > version:6.0.1.GA > Build id:GA-v20130327-2052-B361 > OS: Fedora 18 > When creating a new OpenShift App in the "New OpenShift Application" dialog > I type in my password, (I have an existing account.) and select the checkbox, > "Save password (could trigger storage login)" and click next. The " Secure > Storage" dialog displays. I click the cancel button. Each time I click cancel > in this dialog, the dialog closes and pops back open. It's in an infinit loop. > I must kill the app to get out of this cycle. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12171) Link to the OpenShift status page

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12171?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-12171. --------------------------------- Resolution: Won't Fix Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER. > Link to the OpenShift status page > --------------------------------- > > Key: JBIDE-12171 > URL: https://issues.jboss.org/browse/JBIDE-12171 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.CR1 > Reporter: Andre Dietisheim > Priority: Minor > Fix For: LATER > > Attachments: openshift-status.png > > > OpenShift has a nice status page that informs of ongoing issues on the PaaS. we should point the user to this page if we experience issues while working against the PaaS (ex. when getting 500-errors?). > We could also display the current status in the OpenShift explorer. > !openshift-status.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16976) import wizard: Error dialog after importing application without SSH key on PaaS is not enough descriptive

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16976?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-16976. --------------------------------- Resolution: Won't Fix Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER. > import wizard: Error dialog after importing application without SSH key on PaaS is not enough descriptive > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-16976 > URL: https://issues.jboss.org/browse/JBIDE-16976 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta1 > Reporter: Marián Labuda > Priority: Minor > Labels: application_wizard > Fix For: LATER > > Attachments: error_dialog.png > > > When creating application and following import (git clone after creation process is completed) in case of no SSH key/not added into preferences dialog there is a error dialog with description, that something went wrong during git clone (respectively creating local git repo) and exception thrown. > !error_dialog.png! > It would be nice to have in the dialog, that problem is caused by missing SSH key or at least remove InvocationTargetException from error message - it is useless for user. > Error log stack trace > {code} > java.lang.reflect.InvocationTargetException > at org.eclipse.egit.core.op.CloneOperation.run(CloneOperation.java:176) > at org.jboss.tools.openshift.egit.core.EGitUtils.cloneRepository(EGitUtils.java:270) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.importoperation.AbstractImportApplicationOperation.cloneRepository(AbstractImportApplicationOperation.java:169) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.importoperation.ImportNewProject.execute(ImportNewProject.java:77) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftApplicationWizardModel.importProject(OpenShiftApplicationWizardModel.java:103) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftApplicationWizard$ImportJob.runInWorkspace(OpenShiftApplicationWizard.java:353) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > Caused by: java.lang.IllegalStateException: Preference node "null" has been removed. > at org.eclipse.equinox.internal.security.storage.SecurePreferences.checkRemoved(SecurePreferences.java:354) > at org.eclipse.equinox.internal.security.storage.SecurePreferences.nodeExists(SecurePreferences.java:100) > at org.eclipse.equinox.internal.security.storage.SecurePreferencesWrapper.nodeExists(SecurePreferencesWrapper.java:94) > at org.eclipse.egit.core.securestorage.EGitSecureStore.clearCredentials(EGitSecureStore.java:108) > at org.eclipse.egit.ui.internal.credentials.EGitCredentialsProvider.reset(EGitCredentialsProvider.java:142) > at org.eclipse.jgit.transport.JschConfigSessionFactory.getSession(JschConfigSessionFactory.java:125) > at org.eclipse.jgit.transport.SshTransport.getSession(SshTransport.java:121) > at org.eclipse.jgit.transport.TransportGitSsh$SshFetchConnection.<init>(TransportGitSsh.java:248) > at org.eclipse.jgit.transport.TransportGitSsh.openFetch(TransportGitSsh.java:147) > at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:136) > at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:122) > at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1111) > at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:130) > at org.eclipse.jgit.api.CloneCommand.fetch(CloneCommand.java:178) > at org.eclipse.jgit.api.CloneCommand.call(CloneCommand.java:125) > at org.eclipse.egit.core.op.CloneOperation.run(CloneOperation.java:156) > ... 7 more > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11288) Application wizard: Investigate name exceptions of OpenShift Application

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11288?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-11288. --------------------------------- Resolution: Won't Fix Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER. > Application wizard: Investigate name exceptions of OpenShift Application > ------------------------------------------------------------------------ > > Key: JBIDE-11288 > URL: https://issues.jboss.org/browse/JBIDE-11288 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Stefan Bunciak > Priority: Minor > Fix For: LATER > > > We should find out which names can be used as OpenShift Application name. > I've encountered a problem trying to create aplication called "*richfaces*": > Could not create application "richfaces": The supplied application name 'richfaces' is not allowed > Could not configure application "richfaces" at "https://openshift.redhat.com/broker/cartridge" > After investigating all "naming exceptions" we should add some validation to the OpenShift wizard. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10853) Application wizard: Embed wizard: jenkins cartridge asks for name - why not use default "jenkins" if available (and jenkins-2 if not...?)

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10853?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-10853. --------------------------------- Resolution: Won't Fix Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER. > Application wizard: Embed wizard: jenkins cartridge asks for name - why not use default "jenkins" if available (and jenkins-2 if not...?) > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-10853 > URL: https://issues.jboss.org/browse/JBIDE-10853 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Max Rydahl Andersen > Priority: Minor > Labels: application_wizard, embed_wizard, new_and_noteworthy > Fix For: LATER > > > If you embed the jenkins client you're prompted to create a jenkins appliaction (if there's none yet) and asked to provide some name for this new application. We should - instead of prompting - use a fixed name: jenkins, jenkins-2, jenkins-3 etc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11270) Server editor: Remote branch to use should be a text-field with autocomplete

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11270?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-11270. --------------------------------- Resolution: Won't Fix Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER. > Server editor: Remote branch to use should be a text-field with autocomplete > ---------------------------------------------------------------------------- > > Key: JBIDE-11270 > URL: https://issues.jboss.org/browse/JBIDE-11270 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Lucia Jelinkova > Priority: Minor > Labels: server_editor > Fix For: LATER > > Attachments: egit-remote-branches.png, remote-disabled.png, server_detail.jpg > > > When you open the detail of OpenShift server adapter you can change the Git remote name by typing the new value. Could you change the text field to combo box filled with remote names that are actually configured for the OpenShift project? > !server_detail.jpg! > We decided to match what EGit provides: a text-field which allows freely typed entries (which would create new branches) but also offers auto-completion to match existing branches. > !egit-remote-branches.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15782) Environment variable wizard: Use a duplicate name and dont spot it in the title area

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15782?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-15782. --------------------------------- Resolution: Won't Fix Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER. > Environment variable wizard: Use a duplicate name and dont spot it in the title area > ------------------------------------------------------------------------------------ > > Key: JBIDE-15782 > URL: https://issues.jboss.org/browse/JBIDE-15782 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Andre Dietisheim > Priority: Minor > Fix For: LATER > > Attachments: error-tooltip.png, required-value-missing-real-error-notdisplayed.png, required-value-missing-real-error-notdisplayed.png, required-value-provided-error-displayed.png > > > "bad value" errors in wizards get eventually overwritten by "required value missing": > !required-value-missing-real-error-notdisplayed.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16880) Port Forwarding wizard: can't scroll vertically low enough to view obscured table item

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16880?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-16880. --------------------------------- Resolution: Won't Fix Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER. > Port Forwarding wizard: can't scroll vertically low enough to view obscured table item > -------------------------------------------------------------------------------------- > > Key: JBIDE-16880 > URL: https://issues.jboss.org/browse/JBIDE-16880 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta1 > Environment: Fedora 19, 64-bit, java version "1.7.0_51", OpenJDK Runtime Environment (fedora-2.4.5.0.fc19-x86_64 u51-b31) > Reporter: Michelle Murray > Assignee: Andre Dietisheim > Priority: Minor > Labels: port_forwarding_wizard > Fix For: LATER > > Attachments: OpenShift_pfscroll.png > > > In Port Forwarding window, the last item was obscured. I tried to scroll by using the mouse middle button and also by dragging the scroll bar. Both of these actions show some vertical scroll motion but not enough to view the last item in the table. > Workaround: drag the corner of the port forwarding window to make the window bigger or smaller - last table item is now completely visible and scroll actions move to the absolute bottom of the table. > !OpenShift_pfscroll.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12312) Domain wizard: If domain creation fails because of name that's already used (or forbidden), no info is visible in wizard after you closed the error dialog

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12312?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-12312. --------------------------------- Resolution: Won't Fix Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER. > Domain wizard: If domain creation fails because of name that's already used (or forbidden), no info is visible in wizard after you closed the error dialog > ---------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-12312 > URL: https://issues.jboss.org/browse/JBIDE-12312 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.Final > Reporter: Andre Dietisheim > Priority: Minor > Labels: domain_wizard > Fix For: LATER > > Attachments: domain-name-already-used.png, missing-user-guidance.png, no-error.png > > > If you create a new domain on OpenShift, you'll have to provide it's name. This name has to be unique across OpenShift (for all users). If you use a domain name that's already used, you'll get an error dialog that informs you about the name not being unique across OpenShift. > !domain-name-already-used.png! > Once you close this dialog, noting is showing this error any more. The name field is not decorated with an error marker. > steps to reproduce: > # ASSERT make sure you have an account without a domain > # EXEC launch the *OpenShift Application* wizard > # ASSERT you get to the *Domain creation* dialog > # EXEC supply a valid key and choose a domain name that is *already used* (ex. "domain") > # ASSERT You get an error dialog that tells you that the domain name is already used > # EXEC hit *OK* > Result: > The domain creation dialog has no information that would tell you what you have to correct. > !missing-user-guidance.png! > We should improved this: > * put an error decoration to the name text field > * put the cursor into the name text field (eventually select the whole name in it) > * eventually reach out to #libra to get a way to query the availability of the given name, so that we can validate while typing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14353) Explorer: does not show freshly created jenkins if I cancel "Edit Embedded Cartridges"

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14353?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-14353. --------------------------------- Resolution: Won't Fix Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER. > Explorer: does not show freshly created jenkins if I cancel "Edit Embedded Cartridges" > -------------------------------------------------------------------------------------- > > Key: JBIDE-14353 > URL: https://issues.jboss.org/browse/JBIDE-14353 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Priority: Minor > Labels: explorer > Fix For: LATER > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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