[JBoss JIRA] (JBIDE-16976) OpenShift import: Error dialog after importing application without SSH key on PaaS is not enough descriptive
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16976?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16976:
---------------------------------------------
what is the full stackrace? loooks worrysome we get a InvocationTargetException and not the regular "Auth failed" error.
> OpenShift import: 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: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta1
> Reporter: Marián Labuda
> Priority: Minor
> 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 shell 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.
--
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, 2 months
[JBoss JIRA] (JBIDE-16844) org.eclipse.mylyn.tasks.bugs.support is missing in TP. Unknown extension point: 'org.eclipse.mylyn.tasks.bugs.support'
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16844?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-16844.
-------------------------------
Verified with JBDS 8.0.0.Beta1-v20140402-0037-B82
> org.eclipse.mylyn.tasks.bugs.support is missing in TP. Unknown extension point: 'org.eclipse.mylyn.tasks.bugs.support'
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16844
> URL: https://issues.jboss.org/browse/JBIDE-16844
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core, target-platform
> Affects Versions: 4.2.0.Beta1
> Reporter: Alexey Kazakov
> Assignee: Nick Boldt
> Priority: Critical
> Labels: respin-a
> Fix For: 4.2.0.Beta1
>
>
> Our *org.jboss.tools.common.mylyn* plugin uses *org.eclipse.mylyn.tasks.bugs.support* extension point.
> And our common.mylyn plugin depends on *org.eclipse.mylyn.tasks.core* which depends on *org.eclipse.mylyn.tasks.bugs* where this extension point is declared.
> But *org.eclipse.mylyn.tasks.bugs* was removed from Beta1 target platform: JBIDE-16368
> We don't have any source files in common.mylyn so tycho build works w/o any errors. But plugin.xml validation in my dev eclipse detected this problem.
> So we should get the *org.eclipse.mylyn.tasks.bugs.support* and everything we indirectly depends on back.
--
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, 2 months
[JBoss JIRA] (JBIDE-16968) Performance issue when importing windup project
by Lars Heinemann (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16968?page=com.atlassian.jira.plugi... ]
Lars Heinemann commented on JBIDE-16968:
----------------------------------------
The property tester checks files for the camel content type. If we find such a file, we create a virtual folder and show those file found under that virtual folder. We did not limit that behaviour to Fuse projects. Just wondering why it causes such slow downs. If the user hasn't got hundreds of files in lots of projects inside the workspace I would think it should be done in a few seconds. It is btw. intended behaviour to have this virtual folder in each project containing camel files.
> Performance issue when importing windup project
> -----------------------------------------------
>
> Key: JBIDE-16968
> URL: https://issues.jboss.org/browse/JBIDE-16968
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Reporter: Jess Sightler
> Assignee: Lars Heinemann
> Attachments: jbosstools-diagnostics-20140401153317.zip, jstack1.txt
>
>
> User interface freezes and Gnome pops up the "JBoss - JBoss Developer Studio" is not responding dialog.
--
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, 2 months
[JBoss JIRA] (JBIDE-16968) Performance issue when importing windup project
by Lars Heinemann (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16968?page=com.atlassian.jira.plugi... ]
Lars Heinemann edited comment on JBIDE-16968 at 4/2/14 3:29 AM:
----------------------------------------------------------------
The property tester checks files for the camel content type. If we find such a file, we create a virtual folder and show those files found under that virtual folder. We did not limit that behaviour to Fuse projects. Just wondering why it causes such slow downs. If the user hasn't got hundreds of files in lots of projects inside the workspace I would think it should be done in a few seconds. It is btw. intended behaviour to have this virtual folder in each project containing camel files.
was (Author: lhein):
The property tester checks files for the camel content type. If we find such a file, we create a virtual folder and show those file found under that virtual folder. We did not limit that behaviour to Fuse projects. Just wondering why it causes such slow downs. If the user hasn't got hundreds of files in lots of projects inside the workspace I would think it should be done in a few seconds. It is btw. intended behaviour to have this virtual folder in each project containing camel files.
> Performance issue when importing windup project
> -----------------------------------------------
>
> Key: JBIDE-16968
> URL: https://issues.jboss.org/browse/JBIDE-16968
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Reporter: Jess Sightler
> Assignee: Lars Heinemann
> Attachments: jbosstools-diagnostics-20140401153317.zip, jstack1.txt
>
>
> User interface freezes and Gnome pops up the "JBoss - JBoss Developer Studio" is not responding dialog.
--
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, 2 months
[JBoss JIRA] (JBIDE-16975) jQuery Mobile palette: add drop-down list identifier to version
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16975?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-16975:
-----------------------------------
Fix Version/s: 4.2.0.Beta2
> jQuery Mobile palette: add drop-down list identifier to version
> ---------------------------------------------------------------
>
> Key: JBIDE-16975
> URL: https://issues.jboss.org/browse/JBIDE-16975
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Fix For: 4.2.0.Beta2
>
>
> The implementation for multiple jQuery Mobile palette versions is very clean. But I'm not sure users will intuitively know that they can click on the version number to see a list of available versions and change the version.
> Can a downwards arrowhead be added next to the version number to clarify this? Like in the OpenShift Application connection wizard where the connection field has a downwards arrowhead at the end of the value, or the new server wizard where the profile field has a downwards arrowhead at the end of the value. In both of these the downwards arrowhead immediately signifies to user to click here to see more options.
--
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, 2 months
[JBoss JIRA] (JBIDE-16975) jQuery Mobile palette: add drop-down list identifier to version
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16975?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-16975:
--------------------------------------
Assignee: Daniel Azarov
> jQuery Mobile palette: add drop-down list identifier to version
> ---------------------------------------------------------------
>
> Key: JBIDE-16975
> URL: https://issues.jboss.org/browse/JBIDE-16975
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Assignee: Daniel Azarov
> Fix For: 4.2.0.Beta2
>
>
> The implementation for multiple jQuery Mobile palette versions is very clean. But I'm not sure users will intuitively know that they can click on the version number to see a list of available versions and change the version.
> Can a downwards arrowhead be added next to the version number to clarify this? Like in the OpenShift Application connection wizard where the connection field has a downwards arrowhead at the end of the value, or the new server wizard where the profile field has a downwards arrowhead at the end of the value. In both of these the downwards arrowhead immediately signifies to user to click here to see more options.
--
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, 2 months
[JBoss JIRA] (TOOLSDOC-485) Add info on multiple jQuery Mobile versions in Palette view
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-485?page=com.atlassian.jira.plug... ]
Michelle Murray commented on TOOLSDOC-485:
------------------------------------------
[~sdorfiel], I've made the necessary text changes. Please complete the work for the new screen cap.
> Add info on multiple jQuery Mobile versions in Palette view
> -----------------------------------------------------------
>
> Key: TOOLSDOC-485
> URL: https://issues.jboss.org/browse/TOOLSDOC-485
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: User Guide - Mobile Web Tools
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta1
>
> Original Estimate: 45 minutes
> Time Spent: 45 minutes
> Remaining Estimate: 0 minutes
>
> Use Case: New version of jQuery Mobile is available and Mobile Web Tools has been extended to accommodate it.
> Feature: The palette view now supports jQuery Mobile 1.4. The palette detects the jQuery Mobile JS file version used in the HTML file and switches to the corresponding version: 1.3 or 14. It also can be switched manually. jQuery Mobile Palette v1.4 has its own set of wizards.
> Writer Task: Edit topic 22847. Include info on how to switch between jQuery Mobile versions in palette and that appropriate one is selected by default based on file in editor. Create a new screen cap for figure 'jQuery Mobile Palette in the Palette View' showing 1.4 version.
--
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, 2 months
[JBoss JIRA] (TOOLSDOC-485) Add info on multiple jQuery Mobile versions in Palette view
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-485?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-485:
-------------------------------------
Assignee: Suz Dorfield (was: Michelle Murray)
> Add info on multiple jQuery Mobile versions in Palette view
> -----------------------------------------------------------
>
> Key: TOOLSDOC-485
> URL: https://issues.jboss.org/browse/TOOLSDOC-485
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: User Guide - Mobile Web Tools
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Assignee: Suz Dorfield
> Fix For: 4.2.0.Beta1
>
> Original Estimate: 45 minutes
> Time Spent: 45 minutes
> Remaining Estimate: 0 minutes
>
> Use Case: New version of jQuery Mobile is available and Mobile Web Tools has been extended to accommodate it.
> Feature: The palette view now supports jQuery Mobile 1.4. The palette detects the jQuery Mobile JS file version used in the HTML file and switches to the corresponding version: 1.3 or 14. It also can be switched manually. jQuery Mobile Palette v1.4 has its own set of wizards.
> Writer Task: Edit topic 22847. Include info on how to switch between jQuery Mobile versions in palette and that appropriate one is selected by default based on file in editor. Create a new screen cap for figure 'jQuery Mobile Palette in the Palette View' showing 1.4 version.
--
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, 2 months
[JBoss JIRA] (JBIDE-16976) OpenShift import: Error dialog after importing application without SSH key on PaaS is not enough descriptive
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-16976:
-------------------------------------
Summary: OpenShift import: 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: Bug
Components: openshift
Affects Versions: 4.2.0.Beta1
Reporter: Marián Labuda
Priority: Minor
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 shell 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.
--
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, 2 months