December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-16223) CLONE - Server Adapter: Pushing and Pulling frequently fails because of timeouts that are far too low.

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16223?page=com.atlassian.jira.plugi... ] Marián Labuda resolved JBIDE-16223. ----------------------------------- Resolution: Done > CLONE - Server Adapter: Pushing and Pulling frequently fails because of timeouts that are far too low. > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-16223 > URL: https://issues.jboss.org/browse/JBIDE-16223 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: new_and_noteworthy > Fix For: 4.2.0.Alpha1 > > > Pushing and pulling via the server adapter frequently fails with the server adapter since timeouts are far too low. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-16223) CLONE - Server Adapter: Pushing and Pulling frequently fails because of timeouts that are far too low.

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-16223: ------------------------------------- Summary: CLONE - Server Adapter: Pushing and Pulling frequently fails because of timeouts that are far too low. Key: JBIDE-16223 URL: https://issues.jboss.org/browse/JBIDE-16223 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.1.0.Final Reporter: Marián Labuda Assignee: Andre Dietisheim Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 Pushing and pulling via the server adapter frequently fails with the server adapter since timeouts are far too low. -- 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

1
0
0 / 0

[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: ----------------------------------- https://issues.jboss.org/browse/JBIDE-16090 is an example of where the end-user is negatively impacted when trying to use two tools simultaneously (Firebug Lite & 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-14850) Markers wizard: Restrict available markers depending on application type

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14850?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14850: ------------------------------------- Summary: Markers wizard: Restrict available markers depending on application type (was: Restrict available markers depending on application type) > Markers wizard: Restrict available markers depending on application type > ------------------------------------------------------------------------ > > Key: JBIDE-14850 > URL: https://issues.jboss.org/browse/JBIDE-14850 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.x > > > In JBIDE-14845 we allow users to add and remove markers. We dont filter the markers whether we have a java (jbossas, jbossews) or php, node, ruby etc. application even though some markers are specific to certain application types. We should tell the user what markers may make sense and suggest upon that. -- 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

1
0
0 / 0

[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: ------------------------------------- Summary: Connection dialog: Inform user about a non-valid OpenShift server url in a user-friendly way (was: Credentials dialog: Inform user about a non-valid OpenShift server url in a user-friendly way) > 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: 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-14890) Application wizard: Use EGit recursive merge instead of copying git repository

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14890?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14890: ------------------------------------- Labels: application_wizard (was: ) > Application wizard: Use EGit recursive merge instead of copying git repository > ------------------------------------------------------------------------------ > > Key: JBIDE-14890 > URL: https://issues.jboss.org/browse/JBIDE-14890 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard > Fix For: 4.2.x > > Attachments: user-existing-project.png > > > OpenShift tooling is working around missing recursive merge when importing into an existing Project ("use existing") > !user-existing-project.png! > When using the git command line one is told to merge by using the recursive merge startegy: > {code} > git merge -s recursive -X ours foo > {code} > When we created the JBoss Tools for OpenShift there was no recursive merge in EGit/JGit. We therefore worked around it by cloning the OpenShift repository and copying stuff over. > EGit 3.0 introduced the recursive merge strategy and put it to the default that's being used: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=380314#c22 -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-14768) Connection dialog: Inform users about invalid SSL certificates and allow them to accept/refuse them

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14768?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14768: ------------------------------------- Labels: connection_wizard (was: ) > Connection dialog: Inform users about invalid SSL certificates and allow them to accept/refuse them > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-14768 > URL: https://issues.jboss.org/browse/JBIDE-14768 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: connection_wizard > Fix For: 4.2.x > > > In JBIDE-10447 the openshift-java-client disabled the checks for SSL certificates since those prevented users from connecting to internal/private OpenShift instances: > {code:title=UrlConnectionHttpClient} > private HttpURLConnection createConnection(String userAgent, URL url) throws IOException { > HttpURLConnection connection = (HttpURLConnection) url.openConnection(); > if (isHttps(url) > && !doSSLChecks) { > HttpsURLConnection httpsConnection = (HttpsURLConnection) connection; > httpsConnection.setHostnameVerifier(new NoopHostnameVerifier()); > setPermissiveSSLSocketFactory(httpsConnection); > } > private boolean isHttps(URL url) { > return "https".equals(url.getProtocol()); > } > /** > * Sets a trust manager that will always trust. > * <p> > * TODO: dont swallog exceptions and setup things so that they dont disturb other components. > */ > private void setPermissiveSSLSocketFactory(HttpsURLConnection connection) { > try { > SSLContext sslContext = SSLContext.getInstance("SSL"); > sslContext.init(new KeyManager[0], new TrustManager[] { new PermissiveTrustManager() }, new SecureRandom()); > SSLSocketFactory socketFactory = sslContext.getSocketFactory(); > ((HttpsURLConnection) connection).setSSLSocketFactory(socketFactory); > } catch (KeyManagementException e) { > // ignore > } catch (NoSuchAlgorithmException e) { > // ignore > } > } > private static class PermissiveTrustManager implements X509TrustManager { > public X509Certificate[] getAcceptedIssuers() { > return null; > } > public void checkServerTrusted(X509Certificate[] chain, > String authType) throws CertificateException { > } > public void checkClientTrusted(X509Certificate[] chain, > String authType) throws CertificateException { > } > } > private static class NoopHostnameVerifier implements HostnameVerifier { > public boolean verify(String hostname, SSLSession sslSession) { > return true; > } > } > {code} > We should not simply disable these SSL checks but allow users to accept/refuse them via a 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14825) Application wizard: have to manually create git folder if I dont want to use the default

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14825?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14825: ------------------------------------- Summary: Application wizard: have to manually create git folder if I dont want to use the default (was: application creation/import wizard: have to manually create git folder if I dont want to use the default) > Application wizard: have to manually create git folder if I dont want to use the default > ---------------------------------------------------------------------------------------- > > Key: JBIDE-14825 > URL: https://issues.jboss.org/browse/JBIDE-14825 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.x > > Attachments: non-std-git-clone-location.png > > > steps to reproduce: > # ASSERT: make sure you have an account on OpenShift > # EXEC: launch app creation wizard > # EXEC: in 3nd page uncheck *use default clone destination* and type in some folder that does not exist yet > Result: > You have to create your folder on your own, the wizard wont help you, it'll just error > !non-std-git-clone-location.png! -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-14825) Application wizard: have to manually create git folder if I dont want to use the default

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14825?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14825: ------------------------------------- Labels: application_wizard (was: ) > Application wizard: have to manually create git folder if I dont want to use the default > ---------------------------------------------------------------------------------------- > > Key: JBIDE-14825 > URL: https://issues.jboss.org/browse/JBIDE-14825 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: application_wizard > Fix For: 4.2.x > > Attachments: non-std-git-clone-location.png > > > steps to reproduce: > # ASSERT: make sure you have an account on OpenShift > # EXEC: launch app creation wizard > # EXEC: in 3nd page uncheck *use default clone destination* and type in some folder that does not exist yet > Result: > You have to create your folder on your own, the wizard wont help you, it'll just error > !non-std-git-clone-location.png! -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-14825) Application wizard: have to manually create git folder if I dont want to use the default

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14825?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14825: ------------------------------------- Priority: Major (was: Minor) > Application wizard: have to manually create git folder if I dont want to use the default > ---------------------------------------------------------------------------------------- > > Key: JBIDE-14825 > URL: https://issues.jboss.org/browse/JBIDE-14825 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard > Fix For: 4.2.x > > Attachments: non-std-git-clone-location.png > > > steps to reproduce: > # ASSERT: make sure you have an account on OpenShift > # EXEC: launch app creation wizard > # EXEC: in 3nd page uncheck *use default clone destination* and type in some folder that does not exist yet > Result: > You have to create your folder on your own, the wizard wont help you, it'll just error > !non-std-git-clone-location.png! -- 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

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 December 2013