January 2014 - jbosstools-issues - Jboss List Archives

[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

11 years, 11 months

1
0
0 / 0

[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

11 years, 11 months

1
0
0 / 0

[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: ------------------------------------- I couldn't find action that would activate Edit->Redo menu, do you know one? > 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

11 years, 11 months

1
0
0 / 0

[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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16409) Need to include the latest WTP 3.5.2RC2 into TP for Kepler

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16409?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16409: ------------------------------------ Agreed, if we're using Kepler SR2 bits it's time for the 4.32.x branch to be born. Latest WTP drop I can find on the server is this one: http://download.eclipse.org/webtools/downloads/drops/R3.5.2/M-3.5.2RC1-20... So we can wait until the 20140130 build is released and move up to that in the Kepler SR2 / 4.32.x branch target platform. > Need to include the latest WTP 3.5.2RC2 into TP for Kepler > ---------------------------------------------------------- > > Key: JBIDE-16409 > URL: https://issues.jboss.org/browse/JBIDE-16409 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.1.2.CR1 > Reporter: Victor Rubezhny > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.1.2.CR1 > > > Today, 30 January, 2014 WTP 3.5.2 received an important fix that is required in order to fix JBIDE-14597. > Please make the next release of WTP 3.5.2RC1 available as a part of TP for Kepler. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2887) Drop OS X 10.7 Lion from the support matrix

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2887?page=com.atlassian.jira.plugin.... ] Fred Bricon reassigned JBDS-2887: --------------------------------- Assignee: Len DiMaggio > Drop OS X 10.7 Lion from the support matrix > ------------------------------------------- > > Key: JBDS-2887 > URL: https://issues.jboss.org/browse/JBDS-2887 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements > Affects Versions: 7.1.0.GA > Reporter: Martin Malina > Assignee: Len DiMaggio > Fix For: 7.1.1.CR1, 8.0.0.Alpha2 > > > Since JBDS-2857 adds Mavericks to the support matrix, we can remove OS X 10.7 Lion and keep only the latest 2 versions of OS X. -- 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

11 years, 11 months

1
0
0 / 0

[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

11 years, 11 months

1
0
0 / 0

[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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16403) Welcome page "Show on startup" option is grey

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16403?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16403: -------------------------------- Fix Version/s: 4.1.2.CR1 > Welcome page "Show on startup" option is grey > --------------------------------------------- > > Key: JBIDE-16403 > URL: https://issues.jboss.org/browse/JBIDE-16403 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.1.Final > Environment: Kubuntu 64 bits > Reporter: Emmanuel Hugonnet > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.1.2.CR1, 4.2.0.Beta1 > > Attachments: jboss_central.png > > > The option "show on startup" is displayed with a grey background instead of the default one. Changing theme doesn't affect it. > See screenshot -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16264) @PathParam with hyphen in value shows as JAX-RS error

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16264?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-16264: ------------------------------------- +1 to apply PR on both branches > @PathParam with hyphen in value shows as JAX-RS error > ----------------------------------------------------- > > Key: JBIDE-16264 > URL: https://issues.jboss.org/browse/JBIDE-16264 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.CR1 > Reporter: Jim Boettcher > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.1.2.CR1, 4.2.0.Alpha2 > > > if I have a method like: > @GET > @Path("/rule/{rule-file-name}") > public byte[] getRuleSet(@PathParam("rule-file-name") String ruleSetName) > I get the error: > @PathParam value 'rule-file-name' does not match any @Path annotation template parameters of the java method and the enclosing java type. > If I remove the hyphens from "rule-file-name" the error goes away. > However the hyphen should be allowed. -- 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

11 years, 11 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 January 2014