April 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17215) DownloadRuntime cannot discover root of tar.gz or .tar files

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-17215: ----------------------------------- Summary: DownloadRuntime cannot discover root of tar.gz or .tar files Key: JBIDE-17215 URL: https://issues.jboss.org/browse/JBIDE-17215 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: runtime-detection Affects Versions: 4.2.0.Beta2 Reporter: Rob Stryker Now that downloadruntimes can download and unzip .tar.gz files, it also needs to be able to properly point to the new root folder of the unzipped location. So if a .tar.gz file is /home/rob/tmp/some.tar.gz, and it expands to /home/rob/tmp/my-app-version-2.3.0/ with all files under that, it should correctly identify that new folder as the root of the unzipped archive. -- 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-17032) Ability to configure jQuery / jQuery Mobile versions injected by Palette

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17032?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17032: --------------------------------------------- [~vineet.reynolds] i haven't looked in details on how bower stores it settings but even if we used bower that wouldn't work for projects that doesn't use it (like a maven driven build for a webapp). > Ability to configure jQuery / jQuery Mobile versions injected by Palette > ------------------------------------------------------------------------ > > Key: JBIDE-17032 > URL: https://issues.jboss.org/browse/JBIDE-17032 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.2.0.Beta2 > > Attachments: 2014-04-25 17.02.bmml, 2014-04-25 17.02.bmml, 2014-04-25 17.02.png, SeparateDialog.bmml, SeparateDialog.png > > > Currently the following versions are injected for JQM 1.4: > {code} > <script src="http://code.jquery.com/jquery-1.10.2.min.js"></script> > <script src="http://code.jquery.com/mobile/1.4.2/jquery.mobile-1.4.2.min.js"></script> > {code} > And for JQM 1.3: > {code} > <script src="http://code.jquery.com/jquery-1.9.1.min.js"></script> > <script src="http://code.jquery.com/mobile/1.3.2/jquery.mobile-1.3.2.min.js"></script> > {code} > It would be good if we have a place where users can configure what versions of JQ and JQM they want to inject. -- 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-17207) Run tests on all major OS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17207?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen edited comment on JBIDE-17207 at 4/29/14 9:07 AM: ---------------------------------------------------------------------- just putting this on 4.2 for discussion of options. we do have jenkins windows instances available - but can they run our builds ? if not, maybe get QE to run them manualy on their setup ? was (Author: maxandersen): just putting this on 4.2 for discussion of options. we do have jenkins instance available - but can they run our builds ? > Run tests on all major OS > ------------------------- > > Key: JBIDE-17207 > URL: https://issues.jboss.org/browse/JBIDE-17207 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Reporter: Alexey Kazakov > Fix For: 4.2.0.Beta2, 4.2.0.CR1 > > > Currently, our jenkins server runs JBT jUnit tests on Linux only. It would be good if we also run the tests on Windows and Mac. > For example, we recently ran base, jst and javaee tests on Windows and got more than a hundred failures. Some of them indicated real bugs (not just tests problems). See JBIDE-17200. > We don't have to run them every day. Maybe once a week or month? > cc: [~maxandersen], [~dgolovin], [~nickboldt], [~mickael_istria] -- 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-17207) Run tests on all major OS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17207?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17207: --------------------------------------------- just putting this on 4.2 for discussion of options. we do have jenkins instance available - but can they run our builds ? > Run tests on all major OS > ------------------------- > > Key: JBIDE-17207 > URL: https://issues.jboss.org/browse/JBIDE-17207 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Reporter: Alexey Kazakov > Fix For: 4.2.0.Beta2, 4.2.0.CR1 > > > Currently, our jenkins server runs JBT jUnit tests on Linux only. It would be good if we also run the tests on Windows and Mac. > For example, we recently ran base, jst and javaee tests on Windows and got more than a hundred failures. Some of them indicated real bugs (not just tests problems). See JBIDE-17200. > We don't have to run them every day. Maybe once a week or month? > cc: [~maxandersen], [~dgolovin], [~nickboldt], [~mickael_istria] -- 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-17207) Run tests on all major OS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17207?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-17207: ---------------------------------------- Fix Version/s: 4.2.0.Beta2 4.2.0.CR1 > Run tests on all major OS > ------------------------- > > Key: JBIDE-17207 > URL: https://issues.jboss.org/browse/JBIDE-17207 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Reporter: Alexey Kazakov > Fix For: 4.2.0.Beta2, 4.2.0.CR1 > > > Currently, our jenkins server runs JBT jUnit tests on Linux only. It would be good if we also run the tests on Windows and Mac. > For example, we recently ran base, jst and javaee tests on Windows and got more than a hundred failures. Some of them indicated real bugs (not just tests problems). See JBIDE-17200. > We don't have to run them every day. Maybe once a week or month? > cc: [~maxandersen], [~dgolovin], [~nickboldt], [~mickael_istria] -- 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-16756) Update Cordova version for XCode 5.1 compatibility

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16756?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16756: --------------------------------------------- nothing planned at the moment but if we do want to do one it is good if jira highlights what issues we would like fixed. If this issue is someting that is important to fix in case we do do a release then set it to next 4.1 so it will show up. if not important then reject it. > Update Cordova version for XCode 5.1 compatibility > -------------------------------------------------- > > Key: JBIDE-16756 > URL: https://issues.jboss.org/browse/JBIDE-16756 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: aerogear-hybrid > Affects Versions: 4.1.1.Beta1 > Reporter: Gorkem Ercan > Priority: Minor > Fix For: 4.1.x > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Cordova version prior to version 3.5 are not compatible with XCode 5.1.. Upgrade Cordova shipped with 4.1.x for XCode 5.1 compatibility. > see http://shazronatadobe.wordpress.com/2014/03/12/xcode-5-1-and-cordova-ios/ for details -- 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-16885) Embed wizard: Can provide "Code Anything" without url, should not be able to

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16885?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16885: ------------------------------------- Description: In the wizard to edit the embeddable cartridges there is "Code Anything" cartridge which requires URL of cartridge. If user just selects and does not check this cartridge, it is not possible to hit the OK button (see attached screen wrong_button_accessibility). Also if user check this cartridge but select another one without providing URL to the Code anything cartridge, it is possible to hit the OK button (it should not be - see attached screenshot wrong_button_accessibility2.) was: In shell with embeddable cartridges there is Code anything cartridge which requires URL of cartridge. If user just select and not check this cartridge, it is not possible to hit the OK button (see attached screen wrong_button_accessibility). Also if user check this cartridge but select another one without providing URL to the Code anything cartridge, it is possible to hit the OK button (it should not be - see attached screenshot wrong_button_accessibility2.) Steps to Reproduce: # ASSERT: have an application running on OpenShift # EXEC: OpenShift Explorer: select "Edit Embedded Cartridges" from the context menu # EXEC: check "Code Anything" # ASSERT: "Finish" is disabled, URL text field is decorated with a * to show that the user has to provide an url # EXEC: check another cartridge (ex. mysql-5.5) Result: *Finish* is enabled even though the *Code Anything* cartridge is missing the url Also: # ASSERT: have an application running on OpenShift # EXEC: OpenShift Explorer: select "Edit Embedded Cartridges" from the context menu # EXEC: check "Code Anything" # ASSERT: "Finish" is disabled, URL text field is decorated with a * to show that the user has to provide an url # EXEC: uncheck *Code Anything* Result: *Finish* should get enabled since we're not adding the *Code Anything* cartridge > Embed wizard: Can provide "Code Anything" without url, should not be able to > ---------------------------------------------------------------------------- > > Key: JBIDE-16885 > URL: https://issues.jboss.org/browse/JBIDE-16885 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: embed_wizard > Fix For: 4.2.0.Beta2 > > Attachments: wrong_button_accessibility.png, wrong_button_accessibility2.png > > > In the wizard to edit the embeddable cartridges there is "Code Anything" cartridge which requires URL of cartridge. If user just selects and does not check this cartridge, it is not possible to hit the OK button (see attached screen wrong_button_accessibility). > Also if user check this cartridge but select another one without providing URL to the Code anything cartridge, it is possible to hit the OK button (it should not be - see attached screenshot wrong_button_accessibility2.) -- 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-17002) Add Java 8 connector (JDT/WTP/M2E) in Central for JBT 4.1.2

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17002?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17002: --------------------------------------------- No, i'm not talking about bumping the numbers. I just want to have clarified what: " also fixes missing files that didn't get copied over between stable and development folders when 4.1.2.Final was released 2 weeks ago." means. and it seemed that if it was a trivial thing not something that needed to tied in to the change done for java8 connector update. > Add Java 8 connector (JDT/WTP/M2E) in Central for JBT 4.1.2 > ----------------------------------------------------------- > > Key: JBIDE-17002 > URL: https://issues.jboss.org/browse/JBIDE-17002 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.1.2.Final > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 4.1.2.Final > > Attachments: jbide17002-3-4-features.png, jbide17002-6-7-features.png, jbide17002-patch-catg.png > > > We decided to provide an easy way for JBT users to install Java 8 support in Eclipse Kepler SR2 in 1 click, instead of have to chase the update sites for JDT, M2e and WTP. > * JDT Feature patch : http://download.eclipse.org/eclipse/updates/4.3-P-builds/ > * M2E 1.4.1 (org.eclipse.m2e.feature) http://download.eclipse.org/technology/m2e/releases/1.4/1.4.1.20140328-1905 > * WTP Feature Patch : http://download.eclipse.org/webtools/patches/drops/R3.5.2/P-3.5.2-2014032... > All 3 features should be available via a unique connector in JBoss Central > Software Updates -- 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-15635) Null Pointer when code assumes runtime type cannot be null

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15635?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15635: ---------------------------------------- Fix Version/s: 4.2.0.Beta2 (was: 4.2.x) Priority: Critical (was: Major) reopen for clarificiation and raise priority. This issue was kept opened because being sure we dont fail on runtime less servers...like what will happen when jboss servers are no longer supported in eclcipse Luna. > Null Pointer when code assumes runtime type cannot be null > ---------------------------------------------------------- > > Key: JBIDE-15635 > URL: https://issues.jboss.org/browse/JBIDE-15635 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: Mac OSX 10.8.5 > Oracle JDK 1.7.0_40 > JBoss Developer Studio > Version: 7.0.1.GA > Build id: GA-v20130930-2238-B7 > Build date: 20130930-2238 > Reporter: Cojan van Ballegooijen > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.Beta2 > > Attachments: jbosstools-diagnostics-20131008232745.zip, Screen Shot 2013-10-08 at 2.22.05 PM.png > > > - Installed JBoss Developer 7.0.0GA using > - Upgraded to 7.0.1GA > - Starting JBoss Developer Studio shows the following error window > An internal error occurred during: "Refreshing JBoss Tutorials...". > java.lang.NullPointerException > - The error mentioned before also occurs when doing a refresh inside JBoss Central in the Start from a sample "portlet" > - Starting a new Java EE Web project results in the following error > An error has occurred. See error log for more details. > java.lang.NullPointerException > No error log is created in ~/workspace, tried to find *.log file in JBoss Developer Studio installation directory, no log files. > Found .log in ~/workspace/.metadata > !SESSION 2013-10-08 16:14:47.792 ----------------------------------------------- > eclipse.buildId=unknown > java.version=1.7.0_40 > java.vendor=Oracle Corporation > BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US > Framework arguments: -product com.jboss.jbds.product.product -keyring /Users/cballego/.eclipse_keyring -showlocation > Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product com.jboss.jbds.product.product -keyring /Users/cballego/.eclipse_keyring -consoleLog -showlocation > !ENTRY org.eclipse.core.net 1 0 2013-10-08 16:14:52.252 > !MESSAGE System property http.nonProxyHosts has been set to local|*.local|169.254/16|*.169.254/16 by an external source. This value will be overwritten using the values from the preferences > !ENTRY org.eclipse.jface 2 0 2013-10-08 16:14:52.626 > !MESSAGE Keybinding conflicts occurred. They may interfere with normal accelerator operation. > !SUBENTRY 1 org.eclipse.jface 2 0 2013-10-08 16:14:52.626 > !MESSAGE A conflict occurred for ALT+COMMAND+Z: > Binding(ALT+COMMAND+Z, > ParameterizedCommand(Command(org.jboss.tools.cdi.ui.open.namedBean,Open CDI Named Bean, > Open CDI Named Bean, > Category(org.eclipse.ui.category.navigate,Navigate,null,true), > org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@54158353, > ,,true),null), > org.eclipse.ui.defaultAcceleratorConfiguration, > org.eclipse.ui.contexts.window,,,system) > Binding(ALT+COMMAND+Z, > ParameterizedCommand(Command(org.eclipse.jdt.ui.edit.text.java.surround.with.quickMenu,Surround With Quick Menu, > Shows the Surround With quick menu, > Category(org.eclipse.jdt.ui.category.source,Source,Java Source Actions,true), > org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@5060e945, > ,,true),null), > org.eclipse.ui.defaultAcceleratorConfiguration, > org.eclipse.ui.contexts.window,,cocoa,system) > !SUBENTRY 1 org.eclipse.jface 2 0 2013-10-08 16:14:52.626 > !MESSAGE A conflict occurred for COMMAND+SHIFT+F10: > Binding(COMMAND+SHIFT+F10, > ParameterizedCommand(Command(org.jboss.tools.common.ui.RegisterAsService,Register As Service, > Adds class name to META-INF/services/%serviceType% file after service type is selected in the dialog from types extended and implemented by the class., > Category(org.eclipse.ui.category.file,File,null,true), > org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@a72da3d, > ,,true),null), > org.eclipse.ui.defaultAcceleratorConfiguration, > org.eclipse.ui.contexts.window,,,system) > Binding(COMMAND+SHIFT+F10, > ParameterizedCommand(Command(org.eclipse.ui.window.showSystemMenu,Show System Menu, > Show the system menu, > Category(org.eclipse.ui.category.window,Window,null,true), > org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@7a55e026, > ,,true),null), > org.eclipse.ui.defaultAcceleratorConfiguration, > org.eclipse.ui.contexts.window,,cocoa,system) > !ENTRY org.eclipse.core.jobs 4 2 2013-10-08 16:15:04.413 > !MESSAGE An internal error occurred during: "Refreshing JBoss Tutorials...". > !STACK 0 > java.lang.NullPointerException > at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:158) > at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:151) > at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.getRuntimesFromPattern(WTPRuntimeFix.java:102) > at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.getBestRuntime(WTPRuntimeFix.java:248) > at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.canFix(WTPRuntimeFix.java:130) > at org.jboss.tools.project.examples.ProjectExamplesActivator.canFix(ProjectExamplesActivator.java:796) > at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:68) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) -- 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] (TOOLSDOC-493) Add info for GTK3 issues and workaround

by Jiri Peterka (JIRA)

Jiri Peterka created TOOLSDOC-493: ------------------------------------- Summary: Add info for GTK3 issues and workaround Key: TOOLSDOC-493 URL: https://issues.jboss.org/browse/TOOLSDOC-493 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Components: Release Notes Affects Versions: 4.2.0.Beta1, 4.2.0.Final Reporter: Jiri Peterka Assignee: Michelle Murray Fix For: 4.2.0.Final There are many serious issues related to GTK3 systems (Ubuntu, Fedora and other GNU/Linux distros). For example https://issues.jboss.org/browse/JBIDE-16315 . It would be good to mention that for OS containing GTK3 this tweak is needed to avoid these issues: {code} export SWT_GTK3=0 {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

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 April 2014