[JBoss JIRA] (JBIDE-15932) CordovaSim needs to display console logs especially during startup
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15932?page=com.atlassian.jira.plugi... ]
Ilya Buziuk reassigned JBIDE-15932:
-----------------------------------
Assignee: Ilya Buziuk (was: Konstantin Marmalyukov)
> CordovaSim needs to display console logs especially during startup
> ------------------------------------------------------------------
>
> Key: JBIDE-15932
> URL: https://issues.jboss.org/browse/JBIDE-15932
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Affects Versions: 4.1.1.Beta1
> Reporter: Gorkem Ercan
> Assignee: Ilya Buziuk
> Priority: Blocker
> Labels: jbds711
> Fix For: 4.1.2.Final, 4.2.0.Alpha2
>
>
> When a cordova application is launched the console.log calls are not displayed on Eclipse console (or anywhere else). CordovaSim needs a place to display the logs either within eclipse or on the Ripple console so the user can be notified about errors happening early on.
> Just using firebug or similar would not solve this issue since it is not started early enough.
--
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, 5 months
[JBoss JIRA] (JBIDE-15932) CordovaSim needs to display console logs especially during startup
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15932?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-15932:
----------------------------------------
Summary: CordovaSim needs to display console logs especially during startup (was: CordovaSim needs to display console logs)
Description:
When a cordova application is launched the console.log calls are not displayed on Eclipse console (or anywhere else). CordovaSim needs a place to display the logs either within eclipse or on the Ripple console so the user can be notified about errors happening early on.
Just using firebug or similar would not solve this issue since it is not started early enough.
was:When a cordova application is launched the console.log calls are not displayed on Eclipse console (or anywhere else). CordovaSim needs a place to display the logs either within eclipse or on the Ripple console
> CordovaSim needs to display console logs especially during startup
> ------------------------------------------------------------------
>
> Key: JBIDE-15932
> URL: https://issues.jboss.org/browse/JBIDE-15932
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Affects Versions: 4.1.1.Beta1
> Reporter: Gorkem Ercan
> Assignee: Konstantin Marmalyukov
> Priority: Blocker
> Labels: jbds711
> Fix For: 4.1.2.Final, 4.2.0.Alpha2
>
>
> When a cordova application is launched the console.log calls are not displayed on Eclipse console (or anywhere else). CordovaSim needs a place to display the logs either within eclipse or on the Ripple console so the user can be notified about errors happening early on.
> Just using firebug or similar would not solve this issue since it is not started early enough.
--
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, 5 months
[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 commented on JBIDE-14768:
------------------------------------------
This issue depends on openshift-java-client to allow callbacks which Eclipse may use to present dialogs to the user.
> 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
> Priority: Critical
> 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, 5 months
[JBoss JIRA] (JBDS-2745) Support installation of Early Access / Experimental / Incubating plugins
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2745:
-------------------------------------------
We also need to:
* provide way to update from Central - currently only install, this should be pretty easy to do (just call the normal p2 updateui)
* provide a way to uninstall from Central - this is new AND requires we don't just provide the latest version (this should be tested to see how big a performance impact it has and how many old versions we will store/keep - my guess is All releases, but just latest experimental if that works with p2 uninstall mechanism)
* provide a UI to allow users to know if they are running support or non-supported parts.
> Support installation of Early Access / Experimental / Incubating plugins
> ------------------------------------------------------------------------
>
> Key: JBDS-2745
> URL: https://issues.jboss.org/browse/JBDS-2745
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: central, requirements
> Affects Versions: 7.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Burr Sutter
>
> It's been suggested that it would be nice to have Central available to install non-GA content. How might this appear?
> [~burrsutter], [~maxandersen], are we talking about:
> * an additional dialog warning users about untested content? (that might be ignored / blindclicked)
> * an additional tab in Central for this type of content (what label would you use?)
> * relabelling the content's feature descriptions / titles / copyright / license terms to be clear it's unstable content? (might be ignored)
> * some other workflow?
> See also JBDS-2068.
--
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, 5 months
[JBoss JIRA] (JBIDE-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick reassigned JBIDE-16066:
-----------------------------------------
Assignee: Brian Fitzpatrick
> Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-16066
> URL: https://issues.jboss.org/browse/JBIDE-16066
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.1.CR1
> Environment: JBDS 7.1.0 CR1, EAP-6.1
> Reporter: Radoslav Rábara
> Assignee: Brian Fitzpatrick
> Fix For: 4.2.0.Beta1
>
> Attachments: topDownServer.log
>
>
> Deployment isn't successful when Top-Down web service is created with slider level selected to "Start service" or "Test service". Project is deployed to the server but the service endpoint isn't added so the service is not accessible.
> It works with other slider levels and all levels works when the server isn't started before the web service is created.
--
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, 5 months
[JBoss JIRA] (JBDS-2862) During install, I should be able to create a new directory to install into
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2862?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2862:
-----------------------------
Git Pull Request: https://github.com/jbdevstudio/jbdevstudio-product/pull/123, https://github.com/jbdevstudio/jbdevstudio-product/pull/129 (was: https://github.com/jbdevstudio/jbdevstudio-product/pull/123)
> During install, I should be able to create a new directory to install into
> --------------------------------------------------------------------------
>
> Key: JBDS-2862
> URL: https://issues.jboss.org/browse/JBDS-2862
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.1.0.CR1
> Environment: Mac OS X
> Reporter: Jim Tyrrell
> Assignee: Denis Golovin
> Labels: jbds711
> Fix For: 7.1.1.GA, 8.0.0.Alpha2
>
> Attachments: 2013-12-19_1512.png, Screen shot 2013-12-10 at 12.34.20 PM.png, Screen Shot 2013-12-10 at 3.11.08 PM.png, Select Target Folder_015.png
>
>
> See the attached screen shot, a create new folder button does not seem to exist anywhere to create a new folder/directory to install JBDS.
--
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, 5 months
[JBoss JIRA] (JBDS-2862) During install, I should be able to create a new directory to install into
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2862?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2862 at 1/28/14 10:31 AM:
------------------------------------------------------------
Since code was applied in both jbosstools-4.1.x (for JBDS 7.1.1) and master (for JBDS 8.0.0.Alpha2), I've set the PM and QE ACKs to + and have resolved this issue.
QE can review and verify, then re-open or close.
was (Author: nickboldt):
Code applied in both jbosstools-4.1.x (for JBDS 7.1.1) and master (for JBDS 8.0.0.Alpha2) so resolving. QE can review and verify, then re-open or close.
> During install, I should be able to create a new directory to install into
> --------------------------------------------------------------------------
>
> Key: JBDS-2862
> URL: https://issues.jboss.org/browse/JBDS-2862
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.1.0.CR1
> Environment: Mac OS X
> Reporter: Jim Tyrrell
> Assignee: Denis Golovin
> Labels: jbds711
> Fix For: 7.1.1.GA, 8.0.0.Alpha2
>
> Attachments: 2013-12-19_1512.png, Screen shot 2013-12-10 at 12.34.20 PM.png, Screen Shot 2013-12-10 at 3.11.08 PM.png, Select Target Folder_015.png
>
>
> See the attached screen shot, a create new folder button does not seem to exist anywhere to create a new folder/directory to install JBDS.
--
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, 5 months
[JBoss JIRA] (JBDS-2862) During install, I should be able to create a new directory to install into
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2862?page=com.atlassian.jira.plugin.... ]
Nick Boldt resolved JBDS-2862.
------------------------------
Resolution: Done
Code applied in both jbosstools-4.1.x (for JBDS 7.1.1) and master (for JBDS 8.0.0.Alpha2) so resolving. QE can review and verify, then re-open or close.
> During install, I should be able to create a new directory to install into
> --------------------------------------------------------------------------
>
> Key: JBDS-2862
> URL: https://issues.jboss.org/browse/JBDS-2862
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.1.0.CR1
> Environment: Mac OS X
> Reporter: Jim Tyrrell
> Assignee: Denis Golovin
> Labels: jbds711
> Fix For: 7.1.1.GA, 8.0.0.Alpha2
>
> Attachments: 2013-12-19_1512.png, Screen shot 2013-12-10 at 12.34.20 PM.png, Screen Shot 2013-12-10 at 3.11.08 PM.png, Select Target Folder_015.png
>
>
> See the attached screen shot, a create new folder button does not seem to exist anywhere to create a new folder/directory to install JBDS.
--
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, 5 months