[JBoss JIRA] (JBIDE-15932) CordovaSim needs to display console logs especially during startup
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15932?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-15932:
---------------------------------------
Ilya, use 4.1.x branch for 4.1.2 fixes.
> 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.CR1, 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, 4 months
[JBoss JIRA] (JBIDE-15913) [Android] Export dialogs should check the Android SDK
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15913?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-15913:
--------------------------------------
fixed to master
> [Android] Export dialogs should check the Android SDK
> -----------------------------------------------------
>
> Key: JBIDE-15913
> URL: https://issues.jboss.org/browse/JBIDE-15913
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Reporter: Gorkem Ercan
> Assignee: Gorkem Ercan
> Priority: Minor
> Fix For: 4.2.x
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> If a project is exported for Android without setting the Android SDK preferences. An error occurs. Export wizards should check the availability of the preferences.
> Steps:
> 1. Create a project
> 2. Export Native Platform Project
> 3. Select Android and Click finish.
--
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-15913) [Android] Export dialogs should check the Android SDK
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15913?page=com.atlassian.jira.plugi... ]
Gorkem Ercan resolved JBIDE-15913.
----------------------------------
Resolution: Done
> [Android] Export dialogs should check the Android SDK
> -----------------------------------------------------
>
> Key: JBIDE-15913
> URL: https://issues.jboss.org/browse/JBIDE-15913
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Reporter: Gorkem Ercan
> Assignee: Gorkem Ercan
> Priority: Minor
> Fix For: 4.2.x
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> If a project is exported for Android without setting the Android SDK preferences. An error occurs. Export wizards should check the availability of the preferences.
> Steps:
> 1. Create a project
> 2. Export Native Platform Project
> 3. Select Android and Click finish.
--
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-2769) Shortcut for Redo action is missing
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2769?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-2769:
-------------------------------------
Well, it is not missing. Verified through Window->Preferences General->Keys. It is in all versions you mentioned.
> Shortcut for Redo action is missing
> -----------------------------------
>
> Key: JBDS-2769
> URL: https://issues.jboss.org/browse/JBDS-2769
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: upstream
> Affects Versions: 7.0.0.GA, 7.1.0.Alpha1
> Reporter: Andrej Podhradsky
>
> By default, there is no shortcut for Redo action like in Eclipse (ShiftCtrl+Z).
> I think it would be cool if there is a shortcut for redo by default ;-)
--
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-16328) Buglets in JaxrsResourceMethodValidatorDelegate.validatePublicModifierOnJavaMethod()
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16328?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-16328:
--------------------------------
Fix Version/s: 4.1.2.CR1
> Buglets in JaxrsResourceMethodValidatorDelegate.validatePublicModifierOnJavaMethod()
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-16328
> URL: https://issues.jboss.org/browse/JBIDE-16328
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.1.Final
> Environment: Eclipse 4.3.1 EE bundle + JBoss Tools 4.1.1
> Reporter: Thomas Maslen
> Assignee: Fred Bricon
> Priority: Minor
> Fix For: 4.1.2.CR1, 4.2.0.Alpha2
>
>
> JAX-RS resource methods are often declared in classes, but it is also valid to declare them in interfaces. Methods in classes have to be explicitly declared public (and that's what this validator method checks for -- good), but methods in Java interfaces are implicitly public; explicitly writing "public" just adds clutter.
> The JAX-RS validator does discover resource methods in interfaces and validates them (good), but if the methods aren't explicitly labelled public then a couple of minor bugs surface in this validator method:
> (1) It adds a RESOURCE_METHOD_NO_PUBLIC_MODIFIER problem marker, and
> (2) The Description that's displayed for the marker is "The method '{0}' should be public.", i.e. the "{0}" isn't replaced with a method name
> (Yes, I can certainly dodge this by changing the "Missing 'public' method modifier" preference from Warning to Ignore, but I'm definitely a fan of having the validators there to save me from myself).
--
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-16328) Buglets in JaxrsResourceMethodValidatorDelegate.validatePublicModifierOnJavaMethod()
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16328?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-16328:
-------------------------------------
+1 to apply PR on both branches
> Buglets in JaxrsResourceMethodValidatorDelegate.validatePublicModifierOnJavaMethod()
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-16328
> URL: https://issues.jboss.org/browse/JBIDE-16328
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.1.Final
> Environment: Eclipse 4.3.1 EE bundle + JBoss Tools 4.1.1
> Reporter: Thomas Maslen
> Assignee: Fred Bricon
> Priority: Minor
> Fix For: 4.1.2.CR1, 4.2.0.Alpha2
>
>
> JAX-RS resource methods are often declared in classes, but it is also valid to declare them in interfaces. Methods in classes have to be explicitly declared public (and that's what this validator method checks for -- good), but methods in Java interfaces are implicitly public; explicitly writing "public" just adds clutter.
> The JAX-RS validator does discover resource methods in interfaces and validates them (good), but if the methods aren't explicitly labelled public then a couple of minor bugs surface in this validator method:
> (1) It adds a RESOURCE_METHOD_NO_PUBLIC_MODIFIER problem marker, and
> (2) The Description that's displayed for the marker is "The method '{0}' should be public.", i.e. the "{0}" isn't replaced with a method name
> (Yes, I can certainly dodge this by changing the "Missing 'public' method modifier" preference from Warning to Ignore, but I'm definitely a fan of having the validators there to save me from myself).
--
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