[JBoss JIRA] (JBIDE-16661) Eclipse Console Logging for CordovaSim
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16661?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16661:
---------------------------------------------
Why dont we just treat browsersim and cordovasim the same ?
If browsersim was just a browser it would not be killed when eclipse exits.
Also "just a browser" would have the console in it is own view - but we dont have that so
lets keep it simple and just have browsersim and cordova sim be launched in similar ways.
> Eclipse Console Logging for CordovaSim
> --------------------------------------
>
> Key: JBIDE-16661
> URL: https://issues.jboss.org/browse/JBIDE-16661
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: browsersim
> Reporter: Konstantin Marmalyukov
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.0.Beta1
>
> Attachments: Screenshot 2014-02-27 16.23.47.png
>
>
> If I understand everything correct from email thread [~maxandersen] wants to have something like in attached screenshot(standart console where error log and terminate button presents) for BrowserSim and CordovaSim launching.
> My point that it could be done for CordovaSim because it's a launch tool, but not for BrowserSim because it's "just a browser".
--
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, 1 month
[JBoss JIRA] (JBDS-2913) Console log when running EAP 6.2.x not formatted correctly
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2913?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2913:
-------------------------------------------
this should not happen if you are using JBoss EAP 6 server adapter. if it does that is a regression.
> Console log when running EAP 6.2.x not formatted correctly
> ----------------------------------------------------------
>
> Key: JBDS-2913
> URL: https://issues.jboss.org/browse/JBDS-2913
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: server
> Affects Versions: 7.1.0.GA
> Reporter: Mustafa Musaji
> Assignee: Max Rydahl Andersen
> Attachments: EAP-6.1.0.png, EAP-6.2.1.png
>
>
> When running EAP from JBDS the console logging shows strange characters from the logging. See screen shots comparing EAP 6.1.0 to EAP 6.2.1 (this also happens on EAP 6.2.0)
--
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, 1 month
[JBoss JIRA] (JBIDE-16661) Eclipse Console Logging for CordovaSim
by Konstantin Marmalyukov (JIRA)
Konstantin Marmalyukov created JBIDE-16661:
----------------------------------------------
Summary: Eclipse Console Logging for CordovaSim
Key: JBIDE-16661
URL: https://issues.jboss.org/browse/JBIDE-16661
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: browsersim
Reporter: Konstantin Marmalyukov
Assignee: Konstantin Marmalyukov
Fix For: 4.2.0.Beta1
If I understand everything correct from email thread [~maxandersen] wants to have something like in attached screenshot(standart console where error log and terminate button presents) for BrowserSim and CordovaSim launching.
My point that it could be done for CordovaSim because it's a launch tool, but not for BrowserSim because it's "just a browser".
--
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, 1 month
[JBoss JIRA] (JBIDE-16661) Eclipse Console Logging for CordovaSim
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16661?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-16661:
-------------------------------------------
Attachment: Screenshot 2014-02-27 16.23.47.png
> Eclipse Console Logging for CordovaSim
> --------------------------------------
>
> Key: JBIDE-16661
> URL: https://issues.jboss.org/browse/JBIDE-16661
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: browsersim
> Reporter: Konstantin Marmalyukov
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.0.Beta1
>
> Attachments: Screenshot 2014-02-27 16.23.47.png
>
>
> If I understand everything correct from email thread [~maxandersen] wants to have something like in attached screenshot(standart console where error log and terminate button presents) for BrowserSim and CordovaSim launching.
> My point that it could be done for CordovaSim because it's a launch tool, but not for BrowserSim because it's "just a browser".
--
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, 1 month
[JBoss JIRA] (JBDS-2839) Hybrid/Cordova Usability
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2839?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2839:
--------------------------------------
Epic Name: Hybrid Mobile Usability
> Hybrid/Cordova Usability
> ------------------------
>
> Key: JBDS-2839
> URL: https://issues.jboss.org/browse/JBDS-2839
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Security Level: Public(Everyone can see)
> Components: requirements
> Reporter: Burr Sutter
> Assignee: Gorkem Ercan
> Priority: Blocker
>
> Areas 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 project wizard 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, 1 month
[JBoss JIRA] (JBDS-2839) Hybrid/Cordova Usability
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2839?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2839:
--------------------------------------
Issue Type: Epic (was: Feature Request)
> Hybrid/Cordova Usability
> ------------------------
>
> Key: JBDS-2839
> URL: https://issues.jboss.org/browse/JBDS-2839
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Security Level: Public(Everyone can see)
> Components: requirements
> Reporter: Burr Sutter
> Assignee: Gorkem Ercan
> Priority: Blocker
>
> Areas 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 project wizard 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, 1 month
[JBoss JIRA] (JBIDE-16651) Remove hard-coded enterprise dependency resolution for upcoming archetypes embedding the RedHat Maven repo
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16651?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-16651:
-----------------------------------
Assignee: Fred Bricon (was: Denis Golovin)
> Remove hard-coded enterprise dependency resolution for upcoming archetypes embedding the RedHat Maven repo
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16651
> URL: https://issues.jboss.org/browse/JBIDE-16651
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: maven, project-examples
> Affects Versions: 4.1.1.Final
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.1.2.CR1
>
>
> In JBoss Central, when an Enterprise runtime is selected for any given Archetype, we check if the Red Hat Enterprise repository is available by trying to resolve a redhat version of org.jboss.spec:jboss-javaee-web-6.0. Then, if some essential dependencies are defined in stacks.yaml, we also try to resolve these. If the dependencies can't be resolved, a warning message appears with a link allowing users to add the RH repo to their Maven settings.xml
> Upcoming archetypes will have the Red Hat repository already added to the generated pom.xml, so adding it to settings.xml becomes unnecessary. However, we'd get false positive warning by trying to resolve org.jboss.spec:jboss-javaee-web-6.0 from the settings.xml *before* generating the archetype.
> Our goal is to remove the hardcoded check from MavenArtifactHelper and, when necessary, declare org.jboss.spec:jboss-javaee-web-6.0 as an essential dependency in stacks.yaml for *old* archetypes that do not add the RH repo to the gen'd pom.xml
--
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, 1 month
[JBoss JIRA] (JBIDE-15488) Web Service Tester doesn't work with https and self-signed certificate
by Juergen Zimmermann (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15488?page=com.atlassian.jira.plugi... ]
Juergen Zimmermann commented on JBIDE-15488:
--------------------------------------------
Brian, meanwhile I'm in a totally different project... I'll get back to you in about 2 weeks.
> Web Service Tester doesn't work with https and self-signed certificate
> ----------------------------------------------------------------------
>
> Key: JBIDE-15488
> URL: https://issues.jboss.org/browse/JBIDE-15488
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.0.Final
> Reporter: Juergen Zimmermann
> Assignee: Brian Fitzpatrick
> Fix For: 4.2.x
>
>
> If I test a RESTful Web Service on WildFly 8 which is configured for https, then I just this error message in the response body (for both GET and POST requests):
> {code}
> sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
> {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, 1 month