[JBoss JIRA] (JBIDE-15602) openshift-java-client: ApplicationResource#sshExecCmd is throwing with wrong msg
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15602?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15602:
-------------------------------------
Priority: Minor (was: Major)
> openshift-java-client: ApplicationResource#sshExecCmd is throwing with wrong msg
> --------------------------------------------------------------------------------
>
> Key: JBIDE-15602
> URL: https://issues.jboss.org/browse/JBIDE-15602
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.x
>
>
> The message that is used when throwing an exception is wrong, it's reporting a failure to list forwardable ports where it's failing to execute an ssh-command:
> {code:title=ApplicationResource#sshExecCmd}
> try {
> session.openChannel("exec");
> channel = session.openChannel("exec");
> ((ChannelExec) channel).setCommand(command);
> channel.connect();
> return sshStream.getLines(channel);
> } catch (JSchException e) {
> throw new OpenShiftSSHOperationException(e, "Failed to list forwardable ports for application \"{0}\"",
> this.getName());
> } catch (IOException e) {
> throw new OpenShiftSSHOperationException(e, "Failed to list forwardable ports for application \"{0}\"",
> this.getName());
> } finally {
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-15055) Connection dialog: Inform user about a non-valid OpenShift server url in a user-friendly way
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15055?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15055:
------------------------------------------
This is outdated. The current implementation would inform in a user-friendly way, telling the user that his credentials could not get verified and that he'd look into the Eclipse log for further details:
!cannot-verify.png!
> Connection dialog: Inform user about a non-valid OpenShift server url in a user-friendly way
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-15055
> URL: https://issues.jboss.org/browse/JBIDE-15055
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: cannot-verify.png, could-not-verify-credentials.png
>
>
> In the credentials dialog, if a user provides an invalid URL for the OpenShift server the dialog will correctly error and tell him that it could not verify the credentials while displaying the kind of exception that occourred. While this is correct, we could improve this error message.
> # EXEC: launch OpenShift application wizard from "New wizards" or "Central" so that you get the credentials dialog presented to you.
> # EXEC: if you already have a connection the dialog is using that one. Switch it to *<New Connection>*
> # EXEC: provide username and password and some *invalid server url*
> # EXEC: hit *Next*
> Result:
> The wizard informs you that it could not verify your credentials:
> !could-not-verify-credentials.png!
> Expected:
> The wizard informs you that it could not verify your credentials but doesnt show the exception that occourred. It informs in a more user-friendly way.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-15055) Connection dialog: Inform user about a non-valid OpenShift server url in a user-friendly way
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15055?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15055:
-------------------------------------
Attachment: cannot-verify.png
> Connection dialog: Inform user about a non-valid OpenShift server url in a user-friendly way
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-15055
> URL: https://issues.jboss.org/browse/JBIDE-15055
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: cannot-verify.png, could-not-verify-credentials.png
>
>
> In the credentials dialog, if a user provides an invalid URL for the OpenShift server the dialog will correctly error and tell him that it could not verify the credentials while displaying the kind of exception that occourred. While this is correct, we could improve this error message.
> # EXEC: launch OpenShift application wizard from "New wizards" or "Central" so that you get the credentials dialog presented to you.
> # EXEC: if you already have a connection the dialog is using that one. Switch it to *<New Connection>*
> # EXEC: provide username and password and some *invalid server url*
> # EXEC: hit *Next*
> Result:
> The wizard informs you that it could not verify your credentials:
> !could-not-verify-credentials.png!
> Expected:
> The wizard informs you that it could not verify your credentials but doesnt show the exception that occourred. It informs in a more user-friendly way.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-15055) Connection dialog: Inform user about a non-valid OpenShift server url in a user-friendly way
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15055?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-15055.
--------------------------------------
Fix Version/s: 4.2.0.Alpha1
(was: 4.2.x)
Resolution: Out of Date
> Connection dialog: Inform user about a non-valid OpenShift server url in a user-friendly way
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-15055
> URL: https://issues.jboss.org/browse/JBIDE-15055
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.0.Alpha1
>
> Attachments: cannot-verify.png, could-not-verify-credentials.png
>
>
> In the credentials dialog, if a user provides an invalid URL for the OpenShift server the dialog will correctly error and tell him that it could not verify the credentials while displaying the kind of exception that occourred. While this is correct, we could improve this error message.
> # EXEC: launch OpenShift application wizard from "New wizards" or "Central" so that you get the credentials dialog presented to you.
> # EXEC: if you already have a connection the dialog is using that one. Switch it to *<New Connection>*
> # EXEC: provide username and password and some *invalid server url*
> # EXEC: hit *Next*
> Result:
> The wizard informs you that it could not verify your credentials:
> !could-not-verify-credentials.png!
> Expected:
> The wizard informs you that it could not verify your credentials but doesnt show the exception that occourred. It informs in a more user-friendly way.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBDS-2839) Hybrid/Cordova Usability
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBDS-2839?page=com.atlassian.jira.plugin.... ]
Burr Sutter commented on JBDS-2839:
-----------------------------------
An example of where the end-user will struggle with figuring out how to configure/start/enable LiveReload
> Hybrid/Cordova Usability
> ------------------------
>
> Key: JBDS-2839
> URL: https://issues.jboss.org/browse/JBDS-2839
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Burr Sutter
> Fix For: 8.0.0.GA
>
>
> Area to review:
> 1) Auto setup of the LiveReload Server (JBIDE-16134)
> 2) Run As on Android Device - often fails to find the plugged in device - need better instructions on now to "debug" this issue (adb devices, etc)
> 3) Add to JBoss Central
> 4) Promote from Tech Preview
> 5) Import an existing Cordova project (e.g. TicketMonster: WFK2-168)
> 6) New project works with jQuery Mobile Palette + Backbone
> 7) New project works with AngularJS-based project
> 8) Install Cordova Plugin dialog is slow for scrolling the list of plugins, slow for typing in the project field - focus should not default to project field when the dialog is launched from a specific project (right-click on plugins, Install Cordova Plugin)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16220) create an all-in-one build for JBT projects, using submodules
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16220?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-16220:
------------------------------------
Prototype job here:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-submodule... >=1
> create an all-in-one build for JBT projects, using submodules
> -------------------------------------------------------------
>
> Key: JBIDE-16220
> URL: https://issues.jboss.org/browse/JBIDE-16220
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> Git 1.8.2 includes an option to have submodules track a branch tip, rather than specific commit IDs.
> {code:title=https://github.com/git/git/blob/master/Documentation/RelNotes/1.8.2.txt#L186-L188}
> "git submodule" started learning a new mode to integrate with the
> tip of the remote branch (as opposed to integrating with the commit
> recorded in the superproject's gitlink).
> {code}
> Therefore, while the solution [~dgolovin] has for his https://github.com/dgolovin/jbosstools-submodules project is a decent option, it requires updating to stay current with branch tips. It's therefore only really as useful as it stays current.
> If we can get Git 1.8.2 or newer installed on the Jenkins slaves, we could do a submodule build against whatever branch we wanted - master, 4.2.0.Alpha1x, etc.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months